Document Control
All controlled documents in the QMS must follow this process to ensure version integrity and traceability.
Document Lifecycle
Draft ──► Review ──► Approved ──► Published
│
Rejected ──► Revision
Frontmatter Requirements
Every controlled document must include the following frontmatter block:
---
title: Document Title
author: Full Name
created: "YYYY-MM-DD"
version: vX.Y
status: draft | review | approved
department: Department Name
---
Version Numbering
| Change Type | Action |
|---|---|
| Major rewrite or structural change | Increment major (v1.0 → v2.0) |
| Content update or correction | Increment minor (v1.0 → v1.1) |
| Typo or formatting only | No version change required |
Approval Process
- Author creates document with
status: draft - Author opens a GitHub Pull Request targeting
main - Designated reviewer reviews and comments
- Author addresses feedback and updates
status: review - Reviewer approves the PR → author sets
status: approved - Merged to
main= published
Archiving
Superseded documents are tagged with a superseded-by field and moved to the /archive/ directory. They are not deleted — version history is maintained in git.