Home/Technology
Technology
Deliberately conservative, where it counts
Examination systems are judged on whether they run flawlessly for six weeks a year under load, not on architectural fashion. Our technology choices reflect that: controlled execution environments, a centralised data model, and deployment options that respect institutional data boundaries.
Desktop evaluation client
The marking interface is delivered as an installed desktop application rather than a browser page. This narrows the execution surface, makes the evaluator endpoint an identifiable installed component, and keeps the interface independent of whatever browser and extensions happen to be on an examiner's machine.
Registered evaluators download the client from a supplied link and activate it with issued credentials plus a one-time password sent to their registered mobile number.
Centralised data model
Scanned answer books, paper pattern configuration, panel allocation and question-wise marks live in one central database, indexed subject-wise and UID-wise. That single source is what makes instant retrieval for moderation, audit and re-evaluation possible without a separate archival system.
Web dashboards for authorised stakeholders
Coordinators, supervisors and institutional administrators get browser-based monitoring: expected, received, scanned, evaluated, moderated and rejected counts, progress by faculty, and panel-level allocation status. Monitoring access is separate from evaluation access.
Scanning infrastructure
Book scanners image bound answer books without cutting the spine. Question papers and model answers are digitised alongside the scripts so evaluators mark against the same reference material. Scanned data is encrypted before upload.
Integration approach
Candidate, examination and paper-pattern master data is received from the institution in an agreed structured format; verified marks data is returned the same way for result processing. Field mapping is fixed during scoping so each cycle repeats without renegotiation.
Deployment options
Where an institution requires examination data to remain within its own estate, deployment on institutional infrastructure can be arranged. The deployment model is settled during scoping alongside the security review.
Configuration, not customisation
What gets set up before an examination opens
Most of what looks like bespoke development in examination software is actually configuration — provided the product models the domain properly.
| Configured | Why it must be set before evaluation opens |
|---|---|
| Paper pattern | Questions, sub-questions, maximum marks and solving pattern define the validation rules that bind every evaluator on the panel. |
| Optional-question logic | Determines which questions are considered in the total — the single most common source of post-evaluation disputes. |
| Examiner and moderator panels | Allocation cannot begin until panels exist, and panel structure determines the moderation trail. |
| Lot and medium segregation | Answer books are sorted by subject and medium of answer, which drives how they reach the right evaluator. |
| Retention requirement | Sets how long digital answer books are preserved and how re-evaluation copies are produced. |
Next step
Bring your IT and examination teams to the same demo
Technical evaluation and academic evaluation usually happen in separate meetings, which is where misunderstandings start. We are happy to present to both at once.