This guide explains option blocks scheduling software for academic coordinators and subject allocation teams. Start by choosing a workflow that fits the real work. 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 Scheduling Software: 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 Scheduling Software: 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. |
Start with the complete school programme
List the activities that the school has agreed to provide. Include the group, purpose, responsible role and space for each request. Then separate fixed commitments from windows that the organiser can move. A pupil group may cross ordinary class boundaries, so its other activities deserve a check. The same applies to teachers who support several programmes. For example, an available room does not settle a shared teacher’s conflict. Bring the relevant lesson and duty commitments into the planning review. Keep academic decisions with the responsible staff.
This gives the coordinator a clear set of requests to evaluate before deciding how a scheduling tool should support the work.
Ask staff to read the result
A schedule becomes useful when its readers can act on it. Ask a teacher to follow their own day from the first duty to the last. Next, ask a group coordinator to inspect the complete participant sequence. A resource custodian may need a separate view of preparation and handovers. These readers often notice different omissions. Therefore, inspect the actual supported outputs as part of the buying trial. Use plain room names and distinct activity codes. Confirm who approves changes and which released copy staff should follow.
Finally, compare the workflow with the current programme’s difficult week, including the manual decisions that still need school staff.
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.
Can the programme include groups from different classes?
Use clear group identities for the approved participants. Then review their other commitments alongside the activity. Cross-class membership can create overlaps that ordinary class labels conceal. The academic coordinator should confirm the grouping before the operational schedule is released.
Will the software decide the school’s staffing requirements?
The school’s responsible staff set the required roles and approve suitable assignments. Record those decisions in the planning inputs. Then use the schedule to review the resulting commitments. A free staff window does not itself establish that a colleague has accepted a particular role.
What should we inspect before choosing a plan?
Test a shared teacher, a constrained group and a limited resource. Then introduce one realistic change and inspect the resulting copies. Review the current pricing page for the offered plan and limits. Base the decision on the programme you need to run.
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.