The Plan Slipped Today. Which Order Should Recover First?
Schedule recovery is a business decision, not a race to restart every late job. Priority must reflect commitments, constraints, cost and consequence.
The short answer
When an electronics production plan slips, the factory should not automatically recover the loudest customer or the earliest original job. It should rank the real business consequences of delay against current constraints. Customer commitment, downstream dependency, material availability, changeover, quality risk, cost and recovery probability all matter.
A disciplined recovery process creates a small number of feasible scenarios, makes the trade-offs visible and records why one sequence was chosen. The goal is not to make every bar green again. It is to protect the most important promises with the least additional disruption.
One delay creates several competing emergencies
An SMT line stops for four hours. Three jobs now overlap tomorrow’s capacity. Sales asks to protect the largest customer. Production wants to continue the current product family to avoid changeover. Finance points to an order ready for invoicing. Another plant needs boards for final assembly. Quality warns that overtime on a difficult job increases risk.
Every request is rational from one perspective. If the planner responds to them one at a time, the sequence changes repeatedly and preparation teams chase a moving target. Recovery activity increases while delivery confidence falls.
The factory needs a common decision model before pressure arrives.
Start with current truth, not the old plan
The original schedule explains what should have happened. It is not a valid recovery baseline if material, WIP and capacity have changed.
Before comparing options, refresh:
- actual completed quantity and remaining work;
- WIP location, age and quality status;
- usable material and alternate approvals;
- equipment condition and realistic capacity;
- tooling, programme and labour readiness;
- downstream and subcontract constraints;
- current customer commitments;
- transport and shipment cut-offs.
Without this reset, the planner may choose a sequence that assumes unavailable components or impossible output rates.
The pillar article The Schedule Is Green. Why Is the Line Still Waiting? explains why an executable schedule depends on live readiness evidence rather than calendar allocation alone.
Separate urgency from consequence
Urgency describes how soon an action is requested. Consequence describes what happens if the factory does not act.
A customer escalation is urgent, but another quiet order may feed a contractual installation tomorrow. A high-revenue job may be important, but completing a small batch could release a full downstream shipment. A late order may already have a negotiated date, while an apparently on-time order will miss an immovable transport cut-off.
Recovery priority should consider:
- contractual or customer impact;
- dependency on another factory or final assembly;
- revenue and cash-flow timing;
- strategic programme importance;
- regulatory or quality consequence;
- shelf-life or material exposure;
- cost of delay versus cost of recovery;
- probability that the recovery action will succeed.
These factors do not need one universal formula, but the weighting should be explicit enough that teams understand the choice.
Feasibility comes before desirability
The most important job may not be recoverable first. It could still lack a critical component, programme approval or test fixture. Scheduling it at the top because its consequence is high only creates another failed start.
Evaluate readiness before ranking execution. MRP Says Available. Why Is the Kit Still Short? shows why material must be usable and allocated, while The SMT Line Is Free. Why Can’t the Job Start? broadens readiness to tooling, programmes, people and downstream capacity.
A practical recovery list separates:
- ready now;
- ready by a credible time;
- conditionally ready with an accepted risk;
- blocked with no reliable recovery.
Only feasible jobs should compete for the immediate slot.
Model the consequence of each sequence
A recovery scenario should show more than revised completion dates. It should expose the disruption it creates.
Moving Job C forward may protect a shipment but add two changeovers. Splitting Job A may release urgent quantity but leave inefficient residue. Overtime may restore output while increasing labour cost and fatigue. Moving work to another site may require transport, programme validation and customer approval.
Compare a small number of realistic scenarios using:
- orders and quantities recovered;
- promises newly placed at risk;
- changeover and lost capacity;
- material conflicts;
- quality and technical risk;
- overtime, freight and subcontract cost;
- confidence in the required assumptions.
Scenario comparison prevents the team from calling any single-date improvement a recovery.
Protect the frozen window from constant intervention
If every escalation can reorder the next shift, feeder preparation, kitting, tooling and labour plans never stabilize. The factory creates the very readiness failures it is trying to solve.
Define a frozen dispatch window and an authority for breaking it. A change should require evidence of consequence and an assessment of affected jobs. Outside the frozen window, planning can optimize more freely. Inside it, stability has value.
Track how often the frozen sequence changes and why. Repeated customer priority changes may indicate weak order governance. Repeated material-driven changes may indicate inaccurate readiness. The measure should lead to root-cause improvement, not punishment for adapting to reality.
Use WIP age without making it the only rule
Old WIP deserves attention because it can become hidden behind new emergencies. The article WIP Is Moving. Why Is Lead Time Getting Longer? recommends queue age and hold reason as key visibility signals.
However, oldest-first is not always the best recovery rule. An old lot may remain blocked, while another job can be completed quickly and unlock downstream shipment. Use age as one consequence factor and require a clear plan for anything repeatedly deferred.
This balances flow with customer and business impact.
Coordinate decisions across functions once
Recovery fails when each department maintains its own priority list. Sales ranks customers, production ranks setup efficiency, purchasing ranks shortages and quality ranks holds. The line receives conflicting instructions.
Create one recovery review using shared data. The meeting should decide:
1. What changed from the last agreed plan?
2. Which promises are exposed and by how much?
3. Which jobs are genuinely ready?
4. What scenarios are feasible?
5. Which sequence best protects total business outcome?
6. Who owns each dependency and communication?
7. When will the decision be reviewed again?
Once agreed, the new sequence should update preparation tasks and customer commitments in the same operational model.
Communicate confidence, not false precision
During recovery, dates can become performative. Teams enter a precise time because the system requires one, even though a critical supplier or repair estimate remains uncertain.
Record assumptions and confidence. “Expected restart 14:00, dependent on fixture verification at 12:30” is more useful than an unexplained 14:00 promise. A planner can create a fallback sequence if the checkpoint fails.
This also improves customer communication. The business can explain what is known, what remains conditional and when the next reliable update will occur.
Connect recovery cost to the decision
Premium freight, overtime, split shipments, additional setup and emergency subcontracting can protect revenue but erode margin. If those costs are recorded separately, the company never learns which recovery patterns are economically damaging.
Link exceptional cost to the disruption, job and decision. Compare it with the consequence avoided. Over time, the data can justify preventive capacity, dual sourcing, tooling or process changes.
The Mars platform describes integrated production planning and financial visibility. That connection matters because a recovered delivery is not automatically a successful business outcome if the recovery cost is invisible.
Close the loop after stability returns
Recovery is incomplete until the factory learns why the plan failed and why the chosen response worked or did not work.
Review:
- original disruption and detection time;
- quality of readiness data;
- scenario assumptions versus actual results;
- customer promises protected or missed;
- secondary disruption created;
- total recovery cost;
- planning parameter or process change required.
If the same reason repeats, convert it into an earlier readiness check or a better capacity rule. The objective is not a perfect forecast. It is a planning system that becomes less surprised by known patterns.
A practical recovery scorecard
Useful measures include:
- time from disruption to agreed recovery plan;
- number of sequence changes inside the frozen window;
- orders recovered without creating another miss;
- planned versus actual recovery output;
- premium cost per recovered order;
- jobs selected but unable to start;
- customer communication before commitment breach;
- repeated disruption causes converted into preventive controls.
These measures reward stable, evidence-based recovery instead of visible expediting effort.
Frequently asked questions
Which late production order should be recovered first?
Choose among jobs that are genuinely feasible, then compare customer consequence, downstream dependency, cost, quality risk and recovery confidence. Earliest due date alone may not produce the best outcome.
Should the largest customer always receive priority?
Customer importance matters, but it should be considered alongside contractual impact, downstream dependencies, readiness and the disruption created for other commitments.
What is a frozen production window?
It is a near-term period in which the agreed sequence changes only under defined authority. Stability allows material, tooling and labour preparation to succeed.
Is overtime a good recovery strategy?
It can be, but the decision should include realistic output, labour availability, quality risk and total cost. Overtime should not hide a recurring planning constraint.
How should recovery decisions be documented?
Record the current facts, scenarios considered, chosen priority logic, assumptions, affected commitments, owners and review time. Link exceptional cost and actual result afterward.