SERVICE STANDARD · POINT 13
Use open standards and common components
Shared standards and components help users encounter familiar patterns across services and reduce the cost of building everything from scratch.
Adopt shared patterns, design systems, and data standards so services interoperate and users get familiar experiences. Custom builds should be justified, not assumed.
Government teams commonly use the GOV.UK Design System and related patterns for interface consistency and accessibility. Data standards help services exchange information reliably with other systems.
Custom UI or bespoke data formats should be justified. Diverging from common approaches creates maintenance burden and can confuse users who have learned patterns from other public services.
How teams usually demonstrate this
- Use of established design system components where they fit
- Open standards for APIs and data exchange where integration is needed
- Documentation when custom patterns are unavoidable
- Accessibility benefits from shared component libraries
Phases where this often matters
See also delivery phase guides and how frameworks fit together.
Related standard points
- Point 4: Make the service simple to use
- Point 5: Make sure everyone can use the service
- Point 11: Choose the right tools and technology
Point 13 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.