Handover without lock-in: owning what you pay for

The National Policing Digital Strategy 2025 to 2030 identifies vendor lock-in as a challenge, noting contract extensions with incumbent suppliers "due to a lack of time and resource to explore more strategically valuable opportunities". Government guidance on choosing technology makes the same point from the other direction, advising teams to minimise total cost of ownership, "including reducing the chance of getting locked in to long contracts for specific tools and providers".

Lock-in is decided at the start

The Digital, Data and Technology Playbook advises that early market engagement should inform "intellectual property ownership and exit arrangements". By the time a contract is ending, it is too late to secure them. Ownership, documentation and exit should be agreed before work begins.

What ownership means in practice

• the code lives in a repository the public body controls
• the infrastructure runs in the public body's own cloud accounts
• data can be exported in open formats at any time
• the licences for any third-party components are understood and recorded
• any proprietary dependency is a deliberate, justified choice

Open standards keep options open

The Service Standard asks teams to make new source code open and to use open standards, common components and patterns. The Service Manual explains the practical benefit: using open standards to manage the interfaces between parts of a system "makes it easier to make changes later", including a change of supplier.

A handover people can use

• runbooks for operating the service and recovering it when something goes wrong
• an architecture overview and a record of the key decisions and their reasons
• a demonstrated ability for the public body's own team, or another supplier, to deploy a change
• training for the people who use and support the service
• a period of support after launch, with knowledge transfer built in throughout rather than left to the final weeks

At brytloop, handover is planned from the start of an engagement. We support what we build, train the people who use it, and keep improving it after launch.