What are quality objectives in ISO 9001?

Quality objectives are measurable targets an organization sets to turn its quality policy into action, required by ISO 9001:2015 clause 6.2. They must be established at relevant functions, levels, and processes, and must be measurable, monitored, communicated, updated, and consistent with the quality policy, with a plan for how each will be achieved and evaluated.

What is an example of a SMART quality objective?

"Cut Line 3 scrap from 4.2% to 2.5% by December 31 to support the quality policy on waste reduction, owned by the Line 3 supervisor and reviewed monthly." It is specific (Line 3 scrap), measurable (percentage), achievable (a stretch from the 4.2% baseline), relevant (ties to the policy), and time-bound (December 31).

What does ISO 9001 clause 6.2 require?

Clause 6.2 requires quality objectives at relevant functions, levels, and processes that are measurable, monitored, communicated, updated, consistent with the quality policy, and relevant to product conformity and customer satisfaction. It also requires a plan for each: what will be done, what resources are needed, who is responsible, when it will be done, and how results will be evaluated.

How many quality objectives should a company have?

Enough to cover the promises in the quality policy but few enough to manage, typically five to ten for a single-site manufacturer. Too few and a key function is left uncovered; too many and the review meeting becomes status-reading with no real attention on any single target. Objectives are the metrics you are actively driving, not your whole dashboard.

What is the difference between a quality policy and a quality objective?

The quality policy is the short statement of intent and commitment (delight customers, improve continually). Quality objectives are the measurable targets that make that intent real at each function, with numbers, owners, and deadlines. The policy says where you are going; the objectives say how far, by when, and who is responsible.

Do quality objectives have to be documented?

Yes. ISO 9001:2015 clause 6.2 requires the organization to maintain documented information on its quality objectives. In practice that means they live in the QMS with their baseline, target, owner, plan, and review record, not in a single manager's memory, so they can be monitored and shown at audit.

How often should quality objectives be reviewed?

Line-level objectives are best reviewed monthly, alongside production and safety, so a red number gets acted on quickly. Higher-level objectives are reviewed at least at each management review, typically quarterly. The key is a fixed cadence set before launch, not a once-a-year scramble the week before the audit.

How to Write Quality Objectives (SMART Examples)

Quality objectives are measurable targets that turn the quality policy into action at each relevant function and level. ISO 9001 clause 6.2 requires them to be measurable, monitored, communicated, and consistent with the policy. Write them SMART, assign an owner, and track them.

Most quality policies are a paragraph of good intentions taped to the break-room wall: "We are committed to customer satisfaction and continual improvement." Nobody can act on that. Quality objectives are how you make the policy real. They take a vague promise and break it into specific numbers that specific people are on the hook to move by a specific date. This post covers what the standard actually requires, how to write objectives that pass an audit and drive behavior, and a worked table you can copy.

What does ISO 9001 require for quality objectives?

ISO 9001:2015 clause 6.2 requires an organization to establish quality objectives at relevant functions, levels, and processes. It is not enough to have one objective for the whole plant; the standard expects them where the work happens. The clause then sets seven conditions each objective must meet. The objectives shall:

be consistent with the quality policy;
be measurable;
take into account applicable requirements;
be relevant to conformity of products and services and to enhancement of customer satisfaction;
be monitored;
be communicated; and
be updated as appropriate.

Clause 6.2 also has a planning half that auditors love and most plants skip. For each objective you must determine what will be done, what resources are required, who is responsible, when it will be completed, and how the results will be evaluated. An objective without that plan is a headline with no story, and it is the single most common finding in a clause 6.2 audit. The objectives themselves are documented information you maintain, so they live in the QMS not in one manager's head.

The policy names the intent. Objectives make it measurable by function. The line-level metric is what an operator can actually move.

What makes a quality objective SMART?

SMART is the checklist that separates a real objective from a slogan. Each letter closes a loophole:

Specific. "Improve quality" is not an objective. "Reduce customer complaints on Line 3" is. Name the thing.
Measurable. There has to be a number and a way to read it. If you cannot chart it, you cannot know whether you hit it. This is the ISO 9001 requirement in plain clothes.
Achievable. A target of zero defects by next quarter is a morale killer, not a goal. Stretch from the baseline; do not fantasize.
Relevant. It must trace back to the quality policy and to product conformity or customer satisfaction. An objective about something the customer never notices is off-mission.
Time-bound. A deadline turns a wish into a commitment. "By December 31" is what makes a review meaningful.

The two letters people fake are Measurable and Achievable. "Improve customer satisfaction" with no metric fails Measurable. "100% on-time, zero defects" fails Achievable and quietly teaches everyone that the objectives are theater. Anchor the target to your own quality metrics baseline, then set a stretch that a good year could actually reach.

