Case Study · Web Application
Pilketos
A web application exploring how election administration, polling-station operations, and result reporting can be organized for a student-council election.
- 01 Election setup
- 02 TPS operations
- 03 Results review
The problem
Student elections involve more than displaying candidates. Administrators also need to manage voters, polling-station assignments, operational staff, the election flow, and results. These concerns benefit from a consistent system rather than disconnected spreadsheets.
Application structure
The source repository contains separate routes and views for election setup, candidates, voters, staff, polling stations (TPS), voting, dashboard, and results. Authentication is implemented using Supabase with an application-level user role profile.
Manage the organizational structure of the election.
Separate polling-station and staff interfaces.
Dedicated voter and participant management views.
Dedicated results view and monitoring dashboard.
What the source demonstrates
Inspectable implementation
Distinct React routes cover election setup, candidate records, voters, TPS and staff interfaces, and result pages. The Supabase client and authentication context are present in the repository.
Not yet verified
A fully operating public vote, security against duplicate voting, election-scale load handling, and end-to-end production readiness have not been demonstrated here.
Deployment and responsible demonstration
This project's source is hosted on GitHub and includes GitHub Pages deployment automation. Its Supabase project was inactive when this case study was prepared, so a functional live voting demo is not claimed. A future public demo should run on synthetic voters and a separate database from any real election.
Technology
Future improvements will be documented with reproducible evidence instead of claims about security, throughput, or reliability that have not been tested.