Guide
Sizing training batches for a large team
The right group size is 15–25. Everything above that is a batching problem, and batching is cheaper than it looks.
Updated 10 September 2026
Once a training decision covers more than about twenty-five people, it stops being a training question and becomes a scheduling one. The material does not change. What changes is how you split the group, how you sequence the batches, and how you avoid taking an entire function offline for three days.
This is the part of the process buyers have least experience with, because most people commission training for a large team once or twice in a career. It is also where the cost per head moves most.
The right size for one batch is 15 to 25
Below about twelve, the working sessions lose the friction that makes them useful — there are not enough different projects in the room and challenges get polite.
Above about twenty-five, the working sessions stop functioning. The trainer cannot get around the groups, quieter participants disengage, and the session degrades into a lecture. A lecture is a legitimate format for some content, but it is not what this course is for and it is not what you are paying a day rate for.
Fifteen to twenty-five is the range where the exercises work as designed. That is the constraint that drives everything else in the plan.
Splitting a large department
A department of eighty is three batches, not one very large session. Three batches of roughly twenty-six, or four of twenty if the material warrants smaller groups.
How you split matters. Splitting by intact project team keeps the working sessions coherent — the people in the room are working on the same projects and can build a real plan together. Splitting by seniority is occasionally right when candour is the constraint, though it costs you the cross-level conversation that is often the most valuable part.
Splitting randomly is the one to avoid. It produces rooms where nobody shares a project and every exercise becomes hypothetical.
| Team size | Batches | Days if 3-day course | Notes |
|---|---|---|---|
| Up to 25 | 1 | 3 | Single batch, simplest |
| 26–50 | 2 | 6 | Split by project team where possible |
| 51–80 | 3 | 9 | Spread across weeks so the function keeps running |
| 80+ | 4+ | 12+ | Worth staging over a quarter |
Never stand the whole function down
The operational risk of training a large team is not the cost — it is having nobody available for three days. Batching solves this if you sequence it deliberately.
Run batches a week or two apart rather than back to back, and split each batch so that every project has someone still at their desk. Most clients run one batch per fortnight, which spreads an eighty-person programme across roughly six weeks without a coverage gap.
The other benefit of spacing is that the first batch tells you what to adjust. By the third, the course is materially better fitted to your organisation than it was on day one.
What to decide before asking for a quote
How many people in total, and can they be split by intact project team.
Over what period the programme can run — one quarter is comfortable, one month is tight, one week is usually a mistake.
Whether every batch needs identical content, or whether a senior batch should go deeper on stakeholder and sponsor work.
Who needs to be in the same room as whom. This is the question most likely to be overlooked and most likely to matter.
Questions
›Can we run one large session to save money?
You can, and for a purely informational briefing it is reasonable. For this course it is a false economy: the working sessions are where the value is, and above about twenty-five people they stop working.
The saving is also smaller than it looks once you account for a lower day rate on repeat batches.
›How far apart should batches be?
One to two weeks is the usual rhythm. It keeps operational coverage intact and leaves room to adjust the material between batches.
Much longer than a month and the shared vocabulary starts to fragment — the first batch has moved on before the last has started.
›Should managers attend with their teams?
Usually yes. A manager who has not done the training will not reinforce it, and the practices quietly lapse within a quarter.
The exception is where candour is the binding constraint and people will not speak freely in front of their reporting line. That is worth asking about directly during scoping.
›Can new joiners be trained later?
Yes, and it is worth planning for. A refresher batch six or twelve months on, covering new joiners and anyone who has changed role, keeps the practice from decaying.
It is priced as a repeat batch rather than a new engagement.
Get a scoped quote
Tell us the team, the timeframe and whether you pay the HRD Corp levy. We will come back with a day rate, a shape and an honest answer about whether we are the right fit.