Quality Management System
ISO 9001 Quality Objectives: How to Write Ones That Pass Audit and Help the Business
What clause 6.2 requires, how to make objectives measurable, twelve examples for service and product businesses, how to review them, and a free Excel register.

Written By: Fiona Parker, a BSI-qualified Lead Auditor in ISO 9001. Built and ran a certified ISO 9001 quality management system for six years before moving into auditing, and previously led IT teams in high-performance engineering, including at McLaren
Last Update:
19 October 2026
Quality objectives are the point where an ISO 9001 system stops being a set of documents and starts being a set of commitments with numbers on them. The quality policy says what you care about; the objectives say how much, by when, and who is responsible. Clause 6.2 requires them, requires them to be measurable, and requires you to plan how you will achieve them and check whether you did.
They are also where small businesses most often go wrong, usually by setting objectives that sound good and measure nothing. This guide covers what the clause asks for, how to write objectives that work, twelve examples across service and product businesses, and the register from our toolkit for tracking them. For where clause 6.2 sits in the standard, see the ISO 9001 clauses guide.
Download the free quality objectives register (Excel)
The register has a row per objective with columns for the linked policy commitment, the target, the measure, the owner, start and due dates, a RAG status and a current status note. Three worked examples are in it to show the level of detail. No sign-up needed.
What clause 6.2 requires
Objectives must be established at relevant functions, levels and processes, and they must be:
- Consistent with the quality policy
- Measurable
- Relevant to conformity of products and services and to customer satisfaction
- Monitored
- Communicated
- Updated as appropriate
And for each one, you must plan what will be done, what resources are needed, who is responsible, when it will be completed, and how the results will be evaluated.
The objectives must be kept as documented information. A register is the usual form.
What makes an objective measurable
The test is whether two people looking at the same data would agree on whether it had been met. “Improve customer satisfaction” fails that test. “Raise the average post-project satisfaction score from 4.1 to 4.5 out of 5 by December, measured on the existing survey” passes it.
A usable objective has five parts, and the register has a column for each:
- The objective, in a sentence: what you want to be different.
- The policy commitment it supports, so the auditor can see the trace from clause 5.2.
- The target: a number, a date, or both.
- The measure: where the number comes from and how often it is read.
- The owner: a named role, not “everyone”.
If you cannot fill in the measure column, the objective is not yet an objective.
How many to set
Three to six for a small business. Fewer than three and the auditor will question whether the policy commitments are covered; more than six and they stop being reviewed properly. Each commitment in the quality policy should have at least one objective underneath it, which is usually what sets the number.
Twelve examples
Each of these is written the way it would appear in a register, with a target and a measure. Adapt the numbers.
For any business
- Achieve ISO 9001 certification: pass the stage 2 audit with no major non-conformances by [date]. Measure: audit report.
- Reduce non-conformances: cut recorded non-conformances by 20% year on year. Measure: count in the non-conformance log, reviewed quarterly.
- Close corrective actions on time: 90% of corrective actions closed by their due date, with an effectiveness check recorded. Measure: corrective actions log.
- Complete the internal audit programme: all planned audits completed in the year. Measure: audit programme status at management review.
Service businesses
- On-time delivery: 95% of projects delivered by the agreed date, or re-planned with the client before the date. Measure: project close records.
- Customer satisfaction: average score of 4.5 out of 5 or better on the post-engagement survey, with a 40% response rate. Measure: survey results, quarterly.
- First-time acceptance: 90% of deliverables accepted by the client without rework. Measure: acceptance records.
- Complaint response: every complaint acknowledged within one working day and resolved within ten. Measure: complaints log.
Product and manufacturing businesses
- Right first time: 98% of units passing final inspection without rework. Measure: inspection records, monthly.
- Supplier performance: 95% of deliveries from approved suppliers on time and to specification. Measure: goods-in records, quarterly supplier review.
- Customer returns: return rate below 1% of units shipped. Measure: returns log.
- Calibration: 100% of measuring equipment within its calibration date. Measure: calibration register, monthly check.
Notice that none of these is “be the best” or “improve quality”. They all come from the way the business already measures itself, or could with one more column in a spreadsheet.
Tracking and reviewing them
Set them once a year, review them at every management review, and update the register in between when the data changes. The register in our toolkit uses a RAG status (red, amber, green) against each objective, which makes the management review discussion quick: green objectives get a sentence, amber and red get a decision.
When an objective is met, either retire it and set a harder one, or convert it into a standing KPI that is monitored under clause 9.1 rather than an objective under 6.2. When one is clearly not going to be met, say so in the review and decide whether to change the plan, the target or the date. An objective quietly left red for three reviews is a finding.
Mistakes auditors see most
- Unmeasurable objectives. The commonest finding against clause 6.2 by some distance.
- No link to the policy. Objectives that do not correspond to anything the policy commits to, or policy commitments with no objective.
- No plan. The objective exists but nobody can say what will be done to achieve it, by whom, or with what.
- Never reviewed. Set during implementation, same values at the next audit.
- Only the certification objective. “Achieve ISO 9001” is a legitimate first-year objective; on its own, it says the system has no other purpose.
What changed in ISO 9001:2026
Clause 6.2 itself is essentially unchanged. The related change is in 6.1, where opportunities are now treated separately from risks, so some businesses are adding an objective that captures an opportunity (a new service line, a process improvement, a market) alongside the conformity and satisfaction objectives. That is good practice rather than a requirement. The 2026 emphasis on quality culture also makes it sensible for at least one objective to be about how the business works (for example the audit programme or corrective action closure) rather than only about output. The ISO 9001:2026 changes article covers the rest.
Where to go next
The register is one of the 32 documents in the free ISO 9001 toolkit, alongside the quality policy template the objectives hang off and the management review minutes where they are reviewed. Objectives come from the quality policy, so write that first if you have not. They are reviewed at management review, which has its own guide. If you want help setting objectives that fit your business, our ISO 9001 consultancy programme does it in the planning workshop.
Frequently asked questions
What are quality objectives in ISO 9001?
Measurable targets, set by the organisation under clause 6.2, that put numbers and dates on the commitments in the quality policy. Each must be consistent with the policy, relevant to product and service conformity and customer satisfaction, monitored, communicated and kept as documented information.
How many quality objectives should I have?
Three to six for a small business. Each commitment in the quality policy should have at least one objective supporting it. More than six tend not to get reviewed properly.
What is an example of a quality objective?
“Deliver 95% of projects by the agreed date, or re-plan with the client before the date, measured from project close records and reviewed quarterly; owner: operations manager.” The key elements are a target, a measure, a frequency and an owner.
Do quality objectives have to be SMART?
The standard does not use the term, but its requirements amount to the same thing: measurable, relevant, with a plan, a responsible person, a completion date and a way of evaluating the result. If an objective is SMART it will meet clause 6.2.
How often should quality objectives be reviewed?
At every management review as a minimum, which for most small businesses means quarterly, with the full set reset annually. Progress against objectives is a required input to management review under clause 9.3.