Quality objectives under ISO 9001 clause 6.2: what the standard requires — and what it doesn't

Status. This article was published on 18 September 2026, two days after ISO 9001:2026 was released [1]. Statements about the new edition were checked against a copy of ISO/DIS 9001:2025(en) [2] — the Draft International Standard stage, not the published IS edition and not the German DIN translation (neither was obtainable at the time of checking). Substantive changes between DIS and FDIS are possible. Where the draft status matters, it is stated explicitly. Statements about the 2015 edition were checked against DIN EN ISO 9001:2015-11 [3].

The quality objectives sit on a slide that has not changed in four years. Complaint rate below two percent, on-time delivery above ninety-five, audit findings in single digits. Underneath, a date from January.

In the audit, the question is not about the objectives but about how they developed over the year and who acted on them when. And that is where most organizations go quiet — not because the objectives are missing, but because clause 6.2 makes two demands, and almost everyone knows only the first.

What clause 6.2 actually requires

Clause 6.2 falls into two parts, and the difference between them is the whole point.

6.2.1 concerns the objectives themselves. The organization has to establish quality objectives at the relevant processes, functions and levels. Those objectives must be consistent with the quality policy, be measurable, take applicable requirements into account, be monitored, communicated and updated as appropriate, be available as documented information, and be relevant to the conformity of products and services and to enhancing customer satisfaction [2, clause 6.2.1].

6.2.2 concerns planning how to achieve them. Here the standard asks for five determinations: what will be done, what resources will be required, who will be responsible, when it will be completed, and how the results will be evaluated [2, clause 6.2.2].

Those five are the part that goes missing in practice. A target list answers the first (what) and sometimes the third (who). The resource question, the completion date, and above all the evaluation method rarely appear anywhere — and the evaluation method is the most interesting of them, because it settles before the period starts what achievement will be measured against. Deciding it on evaluation day means deciding it in full knowledge of the result.

This is not an academic distinction. It is why an objectives discussion in an audit rarely turns on how ambitious a target is, and almost always on how the organization arrived at its statement about achieving it.

What the 2026 edition changes

On the draft reviewed, clause 6.2 changes little in substance and a fair amount in structure.

	ISO 9001:2015 [3]	ISO/DIS 9001:2025 [2]
Scope of the objectives	“at relevant functions, levels and processes needed for the QMS”	“at relevant processes, functions and levels” — processes first, the QMS qualifier gone
List in 6.2.1	seven items a) to g), plus a trailing sentence on documentation	eight items a) to h)
Documented information	own sentence: maintain	bullet g): be available as documented information
Relevance to conformity and customer satisfaction	item d), mid-list	item h), at the end
6.2.2 (planning)	five items a) to e)	unchanged, five items a) to e)
Annex A	no dedicated clause on 6.2	A.6.2, an explanatory clause

Three observations.

Reordering to “processes, functions and levels” is more than cosmetic. It puts the process at the head of the list, and the draft simultaneously drops the qualifier limiting this to what is needed for the quality management system. Phrased as a gap-analysis question: do your objectives hang off departments or off processes? For a target list organised along the org chart, that is a real question.

“Maintain” becomes “available”. ISO distinguishes documented information that is maintained (documents that are kept current) from information that is retained (records as evidence). The draft shifts the wording for quality objectives to being available, and at the same time promotes it to a bullet of equal standing next to measurable and monitored. Whether auditors will read a different expectation into that remains to be seen; the direction points away from the document as an end in itself and towards whether the objectives can be found where someone needs them.

6.2.2 stays as it was. That is the most striking line in the table. The part of clause 6.2 that is most often incomplete in audits is neither relaxed nor reworded by the revision. A gap there today is unchanged in 2027. The revision’s other changes — separating risks from opportunities, quality culture, climate change in clause 4 — are covered in the overview of what changes in the 2026 edition.

SMART is not in the standard

The acronym does not appear in the requirements text — neither in 2015 nor in the draft of the 2026 edition. It comes from management literature and has embedded itself in QM training so thoroughly that it is routinely repeated as a requirement of the standard.

The comparison is worth making, because it shows where SMART holds and where it departs from the standard:

