Define what actually counts as an emergency
An alert becomes urgent when the remaining time to act is shorter than the time needed to secure a solution and the potential impact on customers, production or service is significant. A supplier delay is therefore not automatically an emergency when inventory still covers demand comfortably.
Define a small number of shared priority levels so that every case is not labelled “critical”. This protects team capacity and makes escalations more credible with suppliers and management.
Example priority levels
Levels should fit the organisation but must lead to different actions.
- P1: continuity threatened in the very short term.
- P2: high risk without a secured solution.
- P3: deviation to monitor and manage normally.
- P4: information with no urgent action.
Use objective criteria
Combine inventory coverage, supplier lead time, next firm requirement, item criticality, affected customers or production lines and available alternatives. No single criterion is sufficient in every situation.
A simple score or matrix can make the logic reproducible. The objective is not a complex algorithm but a prioritisation rule that can be explained and consistently applied.
Useful criteria
Choose criteria that are available and understood by the operational team.
- Time until stockout.
- Operational impact.
- Item criticality.
- Reliability of supplier commitment.
- Alternative solution available.
- Cost of inaction.
Link every level to a response
A priority only matters when it changes behaviour. P1 may require immediate supplier contact, escalation, transport decision and frequent internal updates. P3 may remain in the normal follow-up routine.
Define who can authorise expensive contingency actions such as expedited freight, alternative purchase, stock transfer or deviation. This saves time when a case becomes truly critical.
Prepare escalation paths
Roles should be known before the emergency occurs.
- Buyer or planner as case owner.
- Purchasing or supplier manager.
- Production / sales depending on impact.
- Management for cost-risk decisions.
- Quality for substitution or deviation.
Reprioritise as the situation changes
Priority is not permanent. A confirmed shipment may reduce risk; another missed commitment may turn a moderate case into an emergency. Review open cases regularly, particularly those approaching stockout.
Close resolved emergencies explicitly so the list does not remain filled with old issues. A clean view improves focus on current risk.
Keep the emergency list short
A real priority list should stay limited. If everything is urgent, the prioritisation system no longer works.
Analyse recurring emergencies
Periodically group root causes such as supplier reliability, inventory settings, forecasting, transport, MOQ, ERP data or demand change. Repetition of the same emergency type points to a structural weakness.
Use the analysis to adjust parameters, strengthen critical suppliers, improve demand visibility or create contingency options. The best prioritisation system is one that helps reduce the number of emergencies over time.
Common mistake to avoid
Prioritising according to who complains most loudly or which supplier answers least quickly. Priority should remain connected to business impact.
Implementation checklist
Before considering the topic under control, check these points in your procurement process.
- Levels defined.
- Criteria objective.
- Escalation mapped.
- List reviewed regularly.
- Recurring causes analysed.
Continue with related procurement guides
Conclusion
Reliable procurement combines coherent parameters, current information and the ability to prioritise exceptions. Use this method as a working framework: adapt thresholds and indicators to your context, measure results and improve the rules progressively instead of managing only through emergencies.