This guide explains option blocks workload planning for academic coordinators and subject allocation teams. 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.
Option blocks place several teaching groups into the same part of the school timetable. The groups may run in parallel, but teachers, rooms and pupil memberships still connect them. Record the approved grouping decisions before placing dated activities. Then review each block as both a set of simultaneous sessions and a collection of individual commitments. This helps the academic team see whether a proposed arrangement fits the available resources. It also makes the effect of a teacher or room change easier to explain.
Subject choices, curriculum decisions and pupil allocation remain with the school’s established academic process.
Option Blocks 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.
An illustrative option block contains four groups, each needing two 40-minute sessions. The total is eight group sessions, but parallel delivery may use only two shared periods if staff and rooms permit. Group-minutes and occupied clock time therefore describe different requirements.
Count each group’s required sessions and identify the approved parallel windows. List the teachers and rooms needed simultaneously. Ask the academic team to resolve impossible combinations before placing the block’s dated activities into a draft timetable for review.
Check the result: All four groups receive their agreed sessions, and the simultaneous staff and room demand fits the chosen windows without confusing eight group bookings with eight separate whole-school periods in the approved schedule.
Option Blocks Workload Planning: setup checklist
| Planning input | What to confirm |
|---|---|
| Approved option group | Use stable codes from the school’s grouping decision. |
| Shared block window | Identify sessions intended to run in parallel. |
| Teacher allocation | Keep each required teaching role explicit. |
| Room requirement | Distinguish ordinary spaces from specialist allocations. |
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
Test a real approved block with a shared teacher and a specialist room requirement. Ask the academic coordinator to follow one pupil group through the proposed sequence, then change a session. The useful result is a clear operational clash review. Do not assume the tool collects subject choices, automatically creates optimal option combinations or replaces a dedicated curriculum-planning process without confirming those capabilities separately.
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 option blocks?
- Assuming parallel sessions cannot share a teacher or pupil conflict.
- Treating a room substitution as a change to pupil subject choices.
- Copying unapproved grouping drafts into a released teaching schedule.
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.