ISO 9001
ISO 9001 quality management systems
Connect customer requirements to how work is done, measured and corrected.
Who it applies to
Organizations developing a quality management system or seeking certification for a defined scope.
What you’ll produce
A process-based quality management system, operating evidence and an external certification decision where pursued.
Track the edition on the certificate and the one being adopted. Use the actual requirements and agreed transition scheme when changing your QMS.
Run the project
Go to the roadmapDecisions for leadership
- What do we need the certification to cover?
- Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
ISO 9001 kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Define scope, processes and quality objectives · Quality lead + operations [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- What would a customer see if one of your key processes failed?
- Which edition governs your current certificate or customer contract?
Worked scenario
A parts manufacturer traces repeat delivery complaints to a change in its inspection handoff. It updates ownership, tests the new procedure and uses the next set of delivery records to see whether the change worked.
What to read next
- ISO 13485
Check specialized QMS requirements for medical-device work.
- 01Define scope, processes and quality objectivesQuality lead + operations · ~21 days
- 02Make quality controls part of operational workProcess owners + procurement · ~35 days
- 03Look for causes and test corrective actionsQuality assurance + customer operations · ~28 days
- 04Audit implementation and track transitionInternal auditor + certification lead · ~28 days
Step by step
Checklist, instructions and 12 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Define scope, processes and quality objectives | Quality lead + operations | Before updating procedures | Set a start date | Scope statement; Process narratives; Performance measures | Open |
| Make quality controls part of operational work | Process owners + procurement | Before routine operation | Set a start date | Control matrix; Evidence index; Supplier terms | Open |
| Look for causes and test corrective actions | Quality assurance + customer operations | At findings and across planned reviews | Set a start date | CAPA log; Test reports; Management review minutes | Open |
| Audit implementation and track transition | Internal auditor + certification lead | Before external audit and at version changes | Set a start date | Internal audit report; Phased legal register; Audit calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Define scope, processes and quality objectives
Map the product or service, its process owners, dependencies and customer requirements, and agree measures that show whether outcomes improve.
What to produce
Scope statementMemo
Gather first
- Service inventory and architecture
- Customer commitments and contracts
- Applicable criteria or legal text
How to prepare it
- Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
- List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
- Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Decision
- Cover the hosted billing service for the April to June review.
- In scope
- Production billing API, hosting, releases and production access.
- Excluded and why
- Internal HR tool. It has no access to billing systems or data.
- Dependencies
- Cloud hosting and corporate identity provider.
- Approval
- Service owner approves after checking the architecture and contract.
Check before handing it over
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Process narrativesMemo
Gather first
- Approved system boundary
- Architecture, data flows, controls and service commitments
- Current reporting instructions or system plan template
How to prepare it
- Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
- Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
- Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Service and objective
- Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
- Boundary and inputs
- Accepted production order events, account identifiers and billing records
- How it works
- Payment result updates invoice status. Release pipeline deploys code with approval.
- Shared roles
- Customer controls user configuration. Hosting vendor manages physical infrastructure.
- Evidence and review
- Architecture v3, deployment records and service-owner review
Check before handing it over
The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.
Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.
Performance measuresSpreadsheet
Gather first
- Baseline evidence
- Approved target or success definition
- Dates, denominator and responsible service
How to prepare it
- Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
- Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
- Check the numbers against source data and explain material exceptions or changes in scope before sharing.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Outcome
- Administrators receive quarterly access review.
- Current and evidence
- 11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
- Target
- All eligible roles reviewed
- Gap and action
- One role missed. Reconcile new roles before next review.
- Owner and review
- IAM lead, next quarter
Check before handing it over
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
- 02
Make quality controls part of operational work
Document acceptance, supplier requirements and change controls. Capture actual inspections, approvals and exceptions.
What to produce
Control matrixSpreadsheet
Gather first
- Applicable criteria, requirements or risk decisions
- Current procedures and configurations
- Names of people operating or reviewing each control
How to prepare it
- Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
- Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
- Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Requirement
- Production access is reviewed periodically.
- Control ID
- AC-04
- Control activity
- IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
- Owner and frequency
- IAM lead, quarterly
- Evidence
- Export with filters, annotated review and removal tickets
- Test and status
- Reconcile export to current roles. Inspect approvals. Operating.
Check before handing it over
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Evidence indexSpreadsheet
Gather first
- Control descriptions and test request
- Source system records
- Defined period and evidence access rules
How to prepare it
- Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
- Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
- Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Evidence ID
- EV-021
- Control or request
- AC-04, October administrator review
- Period and scope
- 1 to 31 Oct 2026 UTC, production tenant
- Source and capture
- IAM export filtered to active elevated roles
- Link or record ID
- Restricted workpaper EV-021 plus ticket IAM-114
- Reviewer and status
- Security assurance, verified
Check before handing it over
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Supplier termsMemo
Gather first
- Current agreement and service description
- Applicable flow-down terms or engagement requirements
- Contract owner and legal review
How to prepare it
- Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
- Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
- Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Party and service
- Northstar hosting provider, production backup
- Clause or requirement
- Incident notification and contacts
- Current position
- General notice terms. No operational escalation contacts listed.
- Change to review
- Add named response channel and request confirmation of the timing.
- Owner, status and record
- Vendor lead, legal review pending, contract register V-018
Check before handing it over
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
- 03
Look for causes and test corrective actions
Compare results to objectives. Identify root causes, assign fixes and confirm effectiveness after implementation.
What to produce
CAPA logSpreadsheet
Gather first
- Finding, risk or test exception
- Root-cause analysis
- Named owner, due date and expected evidence
How to prepare it
- Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
- Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
- Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Finding or risk
- F-008, a departed contractor retained production access
- Cause and effect
- HR event never reached IAM. Admin access remained active.
- Action and owner
- Revoke access and alert on failed HR sync. IAM lead.
- Due and status
- 2026-11-28, in progress
- Closure test
- Simulate departure and verify access disappears within policy
- Approver and evidence
- Risk owner, ticket IAM-114 and retest results
Check before handing it over
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Test reportsMemo
Gather first
- Approved test scope and criteria
- Population and sample records
- Test approach, results and reviewer requirements
How to prepare it
- State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
- For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
- Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Test objective
- Check that production role removals happen within the internal deadline.
- Method and population
- All September departures. Test each privileged account.
- Expected result
- Remove access within one business day.
- Observed result
- 11 on time. One late by two days, ticket IAM-114.
- Finding and follow-up
- F-008. Retest the next departure and verify alerting.
Check before handing it over
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Management review minutesMemo
Gather first
- Agenda or decision request
- Current performance measures and findings
- Proposed actions and participants
How to prepare it
- Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
- Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
- Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Item
- Approve a fix for the missing access-removal retry.
- Inputs reviewed
- September test results and IAM incident root-cause notes.
- Decision
- Approve automatic retry plus daily reconciliation.
- Action and due date
- Platform lead to ship and test by 2026-11-28.
- Residual risk and follow-up
- Manual review remains until rollout. Check at December meeting.
Check before handing it over
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
- 04
Audit implementation and track transition
Sample operating evidence, resolve nonconformities and agree the applicable edition and audit plan with the certification body.
What to produce
Internal audit reportMemo
Gather first
- Approved test scope and criteria
- Population and sample records
- Test approach, results and reviewer requirements
How to prepare it
- State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
- For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
- Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Test objective
- Check that production role removals happen within the internal deadline.
- Method and population
- All September departures. Test each privileged account.
- Expected result
- Remove access within one business day.
- Observed result
- 11 on time. One late by two days, ticket IAM-114.
- Finding and follow-up
- F-008. Retest the next departure and verify alerting.
Check before handing it over
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Phased legal registerSpreadsheet
Gather first
- Current obligations, expiry dates or audit window
- Delivery dependencies and owner availability
- Official rules or engagement confirmation
How to prepare it
- Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
- Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
- Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Milestone
- Quarterly access review approved
- Date and kind
- 2026-12-18, internal target
- Trigger or source
- Internal access control schedule v3
- Prerequisite
- Access export by 2026-12-09
- Owner and reminder
- IAM lead, remind one week before
- Status
- Scheduled
Check before handing it over
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.
Audit calendarSpreadsheet
Gather first
- Current obligations, expiry dates or audit window
- Delivery dependencies and owner availability
- Official rules or engagement confirmation
How to prepare it
- Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
- Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
- Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Milestone
- Quarterly access review approved
- Date and kind
- 2026-12-18, internal target
- Trigger or source
- Internal access control schedule v3
- Prerequisite
- Access export by 2026-12-09
- Owner and reminder
- IAM lead, remind one week before
- Status
- Scheduled
Check before handing it over
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.
Official sources
- ISO · Current ISO 9001 standard (opens in a new tab)
- ISO · 2026 revision and transition information (opens in a new tab)