Maximum Hours as a Rota Constraint
How a maximum on working hours behaves when it meets a rota, why it binds unevenly across a team, and the three places a pattern quietly exceeds it.
What one team's hours looked like when sorted by person rather than by shift
Comfortably inside whatever applies to them.
All voluntary, all the same three people since March.
Two rotas, neither of which can see the other.
Recorded in a different system from the rota.
Asked once, at induction, years ago.
The three people nearest any limit are the three covering a vacancy, and three further lines cannot be answered from the rota at all. The compliance report showed the first line and none of the others. This is one employer's own position, not a statement of what any limit requires.
A maximum on hours constrains a rota differently from a staffing floor. The floor applies to a shift and is visible from above; the maximum applies to a person over a period and is only visible by reading one row at a time.
The rule discussed in “Maximum Hours as a Rota Constraint” is easier to test when the published schedule can be compared with a consistent record of actual hours. A team reviewing view the complete scheduling explanation for job costing with accurate hours can add current attendance and project context while keeping contractual rules and manager decisions explicit.
What the maximum is, over what period it is measured, who is covered and what may be agreed individually differ by jurisdiction, by sector and by agreement, and are a question for somebody qualified in the place concerned. What follows is about how the arithmetic behaves.
Teams documenting “Maximum Hours as a Rota Constraint” may use AHRQ healthcare-workforce resources as an independent reference. Recheck current requirements before changing a live rota.
Why it binds unevenly
A pattern that is comfortably inside a maximum for most of the team can sit on the edge for two people, because the people on the edge are the ones doing the extra shifts, and they are usually the same two people every month.
That is the first thing to look at. The constraint does not apply to the rota; it applies to individuals, and in most teams it is a live constraint for a small minority and irrelevant for everybody else.
The three places a pattern exceeds it quietly
- Additional shifts picked up voluntarily, which are often recorded in a different system from the rota.
- A second job or a bank contract elsewhere in the same organisation, where neither rota can see the other.
- Training, travel or on-call time that may count and is not planned as working time.
The middle one is the most common and the hardest to see. Two rotas, two managers, one person, and each manager is looking at a pattern that is perfectly compliant on its own.
The period, which is the whole argument
Where a maximum is measured over an averaging period, the constraint stops being about any one week and becomes a running total. A rota that is fine in isolation can be the week that tips a quarter.
Whoever builds the rota needs the running total in front of them, not the week. Most systems can show this and most are configured to show the week, because the week is what the rota view is about.
Who is actually at risk
Not the people working the most hours in a typical week. The people whose hours vary most: bank staff, those covering a vacancy, those who took on a temporary secondment while keeping part of their old pattern.
Variability is the signal, not the level, and a list sorted by the variation in weekly hours finds the people the compliance report misses.
The conversation about voluntary extra hours
Where additional hours are offered and accepted, the constraint is usually still a constraint, however willingly the extra shifts are taken. Who may agree to what, and how, differ by jurisdiction.
The operational point is to stop running two accounting systems. If the extra shifts are being recorded somewhere other than the rota, the rota is not a record of what anybody is working, and nothing built on it can be relied on.
What to show the person
Their own running total, at the point of being offered an extra shift. Not a policy reminder, a number: this is your total for the period, this shift would take it here.
That single change removes most of the problem, because the person usually knows their own circumstances better than the rota does and will decline when the number is in front of them.
What it means for building the pattern
A pattern should have slack against the maximum for the people most likely to pick up extra work, which usually means designing the base pattern a little lighter for that group rather than tighter.
Patterns built to the edge leave no room for the thing that always happens, and the thing that always happens is somebody covering a vacancy for four months.
The report that would catch it
One line per person, per period: planned hours, additional hours, total, and the limit that applies to them. Sorted by how close the total is to the limit.
That report takes an hour to build once and almost nobody has it, because the available reports are organised by shift and by cost centre rather than by person.
What to write down
Which maximum applies to which group, over what period, where the running total lives, and who checks it. Four lines on the constraint register.
The fourth is the one that matters in practice: a constraint measured over a quarter with nobody named as checking it is being measured by nobody, and the first anybody knows is at the end of the quarter.