The problem is not the purchase itself. It is the lack of a controlled exception process.
Most businesses do not struggle with planned purchasing in principle. If materials were included in the quote, approved in advance and expected as part of the job, the path is usually clear enough.
The mess starts when a purchase sits outside that original plan.
A technician discovers extra fittings are needed on site. A supervisor needs replacement equipment for the workshop. A project manager asks for an additional item to keep an installation moving. Someone calls a supplier, buys what they need, sends a message to the office and assumes the paperwork can be sorted out later.
That is where surprise costs, duplicated orders, blown margins and approval arguments tend to come from.
The issue is not that unplanned purchases should never happen. In operations-heavy businesses, they are normal. The issue is that many businesses treat them as informal interruptions instead of recognised exceptions with a defined workflow.
A workable approval process for unplanned supplier spend needs to answer five things clearly:
- when a purchase counts as planned versus unplanned
- who can approve it, and up to what value
- what happens when the purchase is genuinely urgent
- how the spend is linked to a job, cost code or overhead account
- what evidence and reconciliation are required afterwards
If those rules are not built into the way work moves, staff will create their own version in phone calls, texts, email chains and verbal approvals. That usually works right up until the invoice arrives.
Start by separating planned purchases from unplanned ones
This sounds obvious, but many approval problems start because the business has not defined the difference properly.
A planned purchase is generally one that already has an approved basis. That basis might be:
- an accepted customer quote
- a bill of materials
- an approved project budget
- a recurring operational budget
- an agreed stock replenishment rule
An unplanned purchase is one that falls outside that approved basis. That does not automatically mean it is wrong. It means it needs exception handling.
For example:
- additional conduit required because site conditions differ from the original scope
- replacement consumables bought because stock was unavailable when needed
- an urgent hire item needed to complete a stage safely
- a workshop or office purchase with no existing approved budget line
- extra materials requested by a customer after work has already started, before the variation is formally priced
That distinction matters because planned and unplanned spend should not follow the same logic.
If a purchase is already covered by an approved quote or internal budget, the system should focus on execution and control. If it is not, the system should shift into exception mode and ask a different set of questions.
Without that split, staff often assume any operational need is self-justifying. It is not. A genuine need still needs a structured path.
The workflow should force the reason for the purchase to be made explicit
Informal purchasing often hides the real issue.
Someone says, “We just need this part today,” but that statement leaves too much out. Is it required because the quote missed something? Because site conditions changed? Because someone forgot to order? Because stock control failed? Because the customer added scope? Because the supplier originally delivered the wrong item?
Those are not the same operational problem.
A good approval workflow should require the requestor to nominate the purchase reason in a structured way. For example:
- quote omission
- scope change
- site condition variation
- stock shortage
- damaged or failed item
- urgent replacement
- internal overhead purchase
- safety or compliance requirement
- supplier error correction
This does two things.
First, it gives the approver enough context to make a sensible decision without chasing basic information.
Second, it creates reporting value later. If unplanned spend is constantly being caused by quote omissions, that is a sales and estimating issue. If it is being caused by stock shortages, that is an inventory or procurement issue. If it is mostly scope change, the variation process may be too slow.
If every exception is just coded as “miscellaneous purchase”, the business learns nothing.
Approval thresholds need to reflect risk, not just dollar value
Most businesses know they need approval thresholds. Fewer design them well.
A threshold structure should not just say who can approve $200, $1,000 or $5,000. It should also reflect the type of spend and the context.
A practical approval model might consider:
- purchase value
- whether the spend is job-linked or overhead
- whether the item is urgent
- whether the item is from a preferred supplier
- whether the purchase creates a customer variation
- whether the spend is recoverable or likely unrecoverable
- whether the item is standard or unusual
For example, a field supervisor may be allowed to approve a small urgent site purchase from an existing supplier to keep a job moving, but not approve a larger ad hoc order from a new supplier for items outside normal scope.
That is a better control than a blunt value-only rule.
A simple delegation model
The exact levels will vary, but the structure should be clear enough that staff do not have to guess. For example:
- field staff can request but not approve
- supervisors can approve low-value urgent operational purchases within defined limits
- project or service managers can approve mid-range job-related exceptions
- overhead purchases require department or operations approval
- higher-value or margin-impacting exceptions require senior management approval
- purchases that may need customer variation approval must trigger that commercial step before final commitment where possible
The aim is not bureaucracy. The aim is to stop approval authority becoming ambiguous under pressure.
A common failure point is “someone senior said it was fine” without any record of what was approved, why, and against which job or budget area.
Urgent purchases need a separate path, not a free pass
This is where many businesses lose control.
Urgency is real. If a team is on site, work is booked, equipment is hired and the next trade is waiting, holding everything up over a small purchase can be more expensive than the item itself.
But “urgent” is also one of the easiest labels to abuse.
The answer is not to ban urgent buying. It is to define what urgent means operationally and what evidence is required when normal approval steps are bypassed.
A useful urgency rule usually includes all of the following:
- the purchase is needed to avoid a genuine job stoppage, safety issue or service failure
- waiting for normal approval would create unreasonable delay or cost
- the item could not reasonably have been planned earlier
- the purchase is still subject to retrospective review
- evidence must be submitted within a defined timeframe
That last point matters. If urgent purchases bypass normal approval but never get reviewed properly, the business has not created an exception path. It has created a loophole.
What retrospective evidence should be required
For urgent site purchases, the workflow should require a short but specific record after the fact, such as:
- who made the purchase
- date and time
- supplier
- items purchased
- amount
- linked job or overhead code
- reason urgency applied
- supporting receipt or supplier document
- photo evidence where relevant
- whether the cost is chargeable, variation-related or absorbed internally
- approving manager for retrospective sign-off
This should not be a long essay. It just needs to be enough to allow later verification and correct coding.
If the business relies on “send the receipt to accounts when you get back”, it will keep dealing with missing paperwork, disputed coding and margin surprises.
Every unplanned purchase needs a destination in the system
One of the biggest reasons unplanned spend causes damage is that the business does not decide where the cost belongs at the time of approval.
If a purchase cannot be linked properly, reporting becomes guesswork later.
Every request should be attached to one of these destinations:
- a specific job
- a specific stage or cost code within a job
- a customer variation pathway
- a workshop or vehicle cost category
- a stock replenishment exception
- a general overhead category
- a capital or asset approval pathway, if relevant
That decision should happen before or during approval, not during end-of-month cleanup.
For job-related purchases, the workflow should answer:
- which job is this for?
- which part of the work does it relate to?
- was it expected in the quoted scope?
- is it recoverable from the customer?
- does it require a variation, internal write-off or further review?
If a technician buys extra materials for Job 482 and the invoice later lands in accounts with no job link, the finance team may code it to a general account just to clear the queue. The cost then disappears from the true job margin, and the business loses visibility twice: once operationally, and again in reporting.
Approval should include a duplicate and supplier check
Many unplanned purchases are not bad decisions. They are duplicate decisions.
One person orders an item because they think it has not been purchased. Another orders the same item later because there is no visible record. Or a team buys from a retail supplier at short notice while the same item was already available through an existing account or preferred supplier.
That is not just a purchasing issue. It is a visibility issue.
Before approval, the workflow should make it easy to check:
- whether the item has already been ordered
- whether a similar request already exists for the same job
- whether the supplier is approved or preferred
- whether the item should come from existing stock
- whether there is already an open variation or budget request covering the need
This does not need to become a heavy procurement exercise. But there should be at least one checkpoint that prevents obvious duplication and off-contract buying.
If that check relies on somebody remembering past emails or searching message threads, it is not a real control.
Evidence requirements should match the type of spend
A sensible workflow does not ask for the same evidence in every case.
A low-value urgent consumable purchase on site should not require the same documentation as a larger unplanned equipment hire or a non-standard supplier order.
What matters is that the business defines the minimum evidence for each category.
For example:
Low-value urgent site purchase
Require:
- supplier receipt or invoice
- job link
- reason code
- basic manager sign-off
Mid-range unplanned job purchase
Require:
- item details
- supplier quote or pricing confirmation
- job link and cost code
- explanation of why it was outside plan
- approval from the relevant operational manager
- variation or recovery decision if applicable
Higher-risk or non-standard purchase
Require:
- comparison or justification
- supplier check
- commercial impact assessment
- higher-level approval
- clear treatment in job costing or overhead reporting
The point is consistency. Staff should know what “complete” looks like before the purchase is made.
When evidence rules are vague, approvals become personality-driven. One manager demands full backup. Another says “just get it done”. That inconsistency usually becomes friction between operations, accounts and management later.
Do not separate approval from customer recovery logic
A common gap in unplanned purchasing workflows is that the approval only asks whether the business should spend the money, not whether the customer should be billed for it.
Those are related, but not identical questions.
An extra item may be operationally necessary, but that does not automatically mean it can be charged. Equally, a chargeable variation may be missed because the purchase was approved purely as a site need.
For job-linked unplanned spend, the workflow should prompt a commercial decision:
- included in existing scope
- customer variation required before proceeding
- proceed now and raise variation after, due to urgency
- non-recoverable internal cost
- pending review
That matters because job cost control is not just about approval. It is about whether the cost lands in the right commercial bucket.
If the team buys first and decides recoverability later, the business will often underbill or absorb costs it should at least have assessed properly.
Post-purchase reconciliation should be built into the workflow from the start
Unplanned purchases are often approved in the moment and forgotten afterwards.
That is where problems spread.
The approval workflow should not end when the item is bought. It should end when the purchase has been matched to its evidence, coded correctly and reviewed for outcome.
That does not mean turning this article into invoice processing theory. It means recognising that approval without closure leaves the exception unfinished.
A practical post-purchase reconciliation step should confirm:
- the purchase actually occurred
- the final amount matches the approved expectation or is explained
- the receipt, supplier invoice or supporting document has been provided
- the cost has been allocated to the right job, cost code or overhead category
- any customer variation or recovery action has been completed or explicitly written off
- any exception reason remains valid
- any pattern requiring operational review has been flagged
For example, if an urgent purchase was approved for site conditions, but the pattern appears across ten jobs in a month, the business may not have a purchasing problem at all. It may have a scoping, quoting or site inspection problem.
That is why reconciliation is not just accounting cleanup. It is feedback into operations.
What a practical workflow looks like end to end
A workable unplanned purchase approval process usually follows a sequence like this:
A need is identified The requestor records what is needed, why it is unplanned, estimated cost, supplier and urgency level.
The request is classified The system identifies whether it is job-linked, overhead, recoverable, urgent, standard or high-risk.
Approval routing is determined Based on value, type and urgency, the request goes to the correct approver.
The approver checks the essentials They assess need, duplication risk, supplier appropriateness, budget or margin impact, and customer recovery implications.
The purchase is authorised or rejected The approval is recorded against the request, not left in a text message or verbal conversation.
The purchase is completed The item is bought, and evidence is attached.
The cost is allocated correctly The purchase is linked to the job, cost code or overhead account.
The exception is closed A final check confirms the documentation, coding and any variation or write-off treatment.
Reporting captures the reason pattern The business can then see what is driving unplanned spend over time.
This is not overengineering. It is the minimum structure needed to stop ad hoc purchasing from turning into after-the-fact detective work.
Good control should not slow down legitimate work
Many businesses avoid formal approval steps because they worry the process will block the field.
That concern is valid if the workflow is badly designed.
A good process does not force every purchase through the same bottleneck. It separates routine planned buying from genuine exceptions, allows fast decisions within clear delegation limits, and reserves heavier approval for higher-risk cases.
In practice, that means:
- small urgent site purchases can move quickly
- larger or commercially significant exceptions get more scrutiny
- staff know what information is required upfront
- approvers are only asked for decisions they actually need to make
- accounts are not left reconstructing what happened weeks later
The fastest workflow is not the one with no controls. It is the one where the correct path is obvious, evidence is captured once, and nobody has to chase the story afterwards.
What good looks like
A well-designed approval workflow for unplanned supplier purchases has a few clear characteristics.
Staff know when a purchase is outside plan.
They know who can approve it.
Urgent purchases have a legitimate path, but they do not escape review.
Every approved spend item is linked to a job, cost code or overhead category.
The business can tell the difference between recoverable variation costs and internal write-offs.
Duplicate and off-contract purchases are less likely because there is a visible record before money is spent.
And when management looks at unplanned spend, they can see patterns that point back to the real operational causes.
That is the broader value here. The workflow is not just about stopping unauthorised spend. It is about making exceptions visible, traceable and learnable.
If unplanned supplier purchases are currently being managed through calls, messages and end-of-month cleanup, it is usually worth mapping the exception process properly before adding more tools around it. Where purchasing touches jobs, approvals, field teams and reporting, 5M Consulting can help design a workflow that keeps control without making legitimate work harder.