This guide explains marking panel schedule import for the examinations officer and subject heads. Start by preparing clean scheduling data and checking a small sample. 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 Schedule Import: worked example
Illustrative planning example. The numbers and timings below explain a possible situation; they are not customer results or required staffing standards.
A department workbook mixes individual work blocks with panel meetings. It also stores a meeting date as text in one row and as a spreadsheet date in another. A large import could hide both issues.
Separate activity types and normalise dates in a working copy. Use neutral session codes instead of assessment records. Test a small sample through the actual template and compare the rendered dates.
Check the result: The sample creates the expected number of meetings, with correct dates and no confidential learner data in activity labels.
Marking Panel Schedule Import: 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. |
Prepare a minimal scheduling copy
Choose the approved source workbook before preparing an import. A department folder may contain earlier proposals, combined sheets and individual requests for the same activity. Compare them before loading anything. Then use stable codes for staff, groups, rooms and equipment. Keep operational titles clear and remove private notes that do not belong in shared timetable views. Dates and times need consistent values, especially when some cells contain text. Preserve the original file so the coordinator can trace a mapping decision. Finally, prepare the working copy against the current supported import template.
A clean source makes it easier to distinguish an import problem from an unresolved planning decision already present in the spreadsheet.
Test a complete school sequence first
Choose a small sample containing the relationships that matter to the programme. Include a shared teacher, a participant group with two activities and a resource handover where relevant. Then map the fields using the current import template and supported format. Compare the resulting activities with the approved source, including dates, durations and identities. Similar labels can create duplicate resources or split one person into several records. Therefore, inspect more than the total row count. Ask the programme owner to review one complete sequence before loading the remaining data.
Keep a record of the accepted mapping and confirm the full import totals afterwards so the same issue does not recur in a later school planning cycle.
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.
Can we import the school’s existing spreadsheet unchanged?
Compare it with the current supported template first. Standardise identities, dates and separate activity rows where needed. Then test a small complete sequence. Existing spreadsheets often combine planning notes and bookings, so the coordinator should prepare a clear operational working copy before loading the full programme.
Should private pupil notes appear in the imported labels?
Use neutral group and activity codes for the operational timetable. Keep learning, admissions or permission records in the school’s approved process. Then review the imported sample and its outputs. Shared labels should contain the information readers need to follow the programme, without unrelated personal notes.
What is a better check than counting imported rows alone?
Compare one complete teacher, group and resource sequence with the approved source. Check dates, durations and stable identities as well as totals. Then review duplicate-looking records. A matching row count can still conceal an incorrect room mapping or one person split across several names.
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.