Building Your Quality Management System — Documentation and Processes

Building Your Quality Management System — Documentation and Processes

The gap assessment told you where you are. Now comes the real work: building a quality management system that actually functions—not just documentation gathering dust on a shelf, but a living, breathing system that reflects how your organisation actually operates.

This is where many Canadian manufacturers and service organisations get lost. They think ISO 9001 means creating 50 detailed procedures. It doesn't. It means creating the right documentation, at the right level of detail, that enables people to do their jobs consistently and measure results.

In this chapter, we walk you through designing your QMS, documenting key processes, creating useful procedures and work instructions, and integrating everything into a system that your people actually use.

The QMS Documentation Hierarchy

Before you start writing procedures, understand the documentation structure. ISO 9001 doesn't prescribe a specific structure, but a practical hierarchy looks like this:

Level 1: Quality Policy and QMS Overview

Your quality policy - The organisation's public commitment to quality. One page, non-technical, referenced by all employees.

QMS Manual (optional) - An overview document describing your QMS, scope, key processes, and how they interact. Some organisations create this; many don't (it's not required by ISO 9001). If you create one, keep it concise (5-10 pages).

Level 2: Procedures

Procedures describe how major processes work. They're typically 2-4 pages, written for someone who understands your business but might not know the specific process. They cover:

• Purpose and scope
• Roles and responsibilities
• Key steps and controls
• Records created
• Related documents

Examples: Procurement Procedure, Non-Conformance Procedure, Internal Audit Procedure, Management Review Procedure, Corrective Action Procedure, Design Review Procedure (if applicable).

Level 3: Work Instructions

Work instructions are detailed, step-by-step guides for specific tasks. They're typically 1-2 pages, written for an operator or technician who may be new to the task. They include:

• Step-by-step instructions
• Photos or diagrams
• Safety notes
• Quality checkpoints
• Common errors to avoid

Examples: CNC Setup Instruction, Final Inspection Instruction, Shipping Procedure, Material Receiving Checklist.

Level 4: Forms and Records

Forms (job cards, inspection forms, non-conformance logs) and records (completed forms that prove work happened).

Think of it this way:

• Policy: Why we care about quality (one sentence)
• Procedures: How we do major things (the process flow)
• Work Instructions: Detailed how-to guides for specific tasks
• Forms/Records: Evidence that we did it

Designing Your QMS: Process Mapping

Before you write procedures, map your key processes. You need to understand the sequence and interaction.

The Context → Process Mapping Flow

Start by reviewing the context you identified in the gap assessment:

External Context:

• Customer requirements (quality, delivery, technical specs)
• Regulatory requirements (environmental, safety, food safety, etc.)
• Market demands (price, speed, innovation)
• Competitive landscape (who are your competitors? what are they doing?)

  Internal Context:

• Available resources (people, equipment, facilities, budget)
• Current capabilities (what can we actually do?)
• Organisational culture (how do we work together?)
• Business strategy (where are we going?)

Key Processes to Map

Most organisations need to map these core processes:

1. Customer Order to Delivery Process

• Sales/Order entry
• Design or specification review (if applicable)
• Planning
• Procurement (if applicable)
• Production/Service delivery
• Quality inspection/verification
• Packaging/Handoff
• Customer support (if applicable)

  2. Supplier/Procurement Process

• Supplier identification and evaluation
• Purchase order creation
• Incoming inspection
• Supplier performance monitoring

  3. Product/Service Design Process (if applicable)

• Design input (understanding requirements)
• Design development (creating the design)
• Design review (checking the design)
• Design verification/validation (proving the design works)
• Design changes (managing modifications)

  4. Quality Control Process

• In-process inspection
• Final inspection
• Testing
• Non-conformance handling
• Measurement system management

  5. QMS Governance Process

• Document control
• Record management
• Internal audit
• Management review
• Corrective action
• Continuous improvement

Creating a Process Map

Use a simple format:

Process Name: Name

Process Owner: Person responsible

Inputs: What comes into this process?

Steps: 1. → 2. → 3. → (etc.)

