The Technology Code of Practice
The Technology Code of Practice is a set of criteria to help government design, build and buy technology.
The Technology Code of Practice (TCoP) is the agreed standard for cross-government projects and programmes. It is designed to help you migrate from legacy infrastructure, and to manage the full lifecycle of your technology.
The TCoP supports the Local Digital Declaration, which is a shared ambition for designing future local public services.
Each of the 13 principles within the TCoP covers a different area of practice. Together, they explain why each principal matters, what’s expected of you, and how to apply that principle to your own project or programme.
When you must use the TCoP
During government procurement, suppliers on the G-Cloud framework are contractually required to support buyers in meeting the TCoP.
You should also check with your department’s assurance team to confirm which TCoP points apply specifically to your own spending and assurance processes.
When you should use the TCoP
Unlike standards that apply only when a service is being formally assessed, the TCoP sets out principles for technology decision-making that apply throughout the life of your project or programme.
The TCoP should be used alongside other related government standards and guidance. These include:
- the Service Standard and Service Manual, which cover how to design, build and run a service
- the AI Playbook for the UK Government if your project or programme uses artificial intelligence
- Secure by Design, which sets out the security practices you must incorporate when building digital services and technical infrastructure
- Government Functional Standard GovS 005: Digital, which sets expectations for how digital, data and technology are managed across government
You should use the TCoP for all of your technology projects and programmes, and follow as many points as are practical.
For more information about managing digital and technology spending and assurance, see the Digital Assurance Playbook.
1. Define user needs
Understand your users and their needs. Develop knowledge of your users and what that means for your technology project or programme.
Read point 1 - Define user needs.
2. Make things accessible and inclusive
Make sure your technology, infrastructure and systems are accessible and inclusive for all users.
Read point 2 - Make things accessible.
3. Be open and use open source
Publish your code and use open source software to improve transparency, flexibility and accountability.
Read point 3 - Be open and use open source.
4. Make use of open standards
Build technology that uses open standards to ensure your technology works and communicates with other technology, and can easily be upgraded and expanded.
Read point 4 - Make use of open standards.
5. Use cloud first
Consider using public cloud solutions first as stated in the Cloud First policy.
Read point 5 - Use cloud first.
6. Make things secure
Keep systems and data safe with the appropriate level of security.
Read point 6 - Make things secure.
7. Make privacy integral
Make sure users rights are protected by integrating privacy as an essential part of your system.
Read point 7 - Make privacy integral.
8. Share, reuse and collaborate
Before building something new, find out whether government has already solved this problem, and make it easier for others to reuse what you build.
Read point 8 - Share, reuse and collaborate.
9. 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.
Read point 9 - Integrate and adapt technology.
10. Make better use of data
Use data more effectively by improving your technology, infrastructure and processes.
Read point 10 - Make better use of data.
11. Define your purchasing strategy
Your purchasing strategy must show you’ve considered commercial and technology aspects, and contractual limitations.
Read point 11 - Define your purchasing strategy.
12. Make your technology sustainable
Increase sustainability throughout the lifecycle of your technology.
Read point 12 - Make your technology sustainable.
13. Meet the Service Standard
If you’re building a service as part of your technology project or programme, you will also need to meet the Service Standard.
Contact us
If you have any questions or feedback, email publicsector.architecture@dsit.gov.uk.