ISO 9001 clause 7.1.3: keep infrastructure fit for the process

What clause 7.1.3 requires in practice

Clause 7.1.3 requires the organisation to determine, provide and maintain the infrastructure needed to operate its processes and achieve conformity of its products and services. The three verbs matter: working out what is needed, putting it in place, and keeping it in a condition that continues to meet the need.

A note in the clause confirms that infrastructure can include buildings and their utilities, equipment (both hardware and software), transport resources, and information and communication technology. It also points out that this applies to all types of work, whether on site, remote or a mix of the two. This is a helpful reminder that infrastructure is not limited to factories; a service organisation depends on networks, devices, access and applications just as heavily.

The clause does not demand a maintenance programme in a given format. It expects maintenance in proportion to the effect on conformity. The output is infrastructure that is suitable and kept suitable.

Identify the dependency and required capability

Start with the process and the conditions necessary for it to work. A service desk may depend on reliable access to current customer information. A production activity may depend on equipment capable of holding the required process conditions. A project team may need suitable means to transport and protect materials before use.

Define the necessary capability clearly enough to assess the arrangement. Avoid relying only on an asset inventory or a supplier's general product description. The same infrastructure may be suitable for one task and unsuitable for another, particularly when requirements or operating conditions change.

Maintain suitability, not merely possession

Maintenance can include servicing, repair, configuration management, updates or other arrangements appropriate to the infrastructure. The clause does not impose one preventive-maintenance interval or require the same method for every asset. Consider the effect of deterioration or loss of function on the process and its results.

Where external providers supply or maintain infrastructure, clarify relevant responsibilities and controls. A hosted application or rented facility can still be essential to the QMS. The organisation needs to understand the interface and respond when the arrangement does not meet its operating needs.

Why fit infrastructure matters to the business

Infrastructure failures hit customers fast and are costly to fix under pressure. A machine drifting out of condition produces defects before anyone notices; an overloaded system slows every service request; a poorly planned remote working set-up leaves staff improvising with personal tools. Maintaining infrastructure to a level that matches its importance is far cheaper than recovering from the breakdown, the recall or the lost client. It also supports consistency, because staff who can rely on their tools can concentrate on the customer. Auditors treat the state of equipment as an accurate indicator of how management invests in quality.

How to implement clause 7.1.3

Link infrastructure to process results, and treat maintenance as part of delivering quality. One way Sterling's teams do this is to begin with the equipment and systems that staff complain about, since these usually reveal where infrastructure and conformity meet. The clause sets the outcome, and the choice of maintenance method, schedule format or software tool remains with the organisation. Include shared and rented facilities, since an arrangement with an outside party still has to meet the need.

1. List the buildings, equipment, software, transport and communication systems each process relies on.
2. Mark the items whose failure would affect conformity, and treat those as critical.
3. Decide what suitability means for each critical item, for example capacity, availability or condition.
4. Set maintenance or review arrangements in proportion to the risk, using supplier guidance where relevant.
5. Include remote and hybrid working arrangements, not only premises.
6. Capture faults and near misses, and use them to change maintenance and replacement plans.
7. Plan replacement or upgrade before infrastructure becomes unreliable.

Illustrative software example: a dependable build environment

Illustrative construction example: handling project materials

A hypothetical contractor expands the volume of prefabricated items delivered to a site. The existing handling and storage arrangement was designed for a smaller flow, and items are repeatedly moved while awaiting installation. Damage and identification problems begin to affect conformity.

The project team assesses the infrastructure needed for the actual flow, including suitable handling resources and storage arrangements. It assigns responsibility for maintaining the arrangement and checks whether items remain suitable for use. Technical handling methods must be determined competently for the project; the QMS lesson is to connect infrastructure capacity and condition with quality, rather than assume the previous arrangement remains adequate.

Consider remote and distributed work

For remote work, infrastructure may include the applications, access arrangements and communication resources needed to perform the process. The relevant question remains whether the work can be done effectively and conforming results achieved. A remote-work policy does not establish that each necessary operating dependency has been addressed.

Across sites, a common infrastructure standard can support consistency, but local conditions may require different provision. Review interfaces between central and local support so that maintenance or change decisions do not unintentionally remove a capability needed by another team.

Evidence and review

Common nonconformities with clause 7.1.3

Findings arise where infrastructure is used but not managed. Typical examples: Auditors tend to find these by walking the process and asking how a given machine or system is kept fit, then comparing the answer with what was done. The clause does not expect a maintenance plan for every item, but it does expect that critical infrastructure is managed deliberately.

• Critical equipment is run to failure and no one has judged its effect on conformity.
• Software or systems used in delivery are unsupported or lack suitable capacity.
• Maintenance arrangements exist but are not followed.
• Remote workers lack access or tools the process needs, and the gap has been worked around informally.
• Recurring faults appear in complaints but never reach maintenance planning.