This guide explains revision group workload planning for subject heads and revision programme coordinators. 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.
Revision groups often cross ordinary class boundaries. A pupil may attend support in several subjects, and teachers may offer a mixture of whole-group sessions, focused practice and short reviews. Record the approved groups and session purposes before filling the available timetable. Then identify shared pupils, scarce specialist rooms and teachers with other duties. This helps the coordinator compare competing requests without assuming that every group needs the same amount or type of time.
It also makes late changes easier to explain while keeping learner assessment records and the choice of revision material in the school’s existing academic systems.
Revision Group 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.
A sample programme has six groups requesting one 50-minute guided session. Four groups also request a 15-minute review. The total is 360 group-minutes, but teacher and room demand depends on which groups attend together and which reviews use different staff.
Count guided work and reviews separately. Confirm whether any combined session is approved and useful for its audience. Compare the full staff commitments with available windows before selecting a weekly arrangement for the proposed revision programme to follow.
Check the result: All six guided sessions and four reviews appear in the request list, with teacher and room totals reflecting the approved delivery format rather than an assumed identical commitment for every group during that week.
Revision Group Workload Planning: setup checklist
| Planning input | What to confirm |
|---|---|
| Revision group code | Keep cross-class participant groups distinct. |
| Session purpose | Separate guided practice, discussion and review. |
| Teacher window | Include normal lessons and other fixed duties. |
| Resource requirement | Record rooms or equipment needed for that activity. |
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
A useful trial follows groups that share pupils across two subjects. Ask the coordinator to change one teacher’s availability and inspect the effect on every affected group. The buying decision concerns a feasible programme and clear outputs. It should not assume the tool diagnoses learning gaps, supplies examination questions or guarantees improved results simply because revision sessions have been scheduled.
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 revision groups?
- Overlapping cross-subject groups that share pupils.
- Assuming all revision sessions require identical room resources.
- Putting individual attainment information into widely shared group labels.
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.