How to Decline a Request

Someone will ask for one of the things in the refusal note, usually with a real frustration behind it.

What does not work

Expressing discomfort, which reads as squeamishness and invites someone else to be asked.

Citing policy without explaining it, which invites a request to change the policy.

A flat no with no alternative, which gets routed around.

Overstating the legal position, which is checked and discredits the accurate parts.

Name the reason that lands

For a commercial audience: the exposure runs the other way. An unlawful deduction or unpaid working time claim has a statutory basis and years of limitation; a break overrun does not.

For an operational audience: the records degrade. People stop reporting faults, absorb minutes quietly, and the data you are relying on stops describing arrivals.

For a people audience: a workforce that believes it is being policed stops giving the informal minutes that were absorbing the overruns, and the net position worsens.

All three are true. Lead with the one that will be heard.

Answer the concern underneath

"People are taking liberties" — measure it. The number is usually small and the causes usually structural.

"Someone punched in for a friend" — that is a real case, and the four tests establish it properly.

"The remote team might not be working" — an output visibility problem, answered by visible work rather than by monitoring.

"We are losing money" — run both columns. It frequently turns out to be true in the other direction.

Offering the real answer turns a refusal into a consultation.

Where not to help improve

Making surveillance less noticeable. Making a deduction harder to spot. Presenting an automatic trigger as human review.

None is a partial improvement, and saying so explicitly is better than leaving it implied.

Recording it

What was asked, by whom, when. What was declined and why. What was offered instead. Who decided.

Findable, so the second identical request is answered by reference.

If overruled

Say so to the people affected, which is honest and preserves what trust remains.

Insist on the mitigations: notice, a fair process, payment for system failures, a route to challenge.

Record your position in writing, dated.

Prepare the position in advance

Written before it is requested.

The categories you will not do, with the reason for each.

Who decides on an exception.

Agreed with whoever owns risk, before anyone asks.

Deciding calmly is much easier than inventing it during a week when someone is frustrated about one person's punches.

A practical configuration prompt

During configuration, use a boundary-testing reference to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.