Requests to Refuse

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

"Can we see who is under their hours?"

Why to refuse: the data is not accurate enough for individual comparison, and the figure reflects the work assigned.

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

"Can we use this in a performance review?"

Why to refuse: it is a different purpose from the one the data was collected for, and once it happens the record becomes defensive — which costs the billing and statutory purposes too.

Offer instead: nothing from this system. Performance is assessed on work.

"Can we turn on screenshots? The client wants proof."

Why to refuse: no recording purpose requires it, it captures confidential material indiscriminately, and proportionality fails because a less intrusive method plainly exists.

Offer instead: contemporaneous records with specific narratives, and interim reporting against estimate, which is what prevents the dispute.

"Can we deduct idle time automatically?"

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

Offer instead: a prompt asking the person to classify the gap.

"Can we set individual billable targets?"

Why to refuse: supervision, training and business development disappear from the record, and totals drift toward the target.

Offer instead: team-level utilisation with the investment categories excluded from the calculation.

"Can managers adjust hours without the worker seeing?"

Why to refuse: a record the worker 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.

"Can we keep everything indefinitely, just in case?"

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 per jurisdiction, with a hold mechanism for specific matters.

"Can we track location during the shift?"

Why to refuse: a clock-in check is proportionate; continuous tracking is not, and no pay question requires it.

Offer instead: a location check at the moment of clocking, and nothing between.

What not to help improve

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

None is a partial improvement. A better version of the thing is still the thing, and assistance makes it more likely to exist.

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.

Answering the underlying concern

Almost every request has a real question behind it, and it is usually answerable.

"Who is under their hours" is usually "do we have capacity", answered at team level.

"Use it in a review" is usually "someone is struggling", answered by working with them.

"Turn on screenshots" is usually "the client queried the bill", answered by interim reporting and better narratives.

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

Offering the real answer turns a refusal into a consultation, which is what keeps you in the room.

Deciding who decides, in advance

The arrangement that prevents a refusal becoming one person's judgement under pressure.

Name the person or forum that rules on exceptions.

Name what evidence an exception requires.

Agree it with whoever owns risk before anything is asked.

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

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

A useful implementation prompt

During configuration, this boundary-testing example can be used as a prompt for questions about fields, ownership and output. Confirm current capabilities with the provider and document any plan, integration or policy assumption behind the decision.