Shared situational awareness requires every responding agency to work from one current picture of an incident rather than from separate versions of it. Reaching that state takes three deliberate decisions: who contributes to the picture, what each agency shares, and when they share it. Chronosoft is an operational resilience platform built to hold that single picture across agencies during a live response.
The phrase sits in almost every multi-agency plan in the UK. It carries real operational weight in the JESIP principles, which name shared situational awareness as one of the five foundations of joint working. Plenty of teams still treat it as a communications problem, solved by adding more people to a call.
A group call creates conversation. Shared situational awareness needs a record.
What shared situational awareness means in practice
Shared situational awareness means every agency understands the same things at the same time: who is involved, where the incident is, and what is happening. The test is straightforward. If two commanders describe the incident differently, awareness is not shared, however much information has passed between them.
Edward Swete Kelly, Chronosoft’s founder and a former paramedic and control room manager, sets the sequence in a specific order. Establish the who first. The what and the when follow from it.
That order matters because the composition of the response determines what the picture needs to hold.
Who contributes to shared situational awareness?
Who contributes depends entirely on the room. A blue light control room draws on police, fire and ambulance. An event control room might draw on police, medical, security and the event organiser instead. Naming that group explicitly is the first move, because an unnamed contributor is an assumed contributor.
Assumed contributors are how gaps form.
Once the group is named, each member’s role in the picture becomes definable. A medical partner reports patient numbers and clinical capability. A utility operator reports asset status and restoration estimates. These are different obligations, and treating them as one generic reporting duty produces vague returns from everyone.
Under the Civil Contingencies Act 2004, Category 1 and Category 2 responders carry different statutory duties. That split gives a useful starting point for deciding who contributes what. Local arrangements do the rest of the work, because the statutory tiers rarely map neatly onto a specific incident.
What is worth sharing, and what only adds noise
Sharing information because it exists degrades the picture. It creates noise, and noise creates distraction at the point when commanders can least afford either. The discipline is to define what each agency shares before an incident, then hold to that definition during one.
A short, current, trusted record beats a long one nobody reads.
Most teams lose ground here. Volume feels like diligence. In practice, volume forces a commander to read forty updates to find the two that change a decision. The coordinating role has to be willing to tell a partner agency that a particular data point is not needed.
Defining the requirement in advance turns that into an administrative conversation rather than a confrontation during a live response.
When should agencies share information?
Timing needs a stated pattern, and two work well. A battle rhythm sets fixed intervals so every agency reports at the same points, which suits protracted incidents and planned events. Trigger-based reporting sends an update only when a defined threshold is crossed, which suits fast-moving incidents where fixed intervals either lag or waste effort.
Mature teams usually run both. A battle rhythm carries the baseline, and trigger points interrupt it when something material changes.
The choice needs making before the incident. Settling the reporting cadence at hour two of a major incident costs time the response does not have.
Why shared situational awareness slips under load
Shared situational awareness rarely fails because agencies refuse to share. It fails because the three decisions above were never made explicit, so each agency improvises its own answer.
The pattern repeats. Contributors are assumed rather than named. Everything gets shared because nobody defined what mattered. Updates arrive whenever someone thinks of them. Within an hour the record is long, partly contradictory and no longer trusted, and commanders fall back on phone calls and personal networks.
The shared picture still exists as a document at that point. It has stopped working as a source of truth.
How Chronosoft supports shared situational awareness
Chronosoft holds the who, the what and the when as configuration rather than as convention. Contributing agencies are defined in advance with the access each one needs. Information requirements sit as structured prompts against each agency, so a medical partner is asked for patient numbers and capability while a fire partner is asked for appliances committed and specialist resources.
Reporting cadence is set as a battle rhythm, with trigger-based reporting available alongside it.
The effect is that the discipline described above sits inside the system rather than depending on whoever runs the room that day. Every contribution lands in one record, timestamped and attributed, which also makes that record usable after the incident closes. For more on the artefact itself, see how a common operating picture is built and maintained.
Chronosoft’s own treatment of the toolset sits in the software behind real-time shared situational awareness, and the software question is covered separately in how software supports JESIP joint working.
Frequently asked questions
Is shared situational awareness the same as a common operating picture?
They are closely linked and not identical. Shared situational awareness describes the state agencies are trying to reach. A common operating picture is the artefact that gets them there, holding the agreed information at a point in time. Chronosoft treats the picture as the mechanism and shared situational awareness as the outcome it produces.
Who decides what goes into the shared picture?
The coordinating role sets the information requirements, usually a control room manager or the commander holding the picture. That person defines what each agency reports and how often. Chronosoft holds those requirements as structured prompts, so agencies report against a defined set rather than deciding case by case what seems relevant.
How often should agencies update the shared picture?
Two patterns work. A battle rhythm sets fixed update intervals, which suits protracted incidents and planned events. Trigger-based reporting sends an update only when a defined threshold is crossed, which suits fast-moving incidents. Chronosoft supports both, and many teams run a battle rhythm with trigger-based exceptions layered over it.
Does shared situational awareness require every agency to use the same software?
No. It requires every agency to contribute into one shared record and to read from it. Some agencies work in the platform directly while others feed it through a liaison. Chronosoft is built so partner agencies can contribute at different levels of access without each one replacing its own systems.
Why does shared situational awareness fail during large incidents?
Volume is the usual cause. Agencies share everything available rather than what partners need, so the signal gets buried and commanders stop trusting the picture. Defining the information requirement in advance prevents this. Chronosoft narrows each agency’s contribution to a defined set, keeping the shared record short enough to stay usable.
Bring every agency onto one picture
Shared situational awareness is the product of three decisions made before an incident, and Chronosoft holds those decisions as configuration so the picture survives contact with a live response. Book a demo with the Chronosoft team to work through it against your own control room arrangements.
For a closer look at the platform itself, explore Chronosoft in more detail.