Interoperability Assurance Platform
The problemHow it worksOpen standardRoadmap
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.

See how it works
Interoperability Assurance Annex
River Leam — Leamington Spa
Ed. 2 (2016) · Schema v0.2
JDM
M/ETHANE
PRINCIPLE
GAP
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.

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.
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

Five steps from report to assurance annex

The author stays in control throughout — the tool proposes with rationale; nothing is asserted without human approval.

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.
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

Comprehensive in vision, wedge in delivery

Five modules across the incident lifecycle. Phase 1 ships the calm-time core and the data the later, higher-stakes modules depend on. Each phase has an explicit entry gate.

Phase 1Active
Section 19 Assurance Tool
Turns a Section 19 report into a JESIP-traceable assurance annex, with an openly-licensed tagging schema underneath.
Phase 2Gated
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 3Hard-gated
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 4Gated
JDM Decision-Capture
A guided Joint Decision Model workflow timestamping decisions and rationale into an immutable joint decision log, with anti-inertia prompts.
Phase 5Gated
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 it work on a real Section 19 report.

A working demonstrator is the first proof milestone — explore the full Phase 1 flow with a sample Warwickshire event.

Interoperability Assurance Platform
A proposed climate-resilience Community Interest Company. Underpinning research: “JESIP in Practice: Barriers to Interoperability among Warwickshire's Flood Responders (2018–2023)”, University of Leicester. JESIP edition lineage per the JESIP Joint Doctrine (Editions 2 (2016), 3 (2021); Version 3.1 (2024)). Working draft — names and partner-specific items to be confirmed.