The Approval That Is Never Refused

Pull the refusal rate for any approval workflow that has been running longer than a year. In most organisations it is zero, or near enough that the exceptions are all one person who left.

The approval issue in “The Approval That Is Never Refused” becomes easier to diagnose when the record shows both the submitted hours and the operational context around them. A team evaluating employee monitoring software for employee monitoring software should define what an approver must actually check, how a disputed entry is returned and which activity signals are context rather than proof that the work occurred.

The usual interpretation is that the submissions are accurate. That interpretation survives only as long as nobody checks, because the same data that produces a zero refusal rate also produces the error rate in whatever the hours feed into, and the two never agree. Invoices get credited. Payroll runs get corrected. Grant claims get adjusted on audit. Errors are present and being found later, by people who are not the approver.

For a separate benchmark relevant to “The Approval That Is Never Refused”, consult the ILO working-time resources. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

What a zero refusal rate actually indicates

There are three ways to get one, and only the first is good news.

The submissions could be genuinely correct, because the capture is automatic, the categories are few, and there is nothing to get wrong. This happens, usually in clock-in environments with a single cost code, and it is identifiable: the error rate downstream is also near zero, and the corrections queue is empty. If that is your situation, the approval step is redundant rather than broken, which is a different conversation and a cheaper one.

Far more often the approver cannot tell right from wrong, because they have no independent knowledge of what the person did. Or they can tell, and refusing is socially expensive — it accuses a colleague, it generates a conversation, it delays pay — while approving costs nothing and takes a second. The third is the common case and the refusal rate cannot distinguish it from the first.

The cost of refusing, counted honestly

A manager who returns a timesheet starts a chain. The employee has to redo it. The employee is annoyed, sometimes justifiably, because the thing they did wrong was a code they were never trained on. The payroll deadline moves closer. If the correction does not land in time the person is paid late, and late pay is a serious matter that escalates immediately and lands back on the manager.

Approving costs none of that. The manager presses a button and the week is closed. If something was wrong, it surfaces in eight weeks in a different department, attributed to nobody. The incentive structure is entirely one-directional and no amount of exhortation changes it. This is not a culture problem. It is an arithmetic problem, and it is solved by changing the arithmetic rather than by asking managers to care more.

Making refusal cheap

The lever is the cost of returning, not the willingness to return. Three things move it.

Query rather than reject. A rejected timesheet in most systems bounces the whole week back to the start. A query against a single line, which leaves the rest of the week intact and approved, costs the employee two minutes instead of twenty and costs the manager no relationship capital at all. Most products support this and most configurations do not use it.

Decouple the query from pay. If an unresolved query blocks the entire payment, every query becomes a threat. If the undisputed hours pay on schedule and the queried line settles in the next cycle, the manager can ask a question without holding somebody's rent hostage. This single configuration change does more for refusal rates than any training.

What to measure instead of satisfaction

Approval workflows are usually measured by completion: what proportion of timesheets were approved before the deadline. That number rewards exactly the behaviour that empties the control of meaning, and it is the number on most dashboards.

Replace it, or at least sit two numbers beside it. The query rate — how many timesheets generated at least one question — tells you whether anyone is reading. The downstream correction rate — how many approved weeks were later amended, credited or written off — tells you what the reading missed. A workflow with a 100% completion rate, a 0% query rate and a 6% correction rate is not a strict process catching everything. It is a process catching nothing, and the 6% is the measure of what it is letting through.

The uncomfortable conclusion

If the refusal rate has been zero for a year, the organisation has a choice between two honest positions. Either the approval step is doing nothing and should be removed, which saves everybody time and stops the record claiming a control that does not exist, or it is doing something and should be made capable of refusing.

What is not available is the current position, which is to keep the step, keep the name on the record, and rely on it in disputes while knowing that nobody has ever said no.