A crisis record is more than a decision form. During a prolonged incident, teams need a controlled chronology that survives shift changes, technology degradation, corrections and later assurance. This guide focuses on governance of the combined decision and activity record: who maintains it, how entries are reconciled, how integrity is protected and how the record supports handover and after-action review.
Define two record types in one operating model
The activity log records notable events, messages, actions and status changes. The decision log records choices that alter priorities, resources, risk acceptance, public position or response strategy. They may appear in one timeline, but keep distinct entry types and mandatory fields so consequential decisions are not buried among routine updates. For the field-level decision entry, use the Crisis Decision Log Template.
Assign logging accountability by shift
Nominate a command-support or log-keeper role for each operational period. That role checks timestamps, references, missing owners and ambiguous entries but does not invent rationale. The incident lead remains accountable for decisions. At shift change, explicitly transfer responsibility for the live record and unresolved quality issues.
Run a controlled handover
The outgoing and incoming teams should review open decisions, assumptions awaiting validation, overdue actions, pending approvals, active constraints and decisions approaching a review trigger. Record the handover time and incoming acknowledgement. This turns the log into an operational control rather than a historical diary.
Protect chronology and audit integrity
- Use synchronized time and stable entry identifiers.
- Restrict edit/delete rights and preserve an audit trail for corrections.
- Supersede material decisions rather than rewriting history.
- Reference source evidence such as situation reports, technical assessments and approvals.
- Distinguish confirmed facts, unverified reports and analytical judgments where confidence affects action.
Plan for loss of the primary logging system
Maintain a controlled offline method with pre-numbered or otherwise traceable records, a known time source and a reconciliation procedure. When systems return, preserve original timestamps and source identifiers. Do not collapse multiple offline entries into one summary that destroys chronology.
Reconcile the operational record
At defined intervals, compare the log with task tracking, situation reports, communications and major technical events. Investigate missing consequential decisions and actions that appear in one system but not another. Reconciliation is particularly important before executive briefings and at the end of an operational period.
Control sensitive information and retention
Apply legal, privacy, security and investigation requirements without preventing authorized command roles from accessing operationally necessary information. Avoid unnecessary personal data and speculation. Define retention, legal hold and export responsibilities before an incident so the authoritative record is not lost when temporary collaboration spaces are closed.
Assurance measures
| Measure | What it reveals |
|---|---|
| Entry latency | Whether material events and decisions are captured while still operationally useful. |
| Decision completeness | Percentage of sampled decisions with authority, rationale/evidence, actions and review trigger where applicable. |
| Open-action reconciliation | Whether tasks in the log and task tracker agree at handover. |
| Correction traceability | Whether changes preserve the original entry and reason. |
| Handover exceptions | Unresolved decisions, assumptions or overdue actions accepted by the incoming shift. |
After-action use
Use the preserved chronology to examine decision latency, information gaps, escalation effectiveness and whether actions produced the expected result. Improvement actions should reference the relevant log entries so lessons remain traceable to evidence instead of becoming generic observations.
Reviewer challenge
Select one operational period and reconstruct it without interviewing participants. Verify that major events, consequential decisions, resulting actions, corrections and handover are traceable across the authoritative record. If the sequence cannot be reconstructed, improve governance before relying on the log for regulatory, legal or management assurance.
Make the log decision-grade evidence
A crisis log should let a new shift understand what happened, what was decided, why it was decided and what remains unresolved without reconstructing events from chat messages. Use consistent timestamps, named decision owners, source references, assumptions, actions, due times and status. Distinguish verified facts from reports that are still being checked, and never overwrite an earlier entry simply because later information changed the picture.
For significant decisions, capture the options considered, constraints, consequence of delay and the authority used. Corrections should be appended with a reference to the original entry so chronology and accountability remain intact. Sensitive personal, security or legal information should be handled according to access and retention rules rather than copied indiscriminately into the operational log.
Design for handover, outage and assurance
At shift handover, reconcile open actions, unresolved assumptions, stakeholder commitments, next decision deadlines and the current operating picture. The incoming lead should explicitly accept the handover and identify any item requiring immediate revalidation. If the primary logging platform fails, an approved offline or alternate method should preserve timestamps and later support controlled merge-back without duplicate or lost records.
Test the log during exercises by asking an independent observer to reconstruct a major decision from the record alone. Failure criteria include missing authority, unclear timing, conflicting action status, unverifiable sources or an inability to determine why an option was rejected. Treat those failures as capability gaps and retest after remediation.
Retention and post-incident review should preserve the evidential chain while limiting unnecessary sensitive data. The final record should support lessons learned, regulatory or legal review where applicable, and improvement tracking without turning the live crisis log into an unstructured document repository.
Control quality during high-tempo operations
Assign a log owner for each operational period and use a short quality check at agreed intervals: missing owners, overdue actions, unresolved conflicting facts, decisions without rationale and external commitments without follow-up. This should not slow response; it prevents the record from degrading precisely when the volume of events increases.
For major incidents, preserve exports or snapshots at handover and closure points so later review can demonstrate what the team knew at the time. Access to the authoritative record should be role-based, and any distributed copies should be controlled to reduce conflicting versions.
Related BCM.Center resources: Crisis Decision Log Template: Capture Defensible Decisions in Real Time.