Exam and report card workflows
From exam setup and marks entry to principal review and printable PDF report cards — a practical workflow for international schools.
Results season compresses months of teaching into two weeks of chaos: subject teachers enter marks on different timelines, coordinators chase missing grades, principals discover outliers too late, and IT gets asked to “just mail merge something” for report cards. When marks live in isolated spreadsheets, every term repeats the same emergency.
A coherent exam workflow treats setup, entry, review, and publication as one chain on the student record — the same record attendance and fees already use.
Phase 1: Exam setup and subject schemes
Before anyone enters marks, define:
- Exam session name and academic term
- Classes and subjects included
- Maximum marks per component (written, practical, coursework where applicable)
- Grade boundaries or GPA mapping if you publish both raw and letter grades
- Who may enter vs who may approve
International schools running multiple curricula still benefit from one exam container per session even if report card templates differ by programme. Exams and report cards solution describes how Edument OS models sessions and schemes — the principle applies regardless of vendor.
Import class lists from the SIS; do not rebuild rosters manually. If a student transferred mid-term, their marks history should follow one profile.
Phase 2: Marks entry with guardrails
Teachers need a grid that is fast on a laptop and usable on a tablet. Guardrails matter:
- Warn on marks above maximum or negative values
- Flag blank cells before submission
- Lock subject columns after HOD sign-off
- Show class statistics only to roles allowed to see them (reduce comparison anxiety)
Avoid emailing CSV templates for “convenience.” Email attachments become version forks. Entry inside the system preserves audit.
Phase 3: Review before publication
Principals and coordinators need a review queue, not a folder of forwarded files:
- Missing subjects per student
- Outliers vs class distribution (investigate, do not auto-change)
- Students on leave or exam concessions documented
- Attendance percentages pulled from the same attendance module (attendance best practices)
Review comments should stay off the published card unless policy says otherwise. Internal notes belong in staff views.
Phase 4: Report card generation
PDF report cards should be generated from approved marks, not pasted into Word one student at a time. Templates vary — IB schools may emphasise criteria; British schools may show levels — but generation should be batch with per-student preview.
Parents receive cards through:
- Parent portal download
- Email with secure link or attachment per policy
- Printed distribution for younger years
WhatsApp is usually wrong for full report cards (file size, privacy); use it for notification that results are available in the portal.
Roles and permissions
| Role | Typical permissions |
|---|---|
| Subject teacher | Enter marks for own subjects |
| HOD | Review subject, lock column |
| Exam coordinator | Cross-subject completeness |
| Principal | Final approve session |
| Registrar | Publish to portal on schedule |
Emergency edits after publication need a logged reason. Silent edits destroy parent trust.
Timing with fees and clearance
Many schools tie report card release to fee clearance. If you do, automate the rule and communicate it at term start — not the night before results. Finance and academics should reference the same student flag, not two spreadsheets.
See fee collection without spreadsheets for invoice authority.
Multi-campus and standardisation
Multi-campus operations raise questions: Do all campuses share grade boundaries this term? Do templates differ by country branding? Central academic leadership should publish one results calendar; campuses execute locally with the same deadlines.
Integrations and limitations
Google Classroom can sync courses and rosters; it is not a full exam marks system for formal report cards. Read Google Classroom vs school SIS before expecting Classroom to replace results workflows.
Online exam modules (where offered on Enterprise) may feed marks into the same session — define whether online scores auto-populate or require teacher confirmation.
Migration from legacy tools
Export historical results if regulators or universities require them, but do not let legacy CSV shape your new schema forever. Migration sequencing often places academics after people data and before portal go-live.
Compare OpenSIS or Fedena if you are leaving another SIS — ask specifically about report card templating and principal review.
Checklist before go-live
- Subject schemes tested on one class
- Teacher training on entry and lock states
- Principal review path rehearsed with dummy data
- PDF template signed off by academic board
- Portal publish date communicated to parents
- Attendance on cards verified against attendance module
Exam workflows are where schools prove they are serious institutions. Connected marks, review, and publication save reputational damage from “wrong grade on the PDF” stories — and give teachers their evenings back during results fortnight.
Explore features for examinations module detail and pricing for plan limits on students and teachers.
Moderation meetings that leave an audit trail
Internal moderation — adjusting grade boundaries, discussing outliers — should happen in documented meetings, not silent bulk edits. Capture minutes separately; system logs show what changed, not why. Principals append approval notes when boundaries shift after entry closes.
Special cases schools forget until results week
Exam concessions and access arrangements — extra time, separate room, modified papers — should flag on the student row before marks entry, not as sticky notes.
Transfer students mid-session — marks before arrival may live in another school; decide whether you import historical PDF only or enter carry-forward components.
Withheld results — fee clearance or disciplinary hold should block portal publish automatically when policy requires, with a reason code registrars can explain to parents.
Re-marks and post-publish corrections — require principal approval and parent notification trail; silent PDF swaps destroy trust.
Coordinating timetables and exam seating
Exam weeks stress seating, invigilation, and room swaps. Timetable modules help; if yours is external, at least link exam session registers to class lists in the SIS so marks entry grids match who sat the paper.
Parent communication timeline
Publish a calendar at term start:
- Last day for teachers to enter marks
- HOD review window
- Principal approval date
- Portal publish datetime (timezone explicit for international parents)
WhatsApp or email nudges only after portal publish — not before PDFs are approved.
Quality assurance sampling
Before batch PDF generation, sample five students across programmes:
- Attendance % matches attendance module
- Names match legal profile
- Grade boundaries applied correctly
- Comments appear on right template
One hour of QA prevents a hundred apology emails.
Alumni and transcript requests
Years later, universities ask for transcripts. Archived exam sessions in the SIS beat searching Google Drive for “Results 2024 final FINAL.pdf”. Plan retention when designing session naming — include academic year and programme clearly.
Summary
Results season improves when setup, entry, review, and publish share one system with attendance and student identity. Publish the workflow diagram on the staff wiki before the first practice run — verbal tradition alone will not survive registrar turnover. Invest in moderation discipline, parent calendars, and QA sampling — software accelerates good process; it cannot replace principal judgment on outliers or fee clearance rules your board already approved.
