A voting system built for an actual election.

The challenge

The requirements developed rapidly as organizers prepared for voting across constituencies and wards. The platform had to support administrators managing the election, officers registering or verifying voters, and voters submitting private ballots—all with clear restrictions on who could access what.

The hard part was not just building forms. It was keeping voter-registration records, ballot authorizations, election state, and candidate results consistent while responding to feedback from people actively preparing to operate the system.

What I delivered

• Implemented core workflows in PHP with MySQL/MariaDB persistence and a responsive browser interface.
• Handled optional voter identifiers, secure registration references, gender fields, and officer-facing voter lookups as requirements evolved.
• Developed safeguards around repeat submissions, pending ballots, participation status, and restricted access to election results.
• Prepared deployment updates for shared cPanel hosting and worked through iterative testing and corrections.

Beyond writing the code

On 26 October 2026, I ran remote training over Google Meet to demonstrate the registration, verification and polling workflows to officers. On 27 October, during the actual election, I provided remote troubleshooting and helped organizers navigate the system and constituency result workflows.

The work did not end at deployment. Officers needed a clear process, and issues reported during voting had to be understood and addressed without disturbing votes already cast.

Engineering decisions

• Separation of identity and choice: voter registration and participation records are kept separate from anonymous ballot records.
• Role-scoped operations: administrative and polling-officer workflows limit access to sensitive functions and constituency records.
• Defensive voting flow: transaction-based vote submission, single-use authorization records, and controls for incomplete voting sessions.
• Operational transparency: results access and CSV exports are subject to restrictions; provisional constituency announcement workflows require checks.

This is a project delivery case study, not a claim that the platform was independently security-audited or certified for public elections. No personal voter records, ballots, credentials, or actual results are shown here.

The outcome

The platform was deployed and used to support Development Three Sixty's youth election. I delivered a working system under a compressed schedule, trained the staff using it, and supported live operations remotely. The experience strengthened my skills in requirements discovery, full-stack implementation, deployment, user training, and production support.

It was a useful test of the full job: understanding requirements, building the system, getting it onto hosting, explaining it to users and supporting it under real operating conditions.