A facilities team requests approval to replace an unreliable booking system. The assessment takes two weeks longer than expected. During that period, staff continue reconciling reservations manually, the supplier’s proposed installation date passes, and the implementation team changes its schedule. The approval delay has several possible costs, but they are not all the same kind of cost.
Some can be measured directly, such as additional reconciliation hours or a documented rescheduling charge. Others require assumptions: when the replacement would otherwise have started, how much benefit it would have delivered, or which work the team displaced. Those assumptions should remain visible.
Approval latency is elapsed time between a defined request and a usable decision. It can affect a wider delivery process, but a longer wait does not automatically multiply into a particular financial loss. A useful estimate explains what changed because of the wait and compares that with the purpose and value of the review.
Define When the Request Became Ready and the Answer Became Usable
The facilities request may enter a system before it contains a costed proposal, a data assessment, or the relevant supplier terms. Counting from initial submission captures the requester’s experience. Counting from readiness for a particular review answers a different question about the review service.
Keep both where they matter. A process should not make preparation delays disappear by continually redefining the start date. Equally, an approver should not be treated as though they could decide before essential evidence existed. Recording the reason for waiting makes the distinction useful.
The endpoint also needs care. An approval subject to a condition may not yet permit installation. Record what was authorised, what remained open, and when the team could actually proceed. A short response time is an incomplete measure if the response repeatedly leaves the operational choice unresolved.
For the booking system, the team might record the original request, the complete supplier proposal, the start of assessment, the conditional response, and final permission to schedule. This shows where a change in evidence, capacity, or authority could affect the outcome.
Separate Additional Spending From Work Already Funded
Suppose staff performed twelve extra hours of reconciliation because the old system remained in use. If the organisation uses an illustrative internal rate of $60 per hour, that represents $720 of staff capacity used. It is an estimate of the value assigned to that capacity, rather than necessarily an additional $720 cash payment.
If the hours were paid overtime, the actual incremental payroll cost can be estimated from the applicable payments. If staff completed the work within their normal hours, ask what was displaced. The effect may be delayed maintenance, reduced customer support, or a task completed later without a material consequence.
These distinctions prevent counting the same burden twice. Adding full salaries for the waiting period, the estimated value of displaced work, and overtime can exaggerate the cost if they describe overlapping effects. Explain which quantities are incremental and which represent alternative uses of the same capacity.
Include preparation and revision that the delay actually caused. A supplier changing terms may require rework; answering a necessary question that would have arisen during any timely review is different. The estimate needs a plausible comparison with the process that could reasonably have occurred.
Examine the Effect on the Delivery Path
An approval can take longer without moving the completion date if another dependency still determines when installation can begin. Conversely, a short delay can miss an available installation window and move delivery substantially. The relationship depends on the schedule and available alternatives.
For the facilities team, confirm whether the supplier slot was genuinely available and whether approval was the remaining condition. If building access, staff training, or another procurement decision was also unresolved, attributing the whole later installation date to this approval would be misleading.
Little’s queuing result connects average work in a system, average flow rate, and average time under its stated conditions. It helps relate unfinished requests to flow in a stable process. It does not supply an individual cost multiplier for every delayed approval.
The broader analysis belongs in a map of execution bottlenecks. Identify which dependency constrained the relevant period and how much usable scheduling flexibility remained. This provides a better basis for intervention than assigning the whole project delay to the most visible queue.
A delayed answer may also change the amount of work in progress. The implementation team might start another task while waiting, then need to rearrange it when permission arrives. Record what actually happened, including any useful work completed during the interval. Waiting should not automatically be valued as a fully idle team.
Estimate Delayed Benefits With a Credible Comparison
The new booking system may reduce manual reconciliation after implementation. To estimate benefits delayed by approval, establish a realistic implementation date under a feasible alternative process, then compare it with the actual or forecast date. Include preparation and transition time in both cases.
If the expected saving is uncertain, use a range and explain the basis. A small pilot, observed workload, or comparable installation may help. A supplier’s promised saving should not become a confirmed financial loss simply because the purchase waited.
Distinguish delayed value from value lost permanently. A recurring saving may begin later while remaining available afterwards. A time-limited opportunity may expire. Those situations have different consequences and should not be combined under a generic daily cost of delay.
A decision to decline the purchase also needs a fair comparison. A review that identifies an unsuitable service may avoid future cost, even if it disappoints the requester. The purpose of measuring latency is to improve the timing and quality of decisions, rather than make approval the assumed correct outcome.
Look for Repeated Work and Changed Assumptions
Elapsed time can affect the effort required to resume a request. Evidence may need refreshing, people may have moved to different assignments, or the proposed solution may no longer match the original need. These are possibilities to investigate rather than automatic consequences of every wait.
Sophie Leroy’s research on attention residue examines how attention associated with one task can carry into another. It supports taking switching conditions seriously. It does not establish a fixed recovery time for an engineer returning to an approval request after several days.
For the booking-system review, ask which documents were revised, which assumptions changed, and what work had to be repeated. A brief sample of completed requests can reveal whether the process routinely asks people to reconstruct the same case.
The remedy might be a more complete initial proposal, direct access to a specialist, an available deputy, or an earlier decision about scope. The article on approval checkpoints examines the review route itself. Different causes should not all be answered with a shorter deadline imposed on the same overloaded approver.
Include Requests That Did Not Reach Approval
A sample of completed purchases can miss requests abandoned during the process. The facilities team may have found a different solution, lost the need, or decided that further preparation was not worthwhile. Those outcomes provide relevant evidence, but abandonment alone does not establish that a valuable opportunity was lost.
Record the reason where it is available and distinguish it from an interpretation made later. A requester may say the supplier slot expired, while the records also show that the proposal was outside the available budget. The account should preserve both conditions rather than attribute the outcome to one convenient cause.
Compare similar requests where possible, including their complexity and readiness. An unusually fast approval obtained through a pre-assessed standard route is not a fair baseline for a novel purchase with unresolved requirements. The comparison should describe a feasible improvement to the actual process, rather than assume the organisation could have made every decision immediately with the same assurance.
Use the Estimate to Compare Practical Changes
A useful account can distinguish observed extra work, actual additional spending, plausible delayed benefit, and effects that remain unknown. Present a range where appropriate and state which assumptions most affect the result. Precision should follow the evidence rather than the desired urgency.
Then compare feasible interventions. A standard route for an assessed class of purchases might reduce repeated review. A scheduled decision slot might address availability. A clearer proposal might reduce clarification. Each option has its own operating cost and effect on assurance.
Test whether a faster route preserves the relevant judgement. A response that arrives sooner but omits a condition can create downstream correction. Track the request through to usable authorisation and implementation, including the effort shifted to requesters or other reviewers.
Assign responsibility for reviewing the result. The facilities manager can supply the account of implementation effects, while the review owner explains capacity and assurance requirements. A sponsor may need to settle the trade-off between them. The cost analysis helps that decision by showing consequences; it cannot decide which controls the organisation is authorised to remove.
Approval latency deserves attention when waiting changes what the organisation can deliver or what delivery requires. Measuring those changes carefully makes the case more credible. It also gives reviewers and requesters a shared basis for reducing avoidable delay while retaining the evidence and authority needed for a sound choice.





