ISO 9001 clause 5.1.1: make management accountability visible

What clause 5.1.1 requires in practice

Clause 5.1.1 sets out twelve ways in which top management shows leadership and commitment. In practice they group into four themes:

• Direction: the quality policy and objectives are established and compatible with strategic direction, and the system achieves its intended results.
• Integration and resources: the requirements of the system are built into business processes and the needed resources are available.
• People and culture: managers communicate why effective quality management and conformity matter, direct and support people, support other roles in showing leadership within their areas, and promote quality culture and ethical behaviour.
• Ways of working: they promote continual improvement, the process approach and both risk-based and opportunity-based thinking.

Above all, top management takes accountability for the effectiveness of the system. Notes explain that "business" can be read broadly as the activities central to the organisation's purpose.

Connect strategic direction with operating priorities

Quality policy and objectives need to be compatible with the business's direction. A strategy to provide more complex services, for example, should influence competence, provider arrangements and process controls. Leaders should not approve expansion while assuming the existing QMS can absorb every change without resources or review.

Integration means using the system in decisions such as budgeting, service acceptance, investment and management of change. It does not require replacing ordinary business meetings with ISO-labelled meetings. Existing arrangements can be effective when they address the relevant quality responsibilities and lead to action.

Give other managers the support to lead

Top management must direct and support people contributing to QMS effectiveness and support relevant management roles in their own areas. Consider whether process owners can obtain necessary information, resolve conflicting priorities and escalate constraints. A responsibility written in a job description may be ineffective if the holder cannot influence the process.

Communication should make the importance of effective quality management clear. Employees need to understand why requirements matter and how their work contributes. The message loses credibility when managers reward short-term completion while tolerating missing acceptance evidence, inaccurate records or unreported defects.

Why management accountability matters to the business

When accountability sits with a specialist, other managers can treat quality as someone else's job. Targets then conflict, resources are rationed without discussion and issues are fixed locally while the cause remains. Visible accountability from the top changes that. Budget, hiring and service-acceptance decisions begin to reflect quality needs, and process owners know their escalations will be heard. Customers feel it in more reliable delivery, and staff feel it in clearer priorities. For the business, the benefit is lower cost of failure and better returns on the effort already spent on procedures and training. Without it, a well-designed system can sit unused.

How to implement clause 5.1.1

Choose a handful of leadership behaviours to make observable, and check them against real situations. The aim is observable behaviour, not additional meetings, so use routines the team already follows. Revisit the choices when priorities change, and keep notes short.

1. Map each leadership item in the clause to a decision or routine already present in your management calendar.
2. Where no routine exists, add a short agenda item to an existing meeting rather than creating a new forum.
3. Ask process owners what support they need from top management and record what was agreed and delivered.
4. Agree how truthful reporting is protected, for example when a test manager reports that work is not ready to release.
5. Include quality and ethical conduct in manager objectives and in how performance information is presented.
6. Test understanding by asking managers how they would handle a conflict between delivery pressure and a control, and review the answers together.

Illustrative software example: truthful release information

Illustrative construction example: authority at the interface

A hypothetical contractor's project quality lead repeatedly identifies mismatches between approved information and installation instructions. The lead can report them but has no route to get design, procurement and site management to agree which information governs the next stage.

Top management clarifies escalation authority, assigns responsibility for resolving the interface and provides time for the necessary review. It then examines whether subsequent discrepancies are resolved before affected work proceeds. The improvement demonstrates support for another leadership role. Merely instructing the quality lead to “be more proactive” would leave the organisational constraint unchanged.

Promote processes, risks and opportunities together

The 2026 requirement explicitly includes promoting the process approach, risk-based thinking and opportunity-based thinking. Leaders should encourage people to examine handovers and consider both undesired effects and beneficial changes. These approaches complement one another: a proposed improvement may create new dependencies that need to be understood before implementation.

Continual improvement also requires more than asking for ideas. Management should consider evidence, prioritise useful changes and check whether the system becomes more suitable, adequate and effective. A quality culture can support this by making problems discussable and recognising the people who identify weak assumptions before customers experience their consequences.

Evidence an auditor can follow

Common nonconformities with clause 5.1.1

Findings here usually reflect a gap between management words and management actions.

• Resource requests from process owners are not decided, or decisions are not communicated.
• Records of system performance are accepted without question although they omit inconvenient cases.
• Managers cannot explain how requirements of the system are integrated into their own area's processes.
• Promotion of the process approach and risk-based thinking is limited to training slides, with no effect on decisions.
• Nobody can say who takes accountability for the effectiveness of the system.