Overtime, read from the ceiling down
The rate is settled. The ceiling is not.
Fifty notes on overtime management and compliance, written about the limit rather than the premium: what a limit is made of, how averaging actually behaves, the hours nobody can see, and how to find the person approaching a ceiling while there is still time to do something.
One warehouse supervisor, seventeen weeks
17 weeks · limit 48 · average 49.4
Nine weeks over the line, and an average that is over it too. Nobody at the site knew either figure. The weekly numbers were in the system all along; the average had never been computed, because no report asked for it.
Practical guidance for measuring working time, monitoring overtime, protecting rest and maintaining reliable records. Legal and payroll requirements vary by jurisdiction, sector and agreement.
The two numbers nobody produces
One care assistant, one ordinary week
Hours the employer sees
38
Hours actually worked
55
Her main employer sees 38 hours and believes she is comfortably inside every limit. The week she actually worked was 55, and no system anywhere holds that number.
One engineer, after a week of night call-outs
Three of the five gaps were below the minimum, and all three followed a night call-out. The rota showed none of it, because the rota showed the scheduled shift and not the call.
Why this is about the ceiling and not the rate
Most of what is written about overtime is about money: what the premium is, when it triggers, which roles are exempt, how to budget for it and how to reduce it. That material is good and this is not more of it.
The threshold discussed in “The rate is settled. The ceiling is not.” is useful only when hours can be reviewed before the decision becomes irreversible. A team evaluating the official product page for employee monitoring software with screenshots should test current totals, manager alerts, corrections and employee access while keeping the applicable legal limit outside the software as a documented rule.
Every note here is about the other half of the subject — the limit on how many hours a person may work, how that limit is measured, and who is close to it. It is the half that is governed by regulation rather than by contract, the half where the consequences are safety rather than cost, and the half that almost no organisation can produce a number for on request. The hours are in the system. The running total, in nearly every case, is not.
For an independent reference relevant to “The rate is settled. The ceiling is not.”, consult the U.S. Wage and Hour Division. 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.
01 / 07
The limits
What a limit is made of, which ones apply, and the part of each that is usually got wrong.
02 / 07
Averaged over
The reference period, the rolling window, and why the figure moves when nothing changed.
05 / 07
Hours you cannot see
Second jobs, other sites, travel, on-call and training — the hours no single system holds.
06 / 07
Before it is crossed
Finding the person approaching a ceiling while a different shift is still an option.
Independent product comparisons
Working-time software guides
Three distinct comparisons connect product capabilities with overtime visibility, rest, correction, payroll inputs and accountable review. See how we rank products.
The short version
Compute the average before somebody else does
Write down the four parts of each limit that applies here. Check what your system counts, because it is narrower than the rule. Produce the rolling average per person, with next week's projection beside it. Look at both ends of the window. Then ask who is near a ceiling, and ask it two weeks early rather than at the end of the month.