ProctorSys → Research
Original researchOnly 5 of 61 real exam papers were multiple choice
Before building the way students answer, we wanted to know how exams are actually written — not how exam software assumes they are. So we read 61 real engineering question papers from one student's own folder and counted. Five of them could be answered by choosing an option. The other fifty-six could not.
What the other 56 papers actually asked for
They were not simply "long answer" questions. They were the ordinary working of an engineering course: derive an expression, calculate a value from given conditions, draw and label an arrangement. One asked the candidate to express quantitatively what changes when a plate is moved by 2.1 × 10⁻⁴ cm.
None of that can be typed comfortably, and none of it can be scored by comparing a selected option against a key. It has to be written, and it has to be read by a person.
Why this decides which software an institution can use
Most online examination platforms are built around a question that can be auto-scored: one stem, four options, one key. Everything downstream assumes it — the import format, the marking, the instant result.
If ~92% of a department's papers do not look like that, then such a platform can run a small minority of its exams. The rest either get rewritten into multiple choice — changing what is being assessed — or stay on paper. In practice, they stay on paper, and the software is used for practice tests rather than for the exams that matter.
The practical test for any exam platform: take one of your own past papers, unmodified, and ask whether the system can run it as written.
If the honest answer is "after we convert the questions", the conversion is the real cost — and it recurs every term.
The limits of this study, stated plainly
This is a small, non-random sample and it should be read as an indication, not a national statistic. We would rather say so than have somebody discover it later:
- 61 papers, from one student's folder. Not sampled across institutions, states or boards.
- Engineering only. A commerce, law or humanities paper may distribute differently — though rarely towards more multiple choice.
- "Readable" was a filter. Papers too damaged or poorly scanned to read were excluded, and their format is unknown.
- Counted by hand, by us. We had an interest in the answer, which is exactly why the method and the raw figures are stated rather than summarised.
What it is enough to establish is narrow and, we think, sufficient: written answers are not an edge case in Indian engineering exams. Any software that treats them as one is solving a different problem from the one an exam department has.
What we built because of it
This finding is the reason ProctorSys does two things most exam platforms do not.
- It reads the paper you already printed. Upload the PDF or Word file as your department wrote it, and the questions — and any answer key — are recovered from it, then shown to you for correction. No retyping into a template.
- It accepts handwriting. The student writes on paper as always, photographs each sheet with their phone during a short supervised window after submitting, and the examiner marks those pages onscreen beside the marks box.
Neither is a feature we would have prioritised from a feature list. Both came from counting.
See it run on one of your own papers
The fastest way to judge any of this is to hand us a past paper and watch what the software makes of it. Twenty minutes, nothing to install.