ISO 9001 clause 7.3: help people understand their quality impact

What clause 7.3 requires in practice

Clause 7.3 asks the organisation to make sure that everyone doing work under its control understands five things. The first is the quality policy. The second is how their own work adds to making the quality management system effective, including what better performance brings. The third is what follows if the system's requirements are not met. The fourth is the quality objectives that apply to their role. The fifth is the organisation's quality culture and ethical behaviour, a point the 2026 edition spells out.

The wording covers anyone working under the organisation's control, so contractors, agency staff and temporary workers fall inside the scope as well as employees. The clause requires awareness, meaning an understanding of why things matter. That differs from competence under clause 7.2, which concerns the ability to perform a task. The practical output is people who can explain, in their own words, how their daily choices affect customers and the reliability of records. The clause does not list an induction course, a test or a signed acknowledgement. Those are methods an organisation may choose, and none is mandatory by itself.

Connect the policy with the person's contribution

Explain how the person's work supports the QMS and the benefits of improved performance. The contribution of a purchasing employee may concern clear provider requirements; a developer's contribution may concern traceable customer acceptance conditions. A general statement that “quality is everyone's job” needs practical meaning.

Relevant quality objectives should be understandable. Staff need to know which result matters and how their work contributes without creating an incentive to conceal problems. If a target concerns accurate resolution, explain why closing a case without resolving it does not support the intended outcome.

Explain consequences without relying on fear

Awareness includes the implications of not conforming to QMS requirements. Discuss effects on customers, connected processes and the reliability of evidence. The purpose is to support sound decisions and appropriate escalation, not to make employees afraid to report uncertainty or a mistake.

The 2026 inclusion of quality culture and ethical behaviour reinforces the need for consistent management signals. People should understand that accurate information and responsible decisions matter, including when the news is uncomfortable. A presentation promoting honesty is weakened if supervisors reward misleading records during a busy period.

Why awareness matters to the business

Most quality failures that reach a customer begin with someone who did not realise a step mattered. A person who understands what the policy means for their role is more likely to raise a doubt, follow a check or flag a poor record before it spreads into the next process. That protects customer trust and reduces rework, complaints and the cost of putting things right after delivery. Awareness also supports accurate reporting, because staff who see the reasons behind a target are less tempted to hit it by shortcuts. For leaders, it is one of the few requirements where the visible behaviour of managers is as important as any written message. At audit, weak awareness is quickly exposed when an auditor simply asks a few people why their work matters to the customer.

How to implement clause 7.3

Treat awareness as a conversation tied to real work, then check that it landed. One way Sterling's teams approach it is to start from the five topics in the clause and ask what each means for a particular role.

1. List who works under the organisation's control, including contractors and temporary staff, and group them by the work they do.
2. For each group, translate the quality policy and relevant objectives into one or two plain examples from their daily tasks.
3. Explain the effect on customers and on the next process if a step is skipped or a record is inaccurate, without using fear as the message.
4. Describe the organisation's expected quality culture and ethical behaviour, and show how people can raise a concern or admit a mistake safely.
5. Deliver the message where people already meet: team briefings, onboarding, shift handovers or short walk-throughs at the workplace.
6. Check understanding by asking people to explain their contribution, and watch whether managers' own decisions match what was said.
7. Repeat the message when the policy, objectives or processes change, and when new people join.

Evidence an auditor expects for clause 7.3

The clause does not call for one particular record, so an auditor mainly looks for proof that people actually understand. Typical evidence includes:

• interviews in which staff describe the quality policy, their objectives and their own contribution;
• records of briefings, onboarding or toolbox discussions, including who took part and what was covered;
• observation that people raise concerns or report errors through the expected route;
• communication material that matches the current policy and objectives, and reaches contractors as well as employees;
• signs that managers act consistently with the stated culture, for example how a missed target is handled.

Common nonconformities with clause 7.3

Auditors tend to find the same few gaps when awareness is treated as a formality.

• Staff cannot describe the quality policy or say which objectives relate to their work.
• Awareness material exists but has not reached contractors, temporary workers or a night or remote team.
• People do not understand what happens to the customer or the next process if they do not follow the requirements.
• Briefings were delivered once and not refreshed after the policy or objectives changed.
• Messages about honesty are undermined by managers who accept inaccurate records during busy periods.

Illustrative manufacturing example: an incomplete check

Illustrative software example: an undocumented assumption

A hypothetical software developer changes an agreed behaviour after assuming a customer requirement is outdated. The developer is technically skilled but does not appreciate why an unreviewed change can affect customer acceptance and related test evidence.

The project lead explains the requirement-change route using the actual handover between customer review, development and testing. Staff discuss how to raise a proposed improvement without silently changing the accepted basis. The organisation checks understanding through later change discussions. Requiring the developer to memorise the quality policy would not, by itself, address the specific awareness gap.

Reach people in different working arrangements

The clause applies to relevant people doing work under organisational control. Consider temporary personnel, remote teams and others whose work affects the QMS. They may need information tailored to their responsibilities and access to the same escalation principles as permanent staff.

Use suitable communication and learning methods. Briefings, induction, examples, team discussions and feedback can contribute. The standard does not prescribe one duration, delivery platform or annual awareness course. Check whether the approach reaches the intended people and makes sense in their working context.

Evaluate understanding proportionately

No separate awareness record format is prescribed by this clause. Evidence can include employees' explanations, observed behaviour and the way relevant issues are raised. Attendance records may support the account, but they should not be treated as automatic proof of understanding.

Common weaknesses include generic content disconnected from the role, objectives communicated only to managers and confusion between awareness and competence. Another is blaming individuals for not understanding a message that conflicts with actual incentives. Review both the communication and the surrounding management behaviour when an awareness problem recurs.

Competence addresses the ability to apply knowledge and skills. Awareness explains relevant purpose, contribution and consequences. An effective support approach considers both without assuming one replaces the other.