Paper timetable, digitised
The exam calendar and room allotment moved off a printed circular and into a shared sheet — the seed of the Scheduling module.
About
Exam ERP System started as a simple question: why does a student need to check three different places — a printed sheet outside the exam cell, a PDF on the college site and a forwarded WhatsApp message — just to know their own seat number? This project puts every stage of the exam cycle behind one login, for the exam cell and the student alike.
How it developed
Each release matched an actual exam cycle at our pilot college, so every module was tested against a real notice board before it replaced one.
The exam calendar and room allotment moved off a printed circular and into a shared sheet — the seed of the Scheduling module.
Students could log in and download a hall ticket instead of collecting a stamped photocopy from the exam cell counter.
Room-wise attendance and incident logs replaced the paper attendance sheet passed around during the exam.
Result publishing and a trackable revaluation request closed the loop from admit card to grade sheet.
What we optimise for
A seat number, a venue and a result should say the same thing everywhere a student looks for them.
If a first-year exam clerk can't use a screen without a manual, the screen is wrong, not the clerk.
A mark, a seat or a schedule can always be traced back to who changed it and when.
The team
Each contributor owns one part of the system end to end — page, styling and behaviour — mirroring how a real exam cell splits work across staff.
Owns the first impression — the hero, module preview and workflow overview.
Tells the story of the project, its timeline and the team behind it.
Documents every module in the system, from scheduling to grievance handling.
Maps modules to the problems they solve for students, faculty and admins.
Builds the contact form and the login, sign-up and password-recovery flow.
Merges every branch, tests the full site, and ships it to production.