lamp.
ResourcesPricingAbout
3 min readBy

Plan-to-deliver: exception and recovery register

This register captures every event that breaks the day's plan, and the steps taken to get delivery back on track. Planners, shift supervisors and operations managers use it so that disruption is recorded with its cost and its owner, not just handled by phone. It also shows which disruptions repeat, which tells you where the plan itself is weak.

When to use it

Make an entry as soon as something forces a change to the daily plan: a rush order arrives, an operator is absent, a machine stops, material is late, or two jobs need the same resource at the same time. Fill in the recovery step before the shift ends.

The template

Exception typeWhat to record about the effectFirst recovery stepOwnerEvidence to attachEscalate when
Last-minute rush orderOrder, quantity, jobs that will be pushed backCheck free capacity, then accept, refuse or agree a later datePlannerDemand forecast update, customer messageA pushed-back job has a firm customer date
Worker absentName, skill missing, hours lostMove a trained person or reassign work to another shiftShift supervisorAttendance, capacity boardSkill cannot be covered for more than a day
Equipment unavailableMachine, expected repair time, jobs affectedReroute to another machine or outsource the operationOperations managerBreakdown note, daily planRepair time is unknown
Material late or shortItem, shortfall, new arrival dateSubstitute, part-ship or reorder by a faster routePlannerSupplier message, stock countSubstitution needs customer approval
Schedule clashWhich jobs, which resource, who decidedRank the jobs by customer date and move the lower onePlannerDaily plan before and afterBoth jobs have the same firm date
Plan not met at end of dayGap in units or hours, reasonPlace the gap in tomorrow's plan, and tell the customer if dates moveShift supervisorProgress notesGap carries into a third day

How to fill it

  • Exception type: choose the closest line or add one, and reuse the wording so that you can count each type monthly.
  • What to record about the effect: units, hours or rupees. "Production loss" is not enough.
  • First recovery step: what was done first, not what went wrong.
  • Owner: one person who will see it through.
  • Evidence to attach: the plan or note that shows the change. Copy the row for each event and add the date logged, case or job number and the next check date.

Example row

JobDate loggedExceptionEffectRecovery stepOwnerNext check
J-21809/11/2026Equipment unavailableLathe 3 down, 6 machine hours lost, ₹14,400 of jobs delayedOutsourced 2 hours of turning to a local workshop, remainder moved to Lathe 1Operations manager10/11/2026

Review and sign-off

  • The shift supervisor reviews open entries at every huddle, and the operations manager reviews the whole register weekly.
  • Close an entry only when the plan is back on track, and write the closing date and what fixed it.
  • Escalate to the owner when the same exception type appears three times in a month, or when a firm customer date is lost.

Keeping up to date

  • Keep closed registers for the period your CA or the law requires.
  • At month end, count entries by type and decide whether to change safety stock, spare capacity or maintenance timing.
  • Do not delete old rows. Correct a mistake with a new dated line.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →