When the Working Day Actually Starts
Where the paid shift begins when the work before it is required, the difference between arriving and starting, and how to find the minutes nobody is claiming.
Minutes before the scheduled start, recorded against worked, one team, one week
Not claimed by anybody and not usually work.
Four minutes each morning, five people.
Issued from a cage that opens at the hour.
Expected, attended, never recorded.
Required before the shift can run.
The scheduled start itself.
Two hours and five minutes across one small team in one week, all of it before the paid shift started. Whether each of these is working time differs by jurisdiction and by the facts; this is one employer's own reconstruction.
The paid shift starts when the employer requires something of the employee, not when the schedule says the shift begins. If somebody has to collect equipment, start a machine, take a handover or queue for a terminal before they can begin, those minutes are doing work for the employer — and in most organisations none of them is recorded anywhere.
The time question in “When the Working Day Actually Starts” is easier to resolve when actual work, scheduled time and later corrections remain distinguishable. A team assessing this time-recording resource for employee monitoring for performance reviews can use its project and time records as operational evidence, while local rules, employee explanations and accountable review still determine what must be paid.
This is the largest single source of unpaid time in the places that have it, and it is invisible precisely because nothing is being deducted. Nothing goes missing from a record; the record simply starts later than the work did.
For an independent reference relevant to “When the Working Day Actually Starts”, consult the Cloudflare zero-trust overview. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.
Required is the word that does the work
The question is not whether somebody was on the premises or whether they were being useful. It is whether the employer required the activity, or whether the activity is so closely tied to the work that it cannot sensibly be separated from it.
Where that line falls differs by jurisdiction and has moved in several of them. It is a question for somebody qualified in the place concerned. What does not differ is the operational step: list what people actually have to do before they can start, and ask of each one whether it is required.
What to look for
- Collecting tools, keys, radios, a vehicle or a device from a store that opens at a fixed time.
- Taking a handover from the outgoing shift.
- Starting, warming up or checking equipment.
- Security screening, sign-in or a health check.
- Queueing at a terminal where only one exists for a large team.
- Reading messages or a briefing that the employer expects to have been read.
The last two are the ones organisations resist, and they are also the easiest to measure: the terminal logs show the queue, and the briefing system shows when it was opened.
Arriving early is not the same thing
Somebody who arrives twenty minutes early to have coffee is not working, and treating every early arrival as paid time is both wrong and unaffordable. The distinction is whether the employer required it.
That is why the fix is rarely "pay from the badge-in". It is to identify which required activities happen before the scheduled start, and either move the scheduled start earlier or record those activities properly.
Finding the minutes
- Stand at the start of a shift and watch what people do, for three days.
- Ask five employees to describe their first fifteen minutes, separately.
- Compare the terminal timestamps with the scheduled start times, in aggregate.
- Look at who opens the equipment store, and when.
- Check whether the handover is on anybody's schedule at all.
- Write down each activity, who requires it, and roughly how long it takes.
Step two produces better information than any system. People describe their morning accurately and without resentment when they are not being asked to justify it.
The honest responses
There are three, and all of them are legitimate. Move the scheduled start earlier, so that the required activity sits inside the paid shift. Remove the requirement, by issuing equipment at the end of the previous shift or putting the handover inside the shift. Or pay for it as recorded time.
What is not legitimate is the fourth option, which is what usually happens: continue to require it, continue not to pay for it, and rely on nobody raising it.
The aggregate is the argument
Five minutes a day sounds like nothing, and that is why it survives. Five minutes a day across forty people for a year is roughly five hundred hours, which is a quarter of a role and considerably more than the cost of fixing the schedule.
Computing that figure is the single most effective way to get the problem looked at, because it converts something that reads as pedantry into a line somebody recognises.
The person who opens up
Somebody has to unlock the building, disarm the alarm, switch on the lights and open the equipment store, and that person starts earlier than everybody else by necessity rather than by choice.
In small operations this is frequently a supervisor on a salary, and the extra twenty minutes a day vanishes into the salary without anybody calling it anything. In larger ones it rotates, which makes it visible in the rota and therefore fixable. The first case is the one worth looking for, because nothing in any system will surface it.
The record of each decision
For each required pre-shift activity: what it is, who requires it, how long it takes, and what was decided. Three lines each.
That record is what makes the decision defensible and what stops it quietly reverting when a shift pattern changes. A schedule moved earlier in March drifts back in September unless somebody wrote down why it moved, and the drift is nobody's decision — which is the pattern this whole collection is about.