If your quality policy lives in a PDF nobody has opened since the last audit, you’re not alone. It’s one of the most-written, least-used documents in a QMS — and it’s exactly what an auditor catches with two questions: “can you explain the policy without reading it?” and “how does it connect to what you measure every month?” If the answers are “no” and “not sure,” the problem isn’t the wording. It’s that the policy and the objectives never connected to real work.
This guide covers the two things ISO 9001 actually requires (policy and objectives), shows real examples of both done well and done badly, and — what almost nobody does — how to keep them alive after the audit instead of filing them away.
Table of Contents
What the standard actually requires
ISO 9001 asks for two related but distinct things:
- A quality policy (clause 5.2): top management’s general commitment to quality and continual improvement. It’s the “why” — the frame decisions get made inside.
- Quality objectives (clause 6.2): specific, measurable targets aligned with that policy, reviewed periodically and communicated to whoever has to deliver them.
The most common mix-up: treating the policy as if it were the objective. “Our policy is to deliver quality products” isn’t an objective — it’s an intention. The objective is the metric that proves the intention is actually happening.
Quality policy examples: what makes one actually work
Most quality policies are interchangeable between companies — swap in a competitor’s name and no one would notice. To make yours say something real:
- Start from your actual context, not a template. What do you promise a customer that sets you apart? What quality problem has cost you the most in the past?
- It should be explainable in one sentence, without reading it. If a plant manager can’t paraphrase it in 10 seconds, it was written for the auditor, not the team.
- Link it explicitly to the objectives. A policy without objectives grounding it is a statement of intent. With objectives, it’s a verifiable commitment.
- Sign it and actually communicate it — not just post it on a wall. Include it in new-hire onboarding and revisit it when business priorities shift.
Weak quality policy example: “We are committed to delivering quality products and services, meeting customer requirements, and continually improving our management system.”
Quality policy example with real context: “At [company], quality means the customer never has to double-check what we deliver. We commit to meeting agreed specifications, reducing nonconformity returns year over year, and giving every employee the training and tools to make that happen.”
The second one isn’t longer for decoration — it’s longer because it says something specific you can actually trace into the objectives that follow.
Quality objectives: get this right and everything else follows
A quality objective that actually works meets the SMART standard, adapted for a QMS:
- Specific: not “improve quality,” but “reduce the rejection rate at final inspection.”
- Measurable: tied to an indicator you already track or can realistically start capturing.
- Achievable: an impossible 6-month target just demotivates everyone by month 3.
- Relevant: connected to the policy and a real business pain point.
- Time-bound: quarterly or annual, with a review date on the calendar — not “ongoing.”
Example table (policy commitment → objective → indicator → target):
| Policy commitment | Quality objective | Indicator | Target |
|---|---|---|---|
| Reduce nonconformity returns | Lower the customer return rate | % returns / orders delivered | From 4% to 2% in 12 months |
| Meet agreed specifications | Reduce final-inspection rejects | % pieces rejected | Under 1.5% monthly |
| Equip the team | Onboard 100% of new hires on the QMS | % new hires onboarded within 30 days | 100% every quarter |
If your objectives don’t look like this table — if they’re sentences with no number, no indicator, and no date — they’re not quality objectives in the sense the standard means yet. They’re good intentions.
How to keep them alive after the audit
This is the step almost nobody does, and it’s the difference between “we comply to comply” and a QMS that actually works:
- Review them in management review, not only when the external audit is approaching. See our ISO 9001 management review guide.
- Feed them from the same indicators you already use to run the business, not a parallel report built just for the auditor. See our guide on quality KPIs for ISO 9001.
- Communicate progress, not just the target. An objective nobody sees moving is indistinguishable from one that doesn’t exist.
Common mistakes when writing quality policy and objectives
- Copying a generic policy template off the internet without adapting it to the business.
- Confusing policy (intent) with objective (measurable target).
- Setting objectives with no indicator or clear owner following up.
- Reviewing them only once a year, right before the audit.
- Never telling the operating team they exist — they live only in the QMS documentation.
How QW360 supports quality policy and objectives
Writing the policy and objectives is an afternoon’s work. Keeping them alive — tied to real indicators, reviewed at every management meeting, visible to whoever has to deliver them — is what usually gets lost between the objectives spreadsheet and the policy PDF. QualityWeb 360 keeps them in one place, tied to the same indicators you already manage, so the next audit doesn’t start from zero.
Frequently asked questions
Is the quality policy the same as the company mission?
Not necessarily. The mission is the business’s general purpose; the quality policy is the specific commitment to quality and continual improvement within the QMS. They can align, but the policy still has to meet clause 5.2’s requirements.
How many quality objectives should I have?
The standard doesn’t set a number. It’s better to have 3-5 objectives that are actually tracked than 15 that nobody reviews.
How often should quality objectives be reviewed?
At minimum, at every management review (typically annual). Many companies review them quarterly alongside their operating indicators — it’s the practice that delivers the best results.
Who should write the quality policy?
Top management is responsible for establishing it (clause 5.2), though in practice it’s usually drafted together with the quality manager and then validated and signed by leadership.
Should quality objectives stay the same every year?
No. They should evolve with the business — if you’ve sustainably hit a target, raise it or shift focus to another real pain point. An “achieved” objective that repeats unchanged year after year stops adding value.
