The quality objectives

In plain words

Quality objectives are where your policy turns into measurable undertakings. The standard demands: objectives for the relevant functions, levels and processes; consistent with the quality policy; measurable (or at least clearly assessable); relevant to the conformity of your products and to customer satisfaction; monitored, communicated, updated as needed — and documented. Here the paper is mandatory.

The second, often overread part: every objective comes with the planning of its achievement — what will be done, with which means, who is responsible, by when, and how you will evaluate whether it worked. An objective without this plan is a wish.

For a small company this does not mean a KPI landscape — it means the opposite: two to four real objectives a year, each with a number, a name and a date.

Why this requirement exists

The policy alone remains intent — the objectives make it checkable. They are the engine of the improvement loop: context (4.1) and risks (6.1) become direction (5.2), direction becomes numbers (6.2), numbers become actions, and the management review (9.3) closes the loop with the question: achieved or not — and why?

The word measurable is the core of the clause. It separates steering from hoping: “improve quality” cannot be missed and therefore cannot be achieved either. Only the number makes honest evaluation possible — and honest evaluation is what auditors want to see, especially on missed objectives.

What good looks like

In a company of 12 people: two to four annual objectives, each on one line — target value, owner, the key actions, date, measure. Derived from the policy and the risk and opportunity overview (6.1), held in a short released document, glanced at quarterly (the Monday huddle is enough) and honestly evaluated at year-end in the management review.

Good also means: the team knows the objectives. Not all four by heart — but whoever stands in production knows that the scrap rate is the year’s objective and where it currently stands.

What changes as you grow: From around 50 people objectives cascade to areas — every process owner carries one — and get their own review rhythms. From 100–250 people an objective system with process indicators and target agreements emerges. The danger grows too: the bigger the system, the more the difference matters between the few real objectives and the measuring apparatus around them.

The minimum to pass

• A documented, released objectives document — the objectives themselves are mandatory documented information.
• The objectives are measurable or clearly assessable and recognisably derived from the policy.
• Per objective: actions, owner, date and evaluation criterion — the planning is half the clause.
• The status is tracked — evidenced at least in the management review, better during the year.

What an auditor asks for

• The objectives document itself — and the derivation: which policy sentence, which risk stands behind which objective?
• Interim status: where were the objectives looked at during the year, and what was done on deviation?
• The honest year-end evaluation — one cleanly analysed missed objective convinces more than four smoothly achieved ones.
• In conversation: does the team know “its” objective and the current standing?
• The consequence: what became of the evaluated objective in the new year — continued, tightened, replaced?

Common traps

• The KPI zoo. Fifteen figures on a dashboard are not objectives — they are instrumentation. An objective has a target value, a name and a date; everything else is observation.
• Unmeasurable wishes. “Increase customer satisfaction”, “strengthen quality” — not assessable, therefore not steerable. The auditor’s follow-up is always the same: how would you have noticed it was achieved?
• Objectives without a plan. The target stands, but nobody wrote down who does what by when. The planning of achievement is an explicit part of the clause — its most forgotten one.
• Copy-paste from last year. The same objective, never achieved, never changed — three years running. That documents not persistence but missing evaluation.
• Objectives past the team. If nobody but the managing director knows the objectives, they can steer nothing. Communication is part of the requirement.
• Financial objectives only. Revenue and margin are business objectives — quality objectives pay into product conformity and customer satisfaction. Overlap is allowed; confusion is not.
• The standing objective “zero defects”. Right as an attitude, unassessable as an annual target — and demotivating after the first defect. Better: the concrete next step (from 3% to 2%).

Worked example

Berger Präzisionsteile GmbH runs three annual objectives, as a table in the released objectives document:

At the quarterly glance, objective 1 stands at 16% — management adds a second action (direct approach instead of fair only). At year-end it is missed at 17%, and exactly that is what the management review says: analysis (the fair brought contacts, but slower than planned), consequence (objective stays, action mix renewed). Objective 2 ends at 1.8% — achieved. The auditor spent most time on the missed objective — and named its treatment a strength in the report. Honestly missed beats prettily achieved.

← All ISO 9001 topics · To the knowledge hub