An exam season that does not depend on a spreadsheet at two in the morning.
Calendars, eligibility, seating, hall tickets, invigilation, incidents, masked evaluation, tabulation and results on one exam record. Every candidate, script and mark carries the rule, the evaluator and the approval behind it.
The problem
The exam season runs on institutional memory and three people who cannot take leave.
Every term the exam cell rebuilds the same machine: a seating plan in a spreadsheet, an eligibility list circulated by email, hall tickets mail-merged the night before, invigilator duty on a printed sheet, and a mark sheet keyed twice because the evaluator wrote on paper. It works because a few people know where everything is, which is exactly the risk.
Three things go wrong every season. Logistics are assembled by hand, so a hall clash or an ineligible candidate is discovered at the door. Evaluation happens off-system, so blindness, double valuation and variance checks depend on discipline rather than design. And results are published without a trail, so a challenged mark six months later cannot be explained.
The operating model
One exam record, and the rules travel with it.
Four design choices turn examinations from a term-end scramble into an operating layer: the exam is a governed object, eligibility is settled before a hall ticket exists, evaluation is blind by construction, and nothing publishes until the gate is complete.
The exam is an object, not a spreadsheet
Sessions, papers, halls, candidates, invigilators and scripts are linked records with their own status. Change a session time and the hall tickets, duty roster and attendance sheets change with it, because they are views of the same object.
Eligibility is settled before a hall ticket exists
Attendance, internal marks, fee clearance, registration and disciplinary status are evaluated as rules. A candidate who does not qualify becomes an exception with a named approver, not an argument at the hall door.
Evaluation is blind by construction
Masked identifiers replace candidate identity at script allocation, teaching faculty can be excluded from their own sections, and double valuation with a variance rule is configuration rather than goodwill. Every unmasking is an audited event.
Nothing publishes without the gate
Tabulation, moderation and approval must be complete before a result reaches a student. Revaluation creates a new version and preserves the original, so a mark can always be explained later.
What it does
Five things an exam cell needs. One record.
Planning and eligibility, seating and hall tickets, conduct and integrity, evaluation, and results with revaluation. Pick one to see what sits inside it.
Click any block to explore
The season laid out, and who may sit settled early.
- Examination calendar and session scheduling across campuses
- Regular, supplementary, repeat, special and makeup exam types
- Exam registration and candidate application windows
- Eligibility rules on attendance, internal marks and registration status
- Fee clearance and financial hold checks before admission
- Disciplinary and debarment status enforced as a rule
- Exception queue with a named approver and a stored reason
Allocated by rule, printed from one source of truth.
- Hall and room registry with capacity, layout and building
- Automatic seating allocation with spacing and mixing rules
- Multi-hall, multi-building and multi-campus allocation
- Hall tickets with photo, seat, venue, session and instructions
- Seating charts, door lists and attendance sheets from the same allocation
- Invigilator duty roster with availability and no double booking
- Script bundle and packet tracking between hall, store and evaluation
What happened in the hall becomes a record, not a memory.
- Attendance capture per candidate, per session
- Absentee and no-show reporting in real time
- Invigilator session log with handover and remarks
- Incident and malpractice records with category, evidence and statements
- Routing to the examination committee with decision, penalty and appeal history
- Answer script accountability from issue to collection
- Special arrangements and accommodations recorded against the candidate
Blind by construction, and marked once.
- Masked identifiers issued at script allocation
- Evaluator allocation with exclusion of the teaching faculty
- Double and triple valuation with a third-evaluator variance rule
- Onscreen evaluation with annotation and question-wise mark entry
- Marking schemes and rubrics presented alongside the script
- Evaluator progress, throughput and pending load tracking
- Question-wise marks flow straight to tabulation and outcome attainment
Tabulated, gated, published, and revisable with history.
- Tabulation with internal and external mark consolidation
- Grading scheme application, borderline and grace-mark rules
- Moderation sampling and statistics before and after adjustment
- Multi-level approval, then publication to student records
- Revaluation, recounting and challenge requests with fee and window control
- Fresh evaluator with original marks hidden, revision rule applied
- Result versions preserved, with pass rate, distribution and topper statistics
Inside the product
The whole exam season, in one place.
This is the application, not a diagram. Move through the surfaces your exam cell works in: the exam plan, eligibility, seating and hall tickets, conduct and incidents, evaluation, and results with revaluation.
| Hall | Capacity | Rule applied | Status |
|---|---|---|---|
| MAIN-01 | 120 of 140 | No two candidates from one course adjacentspacing 1 seat | Charted |
| SCI-204 | 48 of 60 | Programme mixing across rowshall registry | Charted |
| CITY-3B | 40 of 40 | City campus cohort, travel avoidedcampus rule | Charted |
| ACC-01 | 6 of 10 | Extra time and scribe arrangementsaccommodations | Confirmed |
Lifecycle or product
The lifecycle is the operating model. This is the product that runs it.
Two pages, two jobs. Read the lifecycle to understand how evaluation connects to curriculum, records and accreditation; read this page to see the application your exam cell opens on the first morning of the season.
One of the institutional lifecycles: the governed model for assessment patterns, exams, grading, moderation and attainment.
The application that runs the exam season: calendars, eligibility, seating, conduct, evaluation and results.
How does evaluation connect to curriculum, records, quality and accreditation?
What do exam cell officers, invigilators and evaluators actually see and do in each screen?
The full evaluation model, including exam administration, grade entry, moderation and publication.
Calendar to result: eligibility, seating, hall tickets, conduct, masked evaluation, tabulation and revaluation.
You are designing the operating model or comparing architectures.
See the lifecycle →
You are replacing exam spreadsheets or a standalone exam tool.
See inside the product →
Displacement
A standalone exam tool schedules the exam. It cannot tell you who is eligible.
Exam tools that sit beside the systems of record start from an upload. A candidate list is exported, seated and marked in a second place, then results are keyed back. The tool cannot see attendance, internal marks or a financial hold, so eligibility is checked by hand, and a mark challenged six months later has no chain to follow.
Checked by hand against three lists.
A rule on live attendance, marks and clearance.
Keyed back from a mark sheet.
Entered question-wise, straight into tabulation and attainment.
Reconstructed from paper, if at all.
Opened on the record: evaluators, versions, approvals.
Good at logistics. Disconnected from attendance, fees, records and outcome attainment.
Also part of the operating system
Examination Management is also part of Assessment & Outcomes.
Connect it and eligibility, evaluation, results and attainment run on the same records, so a published mark reaches the transcript and the evidence pack without being re-entered.
Built for every role
One exam record. Five views of the same season.
Runs the season from one plan, and spends the week on exceptions, not rebuilds.
Attendance, script counts and incidents captured in the hall, on the session.
Marks a masked script question-wise against the scheme, with no mark sheet to copy out.
Approves results only when tabulation and moderation are complete.
Hall ticket, seat, result and revaluation status in one place, with the dates.
What academic teams say about running examinations on Creatrix.
Creatrix Campus has helped us centralise all student information in one reliable and intuitive system, improving efficiency and reducing errors. We use it to manage student data, schedule sessions, and automatically generate transcripts, which has simplified many of our academic processes.
What I like best is its user-friendly and intuitive design. It makes managing tasks, attendance and academics seamless and efficient.
Go deeper
From the Creatrix library.
Blogs, whitepapers and case studies for the people who run the season: exam cells, controllers, evaluators and registrars.
Frequently asked
Plain answers about examinations.
How does the system decide who may sit an exam?
Eligibility is evaluated against your rules before a hall ticket exists: registration status, attendance percentage, internal marks, fee clearance, disciplinary status and any programme-specific condition.
Exceptions are raised for a named approver rather than resolved at the hall door, and the decision, the rule and the approver stay on the candidate record.
Does it allocate seating and produce hall tickets?
Yes. Seating is allocated from a hall and room registry against capacity, spacing and mixing rules such as no two candidates from the same course side by side, across multiple buildings and campuses.
Hall tickets, attendance sheets, seating charts and door lists are generated from the same allocation, so what the invigilator holds and what the candidate holds cannot disagree.
How is blind evaluation enforced?
Candidate identity is replaced by a masked identifier at script allocation, so the evaluator sees the script and the scheme but not the student.
Allocation can exclude the teaching faculty for that section, double or triple valuation is supported with a third-evaluator rule on variance, and every unmasking is an audited event with a reason.
Do you support onscreen evaluation?
Yes. Scanned scripts are distributed to evaluators with annotation, question-wise mark entry against the scheme, running totals, and completion tracking per evaluator and per paper.
Question-wise marks flow straight into tabulation and outcome attainment, so nothing is re-keyed from a mark sheet.
How are malpractice and incidents handled?
An incident is a record, not a note in a diary. The invigilator raises it in the session with category, evidence and statements.
It routes to the examination committee for a decision, and the outcome, penalty and appeal history stay attached to both the candidate and the session.
What happens with revaluation and recounting?
Requests are raised within the configured window, priced and paid where a fee applies, then allocated to a fresh evaluator with the original marks hidden and your revision rule applied.
The original result is preserved, a new version is created, and the reason, evaluators and approvers are recorded.
Can we run it standalone?
Yes. It runs on its own against candidate and registration data imported from your existing student system, and it connects into the Academic Operating System when you are ready, so eligibility, evaluation, results and attainment run on the same records as registration, grading and accreditation.
SEE IT ON YOUR OWN EXAM SEASON
Bring one session and one hall. We will seat and evaluate it live.
A tailored proof session uses your eligibility rules, your halls and your evaluation policy, not a canned demo. Leave with a named, dated next step.