Data artefact templates and rubrics

Template

Rubric (what "good enough" looks like)

• Scope and boundaries are clear (what is in/out).
• Field meanings are unambiguous and owned.
• Quality expectations include thresholds.
• Evidence is identified (what you would log/measure/keep).

Worked example (short)

Example (short):
Owner: Payments data team.
Freshness: < 2 hours.
Completeness: 99.5% for required fields.

Template

Rubric (what "good enough" looks like)

• Next actions are concrete and realistic.
• Each check has an action and an owner.
• Incident plan includes rollback or containment.
• Evidence is identified (what you would log/measure/keep).

Worked example (short)

Example (short):
Check: null rate for customer_id < 0.1%, action: block downstream refresh and page owner.

Template

Rubric (what "good enough" looks like)

• Trade-offs are stated, not implied.
• Decision rights are explicit (no 'everyone owns it').
• Evidence is identified (what you would log/measure/keep).
• Next actions are concrete and realistic.

Worked example (short)

Example (short):
Schema changes require owner approval + automated contract tests.