Approval, the Link That Deletes Quietly
What happens to hours that are neither approved nor rejected, why unapproved time is worse than refused time, and the two reports that make it visible.
Hours approved against hours worked, one department, one month
Approved automatically.
Approved by the manager.
Fifty-three hours left unactioned past the cut-off.
Not picked up in the following period either.
Reconstructed afterwards from other systems.
One hundred and fifty-two hours were worked and not approved, and ninety of them had been recorded and submitted. They were not rejected; nobody acted on them. This is one employer's own month, not a statement of what any rule permits.
Hours that are neither approved nor rejected are the worst state in the whole chain, because nothing decided them. A rejection is a decision somebody can argue with. An entry that sat in a queue past the cut-off and then stopped mattering is work that was done, recorded, and quietly disposed of by a deadline.
The workflow in “Approval, the Link That Deletes Quietly” becomes more reliable when captured time, approvals and later changes can be followed separately. For teams exploring employee monitoring software, employee monitoring software can provide useful operating context, while payroll rules, employee explanations and final decisions remain with accountable people.
Approval is also the only link where the deletion leaves no trace in the pay figures. Nothing was deducted; something simply never arrived.
For an independent reference relevant to “Approval, the Link That Deletes Quietly”, consult the ILO working-time resources. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.
The three outcomes, and the fourth
An entry can be approved, rejected with a reason, or amended and approved. Those are the three the process is designed for.
The fourth is expiry, and in most systems it is not called anything at all. The period closes, unapproved entries do not flow to pay, and no report exists showing what they were.
The two reports to build
- Unapproved at cut-off: every entry not actioned when the period closed, by person, by manager, by value.
- Approval latency: how long entries sit before somebody acts, by manager.
The first is the one that finds the money. The second is the one that predicts it, because a manager whose median approval time is eleven days in a weekly cycle is going to miss cut-offs structurally rather than occasionally.
Why managers do not approve
Rarely refusal. Usually volume, timing and a screen that shows a hundred identical rows with no indication of which ones matter.
Approval queues are also frequently sent to the wrong person — a manager who was not there, who has no way to know whether the overrun was genuine, and who therefore does the only safe thing available to them, which is nothing.
Making the queue answerable
An approval screen should show only the entries that differ from what was expected, with the reason the employee gave, and should take one click each. A queue that lists every entry teaches managers to approve in bulk without reading, which is the same as not approving at all.
Bulk approval is worth looking at on its own. Where a manager approves four hundred entries in ninety seconds, the control is decorative, and the organisation should either make it real or stop relying on it.
Approval is not permission
A distinction worth stating internally, because managers routinely believe the opposite: approving time is confirming that it was worked, not granting permission for it to have been worked.
Work that was done without authorisation still happened. Whether it should be paid, and what to do about the lack of authorisation, are two separate questions, and conflating them produces the specific outcome where a manager refuses to approve as a sanction.
That is a disciplinary decision taken through the payroll system, it is rarely defensible, and it leaves a record showing exactly what it was.
Telling the employee
An entry that is rejected or amended should generate a message to the person, saying what changed and why. Most systems can do this and most have it switched off.
Where that notification exists, disputes surface in the same week and are cheap. Where it does not, the employee discovers a discrepancy on a payslip, has no way to connect it to a particular day, and raises it as a general complaint about being underpaid — which is far harder to answer even when the organisation was right.
Who approves when the manager is away
Approval queues stall during leave, and leave is predictable. A named deputy, configured in advance rather than arranged by email, removes most of the expiry described above.
The test is simple: pick a manager currently on leave and look at their queue. If it is accumulating, the organisation has a structural gap that recurs every time anybody takes a holiday, which is to say constantly.
Approving your own time
Where managers record and approve their own hours, the control is nominal, and that is the normal arrangement for supervisors and small-site managers.
It is worth either accepting explicitly — with a periodic review of their entries by somebody above them — or removing the pretence. What should not happen is an approval step that exists on paper, is exercised by the person whose time it is, and is relied on as a control by anybody reading the configuration.
Catching what expired
For anything already lost: run the first report for the past twelve periods, total it, and decide. Hours that were recorded and never actioned are not a grey area, and the longer the list runs the more expensive the eventual answer becomes.
Then set the queue so it cannot happen again — escalation after a few days, a named deputy, and a rule that nothing expires silently. An entry that nobody acted on should end up on somebody's desk rather than in the past.