Data Ownership and Stewardship: Assigning Accountability by Domain

Most data problems in senior housing & care are not technical. They are questions of authority. When census disagrees with billing, the real question is who decides which one governs, and in many organizations the answer is no one in particular. The discrepancy is discussed in a meeting, adjusted in a spreadsheet and found again next month.

Data ownership turns that recurring argument into a decision with a named decision-maker. Stewardship turns the decision into daily practice. Together they are the first step in any operator data governance framework, because every later step — definitions, access, reconciliation, lineage and vendor terms — needs someone with the authority to approve it.

Ownership does not mean the owner does the work or controls the system. The owner holds a decision right: what a figure means, how it is computed and when a change to it is approved. The steward carries the daily responsibility for quality. Keeping those two roles distinct is what makes the model workable for a busy executive team.

1. Step 1

   Inventory your data domains

   List the categories of data that appear in portfolio reporting and decision-making. Most operators start with five: clinical, payroll and workforce, financial, census and occupancy, and CRM. Note which systems hold each domain's records; a single domain often spans several systems.

2. Step 2

   Name one accountable owner per domain

   Choose an executive who already answers for the outcomes the domain measures — the chief clinical officer for clinical data, the CFO for financial data. One name per domain. Where two leaders share an interest, decide who governs the definition and record the other as an approver.

3. Step 3

   Appoint stewards close to the work

   Stewards maintain quality day to day: they answer questions about fields, review exceptions and route corrections. A business office manager may steward census at a community; a payroll manager may steward hours worked. Give stewards set time for the role.

4. Step 4

   Write down the decision rights

   For each domain, record what the owner decides (definitions, tolerances, access approvals) and what the steward handles (corrections, exception review, questions). A one-page charter per domain is enough to start.

5. Step 5

   Publish the assignments and review them

   Make the owner and steward list visible to every analyst and community leader. Review it at least annually and whenever leadership changes, so ownership never lapses silently when someone leaves.

• A committee as owner. A data governance committee is useful for coordination, but it cannot be the owner. Disagreements need one person with the authority to settle them.
• Owners without stewards. Executives rarely have time to review exceptions. Without stewards, ownership exists on paper and the backlog of breaks grows.
• Ownership by system instead of domain. Assigning the EHR to clinical and the billing system to finance leaves shared fields, such as care level, without a clear owner.

Next guide: Access Controls for Operators: Role-Based Access, Least Privilege and Quarterly Reviews

Or return to the full data governance playbook for senior housing & care.