Integrate and adapt technology
Make sure new technology works with what you already have, and take a considered, risk-aware approach when adopting new or emerging technology.
Point 9 of the Technology Code of Practice (TCoP) explains how you should plan the integration of new technology with your existing systems, and apply extra checks when adopting technology that is new or unproven.
Why you should integrate and adapt technology
In government, new technology usually has to work alongside legacy systems, existing skills, support arrangements, and established governance processes. If you don’t integrate new technology properly, it can create compatibility gaps, unplanned downtime, and systems which, in the future, lack support.
When the technology itself is new or unproven, it can fail, be discontinued, or turn out to be the wrong tool for a need that more mature technology would have been better suited for.
Technology choices should never be made in isolation. This TCoP principle exists to enable you to make informed integration and adoption decisions by considering both your existing estate and the maturity of your chosen technology.
What good integration and adaption looks like
You have successfully met this principle if:
-
you can show how a new technology will work alongside your existing infrastructure, support model and governance, and not just that it works in isolation
-
you can describe your target architecture and transition path from where you are now, using a recognised approach, such as baseline, target, and transition architectures (which are used in frameworks such as the The Open Group Architecture Framework)
-
you’ve broken integration into smaller, manageable increments rather than one large change, so that problems surface early rather than at go-live
-
your configuration management is defined, and component and integration testing happens automatically as part of your build process rather than being manual or only carried out at the end of the process
-
where you’re introducing emerging technology, you can always show that you have considered a mature alternative first, and can justify why the emerging option was chosen
-
you have a plan for the technology if it fails or is discontinued
-
you’ve identified the skills your organisation needs to support and continuously improve the technology, not just to deploy it.
-
privacy and security implications have been considered as part of the technology decision, particularly when buying from suppliers
-
where automated decision-making is involved, you can show alignment with the Ethics, Transparency and Accountability Framework for Automated Decision-Making
How to apply this principle
This principle applies whenever you’re introducing new technology into any existing environment, and not just for large-scale re-platforming.
You should apply a level of scrutiny which is proportionate to risk. For example, if you’re integrating a mature technology into a simple environment, this will need a lighter check than if you’re introducing an emerging technology to critical infrastructure.
If you’re planning a legacy integration, you should identify compatibility gaps and support requirements early, not only at go-live.
If you’re planning larger or more complex integrations, they should be split into smaller stages against your target architecture. There should be automated testing at each stage rather than just once at the end.
Examples of emerging technologies around government
‘Emerging technologies’ is a broad term for a range of tools and techniques that are at different stages of development. Examples of emerging technology include:
-
artificial intelligence (AI) and machine learning
-
distributed ledger technologies (DLT) and blockchains
-
quantum computing
Emerging technologies are often categorised together, but some are more mature than others.
Examples of AI technology
Several government organisations are using or trialling artificial intelligence. GOV.UK Chat is an AI assistant built by the Government Digital Service (GDS). It has been launched within the GOV.UK app to answer questions on topics including tax, benefits, and visas with 90% accuracy.
The Driver & Vehicle Licensing Agency (DVLA) have also deployed an AI-based natural language interactive voice response (IVR) on its contact centre voice channel. This allows callers to describe their enquiry in their own words rather than having to navigate a traditional touchtone menu.
Since its implementation, the average call navigation time has been cut in half. For more information, see DVLA: Contact Centre Natural Language IVR .
If you are considering using artificial intelligence, read the AI Playbook for the UK Government.
Examples of quantum computing
Quantum computing has moved well beyond the theoretical phase. In March 2026, government committed up to £2 billion to quantum technologies. This includes ProQure: Scaling UK Quantum Computing, which is a procurement programme that aims to deploy large-scale quantum computers as part of the national computing infrastructure by the early 2030s.
Additional considerations
This principle covers the integration and adoption of technology you have already chosen. If you’re still deciding which platform or supplier to use, read TCoP point 11 - Define your purchasing strategy.
All security practices for any new or integrated technology must follow the Secure by Design approach, and you should maintain continuous security compliance as the technology evolves rather than assessing it only at the point of integration.
For help identifying legacy systems, use the Updated Definition of Legacy IT. Legacy systems are not defined by age alone; where continued use of a technology creates unacceptable burdens or risks, it may be a legacy system.
Communities
Sharing experiences with others who are adopting new or emerging technology will help you to apply this principle. If you have a government email address, you can join the cross-government Slack.
For more information on communities, see TCoP point 8 - Share, reuse and collaborate.
Contact us
If you have any questions or feedback, email publicsector.architecture@dsit.gov.uk.
Next: Technology Code of Practice point 10 - Make better use of data