Skip to content

Closing an incident

Closing an incident tells every phone the incident is over, stops check-in, and hands the incident to ERM Core as a draft loss event — no re-keying. The incident timeline, from the first warning to the close, is exported for the post-incident review.

Who may do it: the BCP head orders the close; the BCP head, the alternate or an activated operator enters it.

  1. Open Command and choose the hazard.
  2. Choose Closed and write the note — for example “Water has receded; all staff accounted for; normal working from Monday.”
  3. Optionally take down the incident’s announcement at the same time.
  4. Tap Save. Every staff phone is told the incident is closed.
Check-inStops. The last check-in of each person stays in the timeline.
RoomsThe team and incident rooms become read-only and stay with the incident record.
OperatorWith no incident open, the operator’s activation ends after the set number of hours.
Draft loss eventA draft loss event is created in ERM Core, linked to the incident. It carries no amounts: the Entity Risk Manager completes it — dates, cause, Basel event type and amounts — and validates it.
KRIThe close is recorded as the hazard’s KRI observation (Normal → Green).
  1. Open the closed incident and tap Timeline.
  2. The timeline lists every warning, level change and note, announcement, call-tree activation and coverage figure, and check-in counts by round — from the first warning to the close.
  3. Tap Export for Excel or PDF, with Thai fonts correct.

Use it for the post-incident review. Each lesson recorded there becomes an action item with an owner and a due date in the shared action register.

  • A note is required to close.
  • One draft per incident. The loss event is created once and linked both ways.
  • No amounts from BCP Core. Amounts, validation and the materiality tier are the Entity Risk Manager’s acts in ERM Core — see Validation and visibility.