Software supports JESIP joint working when it follows the way an agency already responds, and it obstructs joint working when it asks responders to decide which doctrine applies before they can act. Chronosoft is built around that distinction, shaping itself to the nature of the incident rather than asking a responder to select a framework first.
Doctrine came first and software came second. Any honest assessment of JESIP joint working software starts there.
The JESIP principles were written for people, not for systems. They describe how commanders from different services co-locate, communicate, share understanding and reach joint decisions. None of that requires software. Agencies achieved it with radios, whiteboards and discipline long before a platform existed.
What software changes is the cost of doing it consistently at scale, across long incidents, with a record left behind.
Where software genuinely helps JESIP joint working
Four things are difficult to sustain manually and become straightforward once a system carries them:
- Holding one current picture that every agency reads from, rather than several versions circulating by email and phone.
- Recording who knew what and when, without anyone stopping to write it up separately.
- Prompting each agency for the specific information partners need, at the interval the incident requires.
- Carrying the structure across a shift handover, so an incoming commander inherits context rather than reconstructing it.
Each of these supports JESIP joint working without replacing the judgement behind it. The commander still decides. The system removes the administrative drag around the decision.
Long incidents show the difference most clearly. Discipline that holds for two hours rarely holds for two weeks, and that is where a system earns its place.
Where software gets in the way of JESIP joint working
Poorly designed software introduces a second problem on top of the incident. Edward Swete Kelly, Chronosoft’s founder and a former paramedic and control room manager, puts the failure plainly. A responder should not have to think about which doctrine applies or which framework is relevant before the system will let them work.
Three patterns cause it:
- Doctrine as a menu. The system asks the user to classify the incident against a framework before any information can be entered, which front-loads a decision that often cannot be made yet.
- Modules that mirror the doctrine document rather than the response. A separate area for each JESIP principle looks tidy in a demonstration and fragments the work in practice.
- Mandatory fields that assume a linear incident. Real responses loop back, and a system that refuses to progress without complete information invites workarounds.
Workarounds are the real cost. Once responders start keeping a parallel record because the system is slow, the audit trail is already broken.
The bouncing ball approach
Chronosoft’s design starts from the observation that incidents differ in shape rather than only in scale. A structure collapse, a planned demonstration and a multi-day utility failure all draw on the same doctrine and follow different paths through it.
The platform adapts to that path as the incident reveals it. Responders work forward through their normal sequence, and the doctrinal structure is satisfied as a by-product rather than as a separate task.
Chronosoft was built across a decade supporting agencies through live incidents, and the flow reflects what those agencies actually did rather than what a doctrine summary suggests they should have done.
Four tests for JESIP joint working software
- Can a responder start recording before the incident has been classified?
- Does the system prompt for information, or does it wait to be filled in?
- Does a shift handover transfer context automatically, or does someone write a summary?
- Would a responder still use it at hour thirty of a protracted incident?
A platform that passes all four supports JESIP joint working. A platform that fails the first two is doctrine as a checkbox.
For the underlying practice this depends on, see what shared situational awareness actually requires.
For the doctrine itself rather than the tooling, see the joint emergency services interoperability principles in full.
Frequently asked questions
Is any software formally certified as JESIP compliant?
No certification scheme exists, and no vendor can claim compliance in a formal sense. JESIP sets principles for people and organisations rather than technical standards for software. Assessment is therefore done by inspection during evaluation. Chronosoft describes its alignment as a design intent, demonstrated by running an agency’s own scenario rather than by a compliance badge.
Can agencies meet JESIP without any platform at all?
Yes. Agencies achieved joint working with radios, briefings and paper long before software existed, and the principles remain achievable manually. What changes with scale and duration is the effort required to sustain it consistently and to leave a defensible record. Chronosoft reduces that effort rather than supplying the doctrine itself.
Does every partner agency need an account to benefit?
No. Partner agencies can contribute through tiered access, through a liaison working in the system on their behalf, or through structured exchange with their own tools. Chronosoft supports several levels of access, so a partner can read the shared picture without replacing its existing systems or licensing every member of staff.
How does software help with the joint decision model?
It helps by holding the information the model consumes and by recording the decision reached, including the rationale and the time. The judgement stays with the commander. Chronosoft captures decisions against the shared picture, so a later review can see what was known at the moment a decision was made.
What is the main sign that a platform is interfering rather than helping?
Parallel record keeping. When responders maintain a notebook or spreadsheet alongside the system because the system is too slow during an incident, the platform has failed regardless of its feature list. Chronosoft is designed so the fastest way to record something is inside the system.
See it against your own response
Chronosoft supports JESIP joint working by following an agency’s existing response sequence, so doctrine is satisfied as a by-product of the work rather than as a task alongside it. Book a demo with the Chronosoft team and run one of your own scenarios through it.
For a closer look at the platform itself, explore Chronosoft in more detail.