The counter-intuitive starting point for this audit is that the biggest findings are usually procedural rather than technical. Fleets expect to find that the wrong specification is being bought, and they more often find that the right specification is being bought off-contract, at three different prices, and partly left unused in a store room.
This is a fault-to-fix method for auditing blade spend: reconciling the sources before analysing them, comparing spend on a basis that reveals outliers, and following the three findings that appear in most first audits to their causes.
Data sources and reconciliation
Four sources hold blade spend, and they disagree. The purchase ledger records what was bought and from whom. The store records what was received and issued. The workshop job cards record what was fitted. And the machine records, where they exist, record what is on each unit now.
The reconciliation is mechanical and it is where the findings come from. Items received but never issued indicate stock that is not moving. Items issued but not fitted indicate either recording errors or loss. Items bought outside the contract show as purchases from suppliers that do not appear in the contract list. Running the three checks on one season’s data is usually enough to size the problem.
Spend per vehicle and per lane km
Spend per vehicle is the wrong denominator.
Vehicles do not do the same work, and spend per year is worse because it mixes a mild winter with the one before it. The figure that reveals outliers is spend per unit of work.
Expressed per lane kilometre treated or per ice-control event, a machine that costs twice the fleet average is either working a route nobody has compared it against, has a fitment problem, or is being serviced differently.
The normalised figure does not say which, and it identifies where to look. The measurement that supports it is described on the cost per lane kilometre page.
Price variance across depots
Price variance is the fastest finding to quantify and the easiest to correct. The same item bought under the same contract but invoiced at different prices across depots usually reflects three causes: freight charged differently, a quantity break not taken, or a purchase made outside the contract entirely.
The comparison is worth running line by line rather than in total. A total that looks acceptable can hide one item bought at a premium in one depot and another bought below contract in a second, and only the line-level view shows which supplier or which process produced each.
Off-contract purchasing patterns
Off-contract purchasing is the finding that most often explains both price variance and stock problems, and it has operational causes rather than dishonest ones.
Three causes account for most of it. An emergency purchase during a storm, when the contracted supplier could not deliver in time. A specification the contract does not cover, so the depot bought what it needed locally. And habit, where a depot has used a supplier for years and continued after the award. Only the third is a compliance issue; the first two are signals that the contract’s supply arrangements or specification do not match what the fleet actually needs.
Inventory write-offs and losses
Write-offs are the quietest leak and the easiest to overlook because they appear in the accounts rather than in the operational records. The items to look for are stock written off at year end, stock transferred between depots without a recorded reason, and stock that has not moved for two seasons.
Stock that has not moved is worth quantifying even where it has not been written off, because it is capital the fleet has already decided it does not need. Matching the immobile list against the fleet’s current machines usually shows whether it is obsolete or simply badly distributed. The stock level that prevents both write-offs and emergency purchases is described on the inventory planning page.
Savings opportunities by category
The table below sets out what each finding usually costs and what corrects it.
| Finding | Usual cause | Correction |
|---|---|---|
| Price variance across depots | Freight differences or purchases outside the contract | Single ordering point at contract prices |
| Emergency purchases | Contract lead time longer than the season’s need | Stock level set from consumption and lead time |
| Uncovered specifications | Contract does not include a pattern the fleet runs | Add the line to the next scope |
| Immobile stock | Over-ordering or fleet change since purchase | Consolidate, redistribute or write off deliberately |
| High spend per unit of work on one machine | Fitment condition or route difference | Inspect the machine before changing the specification |
The fifth row is the only technical finding in the list, and it is worth resisting the temptation to act on it first. Confirming whether the machine is loading its edge unevenly takes one inspection, and it is often the whole explanation.
Reporting to council or board
An audit report is most useful when it separates the findings that need a decision from those that need a procedure. The first category is small: a specification change, a stock level, or an additional line on a contract. The second is larger and cheaper, and it can be implemented without a vote.
Two figures carry the report. The variance found, expressed as a proportion of the spend audited, and the portion of it that is recoverable in the next cycle rather than retrospectively. A report that claims the whole variance as a saving invites a question about why it was not recovered; one that states what will change next year is defensible. Cost context for both figures is published by the Transportation Research Board and the Federal Highway Administration.
What the audit cannot fix
Three problems survive a spend audit because they are not spending problems.
- A specification that does not match the route, which only shows up in the wear data rather than in the ledger.
- A machine condition that loads its edge unevenly, which appears as high spend on one unit.
- A contract that is sound but unused, which is a management issue rather than a procurement one.
The third is the most common reason an audit produces recommendations that are not implemented. A finding that the fleet should use the contract it has requires somebody to change daily practice, and that is a different task from writing a report.
Running the audit in a first cycle
A first audit does not need a full season of clean data. Three sources and one normalising figure are enough to produce findings: the purchase ledger, the store issues and the job cards, normalised against lane kilometres or events per machine.
Reconciling them takes days rather than weeks, and the findings are usually large enough to justify the second cycle with better records. Public sector audit and budgeting practice is published by the National Association of Counties and the American Association of State Highway and Transportation Officials, winter operations research by the Transportation Research Board, and fleet maintenance practice by the Snow and Ice Management Association.
SENTHAI manufactures plow edges, wear plates and carbide inserts in Rayong, Thailand, and issues each lot with the batch and dimensional records that let a purchase be matched to a delivery and a delivery to a machine. Audits that need the item and batch detail clarified can be raised through the contact page, and the planning model the findings feed is described on the procurement forecast page.
FAQ
What is the first step in auditing blade spend?
Reconciling the sources. Purchase records, stores issues and workshop job cards rarely agree, and the differences are where the findings are. Reconcile before analysing, or the analysis will describe the accounting rather than the fleet.
How should blade spend be compared between vehicles?
Per unit of work, not per vehicle or per year. Spend per lane kilometre or per event normalises for the route, which is what differs most between machines, and it is the figure that makes an outlier visible.
What are the most common findings in these audits?
Off-contract purchasing, price variance between depots for the same item, and unused stock written off. All three are procedural, and all three are correctable without changing the product specification.
Does an audit need to change the specification?
Usually not in the first round. Most first-audit findings are procedural: what was bought, from whom, at what price, and what was left unused. Specification questions follow once the spend data is clean.
How is an audit finding turned into a saving?
By changing the cause rather than the line item: consolidating the buying to the contracted supplier, standardising the item across depots, and setting a stock level that prevents both write-offs and emergency purchases.
Send the purchase and item history you have and the routes behind it. The SENTHAI engineering desk will confirm the specification details so the findings can be acted on without changing products that are working.
This article is one step in the Sourcing Carbide Wear Parts Guide, which covers the technical pack, supplier selection, landed cost and supply risk.