Crisis City Incident Log

A fast, disciplined way to capture decisions, actions and rationale in real time during an incident or exercise. Every entry is time-stamped and locked as it is written, and the record saves into your own systems — never onto ours.

Locked and time-stamped

Every entry is stamped and sealed as it is written, and chained so any later tampering shows.

Loggist discipline built in

Fact, assessment and rumour marking, decision rationale and clean handover, guided under pressure.

Stored in your own systems

Records save straight to your own SharePoint or Drive. Crisis City holds nothing.

Sign in

Use your organisation account, or try it on this device.

New to Crisis City? Request access →

Sign-in uses your own organisation account. Crisis City never sees your password and stores none of your incident data.

OPERATIONAL RESILIENCE

Decision Log

Fast, contemporaneous, append-only record keeping. Type the entry, tag it, hit Enter — and you're ready for the next one. Real-time loggist discipline at logging speed.

Incident / exercise name

Reference number

Loggist name (you)

Logging on behalf of (chair / role)

Mode

Location

Agreed abbreviations (optional — short form + what it means)

Who's involved in the response? (name + initials — used to tag who does what)

Entries are time-stamped and locked as you write them, and chained so any later tampering shows. Your log is saved to your own location — this device, or your organisation's SharePoint/Drive when you sign in — never on Crisis City systems.

INCIDENT DASHBOARD

Welcome to the Crisis City Incident Log Tool

A fast, disciplined way to keep a defensible record during an incident or exercise — so the account of what happened, what was decided and why doesn't rest on a spreadsheet and the memory of whoever was holding the pen. Open a new incident, log in real time, hand over cleanly, and close it off with a signed report you can stand behind later.

or open an existing one below

Locked and time-stamped

Every entry is stamped the moment it's written and can't be edited or deleted. Corrections are recorded as visible amendments, so the log still holds up when it's read back months later.

The discipline, built in

Fact / assessment / rumour marking, decision rationale, handover and takeover are part of the tool — so the loggist follows good practice under pressure without having to hold it all in their head.

A report you can hand over

Close the log and it produces a clean, structured PDF — full timeline, open actions, the people involved — ready to file, share, or take into a review or inquiry.

It replaces the spreadsheet

A Word doc or Excel sheet can be changed after the event and leans entirely on the user. This keeps the record contemporaneous and takes the weight off the individual.

How it works

Open an incident

Name it, note who's involved, and you're logging within seconds.

Log in real time

Type each entry, tag it, press enter. It's locked and time-stamped the moment you save.

Hand over cleanly

At shift change, record a handover and pass the pen — the log carries on unbroken.

Close and sign off

Finish with a reason and a sign-off, then export a structured PDF report for your records.

Your incidents

Active incidents

live & in-progress logs

Archived incidents

closed & signed off — read-only, open to export

DECISION LOG

— Ref: — Loggist: — — --:--:--
elapsed 00:00:00

New entry

Type (optional · sticks for next entry)

Decision Action Info Amend

Mark (optional · resets each entry)

Fact Assessment Rumour “ Verbatim ⟲ Reconstructed

Who (optional · who said / did it)

Amends which entry?

+ event happened at a different time

+ attach a file (photo of notes, personal log, document)

Enter save · Shift+Enter new line

🔒

Log closed

This signed-off log is saved and now appears under Archived incidents on the dashboard, where it stays read-only and can be exported any time.

Loggist reference

F / A / R — mark every entry

FACT verified / reliable source · ASSESSMENT your interpretation · RUMOUR unconfirmed.
Never let an assessment look like a fact — they look identical six months later.

The four parts of a decision

1 Situation — what was understood at the time.
2 Options — considered & rejected (who raised, why rejected).
3 Decision — exact wording, time, decider, conditions.
4 Rationale — reason, evidence, risk being mitigated.
Type all four into the box. Especially the why.

Known / Assumed / Unknown

At each decision point capture: Known (verified facts), Assumed (working hypothesis), Unknown (acknowledged gaps). Capturing what you don't know protects the chair from later accusations of recklessness.

5WH — the capture checklist

Who · What · When (to the minute) · Where · Why · How. If a significant entry is missing one, add it before moving on.

Real-time discipline

Target lag 60–90 seconds. Time the event, not the moment you write it. If you missed it, mark Reconstructed — reconstructed entries carry less weight and should be flagged, never disguised.

Corrections

Never erase. Never overtype. Tag Amend, pick the original entry, and write the correction as a new locked entry. Quietly fixing entries destroys evidential value.

What to record verbatim

The decision itself, the rationale, options rejected, senior quotes under pressure, and facts stated by external sources. Mark Verbatim and use the exact words.

Running log

0 entries 0 open actions

No entries yet. Type the first entry and press Enter.

Crisis City Incident Log

Sign in

Decision Log

Welcome to the Crisis City Incident Log Tool

Locked and time-stamped

The discipline, built in

A report you can hand over

It replaces the spreadsheet

How it works

Open an incident

Log in real time

Hand over cleanly

Close and sign off

Your incidents

Active incidents

Archived incidents

New entry

Running log

Shift handover

Who is taking over the log?

Attachment

Add a person to the response

Add an abbreviation

Close the log