Every procedure controlled, and every operator on the current version.
For quality and operations teams who own the quality manual, the procedures and the work instructions. Each one approved, sent to the lines and teams that use it, and on record by person and by version.
Nonconforming Product ProcedureVersion 4.2Owned by Quality & Operations
Drafted
Quality team
Charles Peirce, Quality manager
Clearer hold and release steps, a new disposition form
30 Sep 2026
Step 1 · Operations
David Hume
Operations director
Approved2 Oct 2026
Step 2 · Leadership
Simone de Beauvoir
Chief executive
Approved5 Oct 2026
Sent to everyone
Lines 1 to 3 and Quality, 96 people
95 of 96
acknowledged version 4.2
The documents you own
A quality system is many documents, each controlled, each reaching the people who use it.
Quality policy
Set by top management and understood by everyone, from the line to the office.
Quality manual and procedures
The documented system, each procedure approved and on its own review cycle.
Work instructions
Line-side instructions approved like procedures, so no shift runs on last month’s sheet.
Nonconforming product and corrective action
How product is held, reviewed and released, for everyone who touches it.
Calibration and equipment
The procedure versioned, with calibration certificates kept beside it.
Supplier requirements
Your supplier quality manual, sent to suppliers and acknowledged by them.
Who asks to see them
Wherever you operate, registrars, customers and regulators ask the same question: is this the approved version, and is it the one in use.
ISO 9001, clauses 7.5, 5.2.2
Documented information
Documents approved before use, changes controlled, the current version available where it is used, and the quality policy communicated and understood.
Each document approved, versioned and reviewed
Only the current version reaches the floor
Each person’s acknowledgment, by version
ISO 13485, clause 4.2.4; 21 CFR 820
Medical device document control
Since 2 February 2026, FDA’s quality system rule brings in ISO 13485: documents reviewed and approved before issue, changes approved, obsolete versions kept out of use.
Approval before issue, on record
Every earlier version kept in history
The current version at the point of use
IATF 16949, clause 4.3.2
Customer-specific requirements
Each customer’s requirements are evaluated and built into the system, and the people they affect are told when they change.
Customer requirements held as approved documents
Sent to the lines that build for that customer
Each change approved, then sent again
Wherever you make and ship
Customer and local requirements
Customers, sectors and countries add their own rules to the standard. Each gets its own document beside the core system.
A document for each customer or market
Sent only to the teams it applies to
Each change goes out again
Bring your own rules
Your region’s laws, the standards your customers ask for, and your own house rules. Write each one as a policy, approve it, and send it to the people it covers.