[Développeurs]

Agency Incident Handoff Exchange

The Agency Incident Handoff Exchange module provides a structured, cryptographically auditable mechanism for passing command authority, incident artefacts, resource assignments, and active task lists between responding o

Catégorie: ModulesDernière Mise à Jour: 16 juil. 2026
modulesreal-timecomplianceblockchain

Overview#

The Agency Incident Handoff Exchange module provides a structured, cryptographically auditable mechanism for passing command authority, incident artefacts, resource assignments, and active task lists between responding organisations, whether that transfer is between a municipal fire service and a national civil protection agency, or between two sovereign nations participating in a joint operation.

When a major civil emergency escalates beyond a local authority's capacity, a formal transfer of incident command must occur quickly and without loss of situational awareness.

The module enforces digital handover checklists so that incoming commanders receive a verified, complete briefing package rather than a verbal summary. Every exchange is time-stamped and signed against an immutable audit trail, satisfying chain-of-custody requirements for post-incident review, public inquiries, and defence compliance frameworks. Partial handoffs are supported, allowing one agency to transfer logistical command while retaining tactical authority until the receiving unit is ready to assume full control.

Key Features#

  • Structured Digital Handover Checklists: Enforces mandatory completion of all critical fields, including active tasks, resource registers, negotiation logs, and site intelligence, before a transfer can be confirmed.
  • End-to-End Encrypted Transfer: All incident artefacts, including maps, evidence, personnel lists, and communication logs, are transmitted over encrypted channels and stored with classification-appropriate protections.
  • Cryptographic Audit Trail: Every handoff event is recorded with a tamper-evident signature, capturing the identities of both parties, the exact timestamp, and the classification level of the exchanged material.
  • Partial and Incremental Handoff: Allows phased transfer of command authority, for example handing over logistics and resource management while the originating agency retains tactical or negotiation roles until an agreed threshold is met.
  • Cross-Jurisdictional Data Normalisation: Translates terminology, classification markings, and data formats between agencies using different national or organisational systems, so the receiving commander sees a coherent picture without manual reconciliation.
  • Role-Based Delegation Controls: Granular permission model ensures that only authorised commanders at the appropriate clearance level can initiate, accept, or reject a handoff, with all delegation decisions logged.
  • Shift Relief and Routine Transfer Support: Supports planned shift-change handovers as well as emergency escalations, giving incoming commanders an auditable snapshot of the current operating picture and all pending actions.
  • Live Emergency Call Transfer with Context Continuity: Extends the handoff model to active emergency calls passed between call centres on the platform. A caller context packet, covering the caller's identity, location, the linked dispatch incident, triage summary, and the reason for transfer, travels with the call and is released to the receiving centre only once the carrier confirms the genuine inbound call, so context can never be claimed by the wrong party. Operators review and approve exactly which facts accompany the call, destinations are drawn from an administrator-governed agency directory, and the receiving call taker sees the transferred context immediately on answer.

Use Cases#

  • A municipal emergency management agency formally escalates a complex flood response to a national civil protection authority, transferring the incident command package, resource deployment log, and evacuation status in a single verified exchange.
  • A law enforcement commander passes a hostage negotiation incident to a specialist federal tactical unit, transferring all prior communication logs, site maps, and negotiator notes with full provenance intact.
  • Two nations participating in a joint PESCO civil-military exercise conduct a coordinated handoff of a simulated mass-casualty incident at a national border crossing, with each side operating under its own data sovereignty constraints.
  • An incident commander performing an end-of-shift relief uses the module to transfer the live operational picture and all open task assignments to the incoming commander, with automatic confirmation that the relief has been accepted and logged.
  • A coastal guard authority hands off an active maritime search and rescue operation to a neighbouring nation's maritime rescue coordination centre, including vessel tracks, weather assessments, and search sector assignments.
  • An emergency call centre transfers a live 112 call about a coastal incident to the coast guard, with the caller's location, triage summary, and transcript excerpt attached, so the receiving operator answers already briefed and the caller never has to repeat their emergency.

Integration#

The Agency Incident Handoff Exchange module works in conjunction with the Unified Command, Case Management, and Communications modules. When a handoff is confirmed, command hierarchy records and communication channel assignments are updated automatically to reflect the new lead agency, active cases and evidence chains are transferred or shared at the appropriate classification level, and all parties receive real-time notification of the change in authority. The module exposes a documented REST and typed integration interface so that external command-and-control systems operated by partner agencies can initiate or acknowledge transfers programmatically without requiring direct platform access. Live emergency call transfers between call centres, including the continuity packet lifecycle, the carrier-confirmed release of caller context, and the governed transfer directory, are described in depth in the Emergency Call Transfer with Context Continuity documentation.

Open Standards#

  • NIEM (National Information Exchange Model): Used as the canonical schema for encoding incident data packages exchanged between agencies with disparate data models, ensuring semantic interoperability during cross-jurisdictional transfers.
  • NIMS ICS (National Incident Management System, Incident Command System): Handover checklists and command transfer workflows align with ICS form conventions and the standardised incident command handoff protocol, supporting both domestic and international deployments.
  • OASIS Common Alerting Protocol (CAP, ITU-T X.1303): Incident summary notifications generated during a handoff event conform to CAP, allowing downstream warning systems to consume transfer alerts without custom integration.
  • NATO STANAG 2014 (Orders Formats): Command transfer packages use terminology and structure compatible with NATO operational orders conventions, supporting interoperability in multinational and PESCO-aligned exercises.
  • ISO/IEC 27001 (Information Security Management): Audit trail design and access control procedures for classified incident material follow ISO/IEC 27001 controls for information asset custody transfer.
  • ETSI TS 102 181 (Emergency Communications, Requirements for Communication Between Authorities): Handoff workflows take account of the ETSI EMTEL requirements for communication between authorities and organisations during emergencies, preserving continuity of inter-agency communication through a command transition.
  • W3C Verifiable Credentials (VC Data Model): Cryptographic receipts issued on handoff acceptance are structured as W3C Verifiable Credentials, enabling third-party verification of transfer provenance without exposing the underlying incident data.
  • OpenID Connect (OIDC) / OAuth 2.0: Authentication and authorisation of commanders initiating or accepting transfers relies on OIDC identity assertions and OAuth 2.0 scopes, supporting federated identity across national identity providers.

Last Reviewed: 2026-07-16 Last Updated: 2026-07-16

Prêt à Développer ?

Commencez avec nos APIs ou contactez notre équipe d'intégration pour obtenir de l'aide.