How many people can be on leave at once on a team of 16?

Four, assuming 12 have to be on shift. A fifth absence puts the team under its minimum, and the model expects that to happen on about 11.1 days across 261 working days, with 2.02 people away on an average day.

Would hiring more people reduce the shortfall?

Not right away. Headroom moves only in whole people, so a team of 18 still gets 4 concurrent slots and the model expects about 17.6 short days a year, worse than the 11.1 at 16. The next genuine step is 20, with headroom 5 and about 8.6.

What happens in peak leave periods?

The model puts 3.24 people away instead of 2.02, and that rate works out at about 54.5 short days a year if it held all year. Since the model assumes people book leave independently, while real leave clusters on school holidays and the final fortnight of December, treat 11.1 as a floor on the risk.

How Many of 16 Staff Can Be Off at Once?

Sixteen is the smallest team in this library that carries four concurrent leave slots, and it shows: about 11.1 expected short days a year.

Can be away at once4

Short days a year11.1

A team of 16 that needs 12 people on shift can have 4 away at once. The model puts 2.02 people away on an average working day and 3.24 in a peak leave period, so it expects the team to drop below 12 on about 11.1 days out of 261. That is the lowest expected shortfall of any team size under 20 in this library, because 16 is the first size at which a fourth concurrent leave slot appears.

How often that many are actually away

The average is 2.02 people away, and averages do not break rosters. What breaks a roster is the tail: the days when more people than usual are off at the same time. With 16 people each away on 12.6 percent of working days, this is how a year of 261 days is expected to distribute.

0 away

30 days

1 away

69.5 days

2 away

75.5 days

3 away

51 days

4 away

24 days

5 away

8.3 daysshort

6 away

2.2 daysshort

7 away

0.5 daysshort

8 away

0.1 daysshort

9 away

0 daysshort

Everything below 5 away fits inside the roster. Everything from 5 up is a day the operation runs under its minimum of 12, and those add up to about 11.1 days a year.

What is hard about 16

Sixteen lands on a whole-person boundary, and that is the point of this page. Coverage headroom does not grow smoothly with the team; it steps, because you cannot hold three and a half people in reserve. A team of 14 runs on headroom 3 and about 23.6 expected short days a year. A team of 16 runs on headroom 4 and about 11.1. Two more names cut the expected shortfall to less than half, not because two people absorb much absence on their own, but because they bought a fourth whole slot rather than a fraction of one.

The same rule turns against you immediately above this line. A team of 18 still carries headroom 4, the same four slots as 16, but with more people drawing on them, and the model expects about 17.6 short days a year against 11.1 here. The next real improvement is 20, where headroom 5 brings the rate to about 8.6. So growth past 16 without revisiting the minimum of 12 on shift makes the roster worse before it makes it better, and 16 outperforms every smaller size in this library: 12 at about 14.3, 8 at about 18.1, 4 at about 21. If you are at 16 today, the fourth slot is the asset, and it is worth more than the next hire.

Those four slots sit close to the edge, and the numbers around them move fast. Insist on 13 on shift instead of 12 and the expected shortfall goes from about 11.1 days a year to about 35.1; accept 11 and it falls to about 2.8. Underneath all of it, the model assumes people book leave independently of one another, which is the assumption most generous to the roster. Real leave clusters on school holidays and the final fortnight of December, and the team has 400 person-days of annual leave to place across 261 working days. In a peak period the model already expects 3.24 people away rather than 2.02, a rate that works out at about 54.5 short days a year if it ran all year. Read 11.1 as a floor on the risk, not a forecast of it.

Move the minimum, move the answer

The team size is usually fixed. The minimum on shift often is not, and it is the faster lever: making one role coverable for a day changes the arithmetic more than a hire does.

Minimum on shift	Can be away	Short days a year
15	1	161.5
14	2	86
13	3	35.1
12assumed	4	11.1
11	5	2.8
10	6	0.5

What this assumes, and where it is generous

These figures treat each person as independently likely to be away, which is the assumption most favourable to the roster. Real leave clusters: school holidays, the last fortnight of December, and the local summer shutdown pull requests onto the same dates. Treat every number here as the best case, and the peak column as a reminder of how far the real case sits from it.

Run the same team at a peak concentration of 1.6 times the ordinary rate, which is a stated planning assumption rather than a measured figure, and the expected count away rises from 2.02 to 3.24. Held across a full year, that rate would imply about 54.5 short days rather than 11.1. Real years are neither, but the gap between the two is the size of the scheduling problem that leave clustering creates.

The inputs are 25 days of paid annual leave and 8 days of average sickness per person. Both vary by country, and the relief factor library carries sourced figures for 17 of them, from zero statutory leave in the United States to 28 days in the United Kingdom. Swap your own numbers in and the shape of the distribution holds even as the counts move.

What to do with this

Cap concurrent leave at 4 and treat the fifth request as an exception that needs a named plan, because that fourth slot is the whole difference between the 23.6 expected short days a team of 14 lives with and the 11.1 here.
Defend the minimum of 12 on shift harder than you defend headcount: holding 13 pushes the expected shortfall from about 11.1 days a year to about 35.1, while accepting 11 drops it to about 2.8.
Place the team's 400 person-days of leave deliberately across the 261 working days instead of waiting for growth to fix the roster, since a team of 18 still runs on headroom 4 and about 17.6 expected short days.

Common questions

How many people can be on leave at once on a team of 16?: Four, assuming 12 have to be on shift. A fifth absence puts the team under its minimum, and the model expects that to happen on about 11.1 days across 261 working days, with 2.02 people away on an average day.
Would hiring more people reduce the shortfall?: Not right away. Headroom moves only in whole people, so a team of 18 still gets 4 concurrent slots and the model expects about 17.6 short days a year, worse than the 11.1 at 16. The next genuine step is 20, with headroom 5 and about 8.6.
What happens in peak leave periods?: The model puts 3.24 people away instead of 2.02, and that rate works out at about 54.5 short days a year if it held all year. Since the model assumes people book leave independently, while real leave clusters on school holidays and the final fortnight of December, treat 11.1 as a floor on the risk.