Exam session lifecycle

Examination management is organized around sessions (for example Term 1 Finals) that contain scheduled papers per class and subject. An Examination committee can govern paper setting, moderation, seating, and result publication; when no committee is bound, the system preserves coordinator access for those actions. Staff receive the specific setter, marker or invigilator assignments they need, while class teachers use the Class Exams hub for review and optional sign-off.

Create the session against an academic year and keep its dates inside that year. The date validator can flag academic-calendar holidays or non-working days for confirmation, and session creation queues a non-blocking sync of examination days into the calendar. After papers are scheduled, venue allocation and persisted seating are separate preparation steps. Seating is per session, uses active students and room capacity, and does not interpret special-accommodation flags; staff must read those flags on the roster and make any operational adjustment manually.

The end of the cycle has two publication concepts. A paper becomes PUBLISHED so its linked FINAL assessment can be marked. Later, session result publication builds SessionGradeCard rows from published papers, freezes any remaining paper marks, and exposes formal results to families. That session card is distinct from the continuous-assessment term report card at /grades/report-cards.

Setup vs day-of

Three-party model

• Examination committee - sessions, schedule, paper publish, results publish/revoke, revaluation queue
• Subject teachers - setter tasks, paper builder, marking tasks, invigilation on exam day
• Class teachers - /my-class/exams review; optional Acknowledge results ready before publish
• Student - /my-exams schedule and hall tickets after schedule publishDate; marks after results publish
• Parent - /parent-dashboard/exams?childId= for the selected child (schedule, tickets, published grade cards)