{"id":"edxl-situation-reporting","slug":"edxl-situation-reporting","title":"EDXL Situation Reporting","description":"A situation report is only useful if everyone reading it can quickly understand what changed, when it was issued, and whether it supersedes the last one. Free-text emails and chat messages can move quickly, but they do n","category":"analytics","tags":["analytics"],"lastModified":"2026-04-22","source_ref":"content/modules/edxl-situation-reporting.md","url":"/developers/edxl-situation-reporting","htmlPath":"/developers/edxl-situation-reporting","jsonPath":"/api/docs/modules/edxl-situation-reporting","markdownPath":"/api/docs/modules/edxl-situation-reporting?format=markdown","checksum":"b345789a2665955ea3853598f30779f1d3ca3efb3d0cb7081176312e1db41743","headings":[{"id":"overview","text":"Overview","level":2},{"id":"key-features","text":"Key Features","level":2},{"id":"use-cases","text":"Use Cases","level":2},{"id":"integration","text":"Integration","level":2},{"id":"open-standards","text":"Open Standards","level":2}],"markdown":"# EDXL Situation Reporting\n\n## Overview\n\nA situation report is only useful if everyone reading it can quickly understand what changed, when it was issued, and whether it supersedes the last one. Free-text emails and chat messages can move quickly, but they do not give command teams or partner agencies a dependable structure for ongoing incident updates.\n\nThe EDXL Situation Reporting module provides a structured way to issue, catalogue, and review formal incident sitreps. It supports sequenced reports for a given incident, captures who issued the update and when, and gives services a standards-based reporting pattern that works for live incidents, multi-agency coordination, and exercises.\n\n```mermaid\nflowchart TD\n    A[Incident Update Needed] --> B[SitRep Issued]\n    B --> C[Sequence Number and Distribution Type]\n    C --> D[Incident SitRep List]\n    D --> E[Command and Partner Review]\n    E --> F[Next SitRep Builds on Prior State]\n```\n\n**Last Reviewed:** 2026-04-22\n**Last Updated:** 2026-04-22\n\n## Key Features\n\n- **Incident-Scoped SitReps**: Keep situation reports tied to the incident they describe rather than a general message stream.\n- **Sequenced Reporting**: Maintain a clear report order so users know which update supersedes the previous one.\n- **Issued-By Context**: Preserve who issued the report and when it became current.\n- **Distribution Type Awareness**: Support different reporting audiences and dissemination patterns without rewriting the reporting model.\n- **Operational Review View**: Give command teams a simple way to review the current and prior structured updates for an incident.\n\n## Use Cases\n\n- **Control Room Incident Updates**: A duty officer publishes a formal sitrep after a major operational change.\n- **Multi-Agency Coordination**: Partner agencies review the same structured incident update rather than relying on ad hoc message summaries.\n- **Shift Handover**: Incoming command staff read the latest sequenced sitreps to understand the current operational state.\n- **Exercise and Training Reporting**: Exercise control teams issue structured sitreps during a scenario for realism and later review.\n\n## Integration\n\n- **Operational Picture and Command Workflows**: Sitreps can complement the live picture with formal narrative updates.\n- **Unified Command and Major-Incident Workflows**: Structured reports can sit alongside checklists, command roles, and resource requests.\n- **Notification and Distribution Services**: A sitrep can be pushed out through the service's wider information-sharing channels.\n- **Archive and After-Action Review**: Sequenced sitreps provide a clean narrative spine for later review.\n\n## Open Standards\n\n- **OASIS EDXL-SitRep**: the module aligns with the emergency data standard for formal structured situation reporting.\n- **EDXL Distribution Element**: sitreps can align with the broader EDXL message-distribution model across agencies.\n- **CAP (Common Alerting Protocol)**: deployments can pair formal sitreps with alert-distribution workflows where incident communications need both.\n- **ISO 8601**: report issue times and sequencing context use a standard date-time representation.\n- **RFC 8259 JSON**: structured sitrep payloads can be exchanged in a standard machine-readable format where JSON transport is used.\n"}