key takeaways
If you only read 30 seconds of this article:
- The four causes: stocking policies that ignore criticality, invisible inventory elsewhere in the network, unmanaged lead-time drift, and planned work that arrives unplanned.
- The fix that backfires: cutting inventory across the board to force planning discipline; emergency spend and excess stock are the same disease expressed in opposite directions.
- Fix visibility first: the remedy for a meaningful class of emergencies already sits on your own shelves, at another site, under another description.
- Design the escalation path for the emergencies that remain, with a capture step so repeat emergencies get engineered out.
First, know what your emergencies are telling you
An emergency-reduction program starts with classification, not policy. Pull a recent period of expedited and off-process orders and classify each by cause; the distribution is the diagnosis. If "we didn't stock it" dominates, you have a policy problem. If "we had it, at another plant" appears at all, you have a visibility problem, where the remedy already sits on your own shelves. "The supplier used to be faster" is lead-time drift, and "the job moved up" is a planning-to-storeroom disconnect. This exercise is small work with a large payoff: it prevents solving the cause you assumed instead of the one you have.
The four causes, and the fix for each
Each of the four causes of emergency MRO purchasing has a distinct fix, and mixing them up wastes the program.
1. Stocking policy that ignored criticality. A part that stops a line should not be a candidate for "don't stock, order on demand," yet usage-based defaults classify it exactly that way because its demand history is nearly empty. The repair is a policy built on criticality, lead time, and usage together, the mechanism in the MRO inventory policy guide [VERIFY-URL: article 8 final URL - publish article 8 first, then link], grounded in the safety stock logic for intermittent demand.
2. Invisible inventory elsewhere in the network. A particularly galling emergency purchase duplicates a part sitting idle two plants away under a different description. Cross-site visibility converts these from purchases into transfers, the core case for spare parts sharing, and duplicate-record cleanup is what makes the visibility trustworthy.
3. Lead-time drift. Policies are set against the lead time at classification; suppliers change, and a short-lead part quietly becomes a long-lead one with nothing flagged in the ERP. Monitoring actual replenishment performance against assumed lead times, at least for critical sub-categories, catches drift before it becomes an emergency.
4. Planned work arriving unplanned. When maintenance planning and inventory run on different calendars, scheduled jobs generate surprise demand the storeroom sees too late. The fix is procedural: kit-and-stage discipline tied to the maintenance schedule, with parts availability confirmed at scheduling time, not execution time.
If you want your last quarter of expedites classified against these four causes, book a call with an MRO expert and bring the export.
Design the escalation path for the emergencies that remain
Some emergency purchases are legitimate: genuine failures of parts no policy would stock. For those, a designed path beats improvisation: pre-agreed expedite terms with strategic suppliers, a clear internal authority chain so approvals move at the speed of the failure rather than the org chart, and, critically, a capture step, every legitimate emergency feeds the next policy review, so repeat emergencies get engineered out. This is the escalation-path discipline from the MRO sourcing strategy, pointed at emergencies specifically.
What not to do
Do not respond to emergency spend by cutting inventory across the board to force planning discipline. Emergency purchasing and excess inventory are the same disease, decisions made without connected data, expressed in opposite directions, and squeezing one symptom inflates the other. The goal is not less inventory or fewer purchases; it is decisions made with the network visible. To baseline where your emergencies actually come from, book a call with an MRO expert.
Where Verusen fits
Three of the four causes are data problems: policies disconnected from criticality, stock invisible across sites, lead-time assumptions nobody reconciles. Verusen connects material, inventory, supplier, and multi-site data across existing ERP and EAM systems so the emergency-generating gaps surface before they generate emergencies. See the Verusen platform or talk through your expedite history.
Frequently Asked Questions
Four root causes account for them: stocking policies that ignore criticality and under-protect consequential parts, inventory that exists at other sites but is invisible under different descriptions, supplier lead times that drift after policies were set, and planned maintenance that reaches the storeroom as surprise demand.
The opposite. Thinning inventory without fixing visibility and policy converts emergency spend into downtime, because both symptoms share one cause: decisions made without connected data. Cut the fragmentation and the false stockouts, and both excess inventory and emergency purchasing shrink together instead of trading places.
With classification, then visibility. Classify a recent period of expedited orders by cause to learn which failure dominates, then fix cross-site visibility first, because emergencies that duplicate stock idle at another plant become transfers instead of purchases, and that remedy already sits on your own shelves.
Yes. Genuine unpredictable failures of parts no reasonable policy would stock are legitimate emergencies. Design their path deliberately: pre-agreed expedite terms with strategic suppliers, a fast internal authority chain, and a capture step that feeds every legitimate emergency into the next policy review.
PN
- Jeremiah Woodford
- CRO, Verusen
Chief Revenue Officer (CRO) at Verusen AI – AI Built for Industry. Designed to Solve What Legacy Systems Can’t.
