Data Asset Management (DAM) capability playbooks
Have your sayHelpSite map

How the portal is designed Level: Advanced

Service design and architecture

The design artefacts behind this portal: why it exists, how it will be tested with users, how it works and how each requirement is proved.

In brief

  • Every requirement traces to the pages that meet it and the checks that prove it.
  • The research plan says how each assumption could be proved wrong.
  • The Service Standard rating is a self-assessment, not an assessment.

Theory of change

Departments must adopt the DAM Policy, but guidance for its three capabilities is spread across many pages and practitioner packs, so the same facts are recorded several times and returns are assembled late.

  1. Inputs

    • Published GOV.UK guidance behind the policy
    • Practitioner playbooks for governance and quality
    • Open standards (DCAT, MEM, DQV)
    • GitHub for hosting, contact and automation
  2. Activities

    • Join the three capabilities into one method with one set of roles
    • Give each role a route and a learning journey
    • Check sources, accessibility and links automatically every week
  3. Outputs

    • One portal with step-by-step methods, templates and modules
    • Open data versions of every requirement, template and term
    • A public record of defects, open items and health
  4. Outcomes

    • Owners, records and DQAPs are set up once and reused
    • Returns are built from catalogue records, not retyped
    • Practitioners know which requirement each step meets
  5. Impact

    • Critical data assets are owned, findable and fit for use across government
    • Services that rely on shared data, and the people they serve, are less affected by poor data

Assumptions to test

  • Practitioners will use a single portal if it saves them effort (untested, OR-04)
  • Hand-offs between capabilities reduce duplicate recording (untested)
  • GOV.UK guidance remains the authority and changes are caught weekly

Page owner: the portal's service owner (a role) · Published 5 November 2026 · Last updated 2026-11-06 · Next review 2027-02-05

Was this page useful? Tell us Tell us privately, without GitHub