Checklist

Operational Data Quality & Ownership Checklist

An interactive checklist teams can use to assign ownership, verify sources, set rules, record evidence, and log data incidents so operational decisions rely on trustworthy data.

Interactive Tool

Operational Data Quality & Ownership Checklist

Use this interactive checklist to assign ownership, verify sources, define data rules, and record incidents so operational dashboards and decisions remain reliable. Save a completed checklist to create a persistent record your team can review, act on, and audit.

Data Incident Ticket Template

Incident ID: [auto]

Summary: [brief description of the issue]

Detected: [YYYY-MM-DD]

Impacted datasets: [list]

Owner: [name]

Remediation plan: [steps and deadlines]

Date this checklist was completed (YYYY-MM-DD).
The team, plant, or site this checklist covers.
Person responsible for executing or coordinating remediations (name and contact).
Role or title (e.g., Operations Manager, Data Steward).
Have you documented each operational data source (system, table, feed) and its owner?
List major sources or note missing sources. Include system names and owners.
Are timestamps consistently recorded and aligned across sources (timezones, formats, latency)?
Describe any alignment issues, their scope, and suggested fixes.
Are rules defined for how to treat missing values (impute, ignore, exclude, substitute)?
Briefly describe the rules and where they are documented.
Is there a documented process for detecting anomalies and escalating them?
List example anomalies, thresholds, or detection rules (e.g., sudden spikes, stale feeds).
Are dataset versions and basic lineage tracked so you can reproduce reported metrics?
Has access to operational data been reviewed (who can edit, who can view)?
Note required changes, outstanding requests, or owners of access lists.
How often will the dataset's quality be reviewed?
Most recent review (YYYY-MM-DD), if applicable.
Planned next review (YYYY-MM-DD).
Your assessment of current operational data quality for the covered datasets.
Links to dashboards, logs, data catalog entries, incident tickets, or screenshots.
Anything else the team should know.
Select Yes to record an incident using the ticket fields below.
Optional: local or system incident identifier (leave blank to auto-generate).
Describe the incident in one or two sentences.
Date the incident was first observed (YYYY-MM-DD).
List datasets, tables, streams, reports, or dashboards affected.
Person responsible for coordinating remediation.
Target date for resolution (YYYY-MM-DD).
Current state of remediation work.
Steps, owners, and checkpoints to resolve the incident.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.