ISO 9001 clause 7.1: provide the resources quality depends on

What clause 7.1 requires in practice

Clause 7.1 is the umbrella for all resources the QMS depends on. The organisation determines and provides what is needed to set up, run, maintain and continually improve the system. In doing so it takes two considerations into account: what its existing internal resources can and cannot do, and what has to come from external providers.

The clause is then developed in subclauses. Subclause 7.1.2 addresses people. Subclause 7.1.3 addresses infrastructure, and 7.1.4 the environment for the operation of processes. Subclause 7.1.5 addresses monitoring and measuring resources, split into general fitness and traceability, and 7.1.6 addresses organisational knowledge. Subclause 7.1.1, the general part, ties them together by asking for a deliberate decision about resources, not an assumption.

The clause says nothing about budgets, headcount or technology levels. It expects a reasoned judgement that the resources are enough for the processes and the results they must deliver, with evidence that the judgement was made.

Look across the resource categories

Start with the process result and the resources on which it depends. Consider staffing capacity, tools and facilities, suitable working conditions, resources used to verify conformity and the knowledge needed to perform the work. A resource shortage may appear as a quality problem in another part of the system.

Do not assume that each category belongs exclusively to one department. Infrastructure may involve IT and facilities, while organisational knowledge may be embedded in experienced staff, methods and digital systems. Coordination matters when a change affects several categories at once.

Why resourcing the QMS matters to the business

A quality system is only as strong as the means behind it. Ambitious policies and targets collapse when the team is short of people, the tools are unreliable or an outside provider cannot deliver. Looking accurately at internal strengths and limits, and at what to obtain from outside, lets leaders spend where the customer will feel it and avoid promising what the organisation cannot support. It also makes resourcing a planned conversation instead of a crisis response, which shows in steadier delivery, fewer last-minute workarounds and a management review that discusses real constraints.

How to implement clause 7.1

Use the resource subclauses as a checklist for each key process, and keep the conclusions short and accurate. One way Sterling's teams do this is to add a resource question to each process review, so the conversation happens with the people who feel any shortfall first. The clause requires a considered determination, not a specific resource plan, and a short note of the conclusion is acceptable when the process is simple. Larger decisions about people, equipment or outside providers deserve a fuller record.

1. Identify the processes that matter most to customers and to conformity.
2. For each, list what is needed across people, infrastructure, environment, measuring resources and knowledge.
3. Assess the current internal capability and note the limits, such as skills, capacity or equipment age.
4. Decide which needs should be met from external providers and how their suitability will be confirmed.
5. Agree actions and owners for each gap, and tie them to planning and objectives.
6. Make resource needs a standing item in management review.
7. Revisit the assessment when workload, technology or customer requirements change.

Illustrative manufacturing example: an inspection bottleneck

Illustrative software example: maintaining a test environment

A hypothetical software company relies on a test environment that no longer represents a significant customer's configuration. Test staff have the necessary skills, but some customer-specific knowledge is held by a former project lead and the environment's maintenance responsibility is unclear.

The resource review connects infrastructure, knowledge and responsibility. The team updates the relevant configuration information, assigns maintenance ownership and checks whether planned tests can now address the customer's requirements. Evidence concerns the suitability of the working arrangement, not simply whether the company owns enough servers or has purchased a testing application.

Distinguish provision from continuing suitability

Providing a resource is not always a one-time decision. Infrastructure and process environments need to remain suitable; monitoring and measuring resources require attention to their continuing fitness; knowledge must be retained, applied and shared where necessary. Changes in products, services or customer requirements can alter what is needed.

A proportionate review considers actual performance and foreseeable demand. Ask whether the available resources support peak loads, important absences and planned changes where those conditions matter to quality. The standard does not impose universal redundancy, headcount or replacement intervals. Decisions should follow the process and applicable requirements.

Use the specific requirements for each resource

People concerns providing the persons needed to operate and control processes, while competence is addressed separately in 7.2. Infrastructure concerns facilities, equipment and other necessary operating resources. Process environment considers the conditions in which work occurs.

Monitoring and measuring resources require valid and reliable verification results, with more specific traceability requirements where applicable. Organisational knowledge concerns retaining and using what the process needs to know. Follow the relevant subclause instead of treating every resource as a purchasing issue.

Evidence and common weaknesses

Explore each numbered part