ISO 9001 clause 6.2: turn quality objectives into managed work
ISO 9001:2026 clause 6.2 requires quality objectives at relevant functions, levels and processes, together with planning to achieve them. Objectives need to be measurable, consistent with the quality policy and relevant to conformity and customer satisfaction. A target without a credible delivery plan is only part of the requirement.
What clause 6.2 requires in practice
Clause 6.2 turns quality direction into measurable commitments and a plan for delivering them. The organisation sets quality objectives for the functions, levels and processes where they matter, and then plans how each will be achieved.
Subclause 6.2.1 sets the qualities of a good objective. It is consistent with the quality policy, measurable, mindful of applicable requirements, monitored, communicated and updated as appropriate. It is held as documented information, and it relates to conformity of products and services and to customer satisfaction. Subclause 6.2.2 covers the plan. For each objective the organisation works out what will be done, which resources are needed, who is responsible, when it will be finished and how results will be evaluated.
The outputs are a set of objectives that people can interpret and an actionable plan behind each one. The clause does not prescribe how many objectives there must be, what targets they carry or what format the plans take.
Choose a result that matters
Start with a relevant customer or process need. An objective might concern reducing a particular recurring error, improving dependable delivery or strengthening a weak handover. The measure should reflect the result intended, rather than count activity that can increase without improving quality.
For example, the number of training sessions delivered is an activity measure. If the concern is inaccurate order entry, the organisation also needs a way to assess whether the relevant errors change. Training may contribute, but it should not be assumed to be the only cause or the only useful action.
Define the measure and its context
A measurable objective needs a clear basis for judging achievement. Explain what is measured, which work is included and how the result will be interpreted. A percentage without a stable denominator or an unexplained change in case mix can make performance look better while the underlying problem remains.
The standard does not impose one set of universal QMS targets. Choose objectives appropriate to the organisation's policy, applicable requirements and operating priorities. Relevant functions and processes may have different objectives, but their incentives should not undermine one another or the customer's overall experience.
Why quality objectives matter to the business
Objectives are how an organisation tells its people what good looks like this year. Without them, effort drifts toward whatever is loudest, and results are explained after the fact. Well-chosen objectives focus teams on customer outcomes such as dependable delivery or fewer repeated errors, make performance discussions factual, and let leaders see early whether a plan is working. The plan behind each objective matters just as much: a target with no owner, resource or date is a wish, and staff learn to ignore it. Auditors and customers read objectives as a sign of how seriously management steers the system.
How to implement clause 6.2
Work from the policy downwards, and keep the number of objectives small enough to follow. One way Sterling's teams do this is to review objectives during the planning round with each function head and record the plan alongside the objective, so that measure, owner and resources are seen together. The standard requires objectives and plans, not a specific scorecard layout or software, so use whatever format your managers will genuinely refer to during the year.
- Start from the quality policy, applicable requirements and the priorities set in planning.
- Select the functions and processes where a result needs steering.
- Write each objective around a customer or process result and decide how it will be measured.
- Define what is counted, which work is included and how the number will be read.
- Build the plan: actions, resources, an accountable person, a completion point and the method of evaluation.
- Tell the people whose work affects the objective, and keep the wording available as documented information.
- Monitor progress, update objectives when conditions change and discuss them in management review.
Illustrative IT example: repeat support contacts
A hypothetical IT service desk wants to reduce avoidable repeat contacts about the same unresolved issue. The team defines the relevant contact types and reviews a baseline sample to understand the causes. It avoids using total ticket closures as the objective because rapid closure can itself create repeat contact.
The delivery plan addresses incomplete diagnosis and unclear customer updates, assigns responsibility for the workflow changes and provides time for coaching. Evaluation checks repeat contacts alongside accuracy and customer feedback. If repeat contacts fall only because staff merge records differently, the organisation has changed the measurement rather than demonstrated the intended improvement.
Illustrative construction example: complete handover information
A hypothetical contractor finds that customer handovers are delayed by missing inspection and product information. It sets a relevant objective concerning complete information at the agreed handover stage. The team defines what counts as complete for the project rather than assuming every handover has identical requirements.
Its plan identifies who obtains provider information, when review occurs and how outstanding items are escalated. Resources include access to the project records and time for coordination. Management evaluates whether handover packages meet the agreed criteria and whether later customer queries reveal omissions. Counting the number of files uploaded would not establish completeness.
Monitor, communicate and update
Objectives must be monitored and communicated, with updates as appropriate. Relevant people should know the intended result and their contribution to it. A centrally managed dashboard may support this, but teams need enough explanation to avoid treating the number as an instruction to manipulate classification or skip necessary work.
When circumstances change, review whether the objective, measure or plan remains suitable. Updating an objective is different from silently changing it after a poor result. Keep the decision understandable and maintain a clear account of performance against the basis that applied.
Evidence and common failure modes
Quality objectives must be available as documented information. Planning evidence may exist in operating plans, project actions or management arrangements; no particular objective template is mandated. The organisation should be able to explain how each relevant objective will be pursued and how results will be evaluated.
Common problems include targets with no owner, owners with no resources and measures that reward the wrong behaviour. Another is reporting a result without analysing why it changed. Use performance evaluation and management review to examine whether the objective and the action plan remain useful, not simply whether a cell is green.
Explore each numbered part
6.2.1 · set quality objectives people can interpret
A useful quality objective states a relevant result and makes achievement assessable. This guide focuses on clause 6.2.1, including policy alignment, applicable requirements, monitoring, communication and updates. Manufacturing and BPO examples show how to define the measure accurately, avoid misleading percentages and preserve the documented basis when priorities or operating conditions change.
6.2.2 · plan how the quality objective will be achieved
A quality target needs a credible route to achievement. This guide explains the planning decisions in clause 6.2.2, including actions, resources, responsibility, timing and evaluation. Software and construction examples show how to address a known performance gap, manage dependencies and distinguish an activity completed from the quality result the activity was intended to produce.
Frequently asked questions
Must every department have a separate quality objective?
Objectives are required at relevant functions, levels and processes. Relevance to the QMS and its intended results matters more than allocating one identical target to every department.
Can an objective be maintained rather than continually increased?
A suitable objective can concern sustaining a necessary level of performance. The organisation still needs continual improvement of the QMS and should review whether its objectives remain appropriate.
Is a KPI automatically an objective?
No. A KPI measures something; an objective states a result to achieve. A relevant indicator can help monitor an objective when its meaning and desired outcome are clear.
Make targets easier to act on
Sterling can help connect quality objectives with delivery plans across functions and sites. Scoped support can include implementation, employee learning and Effivity ISO & GRC automation software for agreed information arrangements. Certification remains an independent decision.
Enrol in KPIs, Objectives & Management Review to strengthen measurement and review skills. Return to clause 6 planning for risks, opportunities and changes.