Why Purchase Order Delays Cost More Than the Repair Itself
It's 6:15pm on a Friday.
A chiller unit trips in the warehouse.
The engineer on-site knows exactly what's wrong and can fix it tonight — if someone can authorise the callout.
The problem is, the person who signs off spend over £200 has already left for the weekend.
The site manager can't approve it.
The office manager doesn't have visibility of the budget line.
By the time anyone with signing authority picks up a phone on Monday morning, the chiller has been down for 60 hours, the goods inside it are compromised, and the "quick fix" has become a much bigger, much more expensive conversation.
Nobody in that chain did anything wrong. The approval process worked exactly as designed. That's the problem — the process was designed for predictable spend, not for a Friday-evening breakdown that doesn't know it's supposed to wait for Monday.
The Approval Process Wasn't Built for Emergencies
Most UK operations teams run maintenance spend through the same purchase order process they use for everything else: raise a requisition, route it for sign-off, wait for approval, then instruct the contractor. According to research on purchase order cycle times, 58% of businesses take two days or more, on average, just to approve and issue a standard purchase order — and that's for routine, business-hours spend with no urgency attached to it.
Now put a genuine emergency through that same process. A production line stoppage. A failed lift. A burst pipe. The approval workflow doesn't have an "urgent" lane. It has one lane, and it moves at business-hours speed regardless of what's actually happening on site.
The Chartered Institute of Procurement & Supply defines predictive and preventive maintenance specifically as strategies to avoid unplanned downtime — but no procurement framework accounts for the fact that unplanned downtime, by definition, doesn't check the calendar first.
What the Delay Actually Costs, Beyond the Repair Bill
The direct repair cost is rarely the expensive part. It's everything that accumulates while the job sits waiting for a signature.
As we've covered in our piece on the true cost of asset downtime, reactive maintenance already runs 3–4x the cost of planned work once you factor in emergency callout rates and expedited parts. A PO delay stacks directly on top of that multiplier — because every hour spent waiting for authorisation is an hour the fault gets worse, not better.
Run the maths on a mid-size site: a single Friday-evening breakdown that sits unauthorised until Monday morning typically means the difference between an £800 same-night callout and a £3,000-plus emergency weekend rate once a contractor finally gets sign-off — before counting the cost of whatever the asset was supposed to be doing for those 60 hours.
On a site running 15–20 reactive incidents a year, even a handful hitting this pattern can represent thousands of pounds in avoidable premium, on top of the underlying repair.
There's also a quieter cost: the relationship damage. A contractor who gets called at 6pm and told to wait until Monday for a signature either declines future emergency work or prices every future job assuming they'll be waiting for approval again. That's a version of the margin problem - except here, the operations team is paying a premium not for hidden costs, but for its own process friction.
Why "Just Give the Site Manager a Higher Limit" Doesn't Fix It
The obvious fix looks simple: raise the site manager's spending authority so they can approve emergency callouts without waiting for someone more senior. In practice, this creates a different problem — a single person now has open-ended authority to commit company money with no structured record of why, no category boundaries, and no automatic audit trail. Finance teams are right to be nervous about that. It solves the speed problem by creating a governance problem.
What's actually needed is authority that is pre-approved by category and capped by amount, not authority that is unlimited and reactive. The distinction matters: a plumber turning up to fix a burst pipe should be able to act immediately up to a sensible ceiling, without that ceiling becoming a blank cheque for every category of spend, indefinitely, with no oversight.
How a Structured Spend-Cap System Actually Solves This
This is the part of our Asset & Facilities Management System that gets the least attention next to compliance tracking and asset tagging — and it's arguably the piece that saves clients the most money in the moments that matter.
Here's how it works in practice:
An Pre-Paid Expense card is issued to Office Mango, no negotiations in the moment of crisis. This is agreed once, as part of onboarding, and reviewed Quarterly.
Pre-approved spend caps are set per tier covering the categories of work most likely to need urgent action (statutory safety faults, production-stopping breakdowns, water/electrical emergencies).
Vetted contractors can act immediately within the cap, without waiting for a same-day authorisation, because the authorisation already happened weeks earlier as part of the agreement.
Anything above the cap still routes through proper sign-off — the system isn't removing financial control, it's removing financial control from the moments where speed matters most and replacing it with a category-based limit set in advance, by the people who should be setting it.
Every spend is logged and reported after the fact, so finance retains full visibility and a clean audit trail — the oversight happens on a reporting cadence, not as a bottleneck in the middle of an emergency.
The effect is simple: the site manager doesn't need to find someone with a signature at 6pm on a Friday. The contractor doesn't need to explain why they can't start without a PO number. The fault gets fixed the same night, within a pre-agreed limit, and the paperwork catches up afterwards instead of blocking the work beforehand.
What Good Looks Like: A Site Running This Properly
A statutory fault (fire panel, water leak, electrical fault) is logged via QR scan the moment it's spotted — day or night.
The assigned contractor from the vetted network sees the fault immediately and can attend without waiting for a purchase order, because the spend sits inside the pre-approved cap for that category.
Work is completed and signed off the same day or overnight, with photo evidence attached to the asset record.
The spend is done through the pre-paid expense card with Office Mango as the cardholder and appears in the next reporting cycle — no chasing, no reconciliation headache, no "who approved this?" conversation three weeks later.
Anything genuinely outside the cap — a major plant replacement, a capital project — still goes through full sign-off, because that's exactly the kind of spend that should be scrutinised in advance.
That's the difference between a process built for routine spend being stretched to cover emergencies, and a process built with emergencies in mind from the start.
The Conversation Worth Having Before the Next Friday-Evening Breakdown
Most operations teams don't think about their approval process until it fails them at the worst possible moment. By then, the cost has already been paid — in emergency callout rates, in a damaged asset, or in a contractor relationship that's now pricing in the friction.
If you want a clear picture of what your current asset base and reactive maintenance spend actually cost — including the hidden premium of after-hours delays — start with the UK Statutory & Operational Asset Compliance Checklist. It takes a few minutes and shows exactly where the gaps sit.
Ready to talk through whether a pre-approved spend structure would work for your site? See how Critical and Operational compare, or book a free site assessment to map the right cap levels and categories for your specific operation.
