Fault-to-fix: exception and recovery register
This register records the faults that did not follow the normal path: a repair that failed, a promised date that was missed, or a part that could not be found. The person in charge of operations or service keeps it so that each exception has an owner, a recovery plan and a cost, and so patterns show before they become habits.
When to use it
Use it whenever a fault misses its promised time, reopens after being closed, needs a workaround, or costs a customer something. Read it weekly with the daily review sheets, and before you decide to replace a machine, change a vendor or revise a warranty promise. An exception is not a failure of the person who raised it. A register that people are afraid to write in stays empty, and the real cost of faults stays hidden.
The template
| Exception no. | Date raised | Fault no. | What went wrong | Type | Impact on customer or stock | Recovery action | Owner | Due date | Cost (₹) | Status and closing date |
|---|---|---|---|---|---|---|---|---|---|---|
| E-001 | Date | Fault number | Plain description | Missed time, reopened, workaround, wrong part, other | Who or what is affected | Step to put things right | Name | Date | Amount | Open, recovered or accepted loss |
| E-002 | ||||||||||
| E-003 | ||||||||||
| E-004 | ||||||||||
| E-005 | ||||||||||
| E-006 |
How to fill it
- Exception no.: number them in order and never reuse a number.
- Fault no.: link to the fault log so the full history can be found.
- What went wrong: one or two plain sentences. Say what happened, not who is to blame.
- Type: pick one word from the list so you can count types later.
- Impact on customer or stock: name the customer, order or item, and the delay in days.
- Recovery action: what will make the customer or the stock whole, such as a replacement, a credit note or a rework.
- Cost (₹): parts, labour, credit given and any goods scrapped. Add a note if the figure is an estimate.
- Status and closing date: close only when the recovery action is done. Use "accepted loss" only with the owner's approval.
Example row
| Exception no. | Date raised | Fault no. | What went wrong | Type | Impact on customer or stock | Recovery action | Owner | Due date | Cost (₹) | Status and closing date |
|---|---|---|---|---|---|---|---|---|---|---|
| E-014 | 21 Oct | 0398 | Water pump repaired on 18 Oct failed again in two days; wrong seal fitted | Reopened | Gupta Dairy order of 600 litres delayed by 2 days | Fit correct seal, send apology call, credit one delivery charge | Imran | 24 Oct | 3,400 | Recovered, closed 24 Oct |
Review and sign-off
- The operations or service head reviews the register every week and signs the page.
- The owner reads the monthly summary of exception types and total cost.
- Escalate to the owner the same day if an exception affects a major customer, involves safety, or if three exceptions in a month share the same cause.
Keeping it up to date
- Close exceptions on the day recovery is done, and write the lesson in the status column in one line.
- Once a quarter, count by type and cost and use the result to change the routine, not just to file it.
- Keep the register for the period your CA or the law requires, since credit notes and write-offs in it support your accounts.