More project photos (3)
The problem
Campus elections are decided by posters, corridor whispers and forwarded messages — while the actual manifestos, where they exist at all, sit in a PDF nobody reads. Voters choose names they recognise rather than promises they compared, and candidates face no structured accountability for what they pledged. This project is a manifesto portal that brings the election onto one page. Each candidate gets a verified profile with a structured manifesto: a candidate statement, key promises each with a named owner and a deadline, and a past record section. A compare view renders two candidates' promises side by side so differences are visible, not rhetorical. Clearly-labelled unofficial straw polls measure sentiment without ever claiming to be the election, and a voter Q&A board lets students upvote questions that candidates answer in the open debate. An election timeline — nominations, manifesto deadline, debate, polling day — anchors the whole cycle. The portal is deliberately information-only: it never conducts the official vote.
Browses candidate cards, compares manifestos side by side and votes in straw polls.
Follow the working sequence
How it works
- The admin creates the election cycle with posts, dates and the manifesto-freeze deadline.
- Verified candidates fill the structured manifesto form — statement, promises with owners and deadlines, past record.
- Voters browse candidate cards by post, open full manifestos and compare any two candidates side by side.
- Students vote in straw polls (labelled unofficial) and upvote debate questions on the Q&A board.
- At the freeze deadline, manifestos lock; the admin exports the frozen set for the record.
- After the debate, top questions and poll trends are archived as the election's public record.
Tech stack:
- PHP · Laravel (REST API + Blade views)
- MySQL (relational schema with seed data)
- HTML · CSS · JavaScript (responsive frontend)
- One-vote-per-student poll logic
- Session authentication
- Role-based access (voter, candidate, admin)
- Manifesto version-freeze export
- Git
| Parameter | Value |
|---|---|
| User roles | 3 (voter, candidate, admin) |
| Manifesto structure | Statement + N promises (owner, deadline) + past record |
| Compare view | 2 candidates, promise-by-promise columns |
| Straw polls | Unofficial, one vote per verified student |
| Q&A | Submit, upvote, candidate answers at debate |
| Manifesto freeze | Timestamped lock with export |
| Official voting | Explicitly out of scope (information portal only) |
| Deployment | Shared hosting, VPS or college intranet |
Project features
- [Structured manifestos] Every candidate publishes promises in a fixed format — promise, owner, deadline — plus a statement and past record, ending the poster-only campaign.
- [Side-by-side compare] Pick two candidates for a post and their promises render in parallel columns; missing promises are visible as gaps, not hidden.
- [Unofficial straw polls] Clearly labelled "unofficial, for discussion only" polls on candidates and campus issues, with one-vote-per-student enforcement.
- [Voter Q&A board] Students submit questions, upvote the best, and candidates answer the top-voted ones at the open debate.
- [Election timeline] Nominations, manifesto freeze, debate and polling day as a public countdown with days-to-vote.
- [Promise tracker hooks] Each promise carries a deadline and owner field so a future tracker can follow delivery after the election.
- [Admin moderation] Candidate verification, manifesto freeze enforcement and Q&A moderation from one admin view.
What is included
- Complete working web application (manifestos, compare, polls, Q&A, timeline)
- Database schema with seed data (posts, candidates, manifestos, polls, questions)
- Admin panel for election setup, verification and freeze
- Frozen-manifesto export for the election record
- Project report PDF (SRS, ER diagram, DFD, test cases, screenshots)
- PPT presentation for final review
- Viva Q&A preparation document (poll integrity, freeze logic, moderation design)
Limitations & prerequisites
- This is an information portal, not an e-voting system — it does not conduct or certify the official election, and straw polls are explicitly unofficial.
- Candidate verification is manual admin approval; integration with the college electoral roll is future scope.
- One-vote-per-student relies on verified accounts; the demo does not implement biometric or OTP de-duplication.
- Poll percentages and manifesto content in the demo are illustrative seed data.
- Post-election promise tracking is a data structure plus future-scope plan, not a built tracker.
Frequently Asked Questions
Does this portal conduct the actual election voting?
No, deliberately not. It is an information and discussion portal — manifestos, comparison, unofficial polls and Q&A. The official election stays with the Election Committee's secret ballot, and every poll on the site is labelled unofficial.
How do you stop ballot-stuffing in straw polls?
Each verified student account gets exactly one vote per poll, enforced server-side; changing a vote is allowed, casting two is not.
What is the manifesto freeze?
Candidates can edit their manifesto until the published deadline; then it locks with a timestamp and the admin exports the frozen set, so promises can't be quietly rewritten mid-campaign.
Who verifies candidates?
The admin, against the official nominations list from the Election Committee. Only verified candidates get profiles and appear in polls.
Can it handle multiple posts?
Yes — posts (General Secretary, Sports Secretary and so on) are a data-driven list, and compare views operate within a post.
Is this project suitable for a final-year project?
Yes — for Computer Science, IT and Web Development programs. It demonstrates content moderation, voting-integrity logic, version freezing and comparison UIs with real civic relevance. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.
Components & software requirements
- PHP · Laravel (REST API + Blade views)
- MySQL (relational schema with seed data)
- HTML · CSS · JavaScript (responsive frontend)
- One-vote-per-student poll logic
- Session authentication
- Role-based access (voter, candidate, admin)
- Manifesto version-freeze export
- Git
Delivery information
Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.
Support terms
Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.
Download free synopsis (PDF)
Enter your name and WhatsApp number — the synopsis PDF downloads immediately. We may send occasional project updates on WhatsApp; no spam.