Waiting for Work
A person on site with nothing to do is being paid for, and some arrangements try to stop paying. That is where the clock gets used for something it should not be.
Idle time, four arrangements
| What happens | Required by | Paid? |
|---|---|---|
| Machine down, operator waiting on site | Breakdown | Paid |
| No deliveries booked, driver in the yard | Demand | Paid |
| Sent home, told to come back at two | Employer | Contested |
| Asked to clock out and stay available | Employer | Contested |
The last line is the one to remove. Clocking out while remaining required is the arrangement that converts a pay question into a records problem.
Work is not evenly distributed through a shift. A machine breaks, a delivery is late, a ward is quiet, a queue of customers does not materialise. The person is there and there is nothing for them to do.
The practical lesson in “Waiting for Work” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring remote employee productivity monitoring, this product guide can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
In an ordinary arrangement they are paid, because they are at work and available, and the risk of there being no work sits with the employer. The interesting cases are the ones where somebody tries to move that risk.
For a separate benchmark relevant to “Waiting for Work”, consult the HSE work-related stress guidance. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.
The default position
A worker present at the workplace, at the employer's direction, ready to work, is generally working whether or not work is available. The employer carries the risk of under-utilisation because the employer controls the scheduling.
This is well settled and most arrangements follow it without thinking about it. The exceptions are where the pressure shows.
The arrangements that test it
Send home early, unpaid. Lawful in some contracts and jurisdictions and not others, frequently subject to a guaranteed minimum payment for having attended. The common failure is doing it without checking what the contract says.
Send home and call back. A split day created at short notice. Rarely permitted without an agreement and almost always resented, because it consumes the whole day for part of the pay.
Ask to clock out and stay on site. The worst version and the most common. The person remains available, remains subject to direction, and has no record of being there. Everything in this collection about unrecorded presence applies, and the person is also now outside the site's own arrangements for people on the premises.
Reclassify the time as a break. Converting idle time into the rostered break, after the fact, so the deduction covers it. It is also usually not a valid break, because the person could be recalled at any moment.
Why the fourth is a trap
A break must generally be uninterrupted and the person must be free of obligation. Idle time during which the person must remain ready is neither, so the reclassification does not discharge the break duty — which means the organisation now owes both the idle time and a proper break.
It is a common move in retail and hospitality and it tends to produce a worse outcome than paying the idle time would have.
Recording it properly
A code for it. Downtime, waiting, no work available — whatever the operation calls it, recorded against the shift rather than hidden.
Doing that costs nothing in pay, because the time is being paid either way, and it produces the operational number: how much paid time is spent waiting, by cause.
That figure is the argument for fixing the cause. A line that is down four hours a week is a maintenance case; a yard with drivers waiting is a booking case. Both are invisible while the time is simply absorbed into the shift.
The other direction
Some operations run the opposite error: recording idle time so carefully that it becomes a stick. A person whose waiting time is reported to them weekly, with no ability to influence it, is being measured on the scheduler's performance.
Keep the measure at the level of the cause. Downtime by line, by depot, by shift — not by person.
Annualised and flexible arrangements
Where hours are averaged over a period, idle time may legitimately be managed by sending people home against banked hours. That is a different arrangement with its own rules and it has to be agreed in advance, in writing, with a defined reference period.
What it is not is a retrospective justification for an unpaid afternoon. The agreement has to exist before the quiet day, not after it.
The check
Ask what happens when there is no work. The answer will be immediate and specific, and it will frequently describe one of the four arrangements above without using any of those words.
Then ask what the record shows for those hours. If the answer is nothing, that is the finding.
Who gets sent home
Where there is discretion about who waits and who is released, the pattern is worth watching. It falls on agency staff, newer people, part-timers and whoever is easiest to send away, and that is a distribution the organisation has not decided and may not be able to defend.
Recording who was released early, by contract type, converts an informal daily decision into a visible one. On most sites the figure is lopsided, nobody intended it, and making it visible is enough to change it.