Incident-to-closure: exception and recovery register
This register records the cases where the normal incident handling breaks down, and how you got back on track. A safety lead or owner keeps it to see which kinds of problem keep returning: hazards left in place, witnesses not heard, actions not done, claims not filed. Each row ends with a prevention step, not just a fix.
When to use it
Add a row whenever an incident cannot move to its next stage as planned, or when an earlier step turns out to have been missed. Review it at the monthly safety meeting, and read it before changing the incident procedure.
The template
| Exception type | What it looks like | Business effect | Usual recovery step | Owner |
|---|---|---|---|---|
| Hazard still present | Machine, floor or stock that caused the incident is back in use | Risk of a repeat injury | Stop use, tag it, repair and inspect | Site supervisor |
| Incomplete witness account | Only one person's version recorded | Weak cause analysis, dispute later | Take statements from remaining witnesses within a day | Safety lead |
| Required report or claim unverified | Nobody has confirmed whether a filing or claim applies | Missed obligation or lost claim | Confirm with the owner and your CA, then record the outcome | Owner |
| Action overdue | Due date passed, no update | Hazard stays open | Re-date with a reason or reassign | Safety lead |
| Evidence lost | Photos or the damaged part discarded early | Case cannot be reviewed | Reconstruct from witnesses, note what is missing | Site supervisor |
| Closure signed without check | Marked done by the action owner alone | False assurance | Independent check, correct the record | Safety lead |
Register entries:
| Date noticed | Incident no. | Exception type | What happened | Impact (₹ or days) | Recovery step | Done on | Prevention step |
|---|---|---|---|---|---|---|---|
How to fill it
- Exception type: use the listed types, and add a new one only when none fits.
- Impact: give a rupee figure or the number of days the case was delayed.
- Recovery step: what you did to get this case right.
- Prevention step: what changes in the procedure or training so the exception does not recur, with a person and a date.
- For an exception that involves a legal report: Check the current rule on the official portal or with your CA before acting.
Example row
| Date noticed | Incident no. | Exception type | What happened | Impact (₹ or days) | Recovery step | Done on | Prevention step |
|---|---|---|---|---|---|---|---|
| 9 October | INC-038 | Evidence lost | Cracked pulley thrown out before photographs | ₹5,200 insurer query, 9 days delay | Took statements and sketched the part from memory | 12 October | Tag and keep failed parts for seven days |
Review and sign-off
- The safety lead reviews new rows weekly. The owner reviews the full register monthly.
- Count rows by type each month and look for repeats.
- Escalate when the same type appears twice in a month, an exception has a money impact above your set limit, or a filing may have been missed.
Keeping it up to date
- Close a row only when the prevention step is done.
- Merge duplicate types and rename those that staff do not recognise.
- Keep the register for the period your CA or the law requires.
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 →