ISO 9001 clause 6.2.1: set quality objectives people can interpret

What clause 6.2.1 requires in practice

Clause 6.2.1 asks the organisation to establish quality objectives at the functions, levels and processes where they are relevant. It then lists the characteristics those objectives need. They should be consistent with the quality policy and measurable, and they should take applicable requirements into account. They should be monitored, communicated and updated as appropriate. They should be available as documented information. Finally, they should bear on the conformity of products and services and on the ability to enhance customer satisfaction.

The words relevant functions, levels and processes matter. The clause does not ask for one organisation-wide set of targets cascaded mechanically; it expects objectives where they can steer actual work. Measurable does not mean that every objective must be a percentage, only that there is a clear basis for judging achievement. The output is a set of objectives that people at each level can read, measure and act on.

Identify a meaningful quality result

Use policy commitments, customer requirements and process evidence to identify relevant priorities. A recurring acceptance problem, unreliable handover or weak response to customer feedback may suggest an objective. Consider applicable requirements so the target does not encourage performance that looks efficient while missing an essential obligation.

An objective should be specific enough for people to understand what achievement means. “Be the best” provides little direction. “Reduce avoidable returns caused by incorrect order configuration” identifies a result that can be defined and investigated. The exact target and method should follow the business's circumstances, not a universal ISO benchmark.

Make measurement reliable enough for the decision

Define the population, measurement method and interpretation. A rate may be useful, but its numerator and denominator must mean what users think they mean. Changes in product mix, customer volumes or classification can affect comparisons. Explain important limits instead of presenting a precise figure as automatically reliable.

Measurability requires a credible way to judge the intended result. Avoid objectives whose apparent achievement depends on subjective interpretation that changes from one reviewer to another. Where judgement is involved, agreed criteria and appropriate evidence can help make the evaluation consistent.

Why well-set objectives matter to the business

An objective that cannot be interpreted produces argument at the end of the year instead of improvement during it. A clear one lets a supervisor see this week whether work is moving the right way, and lets leaders compare functions without confusion. Objectives that count activity, such as sessions held, can rise while customer problems stay put, and incentives attached to them can pull departments in opposing directions. Setting objectives that reflect the customer's experience protects the relationship, focuses spending, and gives auditors evidence that management directs the system with intent.

How to implement clause 6.2.1

Aim for few objectives that people understand, and test each wording on the people who must use it. One way Sterling's teams do this is a short objective-setting session per function, where the draft wording is tested by asking a front-line supervisor how they would measure it on an ordinary week. The clause requires objectives with the stated characteristics; a scorecard, dashboard or register is one convenient place to hold them, but none is mandatory, and the number of objectives is for the organisation to choose.

1. Identify the processes and functions where a result needs deliberate steering.
2. Link each candidate to the quality policy and to relevant customer or legal requirements.
3. Phrase the objective as a result and avoid describing activity.
4. Fix the measure: what is counted, which work is included and how the result is read.
5. Check that objectives across functions do not work against each other.
6. Communicate each objective to the people affected and keep it available as documented information.
7. Set the monitoring rhythm and the trigger for revising an objective.

Evidence an auditor expects for clause 6.2.1

The auditor will test whether objectives are real in the working areas, not just on a management page. Typical evidence includes: Interviews carry weight here. Auditors often ask a team member what the objective for their area is and what they do that affects it, then compare the answer with the documented wording. Records of monitoring help most when they show a discussion and a decision, not only a figure.

• objectives stated for the functions and processes sampled
• records of monitoring results and the discussion they prompted
• observations that staff in the area understand the objectives affecting them
• traceability from objective to policy and to customer or process results
• records of updates when conditions or requirements changed

Common nonconformities with clause 6.2.1

Findings often arise where objectives are decorative. Auditors tend to raise these findings by sampling a process and asking its owner for the objective, the latest result and the action taken when results disappointed. Where the answers are vague, the underlying weakness is usually that the objective was set centrally and never owned locally.

• Objectives cannot be measured, or the basis of measurement is unclear.
• Objectives exist at company level but none reach the processes that influence them.
• Results are recorded but never monitored during the period.
• Staff cannot say what the objectives are or how their work affects them.
• Objectives do not relate to conformity or customer satisfaction, or no longer match the policy.

Illustrative manufacturing example: right first time

Illustrative BPO example: complete case resolution

A hypothetical BPO team sets an objective for cases resolved within the agreed service arrangement. Managers initially count cases as resolved when an agent sends any response. Customer feedback shows that many responses request information already provided or leave the original issue unanswered.

The organisation reviews the objective's meaning with the process owner and defines resolution against the accepted service requirement. It monitors an appropriate sample for completeness and communicates the changed interpretation to supervisors and agents. The example shows why a clear definition matters; it does not establish one mandatory resolution metric for all BPO services.

Communicate the objective without creating a harmful incentive

People should understand the objective and the contribution expected from their work. Explain relevant boundaries, including the requirement to preserve conformity and accurate reporting. A target should not be interpreted as permission to suppress complaints, reclassify defects or bypass checks.

Objectives at different levels should support the overall result. If purchasing is rewarded only for lower unit prices while operations is expected to reduce provider-related failures, management should examine the conflict. The standard does not demand identical measures across teams, but the quality system should not contain incentives that undermine its own intended outcomes.

Retain the documented basis and review changes

The objectives must be available as documented information. The format can be an approved plan, business system or other suitable arrangement. Keep enough clarity about the objective that staff and reviewers know which result applies and how it is monitored.

Update objectives as appropriate when needs or circumstances change. Do not erase an unmet target by retrospectively changing the definition without explanation. Review the reason for change, communicate the new basis and preserve the information needed for a clear account of earlier performance. Typical weaknesses include abandoned objectives, unclear ownership of measurement and reports that nobody uses.