Requests to Refuse

A time-theft concern produces requests quickly, usually from someone frustrated rather than malicious.

"Install monitoring on the remote team"

Why to refuse: it measures keyboard input, not work, and it is gamed by anyone who wants to. The concern is output visibility, which it does not address.

Offer instead: shared plans, written updates, shorter cycles.

"Pull a year of her records and see what turns up"

Why to refuse: browsing without a defined scope is disproportionate and converts a sound concern into something that looks like a search for a reason.

Offer instead: a defined scope, a recorded authorisation, and the four system checks first.

"Dock the minutes"

Why to refuse: without a contractual right it is an unlawful deduction in many jurisdictions, and for system failures it is unlawful almost everywhere.

Offer instead: address the cause, then the ordinary process if a pattern persists.

"Put a fingerprint reader on the door"

Why to refuse: biometric data with a higher legal bar, restricted in several jurisdictions, and disproportionate where a photograph or a supervisor would serve.

Offer instead: state the proportionality argument first. If it cannot be stated, that is the answer.

"Set an automatic warning after three anomalies"

Why to refuse: anomalies include terminal faults, queues and forgotten clock-outs. An automatic consequence built on that will fire at people who did nothing.

Offer instead: a threshold that prompts a human check, starting with the site.

"Call it theft in the letter"

Why to refuse: it implies dishonesty, which is a higher bar and affects the person's future employment. For a few minutes it is inaccurate and will be challenged.

Offer instead: describe the conduct.

"Don't tell them we're looking"

Why to refuse: covert monitoring is an exception requiring specific justification, not a default, and one deployed without it is usually unusable as evidence anyway.

Offer instead: the overt question, which resolves most of these in the first conversation.

What not to help improve

Making surveillance less noticeable. Making a deduction harder to spot. Framing an automatic trigger as a human review when it is not.

None is a partial improvement.

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.

Decide who decides

Before the first request arrives.

Name the person or forum that rules on exceptions.

Name what evidence an exception requires.

Agree it with whoever owns risk.

Publish it internally, so a requester meets a process rather than one person's judgement.

The first decision becomes the precedent whether or not anyone intended it to.

Follow the difficult record

Use the booking workflow example to frame one representative case. The useful evidence is the record created when a value is corrected, approved and exported.