SERVICE STANDARD · POINT 11
Choose the right tools and technology
Technology choices should serve the service long after the initial build team has moved on. The right tool is the one the team can operate, secure, and maintain — not necessarily the newest.
Pick technology that fits the problem, the team, and long-term maintenance — not the newest option by default. Reuse existing platforms and components where they meet the need.
Reuse is often the right answer: shared platforms, design systems, and commodity cloud services reduce bespoke risk. When custom build is justified, the team should explain why existing options were insufficient.
Consider total cost of ownership: hosting, licensing, specialist skills, upgrade paths, and what happens when the vendor or framework changes direction.
How teams usually demonstrate this
- Technology choices documented with rationale
- Reuse of common components, platforms, or patterns where appropriate
- Plan for maintenance, upgrades, and team capability
- Security and accessibility considered in tool selection
Phases where this often matters
See also delivery phase guides and how frameworks fit together.
Related standard points
- Point 12: Make new source code open
- Point 13: Use open standards and common components
- Point 14: Operate a reliable service
Point 11 of the Service Standard is published by the Government Digital Service on GOV.UK. Content is available under the Open Government Licence v3.0. UCD Services explains the standard in its own words and is not affiliated with GOV.UK or the Government Digital Service.