Knogin
[Analytics]

EDXL Situation Reporting

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.

Module metadata

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.

Back to All Modules

Source reference

content/modules/edxl-situation-reporting.md

Last Updated

Apr 22, 2026

Category

Analytics

Content checksum

b345789a2665955e

Tags

analytics

Overview#

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 not give command teams or partner agencies a dependable structure for ongoing incident updates.

The 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.

Diagram

flowchart TD
    A[Incident Update Needed] --> B[SitRep Issued]
    B --> C[Sequence Number and Distribution Type]
    C --> D[Incident SitRep List]
    D --> E[Command and Partner Review]
    E --> F[Next SitRep Builds on Prior State]

Last Reviewed: 2026-04-22 Last Updated: 2026-04-22

Key Features#

  • Incident-Scoped SitReps: Keep situation reports tied to the incident they describe rather than a general message stream.
  • Sequenced Reporting: Maintain a clear report order so users know which update supersedes the previous one.
  • Issued-By Context: Preserve who issued the report and when it became current.
  • Distribution Type Awareness: Support different reporting audiences and dissemination patterns without rewriting the reporting model.
  • Operational Review View: Give command teams a simple way to review the current and prior structured updates for an incident.

Use Cases#

  • Control Room Incident Updates: A duty officer publishes a formal sitrep after a major operational change.
  • Multi-Agency Coordination: Partner agencies review the same structured incident update rather than relying on ad hoc message summaries.
  • Shift Handover: Incoming command staff read the latest sequenced sitreps to understand the current operational state.
  • Exercise and Training Reporting: Exercise control teams issue structured sitreps during a scenario for realism and later review.

Integration#

  • Operational Picture and Command Workflows: Sitreps can complement the live picture with formal narrative updates.
  • Unified Command and Major-Incident Workflows: Structured reports can sit alongside checklists, command roles, and resource requests.
  • Notification and Distribution Services: A sitrep can be pushed out through the service's wider information-sharing channels.
  • Archive and After-Action Review: Sequenced sitreps provide a clean narrative spine for later review.

Open Standards#

  • OASIS EDXL-SitRep: the module aligns with the emergency data standard for formal structured situation reporting.
  • EDXL Distribution Element: sitreps can align with the broader EDXL message-distribution model across agencies.
  • CAP (Common Alerting Protocol): deployments can pair formal sitreps with alert-distribution workflows where incident communications need both.
  • ISO 8601: report issue times and sequencing context use a standard date-time representation.
  • RFC 8259 JSON: structured sitrep payloads can be exchanged in a standard machine-readable format where JSON transport is used.