From the blueprint to the report card
One chain on one set of records: the pattern a paper follows, the paper itself, the exam it is sat in, the marks, and the report card those marks print onto. Nothing is re-keyed between the steps, which is where the arithmetic errors normally come from.
The paper file and the marks ledger
The pattern of a paper usually survives only as last year’s PDF and one teacher’s memory. Marks get written in a subject notebook, copied into a consolidated ledger, then typed a third time onto report cards. Here the pattern is a document, the marks are one row per subject per student, and the report card is printed from those rows.
Last year’s question paper as the only record of the pattern
A subject-wise marks notebook per teacher
A consolidated marks ledger typed up by hand
Report cards filled in from that ledger
Examinations, screen by screen
Each of these is a screen or a service in the module rather than a heading on a roadmap.
Blueprint the paper
Sections with a dominant question type, marks per question, a question count, internal choice, an easy / medium / hard mix and optional chapter weightage — against a total-marks and duration target, with the general instructions that print at the top.
Ten question types
Multiple choice, very short, short and long answer, case study, assertion-reason, fill in the blank, true or false, match the following, and diagram.
Edit the paper as a document
A generated paper opens in a rich-text editor, so wording is corrected where the paper actually is rather than in a separate file, and finished papers are kept in a library you can reopen.
Schedule it, and know where it is
An exam moves through draft, scheduled, ongoing, grading, results-pending-approval, published and archived — so “are the results out yet” has one answer rather than three.
Enter marks from the keyboard
The grade grid steps down on Enter or the arrow keys and takes AB for absent, so a class can be entered without reaching for the mouse.
Build the report card from zones
Switch on what your card carries: header, student block and photo, marks-table columns, co-scholastic activities, an attendance block, a grade legend, remarks, the result, and the signature labels — with a grading scale of bands behind the letters.
The same row, read from somewhere else
The point of an ERP is not that it has a lot of modules. It is that a fee concession, an attendance shortfall and a report card are all reading one record. These are the places Examinations touches.
Attendance
The attendance block on a report card prints working days, days present and the percentage from the attendance register — the same figures a shortage letter is computed from.
Academics
Classes, sections and subjects come from Academics, and the pass mark a promotion rule checks is the mark recorded here.
Reports
An exam marks ledger is one of the built-in report definitions, so marks leave the module as a spreadsheet without a copy-paste.
What Examinations does not do
Stated here rather than discovered in week three. If something you need is on this list, ask before you buy — it is a better conversation than the one after.
Publishing a result sets a status and makes the marks readable on the student’s own exams page. Nothing is sent — no message goes out, and a family learns the results are up by opening the portal.
Paper generation and paper repair call an AI endpoint, and the output is a draft. The teacher review editor exists because it is a draft — a paper should not go to print unread.
Question content is per-school: papers and blueprints your staff create in the product. No licensed question bank is bundled with it.
Set your institution up on Elevate
Start on the free plan for up to 250 students. Paid plans begin at ₹1499 per month, billed to the institution.