SMART	Counterpart in clause 6.2
Specific	no direct counterpart; the closest is the requirement to be relevant to conformity and customer satisfaction
Measurable	6.2.1: objectives must be measurable — but not necessarily quantified, see below
Achievable	no counterpart. The standard nowhere requires an objective to be achievable
Realistic	no counterpart, as above
Time-bound	6.2.2 d): when it will be completed

Two of the five letters, then, have no basis in the requirements text. That is not an argument against realistic objectives — it is an argument against raising or accepting a finding on the grounds that an objective is “not SMART enough”. What is auditable is what 6.2.1 and 6.2.2 say.

Conversely, clause 6.2 contains three requirements that SMART does not mention and that go missing more often than the five letters do: derivation from the quality policy, communication to those involved, and determination of the evaluation method.

Measurable does not mean quantified — and that is now in the annex

The most common follow-up question is what an objective should look like when it cannot sensibly be reduced to a number. Introducing a process. Qualifying a supplier. Migrating to a new edition of a standard.

The ISO 9001 Auditing Practices Group addressed this back in 2016: quality objectives must be measurable and verifiable, but not necessarily quantified; qualitative results can be relevant too, and a yes/no statement on achievement is acceptable provided it is supported by evidence [4]. Those papers always carried the caveat, though, that they have not been through an approval process at ISO or IAF — interpretation, not requirement.

The draft of the 2026 edition takes the same statement into Annex A: objectives have to be measurable as far as appropriate and necessary to monitor their achievement, which does not mean they always have to be expressed in quantitative form [2, Annex A.6.2]. That is the most consequential change to clause 6.2 in practice, and it sits beside the requirements text rather than in it.

Annex A is substantially expanded in the draft and provides, for the first time, an authoritative text on the intent of the requirements. For clause 6.2 that means the “our objective cannot be quantified” discussion no longer has to be argued from a guidance document that explicitly is not a requirement, but can rest on a text that ships with the standard. How much weight that carries in a certification audit depends on whether the annex survives the remaining ballot stages unchanged.

The annex also places clause 6.2 in two contexts absent from the requirements text: quality objectives can be defined at strategic, tactical and operational levels, and they can be linked to the objectives of other management systems, which helps decision-making across system boundaries [2, Annex A.6.2]. For organizations running an integrated management system, that is the warrant for handling quality, environmental and occupational-safety objectives in one procedure rather than three.

“Relevant processes, functions and levels” — the cascade question

The phrase is regularly read as an obligation to cascade objectives completely: from company objective through departmental objective down to process objective, without gaps.

The text does not support that. It requires objectives where it is relevant — and who determines relevance is the organization. The requirement is therefore not one of completeness but of justification: you have to be able to explain why this process has an objective and that one does not.

For improvement objectives the APG states explicitly that there is no requirement to set objectives for all processes at once [5]. Carried over to clause 6.2, that yields the most useful rule of thumb available: an objective belongs where someone makes a decision contingent on it. An objective that changes nobody’s behaviour creates recording effort and audit surface, but no control.

What the annex does support is attribution: a departmental objective can be marked as contributing to a higher-level one without that becoming a calculation. The marking answers what an objective belongs to. Automatic aggregation across levels is not required by the standard, and it is usually wrong on the merits anyway — the average of a complaint rate and an on-time delivery figure is not a quantity anyone can decide on.

The part nobody prepares: the evaluation

Clause 6.2.1 requires objectives to be monitored. Clause 6.2.2 e) requires determining how the results will be evaluated. And clause 9.3.2 c) 4) requires the management review to consider information on the extent to which quality objectives have been met [3, clause 9.3.2]. Three requirements converging on the same record.

In practice that raises the question of what happens between target-setting in January and the review in autumn — and here the standard has an expectation that an annually maintained spreadsheet does not meet. “Monitored” is a continuous activity. How often is for the organization to determine; that there is a stretch between measurements in which nobody could have reacted is the consequence that has to be explained in the audit.

The most defensible form of evidence is also the simplest: a dated series of actual values, each with its period, its status, and, where it stands out, a note explaining it. What such a record answers, a status line in a spreadsheet cannot — namely when a deviation first became visible and what happened next.

Quality objective, KPI, action item

