What the template covers
Short on purpose. The How to use tab explains what a quality manual is and is not, why many organizations keep it deliberately short, how exclusions should be recorded, and the failure modes: the standard restated clause by clause, procedure content pasted in, processes with no owner. The Quality Manual tab is the skeleton, seven sections. The Worked Example tab completes it as a compact manual for a generic mid-size machining company, demonstrating the intended altitude in practice: a map, not a procedures dump.
- Document header — organization, document ID, version, owner, approver, supersedes
- QMS scope statement with an exclusions-and-justification row — which exclusions are permitted is your standard's call, not the template's
- Process-interaction table — process, owner, inputs, outputs, and the related procedure, one row per process
- Quality policy, objectives, and organization rows that point to controlled documents instead of copying them
- Document hierarchy — manual to procedures to work instructions to records — and a revision history that explains why
A map, not a copy of the standard
The manual sits at the top of a document pyramid: the manual describes the system, procedures say who does what and in what order, work instructions carry the task-level detail, and records prove the system ran. A manual that respects that hierarchy stays short, because every question below 'what does the system cover and how do its processes interact' is answered one tier down.
The two disciplines the template enforces follow from that. Point, don't duplicate: every paragraph of procedure content copied into the manual is a second copy that must be revised in step — and eventually isn't. And every process gets an owner: the process table asks for one per row, because a process nobody owns is where systems quietly stop working.
Where this fits in your documentation
Quality system standards treat the manual as part of documentation control — ISO 13485:2016 clause 4.2 (documentation requirements) covers the documentation a quality management system must include, the quality manual among it, and how those documents are controlled. Clause 4.2.2 is the manual-specific subclause: a quality manual states the scope of the QMS with any exclusion justified, includes or references the QMS procedures, describes how the QMS processes interact, and outlines the structure of the documentation — the four things this template's sections cover. Whether your own applicable standard requires a stand-alone quality manual, and what it must contain, depends on that standard — check it rather than assuming.
The same applies to exclusions: which requirements may be claimed as not applicable, and on what grounds, is determined by your organization against its applicable standard. The template gives the exclusion a row and a justification cell — it deliberately does not enumerate what may go in it. Like every controlled document, the manual itself carries an ID, a version, an approver, and a revision history, managed under your own document control procedure — adapt this structure to it and have QA approve the adapted version. Auditors use the manual as a map: one process, its owner, the procedure the row points at. An exclusion without a written justification is the conversation you do not want.
