Who Is Told, and Who Is Not

The report described in the previous note contains names, hours and a state. Who receives it determines whether it changes rotas or changes how people are regarded.

The workflow in “Who Is Told, and Who Is Not” becomes more reliable when scheduled hours, actual time and later corrections can be distinguished. For teams exploring employment of relatives policy, employment of relatives policy with accountable controls can add operational time and project context, provided data collection is proportionate, permissions are limited and every important exception receives human review.

The distribution list is a decision worth making deliberately, because the default — circulate it widely so everybody is aware — reliably produces the second outcome.

For an independent reference relevant to “Who Is Told, and Who Is Not”, consult the Employment New Zealand recordkeeping guidance. 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.

Who needs it

The person building the rota, weekly, filtered to those near a limit. They are the only person whose decisions it can change.

The individual, when they are the subject of it. Their hours are theirs, and they frequently know something the system does not.

Whoever owns working time compliance, monthly, in aggregate and in detail. That is the governance view.

Who does not need it

Other departments. The senior management team, except in aggregate. Anybody who will read it as a list of people working hard, which is how it reads to anybody without the context.

The problem is not confidentiality in a formal sense. It is that the list is easily read as a performance artefact — these people are overcommitted, this manager cannot control their rota — and once it is read that way the incentive to keep the figures accurate disappears.

Telling the individual well

Short, factual, and with a proposal rather than a question. Your average is at forty-six against a limit of forty-eight; on your current rota you cross it in two weeks; we are going to move two shifts.

Not: would you mind working less. Most people near a limit want the hours, and asking them to choose puts a legal constraint on the person least able to absorb it.

What the person might tell you back

That they have a second job. That they are picking up shifts at another site. That the rostered pattern is not what they actually work. That they are about to take leave, which changes the projection entirely.

All four are things the system does not know, and all four come out in a two-minute conversation. That is a substantial part of the value of talking to the individual at all, and it is lost if the conversation is only ever an instruction.

The aggregate that goes upwards

A count by department, a trend over months, and the number of rota changes made for working time reasons.

That view answers the question senior management should be asking, which is whether the organisation is structurally dependent on hours near the limits. It does so without naming anybody, which keeps the reporting honest further down.

When somebody outside the list needs to know

A health and safety representative or a union representative asking about hours is entitled to a serious answer, and the aggregate is usually the right form for it.

Refusing to discuss it is a poor position, because the information exists, it concerns people's working conditions, and the request will not go away. Sharing the aggregate and the methodology, while keeping individual lines to the people who need them, is both defensible and straightforward.

The thing that destroys it

Using the report in a performance conversation with a manager whose department appears on it.

It will have been built from the organisation's own vacancies and its own demand pattern. Treating it as a management failing produces, within one cycle, either fewer hours recorded or more hours recorded somewhere the report cannot see, and both are worse than the problem.

The line at the top of every version

Something like: this report identifies where the organisation's own scheduling is approaching a legal limit, so that it can be changed before it is reached. It is not a measure of individual or departmental performance.

One sentence, on every copy. It sounds like boilerplate and it does real work, because it tells each new reader what the document is for before they decide for themselves.

The copy that gets forwarded

A report sent to three people arrives, within a month, at a dozen, because somebody forwards it to make a point about cover. Nothing stops that and it is worth anticipating.

The protection is the framing line at the top and the absence of anything that reads as a ranking. A document that explains its own purpose in its first sentence survives being forwarded; one that is a bare table of names and hours acquires whatever meaning the person forwarding it wants it to have.