Idea-to-improvement: exception and recovery register
This register records what happens when an improvement idea causes a problem or fails to deliver: quality gets worse, a trial overruns, a target is missed or staff stop following the new method. The owner or operations head keeps it so that trials can be paused, reversed or repaired quickly, and so the same mistake is not repeated on the next idea.
When to use it
Use it whenever a trial or rollout produces a result worse than the baseline, runs past its planned time, causes a customer complaint or requires a rollback. Read it before you approve a new trial in the same area, to see what has already gone wrong there. Trials will sometimes fail, and that is acceptable. What is not acceptable is a failed trial that runs on unnoticed because nobody wrote down that the numbers got worse.
The template
| Exception no. | Date raised | Idea no. | What went wrong | Type | Who or what is affected | Immediate action | Recovery or rollback plan | Owner | Cost (₹) | Status and date closed |
|---|---|---|---|---|---|---|---|---|---|---|
| X-001 | Date | Idea number | Plain description | Quality drop, overrun, missed target, pushback, extra cost | Line, customer, team or stock | Step taken at once | Plan to restore or fix | Name | Amount | Open, rolled back, fixed or accepted |
| X-002 | ||||||||||
| X-003 | ||||||||||
| X-004 | ||||||||||
| X-005 | ||||||||||
| X-006 |
How to fill it
- Exception no.: number in order and never reuse a number.
- Idea no.: link to the idea log so the original expectation and baseline can be found.
- What went wrong: describe the effect in numbers if you can, such as rejects per 100 units, minutes lost or ₹ wasted.
- Type: choose from your list so you can count by type later.
- Immediate action: what was done the same day to limit harm, for example stopping the trial on one line.
- Recovery or rollback plan: how and when the old method returns, or how the new one will be fixed.
- Cost (₹): material, labour, credits and lost sales, with a note if estimated.
- Status and date closed: close only after the plan is done and the reading is back at baseline or better.
Example row
| Exception no. | Date raised | Idea no. | What went wrong | Type | Who or what is affected | Immediate action | Recovery or rollback plan | Owner | Cost (₹) | Status and date closed |
|---|---|---|---|---|---|---|---|---|---|---|
| X-007 | 29 Oct | 019 | New shorter oven time raised under-baked rejects from 2 to 9 per 100 | Quality drop | Bakery line 1, 3 retail orders | Stopped the trial, returned to old timing | Retrain the shift on the old setting, retest at an interim time on one tray batch | Farah | 7,800 | Rolled back, closed 31 Oct |
Review and sign-off
- The operations head reviews the register weekly and signs it.
- The owner reads a monthly total of cost and count by type.
- Escalate to the owner at once if an exception affects customers or safety, or if two trials in the same area fail in a quarter.
Keeping it up to date
- Close entries promptly and add one line on the lesson, so it is available when the next idea is assessed.
- Review the register each quarter and change your trial rules, for example require a smaller pilot, where patterns show.
- Keep the register for the period your CA or the law requires, since write-offs and credits recorded here support your accounts.