Evidence and reporting

Record what happened, who acted and what was confirmed.

Everything reported, assigned, confirmed and changed during the operation automatically becomes the basis for this report. Afterwards you have evidence, not a debate.

Report R1 · evidence and exportFictional example
21:14Crew · Security Zone ANEW
21:15CommandIN PROGRESS
Evidence
3 incidents · v1 to v5 archived
Export
Internal · client
Reporting

From decision to evidence, without reconstructing afterwards

What is decided during an event stays connected to the reason, the person and the outcome. Not because someone wrote it down later, but because it was recorded while the work happened.

  1. 1

    Decision

    What was decided, why, and by which role. A reason is mandatory: a decision without one cannot be explained afterwards.

    South entrance closed due to crowding near the bicycle parking.

  2. 2

    Action

    What was actually done, and by whom. An action without an owner stays undone.

    Two stewards moved to the east side, audience rerouted.

  3. 3

    Evidence

    An observation, photo or confirmation from the person involved. What wasn't recorded says exactly that: "nothing was recorded about this", not "nothing to report".

    Photo of the new setup, confirmed by the security lead.

  4. 4

    Next edition

    Improvement points carry over to next time as explicit items, instead of being buried in an evaluation document.

    Move the bicycle parking or open a second entrance above 12,000 visitors.

FloorPilot does not assess anything and does not declare anything safe. It records what happened, so you can account for it yourself to the parties responsible.

Append-only

The audit log is only ever added to.

TimeRoleActionVersionStatus
13:05Event managerbriefing version 4 publishedv4CURRENT
13:22Security Zone Arole confirmed via crew appv4CONFIRMED
21:14Crew · Security Zone Aincident reported: first aid, Zone AINC-014NEW
21:15Commandincident assigned to first-aid post 1INC-014IN PROGRESS
21:24First-aid post 1status updated after response on siteINC-014RESOLVED
21:31Security Zone Broute update read and confirmedv5CONFIRMED
21:40Commandincident closed with short evaluationINC-014CLOSED
23:58Event managerreport generated for clientR1SHARED
North Quay Festival 2026 · Report R1Fictional example
Incident timeline
3 incidents, all resolved
Change register
Briefing v1 to v5 archived
Confirmations
Sent, read and confirmed recorded separately
Evaluation
Per topic, configurable per operation
✓ Shared with client · municipal summary ready
Shared views

You decide per recipient what's visible.

  • Internal report
    The full operation, for your own team.
  • Client view
    What the client may see, without sensitive detail.
  • Municipal summary
    A traceable overview when it fits.
  • Export
    A complete package with source data and audit.