Requests to Refuse

A working system attracts requests. Some would cost the accuracy the whole thing depends on, and the answer is easier if it was decided in advance.

"Turn on the screenshot feature"

Why to refuse: no recording purpose requires it, it captures confidential and personal content indiscriminately, and a less intrusive method for measuring duration plainly exists.

Offer instead: prompt recording and a contemporaneous record, which is what a client or a manager actually wants.

"Deduct idle time automatically"

Why to refuse: it removes pay for time that may have been worked, without the person's input.

Offer instead: prompt the person to classify the gap.

"Let managers adjust hours without the worker seeing"

Why to refuse: a record the subject cannot see changed is the employer's assertion rather than a record, and in a dispute it is worthless.

Offer instead: visible, logged, disputable edits.

"Estimate the missing entries for us"

Why to refuse: an estimate that becomes someone's pay without their knowledge is the single most common source of grievance here.

Offer instead: contact the person, record what they say, mark the entry as retrospective.

"Keep everything indefinitely"

Why to refuse: excess retention is a failure in its own right, and it enlarges every subject access request and every breach.

Offer instead: retention per category and jurisdiction, with a hold mechanism for specific matters.

"Give me the report comparing individuals"

Why to refuse: the data does not support it, and the comparison measures the work assigned rather than the person. Once people believe it is used this way, the records change.

Offer instead: team capacity against commitments, and a conversation with anyone who appears to be struggling.

"Just let the vendor configure it"

Why to refuse: whoever configures it during implementation is not who configures it for the next three years.

Offer instead: their help alongside your administrator doing the work, which is also how the runbook gets written.

What not to help improve

Making a deduction less noticeable. Making manager edits harder to spot. Making an activity score more persuasive.

None is a partial improvement. A better version of the thing is still the thing.

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 rather than argued again.

Decide who decides, in advance

The arrangement that keeps a refusal from being one person's judgement under pressure.

Name the person or forum that rules on exceptions.

Name what evidence an exception requires.

Agree it before anything is asked.

Publish it internally, so a requester meets a process rather than an obstacle.

Record every decision, because the first becomes the precedent whether or not anyone intended it to.

Answering the real concern

Almost every request has a reasonable question behind it.

"Turn on screenshots" is usually "the client queried the bill", answered by prompt recording and specific narratives.

"Deduct idle time" is usually "we think hours are inflated", answered by looking at the work.

"Compare individuals" is usually "do we have capacity", answered at team level.

"Keep everything" is usually "we lost something once", answered by a hold mechanism.

Offering the real answer turns a refusal into a consultation.

Do not connect data without purpose

A form or lead tool may expose more fields than time reporting needs. Review the documented example and refuse transfers without a named operational use.