In governance initiatives, data owner and data steward commonly refer to two roles: the data owner is the business manager who decides for a data domain, the data steward the person, close to operations, who prepares these decisions and applies them day to day. The data owner sets the definitions, the rules of use, the expected level of quality and the access authorisations. The data steward documents, qualifies anomalies and prepares the decisions. In French, the first is rendered as propriétaire des données, the second as intendant des données: these are customary translations, and job titles vary from one organisation to another.
What separates the two roles is the power to decide. The data owner commits their domain; the data steward prepares the decision, then ensures it is applied. A third role, held on the IT side, applies the rules in the systems: the technical custodian, or data custodian. The whole set-up is presented on our data governance page.
Data owner and data steward facing the same data
| Data owner | Data steward | |
|---|---|---|
| Place in the organisation | A business manager with authority over the process in which the data originate | A business or functional expert who handles the data in their work |
| Decides | The definition, the rule of use, the expected level of quality, access | The cases already covered by the written rule |
| Executes | Little: they sign, decide and refer to the arbitration body when another domain is affected | Documentation, maintaining the glossary, qualifying anomalies, preparing decision files |
| Scope | An entire data domain | Part of the domain: an object, a process, an application |
| Time allocated | Decisions to be made within an agreed time | A share of their working time, written into their assignment |
| Trace left | A record of dated decisions | Up-to-date entries, qualified anomalies, prepared files |
Take a request. Management control would like the notion of “active contract” to exclude suspended contracts. The steward lists the reports that use the notion, compares the two definitions, counts the contracts the change would remove and drafts the proposal. The owner decides, or takes the subject to the arbitration body if finance and sales disagree. The steward then updates the glossary and notifies those who consume the data.
These definitions describe a practice and do not come from a text. The page that dama.org devotes to the DAMA-DMBOK, read on 12 November 2026, presents this reference framework as a work that sets out functions and roles, and specifies that it is not a prescriptive standard. The book is ordered from its publisher: we have not consulted it and attribute none of the splits given here to it.
Scope and time are written into a mandate
The owner’s scope is a domain: the data of a single business object. It is defined by the list of critical data the owner answers for, more reliably than by a department title. When several departments create or modify the same data, appointing a single owner becomes tricky, as our article where to start a data governance strategy explains with regard to the customer domain.
The steward’s scope follows knowledge of the ground. The same owner can rely on several stewards: one per application, per process or per site.
Time also distinguishes the two roles. From the owner, the mandate requires a commitment: to make a decision within an agreed time and to sit on the arbitration body. For the steward, it reserves a workload. Suppose, as a calculation hypothesis, a scope that receives six access requests and four anomaly reports each month, and half a day of handling per case. Ten cases represent five days a month, not counting glossary maintenance. These figures are to be replaced with yours. They show what an appointment “on top of the job” leaves unanswered: the workload exists, and nobody has said what it replaces.
We propose writing into each mandate the scope, the decisions the person can make alone, the expected time frame, the reserved time, the route of appeal and the name of the deputy.
The technical custodian, on the IT side
The technical custodian is the team that operates the systems where the data reside: the team of the source application, that of the platform. It stores, backs up, secures, configures rights, runs checks and keeps logs. It does not set the meaning of a piece of data and does not open access on its own initiative.
An access request shows the sequence. The steward checks the classification of the dataset and the stated purpose. The owner authorises or refuses. The custodian configures the right and keeps a trace of it. For an anomaly, the order is reversed: a check run by the custodian flags it, the steward qualifies it, and the owner only steps in if the correction requires a decision. The anomaly handling process, from qualification to closure, is presented on our data quality page.
The custodian owes the other two roles two things: notice before any schema change or application replacement, and an opinion on the feasibility and cost of a rule before it is decided.
A public text addressed to banks also deals with both sides, business and IT. The Basel Committee’s principles for risk data aggregation require, according to our BCBS 239 entry, defined roles for data ownership, on the business side and on the IT side (paragraph 34 of the document).
Situations where the split becomes blurred
An owner may be one in name only. Appointed with no time frame to meet and no body to sit on, they make no decisions, and the steward decides in their place without having the authority. The record of decisions remains empty, and decisions can be challenged by the first department they inconvenience.
A steward placed in IT poses another difficulty. If they know the processing better than the business rules, the role slides towards that of custodian, and questions of meaning are left without anyone to answer them.
Neighbouring roles add to the confusion. The chief data officer maintains the framework common to all domains and does not decide in place of the owners. In a data mesh, the data product owner, presented in our data product entry, decides on the roadmap of a data product and ensures the satisfaction of its consumers.
The data protection officer holds a function of another origin: a text provides for it. The GDPR, Regulation (EU) 2016/679, read on 12 November 2026 in its consolidated version, deals with the officer’s designation in Article 37. Article 39 gives the officer in particular the tasks of informing and advising the controller and monitoring compliance with the regulation. Article 38(3) requires the controller and the processor to ensure that the officer does not receive any instructions regarding the exercise of those tasks. Paragraph 6 allows the officer to fulfil other tasks and duties, with the controller or processor ensuring that they do not result in a conflict of interests. The expressions “propriétaire des données” and “intendant des données” do not appear in the French version of the regulation. Whether combining the function with one of these roles creates such a conflict is for the organisation and its lawyers to say.
To check the split on a domain, reread its last three decisions and note, for each one, who prepared it, who signed it and who applied it. A slot left without a name points to the mandate to write first.