How to Decline a Request

Someone will ask for something in the previous note, usually with a reasonable concern behind it. How that conversation goes determines both the outcome and whether you are consulted next time.

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.

What works

Name the reason that will land with this audience.

For a commercial audience: legal exposure and the cost of a wage claim, plus the reputational position on screen monitoring.

For an operational audience: the data will stop being accurate, and the accuracy is what the billing and the statutory record depend on.

For a people audience: turnover and the effect on the people who do the unbillable work everything rests on.

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

Answer the underlying question

Almost every request has a real concern that is answerable.

"I want to know people are working" — remote visibility problem. Answered by visible outputs and shorter cycles, not by watching.

"This project is losing money" — a costing question. Answered by effort by project including unbilled, and by the write-off analysis.

"Someone is not pulling their weight" — a management observation. Answered by working with the person, and the timesheet would give the wrong answer anyway.

"The client disputes our hours" — answered by contemporaneous recording and better narratives, not by screenshots.

Offering the real answer is what turns a refusal into a consultation.

Where not to help improve

Some requests should be declined rather than refined.

Making idle deduction less noticeable, making an activity percentage more persuasive, making covert monitoring quieter — none is a partial improvement. A better version of the thing is still the thing.

Say that explicitly rather than leaving it implicit.

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.

Reviewed annually, because circumstances change — which is different from being overturned under pressure.

If overruled

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

Insist on the mitigations you would have required anyway: notice, consultation where required, a purpose limitation in writing, worker access to their own record, a retention period, a route to dispute.

Record your position in writing, dated.

Decide in advance what you would decline to implement personally, because deciding that under pressure produces the wrong answer.

Preparing the position in advance

Written before it is requested, a refusal becomes a reference rather than a negotiation.

State the categories you will not build, with the reason for each.

Name who decides on an exception.

Name what evidence an exception would require.

Agree it with whoever owns risk, before anyone asks.

Publish it internally, so a requester encounters a policy rather than one person's judgement.

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

Naming the reason that lands

The same refusal, framed three ways, for three audiences.

Commercial: legal exposure, the cost of a wage claim, the reputational position on screen monitoring.

Operational: the data stops being accurate, and accuracy is what billing and the statutory record depend on.

People: turnover, and the effect on whoever does the unbillable work everything rests on.

All three are true.

Lead with the one that will be heard, and have the other two ready.

Check the difficult case

Use see this implementation example to frame one representative test for this issue. The useful evidence is not the marketing description itself but the record created when a worker corrects an entry, a manager reviews it and an administrator exports it.