Connecting policing data without replacing core systems

The National Policing Digital Strategy 2025 to 2030 is candid about where policing starts from. It describes "outdated legacy systems which are costly to maintain, poor quality data that cannot be utilised" and a lack of interoperability. It also notes that the flow of data "often stops within force boundaries". For most forces the question is not whether to address this, but how to make progress without a multi-year replacement programme.

Why replacement is rarely the first answer

Core policing systems are deeply embedded in daily operations, and replacing them is long, expensive and risky. The strategy estimates that of around £2 billion policing will spend on IT in 2025 to 2026, around £590 million will go on resources to maintain existing systems. That money is already committed. The more immediate opportunity is to make better use of the data those systems already hold.

Integration first

An integration layer connects to existing systems through their supported interfaces or exports, brings the data into a common model and presents it to the people who need it. The systems of record remain authoritative; nothing is switched off. In practice, this involves:

• capturing data automatically at source, so officers and staff do not re-key it
• mapping each system's records to a shared model with agreed definitions
• matching records that refer to the same person, place or case, with confidence levels that analysts can review
• presenting a single, current view of a case or subject, with a link back to the source record

Accountability designed in

Bringing data together raises the stakes on how it is protected. Processing for law enforcement purposes falls under Part 3 of the Data Protection Act 2018, which sets its own principles and safeguards. Access should be role-based, every view and change should be recorded in an audit trail, and retention rules should be applied consistently rather than left to each source system. The strategy itself identifies "disproportionate retention" as a problem, and a well-designed integration layer is an opportunity to address it.

Aligned with the national direction

The strategy sets an aim of "unified national standards, patterns and enterprise architecture approaches" and of avoiding the risk of vendor lock-in. Local integration work supports that aim when it is built on open standards and documented interfaces, and when the force owns the code, the data model and the infrastructure. It can then be aligned with national capabilities as they mature, rather than becoming another silo.

Where to start

The most effective starting point is one data flow of clear operational value: a view that currently takes an analyst hours to assemble by hand, for example. Prove that it can be produced reliably and securely, measure the time saved, then extend the model system by system. Each step delivers value on its own, and the risk of any single step stays small.

This is the approach brytloop takes: bringing existing systems into one place, with data captured automatically and access controlled and audited from the start, without replacing what already works.