ISO 9001 Clause 7, Support, is everything the quality management system needs to run day to day: resources (7.1), competent people (7.2), awareness (7.3), internal and external communication (7.4), and controlled documented information (7.5).

Clause 7 is the longest clause in ISO 9001 and the least glamorous. It does not set strategy like Clause 5 or control the product like Clause 8. It just makes sure the QMS has what it needs to function: the right people, the right equipment, the right information, in the right place. But "support" is where most plants actually get their nonconformities, because it covers the unglamorous plumbing, calibration, training records, document control, that is easy to let slide until an auditor asks for it.

What does ISO 9001 Clause 7 cover?

Clause 7 has five sub-clauses, and together they answer one question: does the QMS have the support it needs to work? 7.1 is resources. 7.2 is competence. 7.3 is awareness. 7.4 is communication. 7.5 is documented information. The first sub-clause, resources, is itself broken into several pieces that quietly carry a lot of audit weight.

The five sub-clauses of Clause 7 SupportClause 7: the support the QMS runs on7.1 RESOURCESpeopleinfrastructureenvironment for processesmonitoring + measuringmeasurement traceabilityorganizational knowledge7.2 COMPETENCE7.3 AWARENESS7.4 COMMUNICATION7.5 DOCUMENTED INFOA WORKINGQMS
Clause 7 in full. The 7.1 resources sub-clause alone carries six distinct requirements auditors check.

What resources does 7.1 require?

Clause 7.1 requires you to determine and provide the resources needed for the QMS. It breaks into six areas, and each is a common audit topic. People (7.1.2): enough of them, competent, to run the processes. Infrastructure (7.1.3): buildings, equipment, utilities, and IT the work needs. Environment for the operation of processes (7.1.4): the physical and human conditions, temperature, cleanliness, noise, and non-hostile social factors, that affect conformity.

Then two that generate a lot of findings. Monitoring and measuring resources (7.1.5) requires that the gauges and instruments you use to judge conformity are suitable, maintained, and, where measurement traceability is required, calibrated against traceable standards, with records. A drawer full of uncalibrated calipers is a classic Clause 7 nonconformity. Finally, organizational knowledge (7.1.6), new in 2015, requires you to determine and maintain the knowledge the organization needs to operate, and to consider how you will get any additional knowledge you need. This is the clause that speaks directly to tribal knowledge walking out the door when a veteran retires.

What is the difference between competence (7.2) and awareness (7.3)?

Competence and awareness sound similar and are two different requirements. Competence (7.2) is about ability: the people doing work that affects quality must be competent on the basis of education, training, or experience, and you must keep records as evidence. Where there are gaps, you take action, training, mentoring, reassignment, and evaluate whether the action worked. Awareness (7.3) is about understanding: everyone doing work under your control must be aware of the quality policy, the relevant quality objectives, how they contribute to the QMS, and the consequences of not conforming.

The plain-floor difference: competence is "can this operator run the press correctly and can you prove it?" Awareness is "does this operator know why the quality checks matter and what happens downstream if they skip one?" You demonstrate competence with a skills matrix and training records tied to your operator training program. You demonstrate awareness through shift briefings, onboarding, and being able to have the operator explain, in their words, why their job matters.

Where competence gaps show up, 7.2 requires action and then an evaluation of whether the action worked. That last part is the piece plants forget. Sending someone to a training class is an action; confirming afterward that they can now run the job to standard is the evaluation. A training record that only proves attendance does not prove competence. The stronger record shows a qualification: observed, signed off by a competent assessor, and dated, so the skills matrix reflects proven ability rather than good intentions. This is also where 7.1.6 organizational knowledge earns its place, because when a qualified setter retires, the knowledge that made them competent has to survive them, captured in work instructions and cross-training, not lost with their badge.

Competence versus awareness in Clause 7Competence (7.2) vs awareness (7.3)7.2 COMPETENCECan they do the job?based on education, training,or experienceEVIDENCE:skills matrix, training records,qualifications on file7.3 AWARENESSDo they understand why?quality policy, objectives,their contribution + consequencesEVIDENCE:briefings, onboarding,the operator can explain it
Two different requirements. One proves ability; the other proves understanding. Auditors check both.

What does Clause 7.4 communication require?

Clause 7.4 requires you to determine the internal and external communications relevant to the QMS, including what you will communicate, when, with whom, how, and who does it. It is a short clause with a simple test: can you show that quality information moves deliberately, not by accident? Shift handovers, customer feedback loops, changes to a spec reaching the line, a supplier issue reaching purchasing, those are all 7.4 in action.

The weakness 7.4 exposes is the plant that runs on hallway conversations. When the only path for a quality issue to travel is whether the right two people happen to talk before the shift changes, communication is not determined; it is luck. A defined shift handover and a real channel for feedback are what turn 7.4 from a box into a control.

Clause 7.4 is short but it is broader than most plants read it. External communication counts too: how a customer complaint reaches the people who can act on it, how a change to a supplier requirement gets back to purchasing, how a regulatory update reaches the quality team. The clause asks you to decide these paths on purpose rather than leaving them to chance. You do not need a communications plan the size of a phone book; you need to be able to answer, for the handful of quality-critical messages your plant sends and receives, what gets communicated, to whom, when, and by which method.

How much documented information do you need (7.5)?

Clause 7.5 covers documented information, the 2015 term that replaced "documents and records." It has two jobs. Creating and updating (7.5.2): documents need appropriate identification, format, and review and approval. Control (7.5.3): documented information must be available where needed, protected, and controlled for distribution, access, storage, change, retention, and disposition. In short, the right version is available to the people who need it, old versions are not floating around, and records are protected.

Here is the relief most plants need to hear: ISO 9001:2015 does not require a quality manual, and it does not require the old list of six documented procedures. You keep documented information "to the extent necessary" to support your processes, plus the specific documents and records the standard explicitly names. That means you can right-size your documentation to your actual risk instead of building a binder to satisfy a checklist. The catch is control: however much you keep, the current version has to be the one in use, which is exactly where paper-based systems fail and a QMS software record or controlled digital SOPs earn their keep.

How do you control documented information cleanly?

Document control is where Clause 7 findings cluster, and the fix is a simple, enforced lifecycle. Run every controlled document through these steps.

  1. Identify and format it. Give each document a unique title, number, and revision, in a consistent format, so anyone can tell what it is and whether it is current.
  2. Review and approve before release. A named, authorized person approves the document for adequacy before it goes into use. No approval, no release.
  3. Distribute so only the current version is reachable. Put the live version where the work happens and remove old versions from circulation. This is the single most common failure point on paper.
  4. Control changes with a revision trail. When a document changes, update the revision, re-approve, and re-issue, keeping a record of what changed and why.
  5. Protect records and set retention. Records that provide evidence, calibration, training, inspection, are protected from loss or unauthorized change, and kept for a defined period, then disposed of in a controlled way.

Get this lifecycle right and most of Clause 7 takes care of itself, because the training records, calibration records, and process documents the other sub-clauses depend on are all controlled the same way.

The numbers behind the support clause

Clause 7 is where the 2015 revision quietly loosened the paperwork and tightened the thinking.

The through-line of Clause 7 is that support fails quietly: the caliper that drifted out of calibration, the training record that was never updated, the superseded work instruction still taped to the machine. Harmony's connected-worker and operations tools keep competence, work instructions, and quality checks current and visible at the station, so the support the QMS is supposed to have is actually there when the shift runs. See a plant that made that shift in our customer story. Clause 7 supports the work that Clause 8 operation controls, and it delivers on the resources that Clause 5 leadership committed to.