E-Voting System

System design

 Candidate ──► register ──► upload documents ──► admin verification
                                                      │
 Admin ──► elections · users · feedback · notify ─────┤
                                                      ▼
 Voter ──► log in ──► ballot ──► cast vote     ┌─────────────┐
            (blocked if has_voted = 1)  ──────►│   MySQL     │
                                               │ elections   │
 Live results ◄── polling endpoint ◄───────────│ candidates  │
 Voting history ◄──────────────────────────────│ voters/votes│
                                               │ history     │
 Email (PHPMailer/SMTP) ◄── election notices   │ notifications│
                                               └─────────────┘

Key features

• Candidate vetting — document uploads reviewed and marked verified by an admin
• One vote per voter — the ballot is locked once a voter's has_voted flag is set
• Live results page fed by a polling data endpoint
• Election notifications by email and in-app, plus a feedback channel
• Password reset flow over SMTP

What I'd do differently today

Enforce one-vote-per-voter with a database unique constraint and a transaction, not only an application flag — so integrity holds even under concurrent requests.