Key Controls: Where do we check quality? Where could things go wrong?

Outputs: What comes out? Who receives it?

Records: What evidence do we keep?

Metrics: How do we know this process is working? (on-time delivery %, defect rate, cycle time, etc.)

Example: Customer Order to Production Process

For a small operation, you might have 5-7 core processes. For a larger, more complex organisation, you might have 15+. Map only what's material to your scope.

Writing Procedures That People Actually Use

This is critical: procedures need to be useful, not just compliant.

The Procedure Template

Title: Keep it simple. "Procurement Procedure" not "Comprehensive Supplier and Procurement Management System and Controls Procedure."

Purpose: One sentence. What does this process achieve? Example: "To ensure that purchased products and services meet our requirements and are delivered on time."

Scope: What's included? What's not? Example: "Applies to all purchase orders for materials and services related to production. Excludes office supplies and professional services like consulting."

Definitions: Define terms specific to this process if needed. Often not necessary.

Responsibilities:

• Procurement Manager: Evaluates suppliers, issues POs, tracks delivery
• Receiving: Inspects incoming material, signs off on receipt
• Quality: Performs supplier audits annually
• Finance: Processes invoices

Process Steps: Number them. Be clear but not overly detailed. Procedure level = 5-10 steps. Work instruction level = 20+ steps.

1. Supplier Identification: When a new supplier is needed, identify candidates using criteria document
2. Supplier Evaluation: Evaluate candidates on quality, delivery, cost. Document evaluation using Supplier Evaluation Form
3. Supplier Approval: Approved suppliers are added to Approved Supplier List
4. Purchase Order Issuance: For each order, issue a PO that includes our quality requirements and delivery expectations
5. Incoming Inspection: Upon delivery, receiving inspects the shipment per Receiving Inspection Instruction
6. Non-Conformance Handling: If inspection finds problems, initiate Non-Conformance Report
7. Supplier Performance Monitoring: Track on-time delivery and quality. Review quarterly. If performance drops, escalate to supplier management
8. Supplier Audits: Conduct annual on-site audits of critical suppliers

Records: List what gets documented and kept. Example:

• Supplier Evaluation Forms
• Approved Supplier List (updated as needed)
• Purchase Orders
• Receiving Inspection Reports
• Non-Conformance Reports (for supplier issues)
• Supplier Audit Reports
• Supplier Performance Records

  Related Documents:

• Supplier Evaluation Criteria document
• Receiving Inspection Instruction
• Non-Conformance Procedure
• Supplier Audit Procedure

Approval: Document who approved this procedure and when. Review annually and update as needed.

Procedure Writing Tips

1. Reflect Reality

Write down what you actually do, not what you wish you did. If you're planning to change a process (e.g., implementing new equipment), do that first, then write the procedure.

2. Make It Understandable

Use clear language. Avoid jargon. Use short sentences. One idea per sentence. If you need diagrams, include them.

3. Focus on Control Points

Don't describe every micro-step. Focus on the steps where something could go wrong or where you verify quality. A procedure is about control, not documentation for documentation's sake.

4. Be Specific About Authority

Who approves? Who can override? Example: "Procurement Manager can approve POs up to $5,000. Larger POs require Operations Manager approval."

5. Link to Forms

Reference the forms you've created. Make it easy for someone to know what form to use.

6. Include Troubleshooting

In the procedure, note common issues and how to handle them. Example: "If a supplier doesn't meet delivery date, notify Procurement Manager immediately. Procurement Manager will expedite or arrange alternative delivery."

7. Version Control

Every procedure should have a version number and date. When you update it, increment the version number. Keep old versions in an archive (you might need to refer to them later if something happened under an old version).

Sample Procedures for ISO 9001

Most Canadian organisations need to document these key procedures:

Quality Management System:

• Document Control Procedure
• Record Control Procedure
• Quality Policy
• Non-Conformance Handling Procedure
• Corrective Action Procedure
• Internal Audit Procedure
• Management Review Procedure

  Operations:

