A crisis decision log is useful when it lets another authorized person reconstruct what was decided, by whom, on what evidence, and what would cause the decision to change. This resource focuses on the record itself: the minimum fields, writing standard and quality controls for a defensible decision entry during a live incident.
Minimum decision-log fields
| Field | What to record | Why it matters |
|---|---|---|
| Decision ID and time | Stable reference plus the time the decision was actually made; retain entry time separately if later. | Preserves chronology and supports handover. |
| Decision authority | Named person or accountable role and the authority being exercised. | Shows that the decision was made at the correct level. |
| Decision | A precise direction, scope, effective time and any limit. | Prevents vague entries such as “management agreed”. |
| Evidence available | Situation report, technical estimate, map, customer impact, legal advice or other source used. | Shows what was known at the time. |
| Assumptions and uncertainty | Important unverified facts, confidence and consequences if wrong. | Makes uncertainty visible rather than hiding it. |
| Alternatives considered | Material options rejected or deferred and the reason. | Supports later challenge for consequential choices. |
| Actions and owners | Resulting tasks, owner and due time. | Connects the decision to execution. |
| Review trigger | Time, threshold or new information that requires reconsideration. | Stops temporary decisions becoming permanent by accident. |
Write the entry for someone who was not in the room
Use direct operational language. “Evacuate Building B by 14:30; Facilities Lead owns completion” is stronger than “evacuation discussed.” Record the effective scope, constraints and authority. Do not add rationale after the event merely to make a weak record look complete.
Worked example
Decision: suspend customer appointments at Site A until 18:00 and divert urgent cases to Site B. Authority: Incident Director. Evidence: facilities assessment at 11:42 estimates four-hour electrical isolation; Site B confirms 35% spare capacity. Assumption: restoration estimate remains below six hours. Action: Customer Operations issues notifications by 12:15. Review trigger: reassess at 14:00 or immediately if the restoration estimate exceeds six hours.
Keep corrections auditable
Do not silently overwrite an earlier decision because facts changed. Add a superseding entry, reference the original ID and explain what new evidence changed the direction. If an entry was recorded late, preserve both the decision time and entry time.
Separate a decision from routine activity
A task completion, phone call or status update belongs in the activity log unless it changes priority, resources, risk acceptance, public position or response strategy. This distinction keeps consequential decisions visible. For the broader operating model covering activity logging, shift handover, reconciliation and retention, use the Crisis Decision and Activity Log Governance Guide.
Quality check before handover
- Can the next shift tell exactly what remains in force?
- Is the decision authority identifiable?
- Are important assumptions explicit?
- Do resulting actions have owners and due times?
- Is there a measurable trigger for review where the decision is temporary?
- Can supporting evidence be retrieved from the reference recorded?
Evidence for exercises and assurance
During an exercise, sample consequential decisions and measure entry latency, missing fields, unclear authority and overdue review triggers. A good result is not “the form was used”; it is that an independent reviewer can reconstruct the decision chain without interviewing the original participants.
Define decision classes and mandatory fields
Not every decision needs the same level of evidence. Define classes such as life-safety, regulatory, customer/public communication, financial commitment, service prioritization and tactical operating decisions. For higher-consequence classes require authority, alternatives considered, evidence source, affected services or stakeholders, risk accepted, action owner, review time and approval method. The classification should make logging faster during pressure because responders know the minimum evidence expected.
Capture uncertainty without weakening accountability
Crisis decisions are often made before facts are complete. Record what is known, what is assumed and what would invalidate the decision. A statement such as “supplier restoration is expected within four hours” should identify the source and a trigger for reassessment. Avoid presenting estimates as facts. When uncertainty is material, record the contingency that will be invoked if the assumption fails.
Control decision authority during handover
At every command or shift transition, identify open decisions, temporary approvals, delegated authorities, unresolved challenges and the next review trigger. The incoming lead should explicitly accept ownership of decisions still in force. Where authority was delegated because the normal approver was unavailable, record when that delegation expires and whether the decision requires later ratification.
Measure log quality with operational metrics
Useful measures include median time from decision to entry, percentage of high-consequence decisions with named authority, percentage with a review trigger, overdue review actions, corrections made without a superseding reference and decisions that cannot be traced to evidence. Trend these measures across exercises and incidents. A high entry count is not a quality measure; reconstructability and timely review are.
Test a challenged decision chain
During an exercise, introduce contradictory information after a major decision. Observe whether the team notices the change, identifies the affected decision, reassesses it through the correct authority, records the superseding rationale and communicates the changed direction to action owners. Then give the log to an independent reviewer. The test passes only when that reviewer can explain what was decided, why, by whom, what changed and which actions remained outstanding without relying on participants' memory.
Retain the minimum evidence package
For significant decisions, retain the log entry, supporting situation data, approval evidence, resulting actions and any later superseding entry under the incident record. Apply the organization's retention and access rules, especially where personal, legal or security-sensitive information is involved. Restrict editing after closure and preserve an audit trail for authorized corrections. This turns the decision log into reliable assurance evidence without encouraging responders to copy unnecessary sensitive material into the record.
Related BCM.Center resources: Crisis Decision and Activity Log Governance: Handover, Integrity and Assurance.