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
Append-only
The audit log is only ever added to.
| Time | Role | Action | Version | Status |
|---|---|---|---|---|
| 13:05 | Event manager | briefing version 4 published | v4 | CURRENT |
| 13:22 | Security Zone A | role confirmed via crew app | v4 | CONFIRMED |
| 21:14 | Crew · Security Zone A | incident reported: first aid, Zone A | INC-014 | NEW |
| 21:15 | Command | incident assigned to first-aid post 1 | INC-014 | IN PROGRESS |
| 21:24 | First-aid post 1 | status updated after response on site | INC-014 | RESOLVED |
| 21:31 | Security Zone B | route update read and confirmed | v5 | CONFIRMED |
| 21:40 | Command | incident closed with short evaluation | INC-014 | CLOSED |
| 23:58 | Event manager | report generated for client | R1 | SHARED |
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 reportThe full operation, for your own team.
- Client viewWhat the client may see, without sensitive detail.
- Municipal summaryA traceable overview when it fits.
- ExportA complete package with source data and audit.