• Customer Order Process Procedure (or Sales/Order Management)
• Procurement Procedure
• Supplier Management Procedure
• Production/Service Delivery Procedure
• Quality Control and Inspection Procedure
• Equipment Maintenance Procedure
• Measurement and Calibration Procedure

  Design (if applicable):

• Design and Development Procedure
• Design Review Procedure
• Design Change Control Procedure

  HR and Competence:

• Competence, Training, and Awareness Procedure

Creating Work Instructions

Procedures describe what happens and who's responsible. Work instructions describe how to do the task.

The Work Instruction Template

Title: "CNC Setup Work Instruction" (specific and clear)

Process it belongs to: Links to a procedure

For: Who is this for? (new operators, anyone, experienced operators)

Prerequisites: What needs to happen before you start? (material received and inspected, drawings available, previous job cleared)

Step-by-Step Instructions:

1. Detailed step
2. Detailed step

(often 15-30 steps for a complex task)

Quality Checkpoints: At what steps do you verify quality? What should you look for?

Safety Notes: Any hazards? Any safety equipment required?

Common Errors: What mistakes do people make? How do you avoid them?

Records: What do you document? (job card, inspection form)

Images/Diagrams: Photos of correct setup, diagram of how to position material, etc.

Work Instruction Writing Tips

1. Be Granular

A work instruction is detailed. If your procedure says "Set up the machine," the work instruction walks someone through every step: unlatch the cover, position the chuck, insert the collet, tighten the nut, etc.

2. Use Visuals

A picture of the correctly set-up machine is worth 1,000 words.

3. Include Photos of Common Errors

Show what wrong looks like, too.

4. Test It

Have someone new to the task follow your work instruction without asking questions. Do they get it? If not, revise.

5. Keep It Current

When equipment changes or procedures change, update the work instruction immediately.

6. Make It Accessible

Print it and post it at the work station. Or link to it in your digital system. Make sure people can access it easily.

Documentation Systems: How to Manage All This Stuff

You've now created 10-20 procedures, 20-40 work instructions, and various forms. How do you manage them?

Small Organisation (under 50 people): Digital Folder System

You can use a simple shared drive approach:

Quality Management System/ ├── Policies/ │ └── Quality Policy.docx ├── Procedures/ │ ├── Document Control Procedure.docx │ ├── Non-Conformance Procedure.docx │ ├── Procurement Procedure.docx │ └── [etc.] ├── Work Instructions/ │ ├── CNC Setup Instruction.docx │ ├── Final Inspection Instruction.docx │ └── [etc.] ├── Forms/ │ ├── Non-Conformance Report Form.docx │ ├── Inspection Report Form.docx │ └── [etc.] ├── Records/ │ ├── 2024 Non-Conformances/ │ ├── 2024 Inspection Reports/ │ └── [etc.] └── Approved Supplier List.xlsx

Rules:

• Only current versions live in the folder
• Old versions go to an "Archive" folder with the date
• Every document has a version number and approval signature
• Access permissions are set (who can edit?)
• A "Document Register" spreadsheet lists all documents, versions, and approval dates

Medium Organisation (50-200 people): Document Management Software

Consider simple tools like:

