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

One. With 6 people required on shift, a team of 7 carries a single person of headroom, so one approved absence uses the entire allowance and the next request for the same day drops the team below its minimum. Across 261 working days the model expects the team to be short on about 57 of them.

Would hiring an eighth person fix a team of 7?

It helps more than any single hire elsewhere in this library. A team of 8 holding the same minimum of 6 carries 2 people of headroom, and expected short days fall from about 57 a year to about 18.1. Lowering the minimum to 5 while staying at seven does better still at about 12.5 short days, so price both options before committing to the hire.

How much worse is a peak leave period for a team of 7?

In a peak period the average day is already short. The model puts 0.89 people away on an ordinary working day and 1.42 in a peak period, and 1.42 is more than the 1 person of headroom the team has. Held across a full year, that peak rate works out at about 112.1 short days. Because the model treats leave as independent when real requests cluster on school holidays and late December, read that as a floor rather than a forecast.

How Many of 7 Staff Can Be Off at Once?

Seven is the peak of the sawtooth: one person of headroom, about 57 short days a year, and an eighth person cuts that to 18.1.

Can be away at once1

Short days a year57

One. A team of 7 that needs 6 people on shift carries exactly one person of headroom, so a single approved absence spends the whole allowance for that day. The model expects the team to fall short on about 57 of 261 working days a year, the highest figure of any team size in this library, and an eighth person would bring it down to about 18.1.

How often that many are actually away

The average is 0.89 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 7 people each away on 12.6 percent of working days, this is how a year of 261 days is expected to distribute.

0 away

101.3 days

1 away

102.7 days

2 away

44.6 daysshort

3 away

10.8 daysshort

4 away

1.6 daysshort

5 away

0.1 daysshort

6 away

0 daysshort

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

What is hard about 7

Read down the library and expected short days do not fall as teams grow. They climb, then snap back. Four carries about 21 short days a year, five about 32.1, six about 44.3, and seven about 57. Then eight drops to about 18.1. Nothing improved anywhere between four and seven, because headroom only moves when a team crosses a whole person boundary, and across that whole run the minimum on shift rises in step with the team. Seven sits at the top of the climb: the last and worst size before the boundary, and the single worst place to sit in this library.

So the question at seven is not whether the roster is tight, it plainly is, but which lever buys the second person of headroom. Hiring an eighth is one answer and a strong one, taking expected short days from about 57 to about 18.1, which is the largest improvement a single hire produces anywhere in this library. The cheaper answer usually gets skipped. Hold the team at seven, lower the minimum on shift from 6 to 5, and the model expects about 12.5 short days, better than the eighth hire delivers, because a team of seven has fewer people who can be away on the same day than a team of eight does. Headroom is what the roster runs on, not headcount, so test whether 6 is a genuine floor or an inherited habit before you write a job ad.

The averages hide how narrow one slot is. Each person is away on about 12.6 percent of the 261 working days in a year, which puts 0.89 people away on an ordinary day and 1.42 in a peak leave period. In peak the expected number away is already larger than the one slot the roster has, and that rate, held across a full year, works out at about 112.1 short days. Underneath all of it sits 175 person-days of whole team leave demand that has to pass through a gate one person wide. The model also assumes people book leave independently of one another, which is the assumption most generous to the roster, since real requests cluster on school holidays and the last fortnight of December. Every figure here is a floor on the real risk rather than an estimate 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
6assumed	1	57
5	2	12.5
4	3	1.7
3	4	0.1

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 0.89 to 1.42. Held across a full year, that rate would imply about 112.1 short days rather than 57. 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

Test whether 6 on shift is a genuine floor before you hire, because holding at seven and allowing 2 people off takes the model from about 57 short days a year to about 12.5, while an eighth person only reaches about 18.1.
Ration the 175 person-days of annual leave against a calendar rather than a balance, since only 1 person can be away at a time and there are 261 working days to spread that demand across.
Build peak period cover first, where the model expects 1.42 people away against 1 person of headroom and the peak rate works out at about 112.1 short days a year.

Common questions

How many of a team of 7 can be on leave at once?: One. With 6 people required on shift, a team of 7 carries a single person of headroom, so one approved absence uses the entire allowance and the next request for the same day drops the team below its minimum. Across 261 working days the model expects the team to be short on about 57 of them.
Would hiring an eighth person fix a team of 7?: It helps more than any single hire elsewhere in this library. A team of 8 holding the same minimum of 6 carries 2 people of headroom, and expected short days fall from about 57 a year to about 18.1. Lowering the minimum to 5 while staying at seven does better still at about 12.5 short days, so price both options before committing to the hire.
How much worse is a peak leave period for a team of 7?: In a peak period the average day is already short. The model puts 0.89 people away on an ordinary working day and 1.42 in a peak period, and 1.42 is more than the 1 person of headroom the team has. Held across a full year, that peak rate works out at about 112.1 short days. Because the model treats leave as independent when real requests cluster on school holidays and late December, read that as a floor rather than a forecast.