Bringing the three together Level: Practitioner
How the three capabilities join up
Governance gives each asset an owner and a place to decide. Cataloguing describes it so others can find it. Quality proves it is fit to use. The hand-offs below mean each fact is recorded once.
In brief
- Record the owner once, in the ownership register, and reuse it in the catalogue record and the DQAP.
- Use one annual review date per asset for the record, the owner and the DQAP.
- Build the GDS return and the governance evidence from the same records.
Hand-offs between capabilities
| ID | From | To | What passes |
|---|---|---|---|
| IL-01 | Governance 3: Assign | Cataloguing 4: Confirm ownership | The ownership register is the source for the owner and successor on the catalogue record. Record them once. |
| IL-02 | Cataloguing 4: Confirm ownership | Quality 1: Identify critical data | The owner on the catalogue record is the owner who signs off DQAP targets and accepts risks. |
| IL-03 | Cataloguing 3: Test and designate | Quality 1: Identify critical data | The asset boundary set at designation is the scope of the DQAP. No DQAP for fields outside the asset. |
| IL-04 | Quality 6: Report openly | Cataloguing 5: Describe | Quality information is published on the catalogue record, so the record says how good the data is. |
| IL-05 | Quality 6: Report openly | Governance 4: Operate | Quality issues above Medium enter the board's issue and risk log. |
| IL-06 | Governance 2: Frame | Cataloguing 5: Describe | The metadata standard and the classification policy adopted in Frame are what records are checked against. |
| IL-07 | Cataloguing 8: Maintain and review | Quality 8: Review every year | One annual review date per asset covers the record, the owner and the DQAP together. |
| IL-08 | Cataloguing 7: Report to GDS | Governance 5: Assure | The GDS return is part of the governance evidence pack, assembled as you go. |
| IL-09 | Governance 5: Assure | Governance 1: Mandate | Lessons from assurance refresh the mandate for the next cycle. |
One joined-up year
Before the window
- Governance: Confirm the mandate and owners
- Cataloguing: Mobilise and refresh candidates
- Quality: Agree rules for any new assets
Through the year
- Governance: Operate the logs
- Cataloguing: Describe and keep records current
- Quality: Measure each cycle and fix at source
Quarterly
- Governance: Board sees measures and exceptions
- Cataloguing: Check harvest and record currency
- Quality: Update the action plan and statement
Annual review date
- Governance: Assure and refresh the mandate
- Cataloguing: Review every record and submit the return
- Quality: Review rules and targets
One set of roles
The same roles appear in all three playbooks. Records name roles, never individuals.
- Chief data officer (CDO)V: Verified against the primary source
Implements the policy in the organisation and leads the identification exercise; sponsors governance. - Lead policy coordinator (COO)P: Practitioner material from cross-government playbooks not yet published
Coordinates identification, collates and assures the return (including ALBs), and is the link to the Working Group. - Data governance board (BRD)P: Practitioner material from cross-government playbooks not yet published
Sets policy direction, resolves escalations and sees every asset's status. Chaired by the CDO, SIRO or equivalent. - Data owner (OWN)V: Verified against the primary source
Senior leader accountable for the meaning, content, quality and management of the asset; approves changes and signs off targets and risks. - Information asset owner (IAO)V: Verified against the primary source
Accountable to the SIRO for protecting the whole information asset; may hold data owner duties under the IAO or hybrid option. - Data steward (STW)V: Verified against the primary source
Runs the asset day to day: policies and standards, access, quality processes and documentation such as the business glossary in the catalogue. - Data custodian (CUS)V: Verified against the primary source
Technical expert for the system holding the data: storage, access controls, auditable change and disposal. - Catalogue manager (CAT)O: This playbook's own synthesis of published guidance
Runs the organisation's catalogue, its metadata standard and its harvest feed. - Data quality lead or analyst (DQL)V: Verified against the primary source
Methods, profiling, tooling and reporting for data quality. - Data protection officer (DPO)K: General knowledge, not checked against a source in this release
Independent advice on lawful basis, DPIAs and data subject rights. - Data users (USR)V: Verified against the primary source
Teams, services and other organisations that rely on the data; say what they need and report problems. - People the data describes (PUB)P: Practitioner material from cross-government playbooks not yet published
Citizens, communities and their representatives; help spot exclusion and test whether quality information is understandable. - Senior responsible owner (SRO)O: This playbook's own synthesis of published guidance
Accountable for a programme or project meeting its objectives. Makes sure data assets the change creates, alters or retires have owners, budgets and assurance, and signs off handover to business as usual. - Programme or project manager (PDM)O: This playbook's own synthesis of published guidance
Plans and runs the change. Builds DAM activities into the plan, the risk register and gate criteria, and makes sure data owners are consulted at each stage. - Service or product owner (SVO)O: This playbook's own synthesis of published guidance
Owns the service the change delivers. Decides what data the service collects and exposes, and shows DAM evidence at service assessments. - Design authority or solution architect (ARC)O: This playbook's own synthesis of published guidance
Approves data models, platforms and integrations. Checks new designs use open standards, documented schemas and an exit route, so they do not become future legacy. - Data migration lead (MIG)O: This playbook's own synthesis of published guidance
Plans and runs data migration. Profiles quality before moving data, reconciles after, and keeps catalogue entries and ownership in step. - Commercial lead (CML)O: This playbook's own synthesis of published guidance
Runs procurement and manages contracts. Writes data ownership, metadata delivery, quality reporting and exit into contracts. - Programme office and assurance (PMO)O: This playbook's own synthesis of published guidance
Tracks delivery and organises assurance reviews. Checks DAM checkpoints are met at each gate and reports gaps to the senior responsible owner.
Who does what across all three
| Step | CDO | COO | BRD | OWN | IAO | STW | CUS | CAT | DQL | DPO | USR | PUB | SRO | PDM | SVO | ARC | MIG | CML | PMO |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Governance 1. Mandate | A | R | R | C | I | C | |||||||||||||
| Governance 2. Frame | A | R | A | C | C | C | |||||||||||||
| Governance 3. Assign | A | R | C | R | C | R | C | ||||||||||||
| Governance 4. Operate | I | A | R | R | C | C | C | ||||||||||||
| Governance 5. Assure | A | R | R | C | C | C | |||||||||||||
| Cataloguing 1. Mobilise | A | R | C | C | C | ||||||||||||||
| Cataloguing 2. Discover candidates | A | R | C | C | R | C | |||||||||||||
| Cataloguing 3. Test and designate | A | R | R | C | C | ||||||||||||||
| Cataloguing 4. Confirm ownership | A | C | R | R | |||||||||||||||
| Cataloguing 5. Describe | A | R | C | R | C | ||||||||||||||
| Cataloguing 6. Catalogue and expose | A | C | R | R | |||||||||||||||
| Cataloguing 7. Report to GDS | A | R | I | C | R | ||||||||||||||
| Cataloguing 8. Maintain and review | C | A | R | R | |||||||||||||||
| Quality 1. Identify critical data | A | R | C | C | I | ||||||||||||||
| Quality 2. Define rules and targets | A | R | R | C | |||||||||||||||
| Quality 3. Measure a baseline | A | R | C | R | |||||||||||||||
| Quality 4. Prioritise and set goals | I | A | R | C | |||||||||||||||
| Quality 5. Fix causes at source | A | R | R | C | |||||||||||||||
| Quality 6. Report openly | I | A | R | R | I | ||||||||||||||
| Quality 7. Repeat and sustain | A | R | R | R | |||||||||||||||
| Quality 8. Review every year | A | R | C | C |
Was this page useful? Tell us Tell us privately, without GitHub