Data Governance & Ownership

A governance charter, named owners and stewards for every data domain, a classification scheme, access approval and recertification, retention schedules and a clear route for deciding what a dataset means.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Data Governance & Ownership, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

194

Starter tasks

📊 Data & Analytics

Data Governance & Ownership

Assigning owners to data domains, setting access and retention rules, and making clear who decides what a dataset means.

  1. Data governance charter and scope
  2. Map of data domains and current custodians
  3. Appointing a named owner for each data domain
  4. Data steward roles and responsibility matrix
  5. Data classification scheme with four levels
  6. Classifying the fifty most-used datasets
  7. Access request and approval workflow
  8. Retention schedule for analytics data
  9. Data governance council terms of reference
  10. Decision rights over what a dataset means
  11. Quarterly access recertification
  12. Monthly governance council meeting
  13. Joiners, movers and leavers access hygiene
  14. Monthly retention and disposal run
  15. Governance issue log and weekly triage
  16. Orphaned dataset sweep
  17. Annual data owner attestation
  18. Annual governance policy refresh
  19. Monthly governance scorecard
  20. Policy exceptions and waivers register
  21. Data governance frameworks primer
  22. Data protection duties of a data owner
  23. Steward training and community of practice
  24. Writing governance policies people follow
  25. Role-based and attribute-based access models
  26. Chairing a dispute over dataset meaning
  27. Legal holds and records management basics
  28. Central, federated or hybrid governance model
  29. Choosing a governance and access management tool
  30. Replacing individual grants with access groups
  31. Cutting standing administrator access
  32. Clean-up of spreadsheet and shared drive extracts
  33. Retention rules for sandboxes and scratch schemas
  34. Ownership of service accounts and integrations
  35. Approvals for sharing data with third parties
  36. Launching the governance programme internally
  37. Preparing for an external audit of data access
  38. Answering a data handling due-diligence questionnaire
  39. Annual governance report to the executive team
  40. Tabletop exercise for a data access incident
  41. New manager inheriting a data domain
  42. Governance on one page for a small team
  43. Consolidating data ownership after a merger
  44. Handover when a data owner leaves
  45. Remapping domains after a reorganisation
  46. Governance checks for each new data system
  47. Access policies as code in the warehouse
  48. Data product ownership in a data mesh
  49. Approvals for using data to train AI models
  50. Data residency and cross-border transfer map

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Data governance charter and scope

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Governance programmes that begin with a tool purchase and no mandate stall the first time an owner says no.

First tasks

  • List the three data problems that cost the organisation most in the last year
  • Ask the intended executive sponsor for thirty minutes to agree the mandate
  • Draft the charter with scope, out of scope and the final decision maker
  • Publish the signed charter in the governance space and link it from the intranet

Map of data domains and current custodians

Before anyone can be named an owner, someone has to draw the lines: which tables and reports belong to Customer, Finance, Product, People or Supply, and who in practice looks after each today. A domain map built from the warehouse schemas, the main source systems and the people who get the support questions usually shows a handful of domains with obvious homes and two or three that nobody will claim.

First tasks

  • Export the list of production schemas and their table counts from the warehouse
  • Group schemas and source systems into draft domains in one sheet
  • Ask the data team who they go to with questions about each domain
  • Flag every domain with no clear custodian for the sponsor to resolve

Appointing a named owner for each data domain

An owner who was never asked, has no time and does not know what the role involves is a name on a slide, not an owner. Appointing a senior business person per domain, with a one-page role description, an agreed time commitment of a few hours a month and the sponsor's backing, turns the domain map into real accountability.

First tasks

  • Write a one-page data owner role description with a monthly time estimate
  • Agree a shortlist of candidate owners per domain with the sponsor
  • Hold a twenty-minute conversation with each candidate before naming them
  • Record each owner's written acceptance in the ownership register

Make it yours.

Install Data Governance & Ownership, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.