Design-to-launch: exception and recovery register
This register records everything that goes off plan between the product brief and the launch, such as a failed sample, a late supplier or a cost that crept up, and how each one was recovered. Project leads, quality staff and purchase staff use it so that problems are visible early and lessons are not lost once the launch is done.
When to use it
Log an item as soon as a result, date or cost moves outside what the project plan allows. Use it during design and trial, and again in the first month after launch when early customer feedback exposes faults.
The template
Part 1: common exception types and a standard recovery path.
| Exception type | Typical cause | First response | Recovery step | Owner |
|---|---|---|---|---|
| Sample failed a test | Material or dimension off | Stop further trials with the same set-up | Find the cause, change one thing, retest | Quality lead |
| Change after the specification was fixed | Customer or owner request late | Record the change and its cost and time effect | Approve or hold with the owner's decision | Project lead |
| Supplier delay | Supplier capacity or order gap | Ask for a written firm date | Place a backup order or switch supplier | Purchase lead |
| Cost above target | Material price rise, waste, extra step | Recalculate the cost per unit | Rework the design or reset the price | Accounts lead |
| Launch date slip | Combination of the above | Tell everyone affected the new date | Re-plan tasks and confirm customer messages | Project lead |
| First-lot defect | Process not stable | Hold the lot and sort stock | Rework or scrap, then fix the process | Operations head |
Part 2: the register.
| Ref | Date raised | Product or service | What happened | Impact in ₹ | Recovery plan | Owner | Target date | Closed on |
|---|---|---|---|---|---|---|---|---|
| DX-001 | ||||||||
| DX-002 |
How to fill it
- Ref: a running number, never reused.
- What happened: write the observation, not the guess about the cause. The cause goes in the recovery plan once found.
- Impact in ₹: include scrap, rework, extra freight, expedite charges and the margin lost if the price had to change.
- Recovery plan: one or two concrete steps with a person against each.
- Closed on: enter the date only after a retest or a delivered replacement proves the fix worked.
Example row
| Ref | Date raised | Product or service | What happened | Impact in ₹ | Recovery plan | Owner | Target date | Closed on |
|---|---|---|---|---|---|---|---|---|
| DX-007 | 12 Oct 2026 | Steel tiffin set | 3 of 10 sample units leaked at the lid seam during the water test | 4,200 for scrapped samples and a second trial | Change the gasket supplier, make 10 new samples, repeat the test | Quality lead | 22 Oct 2026 |
Review and sign-off
- The project lead reviews open lines every week and the owner signs the register at the launch decision.
- Review weekly during the project and monthly in the first quarter after launch.
- Escalate when the same exception type appears twice, when a line passes its target date, or when a fix needs spending above what the project lead can approve.
Keeping it up to date
- Keep closed lines, since they are the best guide for the next launch's checks and costs.
- At the end of the project write the top three causes and one preventive step for each.
- Retain the register for the period your CA or the law requires, along with test records and supplier correspondence.
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 →