Data artefact templates and rubrics

How to use this

Practical, not perfection

Pick the tier you are studying and copy the template into your notes.
Complete it for one real example (work, a side project, or a safe fictional scenario).
Use the rubric to tighten it until it is defensible.
Paste a short reflection into your CPD record: what you assumed, what evidence you would keep, and what you would do next.

Foundations. Data contract and glossary

Template + rubric + example

Template

Title: Data contract (minimum viable)

Dataset name:
Owner:
Consumers:

Key fields (name, meaning, allowed values)
- 

Definitions (glossary)
- 

Quality expectations
- Freshness:
- Completeness:
- Validity:

Evidence to keep
-

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.

Applied. Quality and trust plan

Template + rubric + example

Template

Title: Data quality plan

1) Risks
- 

2) Checks (what, threshold, action)
- 

3) Monitoring signals
- 

4) Incident handling
- Who owns triage?
- What is the rollback?

5) Evidence to keep
-

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.

Advanced. Governance and operating model note

Template + rubric + example

Template

Title: Governance note

Decision rights
- Who approves schema changes?
- Who can grant access?

Controls
- 

Evidence
- 

Review triggers
-

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.