lamp.
ResourcesPricingAbout
3 min readBy

Order-to-delivery: exception and recovery register

This register records every order that leaves the normal path between order entry and handover, and what was done to bring it back. The order desk, planning supervisor and dispatch or service lead use it so that a problem has a named owner and a next check date instead of living in phone calls. Over a few months it also shows which problems repeat.

When to use it

Make an entry the moment an order cannot follow the plan: the customer changes the specification, material or a person is not available, a quality check fails, or nobody is there to receive the delivery. Do not wait until the end of the day.

The template

Exception typeWhat to record about the effectFirst recovery stepOwnerEvidence to attachEscalate when
Specification changed after order was acceptedExtra cost in ₹, new quantity, new promised dateRe-validate the order and get written confirmation from the customerOrder deskRevised sales order, customer messageCustomer disputes the extra cost
Material or stock not availableItem, shortfall, expected arrival dateCheck alternatives, buy locally or tell the customer the new datePlanning supervisorStock check note, supplier messageNew date is later than the customer can accept
Slot, shift or machine lostWhich booking, how many hours lostRebook the nearest free slot and update the job cardDispatch or service leadUpdated job cardTwo or more orders affected
Work finished lateDays late, reasonAgree a revised handover time with the customerOrder deskJob card, call noteCustomer asks for a discount or cancels
Quality check failedDefect, quantity affectedHold dispatch, rework and recheckPlanning supervisorQuality check sheetRework needs a second recheck
Customer unavailable at handoverAttempts made, extra transport or visit costReschedule with a fixed time and note the contact personDispatch or service leadDelivery note, call logThird failed attempt

How to fill it

  • Exception type: pick the nearest line, or add a new one. Use the same wording every time so that counts are reliable.
  • What to record about the effect: a rupee amount, a number of days or a quantity. Avoid vague words such as "delay".
  • First recovery step: the action taken, not the cause.
  • Owner and Escalate when: one person, and the point at which the owner of the business must be told.
  • Evidence to attach: the paper or message that shows the problem and the fix. Copy the row for each occurrence and add the case ID and date logged.

Example row

CaseDate loggedExceptionEffectRecovery stepOwnerNext check
OD-105706/11/2026Material not available200 units short, ₹18,000 of orders heldBought 200 units locally, new date 09/11/2026Planning supervisor08/11/2026

Review and sign-off

  • The planning supervisor checks all open rows each morning, and the owner reviews the register weekly.
  • Close a row only when the evidence shows the order was handed over or cancelled, and write the closing date.
  • Escalate any row that passes its next check date twice, or any exception that touches more than one customer.

Keeping up to date

  • Keep closed registers for the period your CA or the law requires.
  • Once a month, count rows by exception type and decide whether a repeating problem needs a change in how orders are accepted or planned.
  • Do not delete or rewrite 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 →