lamp.
ResourcesPricingAbout
3 min readBy

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 typeWhat it looks likeBusiness effectUsual recovery stepOwner
Hazard still presentMachine, floor or stock that caused the incident is back in useRisk of a repeat injuryStop use, tag it, repair and inspectSite supervisor
Incomplete witness accountOnly one person's version recordedWeak cause analysis, dispute laterTake statements from remaining witnesses within a daySafety lead
Required report or claim unverifiedNobody has confirmed whether a filing or claim appliesMissed obligation or lost claimConfirm with the owner and your CA, then record the outcomeOwner
Action overdueDue date passed, no updateHazard stays openRe-date with a reason or reassignSafety lead
Evidence lostPhotos or the damaged part discarded earlyCase cannot be reviewedReconstruct from witnesses, note what is missingSite supervisor
Closure signed without checkMarked done by the action owner aloneFalse assuranceIndependent check, correct the recordSafety lead

Register entries:

Date noticedIncident no.Exception typeWhat happenedImpact (₹ or days)Recovery stepDone onPrevention 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 noticedIncident no.Exception typeWhat happenedImpact (₹ or days)Recovery stepDone onPrevention step
9 OctoberINC-038Evidence lostCracked pulley thrown out before photographs₹5,200 insurer query, 9 days delayTook statements and sketched the part from memory12 OctoberTag 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 →