What Gets Asked For

Requests about working time come from four directions: a regulator, a union or safety representative, an individual in a dispute, and occasionally a client auditing a supplier.

The workflow in “What Gets Asked For” becomes more reliable when scheduled hours, actual time and later corrections can be distinguished. For teams exploring ethical employee monitoring, ethical employee monitoring can add operational time and project context, provided data collection is proportionate, permissions are limited and every important exception receives human review.

They ask for overlapping things. Five of the seven can be produced on the day from systems the organisation already has. Two cannot be produced at all unless they already exist, and those are the ones worth attending to now.

For an independent reference relevant to “What Gets Asked For”, consult the official Scrum Guide. 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.

One: the hours

Records of hours worked for named individuals over a stated period. Every organisation can produce something here.

What distinguishes a good answer is whether the figure includes the categories that count and whether that is stated. A set of time-clock totals presented as working time, without a note that travel and on-call are excluded, is an answer that will not survive the second question.

Two: the averages

The rolling average for those individuals over the reference period, as computed at the time.

This is the first of the two that cannot be produced retrospectively with full credibility. A figure recomputed today is arithmetic; a stored contemporaneous series is a record of what the organisation knew.

Three: the rest position

Daily and weekly rest for the period, which means shift-level timestamps. Where the detail has been purged, this cannot be answered at all.

Four: the opt-out agreements and the register

Named documents in most regimes. Either they exist with dates or they do not, and this is the second thing that cannot be created after the fact.

Five: night workers and their assessments

The list of night workers, the date each met the definition, and evidence that a health assessment was offered.

The list can be generated retrospectively from the hours data. The evidence of the offer cannot, and its absence is a clean finding.

Six: the policy as it stood

What people were told, in the version current at the relevant time. Intranet pages get overwritten; dated copies have to have been kept.

Seven: what you did when somebody approached a limit

Not a specified record in most regimes, and the most persuasive thing an organisation can produce. A report showing the position, an action taken, and a rota changed demonstrates a functioning system in a way no policy document does.

The order they arrive in

A regulator usually starts with the policy and the opt-outs, because they are documents, then moves to the hours and the rest for a sample of people.

A representative usually starts with the hours for a specific group and moves to the averages. An individual in a dispute starts with their own records and the amendments to them. A client auditor starts with the policy and the register.

All four converge on the same two questions: can you show the figure, and can you show what you did about it.

Preparing without a project

Three things, none of which takes more than a day.

Start keeping dated copies of the policy and the notice, from now. Switch on the audit trail and the shift-level retention, from now. And start storing the computed averages weekly, from now.

Everything else on the list is an export. Those three are the only items where today's decision determines whether the answer exists in two years, and all three cost configuration rather than money.

What a good position looks like

An organisation that says: here is the hours figure and here is what it includes and excludes; here is the stored average series; here is the rest report; here are the agreements with dates; here is the night worker list and the assessment offers; here is the policy as it stood; and here are the twenty-three occasions last year when we changed a rota because somebody was approaching a limit.

That last item is the one that changes the character of the conversation, and it is the one no regime requires.

Who answers the first question

These requests arrive at whoever is nearest — a site manager, a payroll clerk, a supervisor — and the first answer shapes everything afterwards.

Name in advance who handles each kind and tell the people likely to receive one. The failure mode is not refusing to answer; it is answering helpfully and inaccurately in the first hour, which then has to be corrected, and a correction is heard as a retraction whatever its content.