It is Tuesday afternoon and the draft datesheet went out to heads of department yesterday. By lunchtime three replies have come back. Chemistry and Computer Science are both on the Thursday of week one, and eleven students take both. The Grade 9 practical is booked into the lab on the same morning as the Grade 11 practical. And a parent has already phoned to ask whether the dates are final, because the family is booking flights.
None of these problems is unusual, and none is caused by carelessness. They happen because most datesheets are drafted on a calendar first and checked against reality second. This post sets out a method that reverses that order, so the first draft you circulate is close to the last.
Gather the constraints before you open a calendar
A datesheet is a scheduling exercise, and every scheduling exercise starts with the rules it must obey. Collect them in writing before any date is chosen. A typical list looks like this:
- Window: the first and last permissible examination days, with holidays, events and term dates already removed.
- Sessions per day: one morning paper, or a morning and an afternoon session, and the length of each.
- Papers per class: every subject and component (written, practical, oral) that needs a slot, with its duration.
- Shared resources: laboratories, the hall, computer rooms and their seating capacity.
- Staff limits: teachers who are away on given days, and subjects with a single specialist who must be present.
- Load rules: no more than one paper a day per student, a rest day before the longest paper, and the two heaviest subjects not on consecutive days where possible.
Write the load rules as rules, not preferences, and decide in advance which ones may bend. When the calendar gets tight, you will need to know which rule gives way first, and that decision is easier made calmly in week one than at seven in the evening before publication.
Check clashes against students, not class names
The most common clash is invisible on a class-by-class grid. Grade 11 Science and Grade 11 Commerce look like separate groups, so it seems safe to put their papers side by side. But if both classes feed students into the same Computer Science elective, two papers at the same time puts those students in two rooms at once.
The reliable test is to check every proposed slot against actual enrolments. For each pair of papers scheduled in the same session, ask a single question: is there any student enrolled in both? If the answer is yes, it is a clash, however the classes are named.
Watch in particular for:
- Elective groups that draw from several sections or streams.
- Repeaters sitting a paper with a lower grade while attending a higher one.
- Combined classes where two sections are taught together for one subject.
- Students with an approved subject change during the term, whose old enrolment may still appear on paper lists.
Consider a school where Amina, Rahul and Sophie are the only three Grade 10 students taking Additional Mathematics alongside Biology. A grid built by class would never show it. A check against enrolments flags it immediately, and the fix (moving one paper to the afternoon) costs nothing at draft stage.
Build the draft in a sensible order
Once the constraints are known, the order you place papers in matters. A sequence that works for most schools:
- Place the most constrained papers first. Practicals that need a lab, papers with a single specialist invigilator, and electives that span many groups have the fewest possible slots. Fix them before the easy papers fill the calendar.
- Place the core subjects next, spacing each class's heaviest papers apart.
- Fill in the remaining papers, keeping each class's daily load to the agreed limit.
- Run the enrolment check on the whole draft, not just on the slots you were worried about.
- Review the load per student, looking for anyone with three papers in three days who could reasonably be spread.
Resource capacity deserves its own pass. If the chemistry lab seats twenty-four and Grade 11 has sixty students taking the practical, that practical needs three sittings. Each sitting is a slot in its own right, with its own invigilator, and it has to be planned now rather than discovered on the morning.
Balance fairness as well as feasibility
A datesheet can be clash-free and still unfair. Two patterns are worth looking for before you publish.
The first is uneven load across classes. If Grade 8 finishes in six days and Grade 9 in eleven, Grade 9 families will notice, and some will ask why. Sometimes the difference is unavoidable, but it should be a choice rather than an accident.
The second is the hardest paper on the worst day. The first morning after a long weekend, or the day after a school event that runs late, is not the slot for a paper students find difficult. A quick read of the draft alongside the school calendar catches most of these.
| Check | Question to ask | Typical fix |
|---|---|---|
| Student clash | Is anyone enrolled in two papers in this session? | Move the smaller paper to another session |
| Resource clash | Does the room hold everyone sitting here? | Split into sittings or use a second room |
| Staff clash | Is the specialist available and not invigilating elsewhere? | Swap with a paper that needs no specialist |
| Load | Does any student sit more than the agreed papers per day? | Spread across the window |
| Calendar | Does a hard paper fall after a holiday or event? | Swap with a lighter paper |
Publish once, then manage changes openly
Families plan travel, tuition and childcare around the datesheet. Every silent edit after publication creates a family who planned around the old version. The rule is simple: circulate a draft internally, collect objections within a fixed deadline, fix them, then publish once.
Publication should reach families through the channel they actually use, and students should be able to see their own papers rather than scanning a grid for their class. A personal datesheet also removes the problem of a student in a split elective reading the wrong row.
When a change is unavoidable (a public holiday announced at short notice, a building closure), treat it as an announcement rather than an edit. State what moved, from when to when, and why. Keep a record of the change so that when a parent says "the date was different when I checked", you can show both versions and the date of the notice.
Common mistakes
- Drafting by class grid alone, which hides every clash caused by electives and repeaters.
- Leaving practicals until last, when the only remaining slots do not suit the lab.
- Forgetting the invigilators. A paper with no available invigilator is a clash too, just a later one.
- Treating the published datesheet as a working file that anyone can quietly adjust.
- Ignoring students with access arrangements, whose extra time can push a morning paper into the afternoon slot.
Frequently asked questions
How early should the datesheet be published?
Early enough for families to plan and for teachers to finish the syllabus with the dates in view. Many schools aim for three to four weeks before the first paper, but check your own calendar and any board requirements.
Should every class have the same number of exam days?
Not necessarily. Senior classes often have more papers. What matters is that the daily load is reasonable and that differences are deliberate.
Where this fits
The datesheet is the first step of a longer examination season. For the full picture, from planning through marks entry to report cards, read the examination management guide.
In Scolvia, the datesheet sits alongside class lists, enrolments and the staff timetable, so clashes against real students show up while you draft, and families see their own papers once it is published. The datesheet module and examinations module pages describe how the pieces connect.