• Google Workspace (if you're using Google)
• SharePoint (if you're using Microsoft)
• Confluence (if you want a wiki-style system)
• ISO management software (Ideagen, MetricStream, MasterControl) - these are pricier but purpose-built

Benefits: Better version control, audit trails, automatic notifications when documents are updated, easier to manage access.

Integrating Existing Processes

You probably have existing ways of working. Your job isn't to reinvent everything; it's to formalise and improve what already works.

Example: A 40-person machine shop in Saskatchewan

Current state:

• Orders come in via email or phone
• The owner/operator knows what's feasible; people trust their judgment
• Work is mostly done by experienced people who know the processes informally
• Quality is good, but mostly because the experienced people are good
• No formal procedures; new hires are trained on-the-job

  What you're building:

• Formalise the order-to-delivery process (so any competent person can run it, not just the owner)
• Document inspection criteria (so quality is consistent across all operators, not dependent on one person's judgment)
• Create onboarding procedures (so new hires are trained consistently)
• Keep the informal, collaborative culture (just add discipline)

You're not reimagining the shop. You're documenting and standardising what already works.

The Integration Process

1. Interview key people - Ask them: "Walk me through how we do X process." Write down what they say.
2. Observe the process - Watch it happen. Note steps, controls, decision points, where communication happens.
3. Document the current process - Write what you observed.
4. Review with the team - Does the documentation reflect reality? Adjust.
5. Identify improvement opportunities - Are there steps that don't add value? Are there control points missing? Could it be faster?
6. Incorporate improvements - Update the procedure with improvements.
7. Pilot the procedure - Run it for a month with the original team, using the documented procedure. Refine.
8. Train on the procedure - Once refined, train all relevant staff.
9. Audit compliance - Spot-check that people are following the procedure. Coach as needed.

The Quality Control Procedure: A Deep Dive

Quality control is often the most important procedure in a manufacturing QMS. Let's walk through a typical QMS Quality Control Procedure as an example.

Sample Quality Control Procedure (Manufacturing)

Purpose: To ensure all products meet customer requirements and regulatory standards before shipment.

Scope: Applies to all products manufactured in our facility for external customers.

Responsibilities:

• Quality Inspector: Performs inspections per acceptance criteria, documents results
• Production Supervisor: Ensures inspections happen before release
• Operations Manager: Reviews quality metrics, addresses trends

Process Steps:

1. Establish Acceptance Criteria: Before production begins, quality and engineering review customer drawings/specifications and establish acceptance criteria (dimensions, tolerances, surface finish, material properties, etc.). Document in Acceptance Criteria Form.
2. In-Process Inspection: During production, quality inspector performs checks at defined checkpoints (per Production Control Plan). For example:

• After setup, verify first piece meets spec (First Piece Inspection)
• During production, spot-check every nth piece
• If any deviation found, stop production and notify supervisor

1. Final Inspection: Before a batch is released, quality inspector performs 100% inspection (or sampling per Inspection Plan). Checks:

• Dimensions (use calibrated measuring equipment)
• Visual (surface finish, color, markings)
• Functional (if applicable, test the product)
• Traceability (part numbers, serial numbers, batch codes)

1. Documenting Results: Inspector records results on Quality Inspection Report. Reports include:

• Batch/job number
• Quantity inspected
• Defects found (if any)
• Pass/fail decision
• Inspector name and date

1. Non-Conformance: If inspection finds non-conforming product:

• Segregate the product (don't let it ship)
• Initiate Non-Conformance Report
• Notify Production Supervisor and Quality Manager
• Determine disposition (scrap, rework, concession)
• Follow Non-Conformance Procedure for root-cause analysis

1. Release for Shipment: Only product that passes final inspection is released. Release approval includes:

• Inspector signature
• Quality Manager signature (for batches with any non-conformances)
• Date
• Recorded in Quality Records

1. Performance Monitoring: Monthly, quality manager reviews:

• Inspection reports for trends
• Defect types and frequency
• Non-conformance reports
• Presents findings to leadership in Monthly Quality Review

  Records:

• Acceptance Criteria Forms
• Quality Inspection Reports
• Non-Conformance Reports
• Monthly Quality Review minutes

  Forms Referenced:

• Quality Inspection Report Form
• Non-Conformance Report Form
• Acceptance Criteria Form

Making Your Procedures Work in Daily Practice

Documentation alone doesn't create compliance. People have to actually follow the procedures. Here's how to make that happen:

1. Build Procedures Collaboratively

Include the people who do the work. They'll spot unrealistic aspects and be more likely to follow what they helped create.

2. Train Thoroughly

Don't just hand out procedures. Walk people through them. Show why each step matters. Practice together.

3. Make Procedures Accessible

Post them where people work. Make digital versions easy to find. Don't bury them in filing cabinets.

4. Start with Discipline

In the first month of using a procedure, spot-check compliance. Coach people who aren't following it. Build the habit.

5. Refine Based on Feedback

After people use a procedure for a month, ask: "Is this working? Are there confusing parts? What would make this easier?" Update the procedure.

6. Reinforce With Audits

Regular internal audits check that procedures are being followed. Use audits as learning opportunities, not punishment.

7. Connect Procedures to Business Results

Help people see: "When we follow the quality inspection procedure, we catch defects before they reach customers. That means fewer complaints, happier customers, and job security."

The Integration of Your QMS: Making It a System

You now have procedures, work instructions, and forms. How do they fit together?

Example Flow: Customer Order to Delivery

1. Customer order arrives (email, PO)
2. Feasibility Review Procedure is triggered: Can we make this by the deadline? Do we have materials? Do we understand the spec?
3. If feasible: Production Planning Procedure creates production schedule
4. Procurement Procedure triggers: Order materials per plan
5. Materials arrive: Receiving Procedure triggers inspection
6. Production begins: Production Control Procedure (and related work instructions) guide the work
7. Quality Control Procedure triggers in-process and final inspection
8. If non-conformance found: Non-Conformance Procedure is triggered
9. Product passes inspection: Release for Shipment happens
10. Monthly: Quality Performance Review includes metrics from this job

Every procedure links to others. Forms flow from procedure to procedure. Records build up evidence of the system working.

This interconnected system is what auditors look for. They don't just check if procedures exist; they check if they're actually working together.

Your Documentation Checklist

By the end of this phase, you should have:

Foundational Documentation:

• Quality Policy (documented, communicated)
• QMS Scope (clear definition of what's in, what's out)
• Process Map (showing how key processes interact)

  Core Procedures (10-15, depending on complexity):

• Document Control Procedure
• Record Control Procedure
• Quality Objectives and Planning
• Competence and Training Procedure
• Customer Order/Service Delivery Process
• Procurement/Supplier Management Procedure
• Production/Service Delivery Procedure
• Quality Control and Inspection Procedure
• Non-Conformance and Corrective Action Procedure
• Internal Audit Procedure
• Management Review Procedure
• (Design and Development Procedure - if applicable)

  Work Instructions (20-40, depending on complexity):

• Specific task instructions for each key process step
• Examples: CNC Setup, Final Inspection, Receiving, Packing, etc.

  Forms and Records System:

• All required forms designed and available
• Record retention schedule established
• Record storage system in place (digital, paper, or both)

  Document Management:

• Approved document repository
• Version control system
• Document register
• Archive system for old versions

Timeline for Documentation Phase

For a small-to-medium organisation:

Month 1: Planning and Process Mapping

• Define scope
• Map key processes
• Identify required procedures and work instructions

  Month 2: Procedure Writing

• Draft core procedures
• Interview key people to capture current practice
• Write procedures

  Month 3: Work Instruction Development

• Draft work instructions for key tasks
• Include diagrams and photos
• Pilot with experienced staff

  Month 4: Integration and Testing

• Review all documentation for consistency and completeness
• Pilot use of procedures in one area
• Refine based on feedback

  Month 5: Finalisation and Approval

• Get formal approval from leadership
• Make final updates
• Establish document control system

  Month 6: Rollout and Training

• Train staff on new procedures
• Post work instructions
• Begin enforcing compliance

This assumes you're working with a quality manager or consultant. If you're doing it entirely in-house with limited resources, add 2-3 months.

A Final Word: Procedure Discipline

Documentation can feel tedious. But it's the foundation of a functioning QMS. Procedures do several critical things:

1. Ensure consistency - Everyone does it the same way, reducing variation
2. Enable training - New hires can learn from written procedures, not just from experienced people
3. Provide traceability - When something goes wrong, you can show what should have happened
4. Enable improvement - You can identify bottlenecks and improve documented processes
5. Create accountability - It's clear who's responsible for what

The organisations we work with that succeed at ISO 9001 are those that see procedures not as bureaucracy, but as the backbone of reliable operations.

Need help building your QMS documentation?

PinnacleQMS helps Canadian organisations design, document, and implement quality management systems. We ensure your QMS reflects your actual operations and drives real improvement. Reach out to discuss your documentation needs.

Next: Chapter 5: Training, Competence, and Awareness Programs.