Quality objectives are one of the first things an auditor checks when they arrive at your organisation. Under ISO 9001 Clause 6.2, the requirements are clear: objectives must be measurable, consistent with the quality policy, monitored, communicated, and updated as appropriate. Yet in practice, quality objectives remain one of the most common sources of nonconformities during certification and surveillance audits. The problem is rarely that organisations forget to write them. The problem is that what gets written does not actually meet the standard, and when an auditor starts asking questions, the gaps become obvious very quickly.
On this page
This article gives you practical, real world examples of quality objectives that hold up under scrutiny, explains what makes them work, and shows you exactly where poorly written objectives fall apart during an audit.
What ISO 9001 Clause 6.2 Actually Requires
Before looking at examples, it is worth being precise about what the standard asks for. Clause 6.2.1 states that quality objectives shall be established at relevant functions, levels, and processes. They shall be consistent with the quality policy, measurable, take into account applicable requirements, be relevant to conformity of products and services and enhancement of customer satisfaction, be monitored, be communicated, and be updated as appropriate.
Clause 6.2.2 goes further, requiring that when planning how to achieve quality objectives, the organisation determines what will be done, what resources are required, who will be responsible, when it will be completed, and how the results will be evaluated.
That is a significant list. An objective that simply says improve customer satisfaction does not come close to meeting these requirements. It has no measure, no owner, no timeline, and no defined method for evaluation. An auditor will raise this as a nonconformity, and rightly so.
A related post worth reading is ISO 9001 Clause 6.2 Quality Objectives Explained, which covers the clause requirements in full detail.
The Six Characteristics of an Audit Ready Quality Objective
Good quality objectives share six characteristics that map directly to what an auditor will test. Use these as a checklist when you are writing or reviewing your own objectives.
- Specific: The objective describes a defined outcome, not a general aspiration.
- Measurable: There is a number, percentage, or threshold that defines success.
- Owned: A named person or role is accountable for achieving it.
- Time bound: There is a defined review date or completion target.
- Monitored: There is a process for tracking progress, not just a final review at year end.
- Linked to the quality policy: The objective can be traced back to a commitment in the quality policy.
If any of these elements is missing, an auditor has grounds to raise a nonconformity. The most common gap is measurability, followed by the absence of a monitoring process.
Example Quality Objectives by Industry
The examples below are drawn from real audit scenarios across manufacturing, construction, professional services, and healthcare. Each one is written in a format that would satisfy an auditor, followed by a brief explanation of why it works.
Manufacturing: On Time Delivery
Objective: Achieve an on time delivery rate of 95% or above for all customer orders, measured monthly against confirmed delivery dates, with results reviewed at management review. Owner: Operations Manager. Target date: Ongoing, reviewed quarterly.
This works because the measure is specific (95%), the frequency of monitoring is defined (monthly), the review mechanism is named (management review), and there is a clear owner. An auditor can ask the Operations Manager to produce the last three months of delivery data and verify whether the target is being tracked. There is nothing vague here.
Manufacturing: Product Nonconformance
Objective: Reduce the rate of nonconforming product at final inspection to below 1.5% of total units produced by 31 December, measured monthly using inspection records. Owner: Quality Manager.
This objective connects directly to product conformity, which is explicitly mentioned in Clause 6.2.1. The baseline is implied by setting a target, and an auditor can request inspection records to verify monitoring is occurring. The year end date gives a clear point for evaluating achievement.
Construction: Customer Satisfaction
Objective: Achieve a minimum average customer satisfaction score of 4.2 out of 5 on post project surveys, with surveys issued within 14 days of project completion. Owner: Project Manager. Reviewed at each management review.
Customer satisfaction is a requirement under Clause 9.1.2, so linking an objective to it demonstrates alignment between planning and performance evaluation. The score threshold is measurable, the survey timing is defined, and the review cadence is clear. An auditor will ask to see the survey results and verify the average is being calculated.
Construction: Rework Rate
Objective: Limit rework costs to no more than 2% of total project value per project, tracked through the nonconforming works register. Owner: Site Manager. Reported monthly to the Construction Manager.
This objective is practical and directly tied to a document that already exists in most construction quality management systems. The nonconforming works register provides the evidence trail. An auditor can verify both the objective and the monitoring mechanism in a single document review.
Professional Services: Complaint Resolution
Objective: Resolve 100% of customer complaints within 10 business days of receipt, tracked through the complaints register. Owner: Client Services Manager. Reviewed monthly.
Complaint handling is something auditors will always look at. An objective that sets a response time target and links it to a register gives the auditor a clear evidence trail. The 100% target is ambitious but appropriate for a small volume of complaints typical in professional services.
Professional Services: Internal Audit Programme Completion
Objective: Complete all planned internal audits within the scheduled audit programme year, with no audits deferred beyond 30 days without documented justification. Owner: Quality Manager. Reviewed at year end management review.
This is a process quality objective rather than a product or customer objective. It demonstrates that the organisation is treating its own management system as something worth measuring. Auditors appreciate seeing this because it shows the quality system is genuinely being managed, not just maintained on paper.
Healthcare: Document Control Compliance
Objective: Ensure 100% of clinical procedures are reviewed and approved within their defined review cycle, with no overdue documents at the time of internal audit. Owner: Quality and Compliance Manager. Verified at each internal audit.
In healthcare settings, document currency is critical. This objective is directly verifiable during an audit by checking the document register against review dates. The link to internal audit as the verification mechanism is practical and efficient.
Healthcare: Staff Competence Records
Objective: Maintain complete and current competence records for 100% of staff in roles with defined competence requirements, with gaps identified and actioned within 30 days of identification. Owner: People and Culture Manager. Reviewed quarterly.
This objective connects Clause 6.2 planning to Clause 7.2 competence requirements, which is exactly the kind of cross clause alignment auditors look for in a mature quality management system.
What Weak Quality Objectives Look Like and Why They Fail
It is just as useful to understand what fails as to see what works. Here are three common examples of weak objectives and the specific reasons they would attract a nonconformity.
Weak Example 1: Improve Customer Satisfaction
This fails on multiple counts. There is no measure, no target, no owner, no timeline, and no defined monitoring method. An auditor cannot determine whether this objective has been achieved because there is no basis for evaluation. It is an aspiration, not an objective.
Weak Example 2: Maintain ISO 9001 Certification
This is a common one, and it fails because maintaining certification is not a quality objective in the sense intended by the standard. It says nothing about what the organisation will actually do to improve quality. It is also circular: the purpose of quality objectives is to improve the system, not to preserve the certificate that recognises it.
Weak Example 3: Reduce Complaints
This is closer to acceptable but still falls short. It lacks a baseline, a target, a timeframe, and an owner. Reduce by how much? Compared to what? By when? Who is responsible? An auditor will ask all of these questions and expect answers. Without them, this is not a measurable objective.
How Auditors Test Quality Objectives in Practice
When an auditor sits down to review your quality objectives, they are doing several things at once. They are checking that the objectives exist and are documented. They are checking that the objectives are measurable and have owners. They are looking for evidence that progress is being monitored, not just recorded at year end. And they are checking that the objectives were discussed at management review.
A typical audit sequence looks like this. The auditor asks to see the quality objectives. They review the objectives against the six characteristics described earlier. They then ask the owner of one or two objectives to walk them through the monitoring process. They ask to see the data. They check the management review minutes to confirm the objectives were reported on. If any of these steps produces a gap, they have the basis for a finding.
The most common gap is that objectives exist on paper but nobody can produce monitoring data. The Operations Manager cannot tell you what last month's delivery rate was. The Quality Manager cannot show you the complaint resolution times from the last quarter. The document exists but the system behind it does not. This is what auditors are trained to find.
For a closer look at how auditors approach this clause specifically, see Auditing Quality Objectives: Evidence to Look for Under Clause 6.2.
Connecting Quality Objectives to the Management Review
One of the requirements in Clause 9.3 is that management review inputs include the extent to which quality objectives have been achieved. This creates a direct link between your objectives and your management review process. If your management review minutes do not reference quality objectives, an auditor will raise it.
The practical implication is that your quality objectives need to be designed with reporting in mind from the start. If you cannot produce a simple one page summary of objective status for each management review, your objectives are probably not structured well enough. The best quality objectives are ones where the data practically generates itself through normal operations, such as delivery records, complaint logs, inspection results, and audit completion rates.
If you want to understand how management review fits into the broader picture, How to Conduct an Effective Management Review Under ISO 9001 is a useful companion read.
Setting Objectives at Relevant Functions and Levels
Clause 6.2.1 specifies that objectives shall be established at relevant functions, levels, and processes. This is a requirement that organisations frequently underinterpret. Many organisations set three or four organisation wide objectives and leave it at that. An auditor may question whether objectives have been set at the process or departmental level where the work actually happens.
This does not mean you need dozens of objectives. It means that the objectives you set should reflect the parts of the organisation where quality performance matters most. A manufacturing company might have objectives at the production level, the procurement level, and the customer service level. A small professional services firm might have objectives at the practice level and the administration level. The key is that objectives are not just a head office document: they are connected to the people and processes that deliver quality outcomes.
Reviewing and Updating Objectives
The requirement to update objectives as appropriate is often overlooked. Objectives that were set three years ago and have never been revised are a red flag. An auditor will ask when the objectives were last reviewed and what prompted any changes. If the answer is that nothing has changed in three years, that is a signal that the objectives are not being actively managed.
Good practice is to review objectives at least annually, ideally as part of the management review process. If an objective has been consistently achieved, consider whether the target should be raised. If an objective is consistently missed, consider whether the target is realistic or whether the underlying process needs to change. Either way, the review conversation should be documented.
Practical Tips for Writing Better Quality Objectives
- Start with your quality policy commitments and ask what you would measure to know those commitments are being kept.
- Use the format: achieve X result, measured by Y method, by Z date, owned by W person.
- Choose measures that come from data you already collect, so monitoring does not create extra administrative burden.
- Set between three and eight objectives for most organisations. Too few suggests the system is not being actively managed. Too many becomes unmanageable.
- Make sure every objective has a named owner who knows they own it, not just a title on a document.
- Build objective reporting into your management review agenda as a standing item.
If you are preparing your quality management system for an upcoming certification audit, the article How to Prepare for a Certification Audit as the Quality Manager covers the broader preparation process in practical detail.
Building the Skill to Audit Quality Objectives
If you are an internal auditor or quality manager who wants to audit quality objectives with confidence, the skill is really about asking the right questions and knowing what evidence to look for. The questions are simple: Can you show me the data behind this objective? When was it last reviewed? Who is responsible for monitoring it? What happened when the target was missed?
The evidence is equally straightforward: monitoring records, management review minutes, corrective actions linked to objective shortfalls, and documented objective reviews. If those four things are present and coherent, the objectives will pass an audit. If any of them is missing, you have work to do before the auditor arrives.
Audit Workshop delivers practical internal auditor and lead auditor training across ISO 9001, ISO 14001, and ISO 45001. The courses are built around real audit scenarios, not just clause reading, so you leave knowing how to audit objectives, processes, and systems with genuine confidence. If you are preparing to sit an internal auditor or lead auditor course, or if you want to sharpen your skills before an upcoming certification audit, visit auditworkshop.com to explore the available training options.
