Routes by role Level: Foundation
Start from your role
Choose the role closest to yours. Each route shows what you need to learn, what to do and in what order, and tracks your progress as you go.
In brief
- Pick the role closest to yours. Roles describe responsibilities, not job titles; you may hold more than one.
- Each route has five stages: learn, prepare, do, report and improve.
- Mark steps as done to track your progress. It is saved in this browser only.
Easy read summary
- Choose the job closest to yours.
- You will see the steps for your job in order.
- Tick each step when you finish it.
Tailor to your organisation
Tell us about your role and your organisation, and the page suggests where to start: the modules, the activities and the next checkpoint that fit. If you have taken the self-assessment on the Capability model page in this browser, your organisation's maturity is filled in from it. Nothing leaves your browser.O: This playbook's own synthesis of published guidance
Where to start by maturity
| Maturity | Start with activities at | Next checkpoint | Advice |
|---|---|---|---|
| Beginning | Start | First 30 days | Start small: name owners and list critical assets before buying tools or writing strategies. |
| Emerging | Start | Days 61 to 90 | Finish the basics for your most important assets, then make them repeatable. |
| Learning | Build | Six-month checkpoint | You meet the policy for critical assets. Make the next return easier and fix your weakest strand. |
| Developing | Embed | Twelve-month checkpoint | Make the cycle routine in business as usual, with a budget, and prepare assets for wider reuse. |
| Mastering | Embed | Twelve-month checkpoint | Share what works across government, and help others in your sector. |
What to learn by data literacy
| Literacy | What it looks like | Module levels | Tips |
|---|---|---|---|
| Starting out | Few people outside the data team use terms such as owner, metadata or data quality with confidence. | Foundation |
|
| Building | People in data roles know the terms; others are learning. Some teams already catalogue or check quality. | Foundation, Practitioner |
|
| Confident | Data roles are established, and people across the organisation ask good questions about data. | Foundation, Practitioner, Advanced |
|
Business as usual or change
| Context | What it is | Roles involved | Tips |
|---|---|---|---|
| Business as usual | Running critical data assets day to day: the yearly cycle of review, catalogue upkeep, quality checks and the return. | Chief data officer, Lead policy coordinator, Data governance board, Data owner, Information asset owner, Data steward, Data custodian, Catalogue manager, Data quality lead or analyst, Data protection officer, Data users |
|
| Change programme | A programme or project that creates, changes, moves or retires critical data assets, from business case to handover. | Senior responsible owner, Programme or project manager, Programme office and assurance, Service or product owner, Design authority or solution architect, Data migration lead, Commercial lead, Data owner, Data steward, Data protection officer |
|
| Both | Your organisation runs business as usual and change at the same time, and the same people often do both. | Chief data officer, Lead policy coordinator, Data owner, Data steward, Design authority or solution architect, Commercial lead |
|
Each role's usual context: Chief data officer: both; Lead policy coordinator: business as usual; Data owner: both; Data steward: business as usual; Catalogue manager or data custodian: business as usual; Data quality lead or analyst: business as usual; Programme or project lead: change programme; Commercial or technology lead: both.
Not sure of your maturity? Take the self-assessment first; this page reads the result.
Choose a role
- Chief data officerYou are accountable for adopting the policy across your organisation and, in a department, its arm's length bodies.
- Lead policy coordinatorYou coordinate adoption day to day, collate and assure the return, and represent your organisation at the Working Group.
- Data ownerYou are the senior leader accountable for the meaning, content, quality and management of one or more critical data assets.
- Data stewardYou run critical data assets day to day - their standards, access, metadata and quality processes.
- Catalogue manager or data custodianYou run the catalogue and the systems behind it, so records can be found, harvested and kept accurate.
- Data quality lead or analystYou bring methods and tools for measuring and improving quality across many assets.
- Programme or project leadYou lead a medium or large change programme or project that creates, changes, migrates or retires critical data assets.
- Commercial or technology leadYou choose, buy or build the tools that catalogue, check and govern critical data, and you write the contracts that keep the data yours.
Chief data officer
You are accountable for adopting the policy across your organisation and, in a department, its arm's length bodies.
Your context
You have little time, decide on resourcing and report progress to the Chief Data Officer Council. You need summaries first and detail on request.
Your goals
- Adopt the policy once, without the three capabilities duplicating effort
- Know your organisation's position at any time
- Show credible progress to the CDO Council
What you need
- As a chief data officer, I need see what the policy requires and who does what, so that I can assign the work with confidence.
- As a chief data officer, I need a short, current view of progress, so that I can unblock problems before the return is due.
What gets in the way
- Governance, cataloguing and quality run by different teams record the same facts in different places
- Evidence is assembled in a rush at the deadline
We design for
- Reads on a phone between meetings
- Wants the summary before the detail
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
Every critical data asset has a named owner, a current catalogue record and a DQAP, and the return goes in on time.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: The DAM Policy - what it asks of you15 minutes, foundationNot started
- Learn: Roles and accountability15 minutes, foundationNot started
Prepare
- Agree the mandate and scopeData governance, step 1Not started
- Appoint the coordinating teamData cataloguing, step 1Not started
Do
- Confirm owners for every critical assetData governance, step 3Not started
- Approve designation decisionsData cataloguing, step 3Not started
Report
- Sign off the return to GDSData cataloguing, step 7Not started
Improve
- Review assurance and refresh the mandateData governance, step 5Not started
- Learn: Running the three capabilities as one yearly cycle20 minutes, advancedNot started
- Learn: Leading data asset management - your first year25 minutes, foundationNot started
- Take a baselineCapability playbook, MAT-1Not started
- Rank critical assets by what they make possibleCapability playbook, STR-1Not started
Your learning journey (7 modules, about 145 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M02 Roles and accountability Foundation 15 minNot started
- M03 Setting up governance with five recipes Practitioner 30 minNot started
- M09 Running the three capabilities as one yearly cycle Advanced 20 minNot started
- M10 Inclusive data practice Foundation 20 minNot started
- M12 What makes a critical data asset AI-ready Foundation 20 minNot started
- M18 Leading data asset management - your first year Foundation 25 minNot started
Lead policy coordinator
You coordinate adoption day to day, collate and assure the return, and represent your organisation at the Working Group.
Your context
You work across many teams, often alongside another role. You need one route from start to return and templates you can reuse.
Your goals
- Get the baseline return right first time
- Avoid retyping information that already exists
- Keep arm's length bodies in step
What you need
- As a lead policy coordinator, I need one ordered route from mobilising to an assured return, so that nothing is missed and nothing is done twice.
- As a lead policy coordinator, I need templates that match what GDS asks for, so that the return is collation, not reconstruction.
What gets in the way
- Requests arrive from several directions with different deadlines
- Owners change and nobody updates the record
We design for
- Works compressed or part-time hours and picks tasks up after gaps
- New to data management
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
An assured return goes in on time, built from catalogue records rather than retyped.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: The DAM Policy - what it asks of you15 minutes, foundationNot started
- Learn: Finding and designating critical data assets25 minutes, practitionerNot started
Prepare
- Set up the team and ALB contactsData cataloguing, step 1Not started
- Build the candidate listData cataloguing, step 2Not started
Do
- Run designationData cataloguing, step 3Not started
- Confirm owners and contact pointsData cataloguing, step 4Not started
- Get records completedData cataloguing, step 5Not started
Report
- Prepare and assure the returnData cataloguing, step 7Not started
Improve
- Schedule the annual reviewData cataloguing, step 8Not started
- Learn: Running the three capabilities as one yearly cycle20 minutes, advancedNot started
- Check what each data role needs to knowCapability playbook, SKILL-1Not started
- Add data asset questions to existing checkpointsCapability playbook, ASSR-1Not started
Your learning journey (8 modules, about 160 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M02 Roles and accountability Foundation 15 minNot started
- M04 Finding and designating critical data assets Practitioner 25 minNot started
- M06 Cataloguing, harvesting and reporting to GDS Practitioner 20 minNot started
- M09 Running the three capabilities as one yearly cycle Advanced 20 minNot started
- M10 Inclusive data practice Foundation 20 minNot started
- M12 What makes a critical data asset AI-ready Foundation 20 minNot started
- M18 Leading data asset management - your first year Foundation 25 minNot started
Data owner
You are the senior leader accountable for the meaning, content, quality and management of one or more critical data assets.
Your context
Data ownership is one of several responsibilities. You make decisions and sign off; others do the day-to-day work.
Your goals
- Understand exactly what you are accountable for
- Make decisions quickly with the right evidence
- Name a successor so the asset is never orphaned
What you need
- As a data owner, I need a clear list of the decisions that are mine, so that I can sign off with confidence.
- As a data owner, I need to see how good my data is and what it should not be used for, so that I can accept or reject risks knowingly.
What gets in the way
- Unclear difference between data owner and information asset owner
- Asked to sign things without the context
We design for
- Uses screen magnification at 200 per cent
- Prefers checklists to long text
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
You can explain your assets' purpose, quality and risks, and your successor is named.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: The DAM Policy - what it asks of you15 minutes, foundationNot started
- Learn: Roles and accountability15 minutes, foundationNot started
Prepare
- Accept the role and name a successorData governance, step 3Not started
Do
- Agree quality targetsData quality, step 2Not started
- Decide priorities and accept risksData quality, step 4Not started
Report
- Approve the data quality statementData quality, step 6Not started
Improve
- Hold the annual reviewData quality, step 8Not started
- Learn: Data quality foundations15 minutes, foundationNot started
- Record the main risk to each critical assetCapability playbook, RISK-1Not started
- Find the critical assets held or supplied by third partiesCapability playbook, SUPP-1Not started
Your learning journey (6 modules, about 105 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M02 Roles and accountability Foundation 15 minNot started
- M07 Data quality foundations Foundation 15 minNot started
- M10 Inclusive data practice Foundation 20 minNot started
- M12 What makes a critical data asset AI-ready Foundation 20 minNot started
- M14 Start from the question the data must answer Practitioner 20 minNot started
Data steward
You run critical data assets day to day - their standards, access, metadata and quality processes.
Your context
You do the detailed work and keep the records current. You need step-by-step methods and templates.
Your goals
- Keep the catalogue record and the DQAP current without heroics
- Find problems before users do
- Hand over cleanly when you move on
What you need
- As a data steward, I need step-by-step instructions with templates, so that I can do the work consistently across assets.
- As a data steward, I need one place to record each fact once, so that the catalogue, the DQAP and the register always agree.
What gets in the way
- The same owner and review date recorded in three places
- Quality rules kept only in one tool
We design for
- Dyslexic and prefers short steps
- Uses a screen reader for long documents
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
Every asset you steward has a current record, rules with targets, and a quality statement users understand.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: Describing assets with metadata others can use30 minutes, practitionerNot started
- Learn: Data quality foundations15 minutes, foundationNot started
Prepare
- Agree critical data elementsData quality, step 1Not started
- Complete the catalogue recordData cataloguing, step 5Not started
Do
- Write rules and targetsData quality, step 2Not started
- Measure a baselineData quality, step 3Not started
- Fix causes at sourceData quality, step 5Not started
Report
- Publish the quality statementData quality, step 6Not started
Improve
- Automate checksData quality, step 7Not started
- Learn: Building a DQAP and scoring issues35 minutes, practitionerNot started
- Find out who uses each critical asset and what gets in their wayCapability playbook, CULT-1Not started
Your learning journey (9 modules, about 215 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M05 Describing assets with metadata others can use Practitioner 30 minNot started
- M07 Data quality foundations Foundation 15 minNot started
- M08 Building a DQAP and scoring issues Practitioner 35 minNot started
- M10 Inclusive data practice Foundation 20 minNot started
- M12 What makes a critical data asset AI-ready Foundation 20 minNot started
- M13 From FAIR to AI-ready metadata Practitioner 30 minNot started
- M14 Start from the question the data must answer Practitioner 20 minNot started
- M17 Governing AI use of critical data in practice Advanced 30 minNot started
Catalogue manager or data custodian
You run the catalogue and the systems behind it, so records can be found, harvested and kept accurate.
Your context
You work with tools and standards. You need to know what any catalogue must expose, whatever the product.
Your goals
- Records that machines can harvest, not only people
- Conform to the cross-government metadata standard
- Avoid lock-in to one product
What you need
- As a catalogue manager or data custodian, I need the exact metadata properties and how they map to the standard, so that records conform first time.
- As a catalogue manager or data custodian, I need to know what the Discoverability Platform will expect, so that we do not rebuild the feed later.
What gets in the way
- Guidance and model do not list the same properties
- Internal-only links break outside the organisation
We design for
- Works mainly by keyboard
- English is an additional language
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
Every critical data asset record is complete, conforms to the standard and can be harvested as DCAT.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: Describing assets with metadata others can use30 minutes, practitionerNot started
- Learn: Cataloguing, harvesting and reporting to GDS20 minutes, practitionerNot started
Prepare
- Search existing registersData cataloguing, step 2Not started
Do
- Configure record fieldsData cataloguing, step 5Not started
- Expose records as DCATData cataloguing, step 6Not started
Report
- Produce the return from recordsData cataloguing, step 7Not started
Improve
- Keep records currentData cataloguing, step 8Not started
- Map the tools you have against what the policy needsCapability playbook, TOOL-1Not started
- Learn: Buying tools for data asset management without lock-in30 minutes, practitionerNot started
Your learning journey (7 modules, about 180 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M05 Describing assets with metadata others can use Practitioner 30 minNot started
- M06 Cataloguing, harvesting and reporting to GDS Practitioner 20 minNot started
- M10 Inclusive data practice Foundation 20 minNot started
- M13 From FAIR to AI-ready metadata Practitioner 30 minNot started
- M15 Connecting data to AI with linked data, knowledge graphs and MCP Advanced 35 minNot started
- M19 Buying tools for data asset management without lock-in Practitioner 30 minNot started
Data quality lead or analyst
You bring methods and tools for measuring and improving quality across many assets.
Your context
You support several stewards. You need a consistent scoring method and tools that work without installing anything.
Your goals
- Score issues the same way across assets
- Automate measurement across assets
- Show quality fairly for every group the data describes
What you need
- As a data quality lead or analyst, I need the government scoring method and tools that apply it, so that priorities are consistent and defensible.
- As a data quality lead or analyst, I need checks that break results down by group, so that poor quality for some people is not averaged away.
What gets in the way
- Every team scores issues differently
- Quality reported as one average
We design for
- Colour-blind, so charts must not rely on colour alone
- Works across several devices
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
Every critical data asset has scored issues, automated checks and quality reported by group where lawful.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: Data quality foundations15 minutes, foundationNot started
- Learn: Building a DQAP and scoring issues35 minutes, practitionerNot started
Prepare
- Build the rule libraryData quality, step 2Not started
Do
- Run baselinesData quality, step 3Not started
- Score and rank issuesData quality, step 4Not started
Report
- Publish quality metadataData quality, step 6Not started
Improve
- Automate and monitorData quality, step 7Not started
- Learn: Inclusive data practice20 minutes, foundationNot started
- Prove it with your own data before you signCapability playbook, TOOL-3Not started
Your learning journey (8 modules, about 185 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M07 Data quality foundations Foundation 15 minNot started
- M08 Building a DQAP and scoring issues Practitioner 35 minNot started
- M09 Running the three capabilities as one yearly cycle Advanced 20 minNot started
- M10 Inclusive data practice Foundation 20 minNot started
- M12 What makes a critical data asset AI-ready Foundation 20 minNot started
- M17 Governing AI use of critical data in practice Advanced 30 minNot started
- M19 Buying tools for data asset management without lock-in Practitioner 30 minNot started
Programme or project lead
You lead a medium or large change programme or project that creates, changes, migrates or retires critical data assets.
Your context
Your programme has its own governance, gates, budget and suppliers. Data asset management can feel like someone else's job until a gate review, a migration or handover exposes the gaps.
Your goals
- Pass assurance gates without late data surprises
- Hand over assets with owners and quality plans in place
- Avoid creating the next legacy system
What you need
- As a programme or project lead, I need to know which DAM duties apply to my programme and when, so that they are planned and funded from the business case.
- As a programme or project lead, I need clear data roles inside my programme team, so that nobody assumes someone else is doing it.
What gets in the way
- Data owners sit outside the programme and are hard to reach
- Migration quality problems surface only at cutover
We design for
- Reads on the move between meetings
- Needs a one-page view to share with the programme board
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
Every critical asset the programme touches has an owner, a catalogue entry and a quality plan before the programme closes.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: The DAM Policy - what it asks of you15 minutes, foundationNot started
- Learn: Embedding the policy in delivery and change30 minutes, practitionerNot started
Prepare
- Confirm data owners for every asset in scope of the programmeData governance, step 3Not started
- List the critical assets the programme creates, changes or retiresData cataloguing, step 2Not started
Do
- Agree quality rules and targets with owners before buildData quality, step 2Not started
- Catalogue new assets before go-liveData cataloguing, step 5Not started
- Migrate with reconciliationCapability playbook, LEG-2Not started
Report
- Show DAM evidence at each gate reviewData governance, step 5Not started
- Add data asset questions to existing checkpointsCapability playbook, ASSR-1Not started
Improve
- Hand over the DQAP and ownership to business as usualData quality, step 7Not started
- Learn: Running the three capabilities as one yearly cycle20 minutes, advancedNot started
- Hand over with a checklistCapability playbook, HAND-2Not started
- Pick a few measures and record the baselineCapability playbook, BEN-1Not started
Your learning journey (6 modules, about 135 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M02 Roles and accountability Foundation 15 minNot started
- M11 Embedding the policy in delivery and change Practitioner 30 minNot started
- M09 Running the three capabilities as one yearly cycle Advanced 20 minNot started
- M18 Leading data asset management - your first year Foundation 25 minNot started
- M19 Buying tools for data asset management without lock-in Practitioner 30 minNot started
Commercial or technology lead
You choose, buy or build the tools that catalogue, check and govern critical data, and you write the contracts that keep the data yours.
Your context
You are asked to find a catalogue, quality or master data tool quickly, often with a supplier's suite already on the table. You need requirements you can use, not a lecture on data management.
Your goals
- Buy what the DAM Policy actually needs
- Prove a tool works with our data before signing
- Keep the option to leave
What you need
- As a commercial or technology lead, I need ready-made requirements for each kind of tool, with priorities, so that I can run a request for information without starting from a blank page.
- As a commercial or technology lead, I need contract clauses that protect our data, so that we are not locked in when the contract ends.
What gets in the way
- Supplier demonstrations use their data and not ours
- Bundled suites make it hard to price or leave one part
We design for
- Works to procurement deadlines
- Needs downloads that open in a spreadsheet
Illustrative access needs, not drawn from research with this audience (OR-04).
Success looks like
The tool chosen meets every Must requirement in a proof of concept with your own data, and the contract includes export, exit and data processing terms.
Your route, step by step
Work through each stage. Status updates as you mark steps and learning activities as done.
Learn
- Learn: The DAM Policy - what it asks of you15 minutes, foundationNot started
- Learn: Buying tools for data asset management without lock-in30 minutes, practitionerNot started
Prepare
- Map the tools you have against what the policy needsCapability playbook, TOOL-1Not started
- Find the critical assets held or supplied by third partiesCapability playbook, SUPP-1Not started
Do
- Run a request for information with ready-made requirementsCapability playbook, TOOL-2Not started
- Prove it with your own data before you signCapability playbook, TOOL-3Not started
- Put data terms in every new contractCapability playbook, SUPP-2Not started
Report
- Write and cost the exit planCapability playbook, EXIT-2Not started
Improve
- Check before every renewalCapability playbook, TOOL-4Not started
- Test the exit every yearCapability playbook, EXIT-3Not started
- Learn: Embedding the policy in delivery and change30 minutes, practitionerNot started
Your learning journey (3 modules, about 75 minutes)
- M01 The DAM Policy - what it asks of you Foundation 15 minNot started
- M11 Embedding the policy in delivery and change Practitioner 30 minNot started
- M19 Buying tools for data asset management without lock-in Practitioner 30 minNot started
Was this page useful? Tell us Tell us privately, without GitHub