A single well-formed sentence holds every SMART element. Read your objectives back against this and the weak ones show themselves.

How do you write quality objectives step by step?

The process is short, but the order matters. Skip the baseline step and every target after it is a guess.

Read the quality policy first. Every objective has to trace to it. Underline the two or three promises the policy actually makes; those become your objective themes.
Pick the functions and processes that carry those promises. Production, quality, purchasing, shipping. The standard wants objectives where the work happens, so choose the handful of areas that most affect conformity and the customer.
Establish the baseline. Pull the last few months of the metric. You cannot set an honest target without knowing where you stand today, and "we think it's about" is not a baseline.
Set the SMART target. A specific number, a deadline, and a stretch that is reachable. Write it as one sentence and check it against the SMART anatomy.
Assign the owner and the plan. One name, plus the clause 6.2 planning: what will be done, what resources, and how results are evaluated. No owner, no objective.
Choose the review cadence. Monthly for line metrics, quarterly at management review. Put it on the calendar before you launch, not after it slips.
Communicate it to the people who move it. An objective the line has never seen cannot be met by the line. Post it where the work is and talk about it, not just at the audit.

One trap to name outright: do not set an objective on a metric you cannot yet measure reliably. If two shifts count scrap differently, an objective built on that number will reward whoever counts most generously, not whoever improves the process. Fix the measurement first, then set the target. Getting that order backwards is how objectives quietly train people to game the count instead of moving it.

What do good quality objectives look like?

Here is a small set of objectives written the way an auditor and an operator both want to see them. Notice that each pairs a baseline with a target, names an owner, and sets a cadence.

Objective	Metric	Baseline → Target	Owner	Review
Raise first-pass yield on Line 3	FPY %	93% → 97% by Dec 31	Line 3 supervisor	Monthly
Reduce customer complaints	Complaints / million shipped	420 → 300 this year	Quality manager	Monthly
Close corrective actions on time	On-time CAPA %	74% → 90% by Q3	QA lead	Monthly
Lower cost of poor quality	COPQ as % of sales	9.5% → 7% this year	Plant manager	Quarterly
Improve supplier quality	Incoming defect PPM	1,800 → 900 by year-end	Purchasing lead	Quarterly

Each of those is auditable and actionable. Contrast them with the versions that fail: "improve yield," "fewer complaints," "faster CAPAs." Same intent, zero teeth. The dollar-based objective (COPQ) is worth including on purpose, because it is the one that keeps quality objectives from being seen as the quality department's private hobby. Tie it to cost of quality and the finance team starts caring about your scrap chart.

What do the standards actually say?

The requirements behind quality objectives

ISO 9001:2015 clause 6.2 requires quality objectives to be established at relevant functions, levels, and processes, and to be measurable, monitored, communicated, updated, and consistent with the quality policy (ISO 9001:2015).
The same clause requires planning for each objective: what will be done, what resources are needed, who is responsible, when it will be completed, and how results will be evaluated (ISO 9001:2015, clause 6.2).
ISO maintains a plain-language overview of the standard's structure and intent, including the emphasis on measurable objectives and continual improvement (ISO, Quality management).

How many quality objectives should you have?

Enough to cover the policy's promises, few enough to actually manage. For most single-site manufacturers that is somewhere between five and ten. Fewer than that and you have probably left a key function uncovered; many more and the review meeting turns into a status-reading exercise where nothing gets real attention. Objectives compete for the same management time as everything else in the plant, and a long list loses that competition by diluting focus.

Resist the temptation to write an objective for every metric you track. Objectives are the targets you are actively driving this year, not your whole dashboard. A metric you are simply watching stays on the scorecard; it becomes an objective only when you commit resources and a deadline to moving it. This is exactly the connection between your objectives and your broader set of manufacturing KPIs: KPIs tell you the state of things, objectives commit you to changing a few of them.

How do you keep objectives from dying after the audit?

The failure mode is predictable: objectives get written in January to satisfy the standard, filed, and rediscovered the week before the audit. The fix is to make them live in the same rhythm as the rest of the operation. Review them at the same monthly meeting where you review production and safety, not at a special once-a-year "objectives meeting" nobody protects. Put the current number next to the target on a board the team walks past. When one goes red, treat it like any other problem: open a corrective action name the cause, set a date.

The practical blocker is almost always data. If the number behind an objective takes a day to assemble from paper logs, the review will be stale and the objective will drift. Capturing yield, scrap, and CAPA status as structured data at the point of work is what makes a monthly objectives review a five-minute glance instead of a scramble. That is the problem Harmony's station-level digitization is built to solve, no rip-and-replace, so the objective on the board is always today's number. See it running in the CLS case study and feed the results back into next year's targets. Objectives that live in the daily rhythm improve; objectives that live in a binder expire.