Coordination, unrecorded
Section 19 reports document multi-agency activity in detail but are not written to evidence joint-working effectiveness — and in practice never reference JESIP, the doctrine governing how agencies coordinate.
Public-good software · free to councils
Make multi-agency interoperability traceable — from readiness to assurance.
UK flood response depends on many agencies working together under JESIP — yet the statutory Section 19 record was never built to evidence how they coordinated. This platform turns that record into an edition-correct, defensible assurance annex, on an openly-licensed standard.
11
Warwickshire flood events studied — JESIP absent from every statutory record
3
JESIP editions to scope correctly (2016 · 2021 · 2024)
£0
Cost to councils — an asset-locked public good, openly licensed
The problem
Coordination happens. The record can't prove it.
Underpinning research scoping-reviewed eleven Warwickshire flood events against JESIP and the Civil Contingencies Act, and found interoperability doctrine absent from the statutory record. UK inquiries repeatedly turn on exactly this missing joint-working evidence.
The wrong yardstick
Any credible record must judge an event against the JESIP edition in force at the time. Edition 2 reached only blue-light services; Edition 3 first extended to Cat 2. No current process captures that distinction.
Lessons lost to climate
As flooding grows more frequent and severe, authorities cannot systematically learn what coordination failed — because the record was never structured to show it.
How it works
One report in. A full interoperability toolkit out.
The calm-time core turns a Section 19 report into an assurance annex — the author stays in control throughout, the tool proposes with rationale, nothing is asserted without human approval. That same structured record then powers four more modules across the incident lifecycle.
The core — Section 19 to assurance annex
1
Import
Drop the published Section 19 report. Text is extracted locally, on-device.
2
Resolve edition
The JESIP edition in force on the event date is resolved deterministically.
3
Propose tags
Interoperability passages are tagged against the schema — each with a rationale.
4
Human review
Accept, edit, reject or add every tag. Nothing finalises without approval.
5
Generate annex
Export an edition-correct assurance annex with a doctrine-gap summary.
The platform — five modules across the incident lifecycle
Who it's for
Built for both sides of the assurance gap
LLFA author
The Flood-Risk Officer
Authors Section 19 reports under time pressure. Gets interoperability captured at near-zero effort — plus faster, more consistent report sections they can use immediately.
Accountable body
The Assurance Lead
Accountable when interoperability is questioned after an event. Gets defensible, edition-correct evidence on demand — proof rather than hope when an inquiry asks.
Sector & research
The Researcher
Studies multi-agency coordination. Gets a published, openly-licensed schema and a comparable dataset across events that no single narrative report reveals.
Open standard
An openly-licensed schema, not a walled product
The tagging vocabulary is a public good — versioned, openly licensed, and usable without the tool, so researchers and other authorities apply the same standard and the data becomes comparable across events.
Schema v0.2OGL v3.0 · CC BY 4.0Semantic versioning
£0
Free & asset-locked
No licence fees. A public good held by a CIC under an asset lock — it cannot be enclosed.
⌂
Local-first processing
Reports processed on-device by default; a DPIA-aligned model keeps personal data on your workstation.
§
Not an adjudicator
The tool structures evidence with a rationale on every tag. Humans judge compliance — it never does.
◇
Open & maintainable
Schema and tool openly licensed and versioned, so the community can maintain them as doctrine evolves.
Roadmap
Delivered lowest-liability first — now all live
The build sequenced outward from the evidence-proven calm-time core to the highest-value live coordination layer. All five modules are now live across the incident lifecycle — from Section 19 Assurance, through Jurisdiction Resolver, Coordination Layer, JDM Decision-Capture, to Readiness Micro-Exercise.
Phase 1Live
Section 19 Assurance Tool
Turns a Section 19 report into a JESIP-traceable assurance annex, with an openly-licensed tagging schema underneath.
Phase 2Live
Jurisdiction Resolver
Resolves which authority owns what at a flood incident under the Flood and Water Management Act 2010 (main river / ordinary watercourse / surface water / groundwater / sewers → EA / LLFA / IDB / water company / riparian owner).
Phase 3Live
Cross-Category Coordination Layer
A lightweight browser/mobile common-operating-picture + M/ETHANE / JDM layer for non-blue-light Cat 1 and Cat 2 responders excluded from Airwave/ESN.
Phase 4Live
JDM Decision-Capture
A guided Joint Decision Model workflow timestamping decisions and rationale into an immutable joint decision log, with anti-inertia prompts.
Phase 5Live
Readiness Micro-Exercise Platform
Low-cost, low-time multi-agency flood-coordination micro-simulations for responders who cannot afford full LRF exercises — closing the data flywheel (reports → structured data → drills).
See the full platform on real Warwickshire flood events.
All five modules are live — from Section 19 assurance to jurisdiction, coordination, joint-decision capture and readiness drills. Explore them with sample events.