AKIRA / Practical perspective
Keeping a crisis decision log
A practical guide to recording decisions, evidence, authority and review triggers without turning the response into an administrative exercise.
Published
Record the decision, not every conversation
A crisis decision log should help the next decision-maker understand what was authorised and why. It is not a transcript, a substitute for operational records, or a retrospective defence of every choice. Its purpose is to preserve the information available at the time, the limits of that information, and the reasoning behind a consequential decision. Start it early, even if the first entries are incomplete.
Appoint a log owner and an alternate. Agree where the authoritative record lives, who can read or amend it, and how decisions made outside scheduled meetings reach the owner. Choose a tool the response team can access reliably within approved information controls. A simple structured record is more useful than an elaborate template that nobody maintains during a shift change.
Use a small, repeatable entry
Give each decision a unique reference. Record the time and time zone, the issue requiring a decision, the accountable decision-maker, and the authority under which they acted. Add the options considered, the chosen course, the rationale, and the information relied upon. Identify material assumptions, unresolved questions, and any advice still outstanding. Distinguish a decision from a proposal awaiting approval.
Close the entry with the action owner, the next deadline, and the conditions for review. Link to supporting records rather than copying sensitive material into multiple locations. If a decision was deferred, record who deferred it, the reason, what information is needed, and when it must return. An unresolved decision needs ownership just as much as an authorised action does.
Make uncertainty and alternatives visible
The following example is illustrative, not an account of an AKIRA engagement. An organisation is considering whether to pause a supplier-dependent process after conflicting reports of a disruption. The entry might state that the operations lead authorised a temporary pause, based on a verified loss of availability at one site and an unverified report concerning another. Continuing unchanged and switching immediately to an alternative were considered but not selected.
The rationale should explain the trade-off: a short pause allows verification before a wider commitment, while creating its own continuity consequences. Record which team will verify the second report, who will assess the alternative, and when the decision returns for review. Do not describe the unverified report as an established fact. The entry should make it possible to change course without rewriting what leadership knew.
Connect the record to the response rhythm
At each briefing, review decisions due, assumptions that have changed, and actions that have passed their review point. Ask whether execution is proceeding within the authorised boundaries. A task marked complete does not necessarily mean the decision has achieved its intended effect. Confirm what evidence the accountable owner will provide and whether any resulting exposure needs a further leadership decision.
Keep coordination distinct from execution. An adviser may help structure the log, challenge gaps, and coordinate reporting or provide agreed oversight. The organisation's authorised leaders retain decision authority; accountable teams and appropriately appointed specialist providers carry out direct operational work. Record those roles separately so that a coordinator is not inadvertently treated as the owner of an action they cannot authorise or deliver.
Preserve a usable record as conditions change
Correct errors transparently and retain the earlier entry when a decision is superseded. Link the replacement decision to its predecessor and explain what changed: evidence, assumptions, constraints, or authority. Do not silently edit the original rationale to match later knowledge. During handover, highlight open decisions and imminent review triggers rather than asking the incoming team to reconstruct them from the full history.
Ask appropriately qualified advisers about confidentiality, access, retention, and any applicable preservation requirements. Do not assume that a label alone determines the legal treatment of a record. At stand-down, assign custody of the log, transfer continuing actions to ordinary governance, and identify learning points separately from the contemporaneous account. The test is practical: can a responsible leader see what remains authorised, what needs reconsideration, and who must act next?
Related services
To discuss how this guidance relates to your organisation, contact AKIRA.
Further reading
The First 60 Minutes: A Crisis Readiness Checklist
Friday the 13th: A Weekend of Crises—and a Test of Preparedness
The first 24 hours of a corporate crisis
What boards should expect from a Red Team assessment
Cross-border crisis decisions: keeping authority and context intact