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 type | What to record about the effect | First recovery step | Owner | Evidence to attach | Escalate when |
|---|---|---|---|---|---|
| Specification changed after order was accepted | Extra cost in ₹, new quantity, new promised date | Re-validate the order and get written confirmation from the customer | Order desk | Revised sales order, customer message | Customer disputes the extra cost |
| Material or stock not available | Item, shortfall, expected arrival date | Check alternatives, buy locally or tell the customer the new date | Planning supervisor | Stock check note, supplier message | New date is later than the customer can accept |
| Slot, shift or machine lost | Which booking, how many hours lost | Rebook the nearest free slot and update the job card | Dispatch or service lead | Updated job card | Two or more orders affected |
| Work finished late | Days late, reason | Agree a revised handover time with the customer | Order desk | Job card, call note | Customer asks for a discount or cancels |
| Quality check failed | Defect, quantity affected | Hold dispatch, rework and recheck | Planning supervisor | Quality check sheet | Rework needs a second recheck |
| Customer unavailable at handover | Attempts made, extra transport or visit cost | Reschedule with a fixed time and note the contact person | Dispatch or service lead | Delivery note, call log | Third 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
| Case | Date logged | Exception | Effect | Recovery step | Owner | Next check |
|---|---|---|---|---|---|---|
| OD-1057 | 06/11/2026 | Material not available | 200 units short, ₹18,000 of orders held | Bought 200 units locally, new date 09/11/2026 | Planning supervisor | 08/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 →