Get started Level: Foundation
New or leading? Your first year
New to data asset management, or asked to lead it? This route tells you what to aim for, how to know it is working, and what to do in your first 30, 60 and 90 days, with checkpoints at 6 and 12 months. Targets use the maturity levels on the Capability model page, which follow the Data Maturity Assessment for Government.
In brief
- What to aim for, as Must, Should and Could, with the outcomes each brings.
- Outcomes with indicators and example targets you can adapt.
- A plan for the first 30, 60 and 90 days, with checkpoints at 6 and 12 months and a maturity target for each.
Who this is for
- New to this
You have joined a data team, or been named as an owner or steward, and the terms are new. - Leading a team
You run a catalogue, quality or governance team and need a plan for it. - Leading the capability
You are defining, designing, deploying or enabling data asset management across an organisation.
Six things to know first
- Critical data asset: Data that matters most to services and decisions. The DAM Policy asks you to find these, describe them, name an owner and manage their quality.
- Data owner: The person accountable for decisions about a data asset. Every critical asset must have one.
- Catalogue record: The description of an asset: what it is, who owns it, where it is and how it can be used.
- Data quality action plan: How you know, prove and improve the quality of an asset, in seven steps.
- The yearly cycle: Find, describe, own, check and report, every year, so the return stays true.
- Maturity: How established the practice is, from Beginning to Mastering. You do not need Mastering everywhere.
Then take module M01 and the route for your role.
What to aim for
Aims ordered by priority (MoSCoW). The Must aims are what the DAM Policy needs; the rest make it lastO: This playbook's own synthesis of published guidance.
| Priority | Aim | Outcome | Capabilities |
|---|---|---|---|
| Must | Every critical asset is identified, has a named owner, a catalogue record and a quality plan, and is reported on time. | The organisation meets the DAM Policy. | Identify and scope critical data assets, Data cataloguing and metadata management, Data ownership and stewardship, Data quality management through action plans, Central reporting, assurance and arm's length body coordination |
| Must | The chief data officer leads, a board meets, and decisions are recorded. | Someone is accountable and decisions stick. | Accountable leadership and policy oversight |
| Should | Critical assets are ranked by value and risk, with a plan for the top ten. | Effort goes where it matters most. | Data strategy and prioritisation by reuse value, Data risk management |
| Should | Business cases, spend control and contracts ask about critical data. | New work does not create new legacy. | Investment, business cases and value, Integration with programmes, spend control and assurance, Third-party and supplier data, Avoiding future legacy: open standards, portability and exit |
| Should | Owners and stewards know their role and have it in their objectives. | The work continues when people move. | Data skills, capability and literacy, Ownership transition and handover to business as usual |
| Could | Quality results show in the catalogue, and users can find and request data themselves. | Data is reused instead of collected again. | Catalogue and quality tooling, Data culture and engagement with users |
| Could | Critical assets are prepared for AI use and wider sharing. | The organisation can use AI safely on its best data. | AI readiness and data and AI ethics, Cross-boundary collaboration |
| Won't (this year) | Every data asset in the organisation described and quality-managed. | Start with critical assets; extend once the cycle runs. | Data life cycle management |
Outcomes, indicators and targets
Example targets are examples. Set your own from your baseline, and agree them with your board.
| ID | Outcome | Indicator | Target | Maturity strand |
|---|---|---|---|---|
| OUT-1 | Critical assets are known and owned | Share of critical assets with a named owner and a catalogue record | 100% of reported assets by the return date (example) | Ownership and governance |
| OUT-2 | The return is complete and on time | Return submitted on time with core metadata complete | On time, with no core field blank (example) | Cataloguing and reporting |
| OUT-3 | Quality is known and improving | Share of critical assets with a DQAP and quality in their target range | Every asset with a DQAP; half in range within a year (example) | Quality management |
| OUT-4 | Change does not create legacy | Share of business cases and checkpoints that asked about critical data | All major programmes within a year (example) | Change and investment |
| OUT-5 | People know their role | Share of named role holders who completed core learning | 80% within six months of appointment (example) | Ownership and governance |
Your first year
Five checkpoints. Tick each one off as you go; your progress stays in this browser.
Checkpoint
First 30 days
Focus: Learn, listen and find out where you are.O: This playbook's own synthesis of published guidance
What to do
- Read the DAM Policy page and the guide for your role.
- Meet the chief data officer, the board chair and a few owners and stewards.
- Find last year's return, the asset list and any catalogue.
- Take a first baseline with the self-assessment on the Capability model page.
- You will have
- A baseline
- A list of the people involved
- A first view of gaps
- Questions to ask at the checkpoint
- Do we know our critical assets?
- Does each have an owner who knows it?
- When is the next return due, and what will it show?
- Maturity to aim for
- Ownership and governance: Beginning
- Cataloguing and reporting: Beginning
- Quality management: Beginning
- Change and investment: Beginning
- Playbook activities
Checkpoint
Days 31 to 60
Focus: Agree what to aim for and who does what.O: This playbook's own synthesis of published guidance
What to do
- Rank critical assets with the prioritisation scorecard and agree the top ten with the board.
- Agree your Must, Should and Could aims, and the outcomes and indicators.
- Fill gaps in ownership for the top ten.
- Map your tools against the Must requirements.
- You will have
- Agreed aims and outcomes
- Ranked asset list
- Owners for the top ten
- Tool gap list
- Questions to ask at the checkpoint
- Has the board agreed the aims?
- Are the top ten owned?
- Which gaps would the next return expose?
- Maturity to aim for
- Ownership and governance: Emerging
- Cataloguing and reporting: Beginning
- Quality management: Beginning
- Change and investment: Beginning
- Playbook activities
Checkpoint
Days 61 to 90
Focus: Start the cycle on the assets that matter most.O: This playbook's own synthesis of published guidance
What to do
- Complete catalogue records for the top ten.
- Start a data quality action plan for each of the top ten.
- Add the three data questions to spend control and gate reviews.
- Give every named role holder a learning plan.
- You will have
- Top ten catalogued
- DQAPs started
- Checkpoint questions in place
- Learning plans
- Questions to ask at the checkpoint
- Could we report the top ten today?
- Is each top asset's quality known?
- Are new programmes asked about critical data?
- Maturity to aim for
- Ownership and governance: Emerging
- Cataloguing and reporting: Emerging
- Quality management: Emerging
- Change and investment: Emerging
- Playbook activities
Checkpoint
Six-month checkpoint
Focus: Check progress and fix what is stuck.O: This playbook's own synthesis of published guidance
What to do
- Reassess against the baseline, strand by strand.
- Extend ownership and catalogue records to all critical assets.
- Report benefits against the baseline to the board.
- Run a request for information if a tool gap blocks you.
- You will have
- Six-month assessment
- All critical assets owned
- Benefits report
- Questions to ask at the checkpoint
- Which strands moved, and which did not? Why?
- Are we on track for the return?
- What would we stop, start or change?
- Maturity to aim for
- Ownership and governance: Learning
- Cataloguing and reporting: Emerging
- Quality management: Emerging
- Change and investment: Emerging
- Playbook activities
Checkpoint
Twelve-month checkpoint
Focus: Meet the policy and make the cycle routine.O: This playbook's own synthesis of published guidance
What to do
- Submit a complete, on-time return.
- Reassess maturity and reset targets for the next year.
- Re-rank critical assets and update the plan.
- Evaluate what worked, and share the lessons.
- You will have
- Return submitted
- Annual assessment
- Updated plan
- Evaluation
- Questions to ask at the checkpoint
- Do we meet the Must aims?
- Is the cycle owned in business as usual, with a budget?
- Which Should aims come next?
- Maturity to aim for
- Ownership and governance: Learning
- Cataloguing and reporting: Learning
- Quality management: Learning
- Change and investment: Learning
- Playbook activities
Maturity targets at each checkpoint
Levels follow the Data Maturity Assessment for Government: Beginning, Emerging, Learning, Developing, Mastering. The DAM Policy minimum for critical assets sits around Learning.
| Strand | First 30 days | Days 31 to 60 | Days 61 to 90 | Six-month checkpoint | Twelve-month checkpoint |
|---|---|---|---|---|---|
| Ownership and governance | Beginning | Emerging | Emerging | Learning | Learning |
| Cataloguing and reporting | Beginning | Beginning | Emerging | Emerging | Learning |
| Quality management | Beginning | Beginning | Emerging | Emerging | Learning |
| Change and investment | Beginning | Beginning | Emerging | Emerging | Learning |
Download the plan as CSV.
In business as usual or a change programme
The first year looks different depending on where you work. In business as usual the checkpoints follow the yearly cycle; in a programme, tie them to the programme's phases and gates.
Business as usual
Running critical data assets day to day: the yearly cycle of review, catalogue upkeep, quality checks and the return.
Roles involved: 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
- Put the yearly cycle in the calendar: asset review, metadata update, DQAP review, board and return.
- Budget the cycle in the teams that own the assets, so it does not depend on a project.
- Check handovers six months after each project closes.
Change programme
A programme or project that creates, changes, moves or retires critical data assets, from business case to handover.
Roles involved: 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
- Name the critical assets in the business case, and the business-as-usual owner for each before build.
- Use spend control, gate reviews and service assessments as checkpoints for data.
- Plan migration, reconciliation, exit and handover from the start, not at the end.
Both
Your organisation runs business as usual and change at the same time, and the same people often do both.
Roles involved: Chief data officer, Lead policy coordinator, Data owner, Data steward, Design authority or solution architect, Commercial lead
- Keep one asset register, one set of roles and one catalogue for both, so change feeds business as usual.
- Make programmes hand their assets into the yearly cycle with the handover checklist.
For programmes, the Delivery and change page gives the data asset actions for each phase, from business case to retirement. Tailor your route to see the ones for your phase.
Which maturity model fits your aim
| If you need | Use | Source |
|---|---|---|
| A view of the whole organisation's data maturity, comparable across government | Data Maturity Assessment for Government | Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05 |
| Targets for data asset management specifically, by strand | The DAM strands on the Capability model page (same five levels) | Data Maturity Assessment for Government: FrameworkV: Verified against the primary source on 2026-11-05 |
| Quality targets for one asset | The government data quality issues framework, through the DQAP | Government Data Quality HubV: Verified against the primary source on 2026-11-05 |
| Process discipline in a delivery or service team | A CMMI-style ladder, crosswalked to the same levels | Capability Maturity Model Integration (CMMI)V: Verified against the primary source on 2026-11-05 |
| Comparing with industry data management programmes | DCAM | DCAM: Data Management Capability Assessment ModelV: Verified against the primary source on 2026-11-05 |
Assess and evaluate
- Measure the same way each time, so change is real.
- Report against the baseline, not against an ideal.
- Ask users and owners as well as counting.
- Plan a proportionate evaluation with the Magenta Book once the main change is in.
Use the self-assessment for each checkpoint, and record the result in the checkpoint review record below.
Templates
Names and email addresses. Your own working copies can name the people who hold each role and give their work email addresses, handled under your organisation's data protection rules. Do not publish them: anything you put on GitHub or anywhere public should name roles only.
Capability plan for the first year (T-LDR-1)
Business as usual and change
Aims tab (5 fields)
- Priority (MoSCoW)
- Aim
- Outcome
- Capabilities
- Owner (role)
Outcomes and targets tab (8 fields)
- Outcome ID
- Outcome
- Indicator
- Baseline
- Target
- Target date
- Maturity strand
- Owner (role)
Plan tab (6 fields)
- Checkpoint (30, 60, 90 days, 6 or 12 months)
- Action
- Playbook activity ID
- Owner (role)
- Due date
- Status
Maturity tab (6 fields)
- Strand
- Baseline level
- Target at 90 days
- Target at 6 months
- Target at 12 months
- Evidence
Risks tab (4 fields)
- Risk
- Owner (role)
- Action
- Due date
Download the workbook (OpenDocument spreadsheet, 5 tabs) · Aims (CSV) · Outcomes and targets (CSV) · Plan (CSV) · Maturity (CSV) · Risks (CSV) · All templates (CSV)
Checkpoint review record (T-LDR-2)
Business as usual and change
- Checkpoint
- Date
- Strand
- Level at last checkpoint
- Level now
- Evidence
- What worked
- What did not
- Decision (continue or change or stop)
- Actions
- Owner (role)
- Reviewed by (role or forum)
Was this page useful? Tell us Tell us privately, without GitHub