Data Ownership and Accountability

What it is

It is not about possession. UK government guidance puts it this way: data ownership does not deal with possession of data; it formalises the roles of people responsible for managing data through its life cycle and establishes accountability for access, usage and issue resolution.

Supervisory guidance treats it as a minimum. The European Central Bank lists, among the minimum elements of a data governance framework, data owners responsible for key risk indicators and critical data elements throughout the complete aggregation process.

Why it matters

Supervisors keep finding that weak ownership, not tooling, holds back data programmes. Of 31 banks assessed against the Basel risk-data principles, two were fully compliant.

The Basel Committee attributes delayed compliance largely to lack of prioritisation and insufficient ownership by the board and senior management, alongside data architecture and IT infrastructure challenges.

The problem it addresses

DII editorial view

When nobody has the authority to decide, questions about access, definition and quality circulate without an answer. Ownership assigned in name only, or given to IT for data the business is accountable for, leaves the same gap. Formal roles exist so that a decision about data has someone entitled to make it.

Business and organisational relevance

DII editorial view

Ownership is an organisational decision before it is a data one. It works when the owner is senior enough to decide and is the person the business already holds responsible for the outcome the data supports.

Practical use cases

• Naming an accountable owner for each critical data domain
• Reporting data quality to the board against a small set of indicators
• Settling who decides when two teams disagree about access or definition

Benefits and opportunities

• Decisions about data get made, by someone entitled to make them
• Other governance work, from quality to contracts, has a person to attach to

Risks, limitations and dependencies

• Owners named without authority, time or support
• Ownership assigned to IT for data the business is accountable for
• The evidence is from banking supervision and UK government, and the Basel figure dates from 2023; it does not measure other sectors

Prerequisites for adoption

DII editorial view

• Senior sponsorship; an owner needs authority, not only a title
• A short list of critical data domains to start with
• Clear separation of the owner, steward and custodian roles

Implementation considerations

• Start with critical data. Name an owner with real authority for each critical data domain before attempting the whole estate.
• Report upwards. Report data quality to the board against a small set of indicators.
• Separate the roles. Owner, steward and custodian are different jobs; say which is which.

The DII Radar assessment

Approved DII Radar assessment

DII assesses Data Ownership and Accountability as High relevance, with direction Stable. Its strategic impact is assessed as High and its enterprise adoption as Scaling. It is in the catalogue and is not one of the ten entries on the current Radar.

DII relevance is our assessment of current significance and momentum, based on evidence, market development and adoption. Direction is the observed trajectory of relevance and adoption. Strategic impact is the potential or current significance to enterprise data capability, and enterprise adoption is the extent of current real-world enterprise adoption; together they set the position on the Radar. The Radar is not a prediction, vendor comparison or performance ranking.

Evidence basis: Basel Committee progress report on risk data aggregation (November 2023); ECB guide on risk data aggregation and reporting (May 2024); UK Government data ownership model (April 2026).

What to consider next

DII editorial view

• Name an owner with real authority for each critical data domain
• Report data quality to the board against a small set of indicators
• Settle in advance who decides when two teams disagree