Skip to content
Alpha

This site is an alpha version and is still being developed in the open - your feedback will help us improve it. See the roadmap. Last updated: 14 October 2026.

Version in force: 0.3.0 (6 October 2026).

Incident response (proposed)

A proposed starting shape for detecting, coordinating and reporting on incidents such as animal and plant disease outbreaks, floods and pollution events.

Draft - to be confirmed

Exploratory, early work. Service patterns are starting points for discussion, not agreed designs, and have not been reviewed by the Technical Design Authority. Talk to the architecture team before building on one.

Technology capability: incident and emergency management, under Manufacturing & Delivery. Defra has no Defra-wide answer yet. Typical business capability: 08 Respond to incidents and crises.

Context

Defra and its arm's length bodies respond to incidents that can grow from one report to a national emergency in days. Responders need a shared picture: what has been reported, where, what is being done, and by whom. Systems must scale quickly, work with partners outside Defra, and keep working when demand is highest.

Proposed shape

flowchart LR
    accTitle: Proposed incident response service pattern
    accDescr: Reports arrive from the public through a reporting service, from staff in the field, and from monitoring and partner feeds. An incident service on the Core Delivery Platform records and triages them, and publishes events. Responders coordinate tasks through case and workflow, see a common operating picture on a map from geospatial services, and send alerts through notifications. Data flows to the data platform for reporting and lessons learned.
    PUB(["Public reports"]) --> REP["Reporting service"]
    FIELD(["Field staff"]) --> INC
    MON["Monitoring and<br/>partner feeds"] --> INC
    REP --> INC["Incident service<br/>on CDP"]
    INC -->|"incident events"| MSG["Messaging"]
    MSG --> CASE["Tasks and workflow"]
    MSG --> MAP["Common operating picture<br/>Geospatial"]
    MSG --> NOT["Alerts<br/>Notifications"]
    MSG --> DP["Data platform"]

Questions to answer

To be confirmed

TODO: which incident types are in scope for a shared capability, and which team owns incident and emergency management technology.

  • How do responders outside Defra, such as local authorities and other agencies, get access?
  • What service tier does an incident service need, and how does it scale from quiet to surge?
  • How do existing incident systems in arm's length bodies fit in?

Guardrails to pay attention to