ISO 9001 clause 5.3: give quality responsibilities workable authority
ISO 9001:2026 clause 5.3 requires top management to ensure that relevant responsibilities and authorities are assigned and communicated. The organisation needs clear ownership for QMS conformity, process results, customer focus, performance and improvement reporting, and the system's integrity when changes are planned and implemented.
What clause 5.3 requires in practice
Clause 5.3 asks top management to assign and communicate responsibilities and authorities for the roles that matter to the system. It then names six responsibilities that must be allocated to someone:
- making sure the system conforms to the standard;
- reporting system performance to top management;
- making sure processes deliver their intended results;
- promoting customer focus throughout the organisation;
- reporting opportunities for improvement to top management;
- safeguarding the integrity of the system when changes are planned and put into effect.
The clause does not require a particular job title or a single person. A small business may combine duties and a large group may spread them. What counts is that each is covered, that the holder knows about it, and that the authority matches the responsibility.
Assign the required functions without prescribing a title
The standard identifies responsibilities that need to be covered, but does not require one universal job title or a single person to perform every function. A small organisation may combine roles; a larger group may distribute them across management, process owners and specialist teams. What matters is clear coverage and effective coordination.
Identify who ensures that the QMS meets its requirements and who reports performance and improvement opportunities to top management. Clarify who owns the intended results of each process and how customer focus is promoted. These arrangements should connect with normal management responsibilities, rather than create an isolated quality hierarchy with little influence over the work.
Communicate decision boundaries and escalation
People need to know not only who holds a responsibility but when to involve that role. Define how exceptions, unresolved requirements and resource constraints move to someone with suitable authority. A diagram may show reporting lines while leaving those decision boundaries unclear.
Existing job descriptions, process information, delegation arrangements or team briefings can communicate responsibilities. Those are optional formats. Test their adequacy through an actual situation: when two functions disagree about whether work can proceed, can staff identify who decides and what information that person requires?
How to implement clause 5.3
Allocate duties to real roles and test the arrangement with a difficult scenario. Titles are not prescribed, so concentrate on coverage, knowledge and authority and avoid building a separate quality hierarchy. Revisit the allocation after any reorganisation, and keep notes short.
- List the six responsibilities and write the name of the role currently carrying each one, noting any gaps or overlaps.
- Decide where one person holds several duties, and check that the combination does not create a conflict of interest.
- For each process, confirm that the owner can obtain information, resolve competing priorities and escalate.
- Communicate responsibilities through channels people actually use, such as job descriptions, team briefings or process information.
- Define how decisions move upward when functions disagree or resources are short, and who has the final say.
- Run a realistic scenario, such as a disputed inspection result, and check that staff know who decides and what information they need.
Evidence an auditor expects for clause 5.3
The auditor checks that duties are assigned, known and usable. Authority matters as much as the title.
- Records showing which roles carry each of the six responsibilities.
- Interviews with role holders who can explain what they are responsible for and what they may decide.
- Examples of reports on performance and improvement opportunities reaching top management.
- Observation of how responsibilities are communicated and updated after organisational change.
- Evidence that the integrity of the system was considered when a change was planned.
Illustrative manufacturing example: an uncertain acceptance result
A hypothetical manufacturer finds conflicting inspection results on a batch awaiting dispatch. The production supervisor is responsible for schedule performance, while the quality technician can record results but has no defined escalation route for disagreement. Staff informally choose whichever manager is available.
Management clarifies the authority for evaluating the acceptance position, deciding permitted actions and communicating with the customer where necessary. It ensures that the relevant roles understand the boundary between scheduling and release. Later samples show whether decisions are made by the assigned authority and supported by evidence. The example does not prescribe a particular organisational title or a universal acceptance decision.
Illustrative BPO example: a process moves between sites
A hypothetical BPO company transfers part of a service from one location to another. Training is scheduled, but responsibility for updating customer-specific instructions is assumed to belong to both sites. Each team expects the other to confirm the final version.
The change owner maps the affected QMS responsibilities before transfer, assigns one accountable owner for instruction approval and identifies who verifies readiness at each location. Management checks whether reporting and escalation continue to function after the move. This illustrates maintaining QMS integrity through change, rather than considering a transfer complete when staff accounts have been created.
Keep reporting connected with management decisions
Reporting performance and opportunities for improvement should give top management information it can use. A role that merely circulates a dashboard may not ensure that significant weaknesses reach the appropriate decision-maker. Establish how important issues are highlighted, how decisions are recorded and how unresolved actions are followed.
Customer focus also needs operational ownership. It should not be assumed to belong only to sales or customer service. Purchasing, design, production and support decisions can all affect whether customer requirements are met. Relevant managers need to understand their part in the overall result.
Check gaps when roles or processes change
Restructuring, absence, outsourcing and new services can leave responsibilities unassigned or duplicated. Review authority arrangements when those changes affect the QMS. Temporary cover may need explicit limits and escalation rather than an assumption that another employee has inherited all decision rights.
Common failures include impressive job descriptions that do not match practice, several “owners” with no final decision authority and responsibility assigned to someone outside the relevant management process. Another is confusing the QMS coordinator's reporting work with top management's accountability. The parent leadership requirements continue to apply even when coordination is delegated.
Frequently asked questions
Is a management representative mandatory?
Clause 5.3 requires the relevant responsibilities and authorities to be assigned and communicated. It does not prescribe that particular title or require every responsibility to sit with one person.
Can one person hold several quality roles?
Yes, if the arrangements remain effective and other applicable requirements are met. Consider capacity, competence and any need for impartiality in activities such as internal audit.
Must responsibilities be documented in a RACI matrix?
No specific matrix is required. Choose a method that makes responsibilities and authority clear, current and understood by the people who need to act.
Resolve unclear ownership before it reaches the customer
Discuss QMS roles and process accountability with Sterling. Across business units, agreed support can connect role design, implementation, employee learning and scoped Effivity ISO & GRC automation software. Independent bodies decide certification.
For people managing process information, explore Documented Information Management. Continue to planned QMS changes when a restructure or transfer affects the responsibilities.