Consecutive Days
The longest run anybody has worked is a number every organisation can produce in one query and almost none has ever looked at.
Consecutive working days, one department, longest run per person over eight weeks
18 weeks · limit 7 · average 7.0
Three people in this department worked runs of eleven days or more. All three were covering the same two vacancies. None of it appeared in any report, because every one of those weeks was inside the hours limit.
Consecutive working days is the simplest fatigue measure available and the one organisations are least likely to monitor. It requires no reference period, no definition of what counts, and no decision about averaging. It is a count.
The rest problem in “Consecutive Days” often appears between systems: the rota shows the planned shift while the time record shows what actually happened. For organisations researching step rate compensation, view the solution can provide time and project context, provided call-outs, swaps and corrections remain visible to a responsible manager.
It is also the measure that corresponds most directly to how people experience a demanding period. Nobody says they worked forty-nine point two hours a week; they say they worked eleven days straight.
For an independent reference relevant to “Consecutive Days”, consult the ISO management-system resources. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.
Why it is not covered by the hours limits
Because the hours limits are about totals and this is about distribution. Eleven days of seven hours is seventy-seven hours over a fortnight, which averages below most limits.
So an organisation monitoring hours diligently can have people working runs that any supervisor would recognise as excessive, with every report green. The two measures are independent and both are needed.
Where long runs come from
Vacancies, almost always. A department running two people short covers the gap with the people it has, and the same willing individuals absorb it.
Also: a person who wants the money and keeps saying yes. A rota built a week at a time, so the boundary is never examined. Swaps that extend a run without anybody counting. And absence, where cover is arranged shift by shift with no view of what the covering person has already worked.
The query
For each person, over a rolling window, the longest unbroken sequence of days with any recorded work. Sorted descending.
It is a handful of lines against the attendance data and it needs no configuration decisions. An organisation with no working time monitoring at all could implement this one in an afternoon and have something genuinely useful by the end of the week.
What number to worry at
That is a judgement rather than a rule in most regimes, which is why it has to be the organisation's own. Seven consecutive days is a common line in agreements; some sectors work to shorter, and some patterns legitimately run longer with compensating rest afterwards.
Pick a number, write it down, and make exceeding it something that requires a named person to approve rather than something that happens. The approval is the mechanism; the number mostly serves to trigger it.
The people at the top of the list
They are nearly always the same few names, quarter after quarter. That recurrence is the finding.
A person who appears repeatedly is either holding a skill nobody else has, covering a vacancy that has not been filled, or unable to decline for a reason worth understanding. All three are management problems with management answers, and none of them is solved by a conversation with the individual about their hours.
The run that crosses a rest day in name only
Watch for the pattern where a nominal rest day contains a call-out, a few hours of cover, or a required training session. The day appears as a break in the sequence and was not one.
A run computed from days with any recorded work catches this correctly. A run computed from rostered rest days does not, and the difference between the two is exactly the population most likely to be exhausted.
Linking it to the rest rules
A long consecutive run frequently also breaches weekly rest, particularly where the fortnightly averaging provision described elsewhere in this section has been used without anybody realising.
Running the two checks together — longest run, and weekly rest periods actually taken — produces a short list of people for whom both are true. That list is the organisation's real fatigue exposure, it is usually fewer than a dozen names, and it is actionable in a way that an aggregate compliance percentage never is.
What to do with the first run of the report
Resist the temptation to send it to department heads as a performance item. The runs were worked to cover the organisation's own gaps, usually by its most reliable people, and framing it as a failing lands exactly wrong.
Send it with the vacancy figures beside it. Presented that way the conversation is about establishment and cover arrangements, which is where it belongs, and the people at the top of the list are correctly identified as the ones who have been carrying something rather than the ones doing something wrong.
The run that is somebody's own choice
Some long runs are requested. A person working a block of days to get a block of days off is a common and sensible arrangement, and treating it as a problem will not be understood.
The distinction worth drawing is between a run the person asked for and one the rota produced. Recording which, at the point the pattern is approved, separates the two in the report and means the list of concerning runs is short and genuinely concerning rather than full of people who are perfectly happy.