Major Incident Command with Gold-Silver-Bronze Structure

Overview#

A major incident rarely fails for lack of effort. It fails when commanders at different tiers see different versions of the truth, when SitReps slip because someone has to stop and write one, and when partner-agency entries arrive in a separate inbox rather than the same operational log. This module brings the command structure together.

The Gold-Silver-Bronze module applies JESIP-aligned multi-agency command roles to a single live incident, so strategic, tactical, and operational tiers all share one decision log, one timeline, and one scheduled SitRep cadence across DFB, NAS, Garda, and other responding agencies.

Last Reviewed: 2026-05-05 Last Updated: 2026-05-05

Key Features#

• JESIP-Aligned Role Taxonomy: Gold (strategic, off-scene), Silver (tactical, on-scene), and Bronze (operational, sector) roles seeded from a managed manifest so every major incident starts with the same recognised command structure.

• Single Canonical Incident: Every command tier operates against one canonical incident record, with role assignments stored as a typed extension rather than a parallel record.

• Shared Decision Log: Each command decision at any tier is captured once and visible to every tier, with full author, timestamp, and rationale preserved.

• Multi-Agency Unified Timeline: Cross-agency entries from NAS, Garda, fire, and other responders land on the same unified timeline, tagged as partner-agency entries,, so every commander sees the same authoritative chronological log.

• Scheduled SitRep Cadence: SitReps are generated on a defined cadence and distributed automatically, removing the need for a commander to stand down from active direction to compose them.

• Three-Tier Command Board: The Gold-Silver-Bronze board surfaces role assignments, decision-log entries, strategic intent, and partner activity in a single operator view.

• Distinct from MCI Declaration: The structure may be invoked for major events without a casualty-centric declaration, including flooding, public-order, and chemical incidents, separate from the MCI triage workflow.

Use Cases#

• Major Fire with Multiple Sectors: A Silver Commander on scene assigns Bronze sector commanders to fire-front, evacuation, and welfare, while Gold sets strategic intent off-scene and the same decision log binds all three.

• Public-Order Incident: Garda lead with Gold strategic command, while DFB and NAS contribute Silver and Bronze roles for medical and rescue contingencies, all on the same shared timeline.

• Severe Flooding Event: A regional flood is run as a major incident without an MCI declaration, with sector-based Bronze commanders for affected areas and Gold setting evacuation and resource priorities.

• Chemical or HAZMAT Incident: Specialist Bronze roles work to a Silver tactical plan, while Gold coordinates strategic decisions on cordon, evacuation, and external agency support.

• Sustained Multi-Agency Operation: A long-running incident benefits from scheduled SitReps generated automatically at the agreed cadence, rather than relying on commanders to remember to compose them.

• Command Handover: A relieving commander at any tier inherits the full decision log and timeline, including partner-agency entries, without losing context on prior strategic intent.

Integration#

• Unified Command Framework: The Gold-Silver-Bronze role manifest is seeded into the unified command domain that already underpins live incident command across the platform.

• Live Incident Board: The three-tier role board sits alongside the existing live operational picture, so command structure is visible inside the same workflow as resources, units, and incident status.

• PSAP Console: The board is delivered as a PSAP module so the same tooling used for call-taking and dispatch carries the major-incident command view forward.

• Partner-Agency Handoff: Cross-agency timeline entries are enveloped using the platform's handoff builder when shared with NAS, Garda, or other agencies, keeping outbound entries structured and auditable.

• Decision-Log Eventing: Every command decision emits a typed event so downstream audit, recording, and review systems receive a structured stream rather than free-text notes.

• SitRep Distribution: Scheduled SitReps can be routed to internal command tiers and external partner agencies through the same distribution channels used for other operational messaging.

Open Standards#

• ISO 22320: command structure, role assignments, and decision logging follow the international standard for emergency management requirements for incident response.

• JESIP Joint Doctrine: the Gold-Silver-Bronze taxonomy follows the joint principles for multi-agency working established as a UK and Irish reference for emergency responders.

• EDXL Distribution Element (EDXL-DE 2.0): cross-agency timeline entries are carried inside the standard distribution envelope so partner agencies receive entries in a recognised exchange format.

• EDXL Situation Reporting (EDXL-SitRep 1.0): scheduled SitReps are produced as structured payloads at the agreed cadence rather than as free-text messages.

• Common Alerting Protocol (CAP 1.2 / EDXL-CAP): where escalation requires alerting, the Common Alerting Protocol is used so warnings reach partner systems in their expected form.

• CloudEvents 1.0: every command decision is emitted using the cloud-native event envelope so downstream systems consume a consistent structured stream.

• TLS 1.2 / 1.3 (RFC 5246 / RFC 8446): command, decision-log, and SitRep traffic moves over the standard secure transport baseline.

• JSON (RFC 8259): role assignments, decisions, timeline entries, and SitRep payloads remain easy to exchange across command, partner, and audit systems using a common structured format.