Required, Expected, or Just Sensible
Whether an activity around the edge of a shift is paid turns on who demanded it. The three categories look identical from outside and are decided very differently.
One warehouse, the first twenty minutes
| What happens | Required by | Paid? |
|---|---|---|
| Changing into mandatory PPE | Employer, written rule | Contested |
| Queuing at the security search | Employer, on exit and entry | Contested |
| Walking from the gate to the floor | Site layout | Not paid |
| Pre-shift briefing | Supervisor, every day | Paid |
| Arriving ten minutes early out of habit | Nobody | Not paid |
The two contested lines are the ones the organisation has never decided. They are also the two largest by duration.
The activity at the edge of a shift falls into three groups, and which group it is in decides nearly everything. The trouble is that all three look the same from the car park.
The practical lesson in “Required, Expected, or Just Sensible” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring tips to increase productivity, tips to increase productivity can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
Something the employer requires. Something the employer expects without having said so. And something the worker does because it is sensible, convenient, or habit.
For a separate benchmark relevant to “Required, Expected, or Just Sensible”, consult the GAO Government Auditing Standards. 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.
Required
A written rule, a procedure, an instruction, a condition of the job. Mandatory protective equipment. A security search. A vehicle check before driving. A handover that cannot be skipped. Signing in to a system before the queue opens.
In most jurisdictions, time spent on activity the employer requires, at a place the employer specifies, is working time, and whether a clock recorded it is not the test. This is the category that generates back-pay liabilities, and it is the one organisations most often misclassify as the third.
Expected
Nobody wrote it down and everybody does it. Arriving ten minutes early because the supervisor notices. Starting the machine warming before the shift because otherwise the first hour is wasted. Reading the overnight notes before the handover meeting.
This is the hardest category and the most common. In practice the test applied is whether the person could decline without consequence, and the answer is usually no — which pulls it towards the first category whatever the paperwork says.
An expectation that has been running for years, that everybody follows, and that would cause a problem if stopped, is a requirement that nobody has written down.
Sensible
Arriving early to get a good parking space. Having a coffee. Chatting before the shift. Changing out of outdoor clothes into ordinary ones.
Genuinely the worker's own time, genuinely unpaid, and not controversial. The only risk here is that an employer classifies the first two categories into this one by assertion.
Sorting your own
List what happens between arrival and the punch, from observation rather than from the procedure. Ten minutes at the gate produces the list.
Against each, ask who requires it and where that is written. The answers divide into "there is a rule", "there is no rule but it would be a problem not to", and "nothing would happen".
Expect the middle group to be the largest and to contain the activities with the longest durations. That is the finding, and it is normally a surprise to the people who wrote the procedures.
What to do with the middle group
Decide, rather than leaving it. Either the activity is required, in which case it is inside the paid day and the clock or the shift pattern should reflect that. Or it genuinely is not, in which case somebody has to say so, mean it, and stop the informal expectation.
The second half is the part that fails. An employer that declares the pre-shift briefing optional and then holds it every morning with the supervisor taking note of who is there has not made it optional; it has created a written record contradicted by its own practice, which is worse than before.
The test that settles most of them
Where a line is genuinely unclear, the question that resolves it fastest is not legal. It is: what would happen if the person simply did not do it, and arrived at their machine at the start of the shift having skipped it.
If the answer is that the work could not proceed, or that somebody would say something, the activity is required. If the answer is nothing at all, it is not. Supervisors can answer this in seconds for every item on the list, and their answers are usually more accurate than the procedure, because they are describing what actually happens rather than what was written when the site opened.
Writing it down
One page per site: the activities at the edge, how long each takes, who requires it, and whether it is inside the paid day.
It is the document an inspector asks for, it is the document that settles a dispute in an afternoon rather than a year, and in most organisations it does not exist. Producing it also forces the sorting exercise above, which is where the actual decisions get made.