How to Generate Student Report Cards Automatically with School Software

Why manual report cards break down

• Each subject teacher keeps marks in their own notebook. Aggregating them is a manual exercise.
• Computing percentage, grade, division and rank is error-prone. One wrong cell ripples into 40 wrong report cards.
• Comparing this term’s result with the previous term needs another spreadsheet.
• If a parent disputes a mark two weeks later, no one can tell who entered what.

The full-school version of this pain is documented in 10 benefits of school management software.

Three exam tiers, one machinery

An Indian school year has three independent exam structures — and a sensible school ERP keeps them as separate modules:

• Exam — the formal exams, typically Half-Yearly and Annual, with subject-wise marks.
• Class Test — monthly tests run per class.
• Unit Test — subject- and lesson-level micro-tests.

Each of these has its own list of exams, max marks per subject, grade and division criteria, marks entry, marksheet print and admit card. They share the student database but not the marks data.

This three-tier separation is a core differentiator of how Apna School models exams — see the features page for detail.

Setup — do this once at the start of the session

1. Subjects and class-subject mapping

Define every subject (Mathematics, Science, English, Hindi, Sanskrit, etc.) once. Then map subjects to classes — Class 5 has Math + English + Hindi + Science + Social Science; Class 8 adds Sanskrit. Mark each as Compulsory / Optional / Practical and whether it counts in the result.

2. Exam names and max marks

Per exam tier (Exam / Class Test / Unit Test), define exam names and the max marks for each subject. Annual Exam → Class 8 → Mathematics → 100 marks (75 written + 25 practical).

3. Grade criteria

Set the grade table: A = 86–100, B = 71–85, C = 51–70, D = 33–50, E = 0–32. Add grade points if your school’s board uses GPA. The system grades every result automatically against this table.

4. Division criteria

Set the division thresholds — First Division ≥ 60%, Second Division 45–59%, Pass 33–44%, Fail < 33%. Pass / fail and divisions are derived from this once and applied to every student.

5. Roll-number mapping per exam

Roll numbers for an exam aren’t the same as the class roll. Map a roll number per student per exam — the marksheet and admit card both honour this mapping.

Marks entry workflow

Once setup is done, marks entry is straightforward:

1. Pick the exam tier (Exam / Class Test / Unit Test).
2. Pick the exam (e.g. Annual Exam — Class 8).
3. Pick the subject.
4. The screen shows the class’s student list pre-sorted by roll number; type the marks; save.
5. Repeat per subject. Five minutes per subject for a 40-student class.

The system auto-flags absent students, validates marks against max-marks, and computes grade + percentage + division at save — not in a separate batch run.

Marksheet formats and admit cards

Apna School ships two marksheet formats. Pick whichever your school’s board / parent expectations match. The marksheet shows:

• School name, address, UDISE, affiliation number from the school profile.
• Student name, photo, roll number, class, section, admission number.
• Subject-wise max marks, obtained marks and grade.
• Total, percentage, overall grade, division and pass / fail.
• Rank in class (optional).

The same data is used to generate admit cards for the upcoming exam — one click per class.

Auditability and corrections

If a teacher entered a wrong mark and you find out a week later, the correct workflow is to edit and re-print — not to scratch the printed sheet. The original entry stays in the audit trail; the new mark is what gets printed. This protects the school from the “but I saw 87 on the original” conversation.

For the broader picture, see how fee management uses the same edit-with-reason discipline, and how digital attendance feeds into the working-days calculation that affects exam eligibility for some boards.