Three terms that end up in the same table and are three different things.

A KPI measures. It has a definition, a data source, and a value. Nothing more.

A quality objective under clause 6.2 additionally fixes which value is aimed for, what in the quality policy it rests on, who is responsible, what resources it needs, when it is to be reached, and how it will be evaluated at the end. A KPI is therefore a component of a quality objective, not a synonym for one.

An action item is what someone does to make the value move. It has an owner, a due date, and a status, and it is complete when it has been carried out — regardless of whether the objective was met. That is the distinction most often blurred: “run the training” is not a target, it is an action. Kept as an objective, it is achieved the moment the training happens, even if nothing about quality changed.

Keeping the three apart earns you an answer that is otherwise hard to produce: which of our actions actually fed into an objective? The article on the CAPA process covers the mechanics of the action side.

What a tool has to do for this

The requirements yield a short list, and it is deliberately short, because clause 6.2 does not demand elaborate machinery:

1. The target metric belongs on the objective, not in the head of whoever records the value: target value, baseline, direction, frequency and, where useful, warning and action limits. From those, an actual value’s status can be derived instead of judged.
2. The actual values need a dated history, not an overwritten field. Evidence of monitoring is the series, not the latest state.
3. The 6.2.2 information needs somewhere to live. Resources, ownership, completion date and evaluation method belong on the objective, or they do not exist.
4. Evaluation has to be its own step, with a comment that explains the deviation. An automatically computed achievement status is a proposal; the statement is made by a person.
5. The definition itself has to stay traceable. Lowering a target value or extending a period after the fact is a legitimate adjustment under 6.2.1 — as long as it is visible.

None of this requires software. A spreadsheet can do all of it, if it is kept with discipline. There is only one thing it cannot do: stop last month’s value being overwritten, because the cell is the same one. That is precisely where the gap opens that surfaces in the audit — not through negligence, but through the shape of the tool. How qportal handles this flow is on the quality objectives page.

Conclusion

Clause 6.2 is one of the shortest clauses in the standard and one of the most frequently half-implemented. The reasons are not sophisticated:

• The most widely repeated requirements — SMART, quantification, a gapless cascade — are not in the text.
• The actual requirement has two parts, and the second (6.2.2, planning the achievement) is routinely overlooked.
• The evidence that counts in an audit is the development across the period, not the target value in January and a number in autumn.

The 2026 edition changes little about that — with one exception that saves work rather than creating it: that objectives need not be quantified will in future be stated in the annex of the standard, rather than only in a guidance paper with no approval status.

Sources

1. ISO: ISO 9001:2026, Quality management systems — Requirements. Sixth edition, published 16 September 2026. https://www.iso.org/standard/89433.html (accessed 18 September 2026)
2. ISO/DIS 9001:2025(en): Quality management systems — Requirements. ISO/TC 176/SC 2, committee ballot 27 August – 19 November 2025. Not publicly available; checked against a copy on 18 September 2026 — not the published IS edition, see the status note above. Clauses 6.2.1, 6.2.2 and Annex A.6.2 were consulted.
3. DIN EN ISO 9001:2015-11: Qualitätsmanagementsysteme — Anforderungen (ISO 9001:2015); German and English version EN ISO 9001:2015. Beuth Verlag, Berlin. Clauses 6.2.1, 6.2.2, 9.3.2 were consulted.
4. ISO 9001 Auditing Practices Group: Guidance on: Policy, Objectives and Management Review. Edition 1, 13 January 2016, issued by ISO/TC 176 together with the International Accreditation Forum. https://committee.iso.org/home/tc176/iso-9001-auditing-practices-group.html (accessed 18 September 2026)
5. ISO 9001 Auditing Practices Group: Guidance on: Improvement. Edition 1, 13 January 2016. Consulted for the statement that there is no requirement to set improvement objectives for all processes at once. (accessed 18 September 2026)

The APG papers carry the explicit note that they have not been through an approval process at ISO, ISO/TC 176 or IAF; they are technical interpretation, not a requirement of the standard.

Normative text is protected by copyright; requirements are rendered here in the author’s own words with clause references. Where this text goes beyond the documented sources, that is marked as an assessment.