This guide explains marking panel workload planning for the examinations officer and subject heads. Start by counting requested work and checking the available time. Then use the example and checks below to agree a practical next step with the people who run the schedule.
A marking panel timetable coordinates people and rooms around the school's assessment process. Teachers may need time for individual marking, shared review and a moderation meeting. Those activities are related, but they do not always require the same staff at the same time. List the operational stages before placing meetings. Keep confidential assessment material in the school's approved systems and use neutral session labels in the schedule. The timetable can then show who needs to attend, which room is reserved and when a panel decision is due.
It should not imply that scheduling software marks work or determines grades.
Marking Panel Workload Planning: worked example
Illustrative planning example. The numbers and timings below explain a possible situation; they are not customer results or required staffing standards.
Five subject panels each request a 60-minute review and a 30-minute final meeting. That is 450 panel-minutes. It is not 450 minutes for every teacher, because panel membership differs.
Count sessions first, then calculate each required attendee's commitments from their panel membership. Separate solo work from shared meetings so the room and staff totals remain meaningful.
Check the result: The session total matches the request list, and one teacher who belongs to two panels has a correctly counted personal workload.
Marking Panel Workload Planning: setup checklist
| Planning input | What to confirm |
|---|---|
| Panel code | Identify the subject panel without including learner records. |
| Required roles | Separate all-panel meetings from smaller review groups. |
| Stage deadline | Record the agreed completion point for each operational stage. |
| Room requirement | State the meeting space and approved equipment needed. |
Count participation and resource time separately
Start with the sessions the school has approved, including their purpose and required attendance. A shared activity can serve several groups in one room. However, the same programme may need extra preparation from a teacher or support colleague. Count those commitments separately. For example, two repeated workshops create two trainer bookings even when each participant attends only one. Keep a request list with stable activity codes so revisions can be checked. Then compare group participation, staff time and resource occupancy. These totals answer different planning questions.
A clear count helps the coordinator explain whether an extra request needs another window, a different format or an approved resource change.
Settle requests before filling the timetable
A large request list often contains preferences as well as agreed requirements. Ask each organiser to confirm the sessions their programme actually needs. Then identify requests that duplicate another sheet or replace an earlier proposal. Subject heads should decide which delivery changes are acceptable. The scheduling review can show their consequences, but it cannot settle educational priorities by itself. Therefore, keep unresolved requests visible rather than making them disappear from the count. Review the least flexible staff and specialist spaces early.
Finally, compare the draft with the approved list and explain any activity still awaiting a decision before the school releases a working programme.
Questions to ask before choosing software
The useful buying question is whether the panel can protect review time without creating teaching clashes. Use a realistic subject meeting and a shared head of department in the trial. Check that a later review date does not silently leave the panel's final meeting unchanged. Assessment decisions remain with the school; the schedule makes their operational sequence visible.
Bring a representative example to your evaluation. Review the current VeloRoster plan and its limits and Try interactive demo → that reflects your team’s people, spaces and timing needs.
Frequently asked questions
What should we avoid when planning marking panels?
- Treating all marking time as a meeting for every teacher.
- Including learner names or grades in public activity labels.
- Moving a review session beyond the final panel meeting.
Review these points with the activity owner before you approve the plan.
Should one joint activity count once or once per group?
Count the resource booking once when groups share the same activity. Also record each group’s intended participation. Those two views describe different demand. Then check the approved capacity and staffing arrangement for the combined session before treating it as a feasible shared booking.
How should preparation time enter the calculation?
List preparation where it creates a real staff or resource commitment. Use a duration agreed by the activity owner. Then connect that work to the session it supports. This avoids counting only pupil-facing time while leaving essential school duties outside the planning review.
What if the requested sessions do not fit?
Show the unmet requests and the resources causing the restriction. Then ask the responsible school lead to compare acceptable changes in timing, grouping or delivery. Keep the decision explicit. A timetable should not quietly remove an agreed activity to make the remaining grid appear complete.
Take the next step. Explore the VeloRoster interactive demo with sample data, then check your requirements against the current access and pricing details. Keep the operational decisions in this guide with the people responsible for your organisation’s schedule.