- Purpose
- Put numbers on quality. Define how it gets measured, reported, and fixed when it slips.
- Intended user
- Data program owners, vendor managers, and quality leads.
- Version
- 2026.07
- Reviewed
- 2026-07-12
- Owner
- AuraOne Open maintainers
- Next review
- 2027-01-12
- Source commit
- f14253719a9c3bfe2b282b816bab24929529fb3e
- Update policy
- Reviewed at least every 180 days. A material change to the product, the workflow, or a legal or procurement boundary also triggers a review.
Planning and legal boundary: Planning aid only. Nothing here is professional advice. It does not replace review by your own legal, security, and procurement teams. Qualified reviewers must adapt and approve any production use.
Metric definitions
Define the unit, the population, and the sampling method behind every measure.
Service review
Set how often you review, what the review packet contains, and who approves it.
Remediation and escalation
Write the path from a missed threshold to a fix. Then write the path to termination.
Related resources
Continue with the related planning documents rather than treating one template as a complete procurement or approval process.