Skip to content
Alpha

This site is an alpha version and is still being developed in the open - your feedback will help us improve it. See the roadmap. Last updated: 14 October 2026.

Version in force: 0.3.0 (6 October 2026).

The architecture handrail

Guardrails tell you where the edges are. The handrail is something to hold on to: a shared map of what Defra does, the technology that enables it, and what already exists that you can reuse.

What is in the handrail

  • Services and capabilities


    Defra's service taxonomy - outcomes, services, products, capabilities, components and data - and how the handrail fits into it. Draft.

  • Business capabilities


    What Defra does - nine core and two supporting capabilities, independent of organisation and technology.

  • Technology capabilities


    What technology does to enable the business, in Technology Business Management (TBM) level 1 and level 2 areas.

  • Capability mapping


    Which technology capabilities each business capability depends on - and where the biggest reuse opportunities are.

  • Reference architecture


    A layered view of Defra's technology. Coming in a future iteration.

How layers connect

Outcomes are delivered by business capabilities. Business capabilities are enabled by technology capabilities, which are provided by products and platforms. Those products and platforms are assembled into the services users see.

flowchart TB
    accTitle: How the handrail layers connect
    accDescr: Outcomes lead to business capabilities, which need technology capabilities, which are provided by products and platforms, which make up the services users see. Services deliver the outcomes.
    O["Outcomes<br/>(Environmental Improvement Plan, priority outcomes)"] --> BC["Business capabilities<br/>what Defra does"]
    BC --> TC["Technology capabilities<br/>what technology must do"]
    TC --> P["Products and platforms<br/>Defra ID, CDP, GOV.UK Notify..."]
    P --> S["Services<br/>what users see"]
    S -.->|"deliver"| O

These layers line up with Defra's service taxonomy - see services and capabilities for definitions and how they connect.

Business capabilities change slowly. Products and services change quickly. Mapping one to the other lets us:

  • see duplication - five case management systems serving the same capability is a reuse opportunity
  • target investment - fund the technology capabilities that enable the most business capabilities
  • give teams a head start - a new licensing service starts from the regulatory casework service pattern, not a blank page
  • talk to the business in its own language - capabilities, not systems

Using the handrail on your project

  1. Find your business capability. Which of the eleven capabilities does your service support? Most services support one or two.
  2. Check the technology capabilities it needs. The capability mapping shows which technology capabilities each business capability typically depends on.
  3. Use the strategic options first. Each technology capability lists what to use. If it is marked gap, talk to the TDA so we solve it once.
  4. Start from a service pattern if one fits.
  5. Record your choices in an ADR, naming business capability ids (for example BC05) and technology capabilities (for example Enabling Platforms) so decisions can be found later.

Technology radars

Two radars sit alongside the handrail.

Defra staff only

These links only open on a Defra device, or on the Defra VPN, and you need to be signed in with your Defra account. They will not work from a personal device or for delivery partners without Defra access.

Radar What it tells you Use it to
Tools radar (Defra device or VPN) The software tools approved for use in Defra Check whether a tool is already approved before you buy or adopt one (GR-TECH-01, GR-TECH-04)
Emerging Technology Radar 2026 (Defra device or VPN) The emerging technologies Defra is watching, what is ready to use now, what is on the horizon and what still needs time to mature Spot opportunities early, and find out whether a technology is mature enough before you build on it

The Emerging Technology Radar is published each year, and the 2026 edition added 28 technologies. It is organised around four themes that match where Defra group priorities are heading:

  • Digital transformation and data-driven services - such as AI agents, digital twins, geospatial intelligence and privacy-preserving data tools
  • Environmental intelligence and resilience - such as quantum sensors, edge intelligence, drones, autonomous vehicles and real-time monitoring
  • Sustainable digital operations and leadership - such as energy-efficient compute, green software practice, circular IT asset management and lower-carbon cloud options
  • Cybersecurity and operational resilience - such as secure multiparty computation, homomorphic encryption, post-quantum cryptography and AI-supported cyber defence

The emerging technology radar is not a list of approved technology. Before adopting an emerging technology, check the technology capabilities and the guardrails, and talk to the architecture team - novel use of AI goes to the Technical Design Authority (GR-AI-06).

Machine-readable model

The capability models are maintained as YAML in the repository and published as JSON so other tools - portfolio management, architecture repositories, dashboards - can use them:

The site build validates the model: unknown references or technology capabilities that support nothing will fail the build.