1. Institution onboarding
Create or join an institution space. Admins configure branding, users, and package limits. Students are imported and verified against the official roll.
How Electra runs an election
A clear lifecycle from setup to published results — so administrators, managers, candidates, and students always know what phase they are in.
2. Election configuration
Define title, year, positions, and phase windows: registration, campaign, voting, and results. Retention policy is set for post-election data lifecycle.
3. Candidates & campaigns
Candidates are approved for positions. Optional running-mate pairing. Campaign materials (manifestos, posters, documents) are submitted and can be moderated.
4. Voting code issuance
Voting managers issue single-use codes to verified students — individually or in bulk — with configurable expiry. Codes are hashed at rest.
5. Secure voting
Students enter institution ID, student code, and voting code. They cast one ballot per position. Codes are consumed; duplicate votes are blocked by unique constraints.
6. Results & closure
After voting closes, institutions publish official result snapshots. Turnout history and exports support transparency. Retention and cleanup follow policy.