Responsible systems

Give a dataset an accountable owner

Editorial edition · 16 November 2026

The idea

A dataset can be technically available while nobody knows who can explain its meaning or approve a change. Ownership creates a route for questions and decisions. It should describe a responsibility that survives staff changes, not only a person's name in a spreadsheet.

Design choice

Distinguish the person responsible for business meaning from the team operating the storage. Define how questions are routed and how ownership changes are recorded. A backup contact is useful when an urgent issue appears outside normal availability.

Worked example

The platform team can restore a table, but the data owner decides whether a changed status code still means the same business event.

Before you ship

  • Assign meaning and operational responsibilities
  • Define a handover process
  • Test the contact route

Examples are illustrative. Adapt the checks to your own environment.

Further reading

W3C provenance overview

Search the library