Menu
ISO 9001 Clause 7.2 Competence: What Auditors Expect From Training Records

ISO 9001 Clause 7.2 Competence: What Auditors Expect From Training Records

Plain-English guide to ISO 9001 competence requirements: Clause 7.2's four steps, proving training effectiveness, and audit-ready skills matrices.
ISO 9001 Clause 7.2 Competence: What Auditors Expect From Training Records

ISO 9001 Clause 7.2 requires organizations to determine the competence people need, ensure they have it through education, training, or experience, act to close any gaps and evaluate whether those actions worked, and retain documented evidence of competence. It is one of the shortest clauses in the standard yet a steady source of audit findings, because most factories can prove who attended training but not whether it worked. This guide translates the ISO 9001 competence requirements into plain English and shows what certification auditors expect to find in your records.

The four requirements of Clause 7.2 in plain English

Clause 7.2 of ISO 9001:2015 packs four obligations into a few lines, referenced as 7.2 a) through d):

  1. Determine: define the competence needed for each role and task that affects quality performance: what must a setter, an inspector, or a maintenance technician actually be able to do?
  2. Ensure: confirm those people are competent on the basis of appropriate education, training, or experience. A setter with fifteen years of documented experience and no certificate can be fully compliant.
  3. Act: where gaps exist, take action (training, mentoring, supervision, reassignment, hiring) and then evaluate the effectiveness of that action. The evaluation is not optional; it is written into 7.2 c).
  4. Retain evidence: keep documented information that demonstrates competence, not merely participation.

The scope, "persons doing work under the organization's control," also covers contractors, agency workers, and temporary staff.

Competence is not the same as training

ISO 9000:2015 defines competence as the ability to apply knowledge and skills to achieve intended results. Training is one input, not proof. An operator who completed a course but still cannot hold tolerances is trained yet not competent; a technician who never attended a course but consistently completes work orders correctly may be fully competent through experience. Auditors look for a chain of logic, not a folder of certificates: the ability each role requires, how it was confirmed, what you did about gaps, and the evidence behind each step.

The classic nonconformity: attendance without effectiveness

The most common Clause 7.2 finding follows the same script. The auditor picks an operator, asks what competence the task requires, and requests the records. The company produces a signed attendance sheet. The auditor asks one question: how did you evaluate whether that training worked? Silence, and a minor nonconformity follows, typically worded as "the organization could not demonstrate that the effectiveness of actions taken to acquire competence had been evaluated (7.2 c)."

Acceptable effectiveness evidence includes:

  • An observed task demonstration checked against the control plan or work instruction, signed and dated by an assessor.
  • A written or practical assessment with a defined pass threshold.
  • Supervisor sign-off after a set number of supervised runs.
  • Movement in process data after training, for example scrap rate, first-pass yield, or SPC performance.

Pick one or two methods, define them in your procedure, and apply them within a set deadline, typically 30 to 90 days after training.

Worked example: closing a competence gap on a CNC cell

A machining cell runs 12 operators across three shifts. The skills matrix requires level 3 (works independently) for tool changeovers; the annual review finds 5 operators at level 2 (works under supervision). The data shows why it matters: level 2 shifts average 4.6 percent scrap and 58 minute changeovers, against 1.9 percent and 41 minutes for level 3 crews.

The quality manager records the gap and acts: a two-day setter course plus ten supervised changeovers per operator. Sixty days later comes the effectiveness evaluation required by 7.2 c): each operator performs an observed changeover against the control plan checklist. Four of the five pass and move to level 3; scrap on their shifts falls to 2.1 percent and average changeover time to 43 minutes. The fifth stays at level 2, gets 30 more days of mentoring, and is booked for reassessment.

The retained evidence: the updated skills matrix, five signed and dated observation checklists, and the before and after production data. That is a fully compliant Clause 7.2 record set.

How a skills matrix satisfies documented information

Clause 7.2 d) does not prescribe a format, but a skills matrix is the most audit-friendly way to retain evidence because it shows determination, assurance, and gaps on one page. A robust matrix contains:

  • Rows for people and columns for tasks, each tied to a role requirement.
  • Defined proficiency levels, for example 0 (untrained) to 4 (can train others), with written criteria so scoring is not subjective.
  • Required level next to assessed level, making gaps visible at a glance.
  • Assessor name, assessment date, and next review date for every entry.
  • Version control, since the matrix is documented information under Clause 7.5.

Keep the matrix living. Update it when processes change, when autonomous maintenance transfers tasks to operators, and after every effectiveness evaluation. A matrix last touched two years ago is itself an audit finding.

Where Fabrico fits

The hardest part of Clause 7.2 is the effectiveness evaluation, and that is fundamentally a data problem: you need objective before and after numbers per line, shift, and task. Fabrico provides that real-time data foundation. Its production monitoring tracks OEE, scrap, and downtime in real time, including on legacy machines with no PLC through computer vision, so you can show an auditor how performance moved after training. On the maintenance side, the CMMS keeps a timestamped history of work orders and preventive tasks per technician, which doubles as evidence of experience under 7.2 b). Because Fabrico is EU-built with EU data residency, personnel-linked records stay where your GDPR obligations expect them.

Frequently Asked Questions

Does ISO 9001 require training records for every employee?

No. Clause 7.2 requires evidence of competence for people whose work affects quality performance, and that evidence does not have to be a training record. Diplomas, documented experience, observed assessments, and supervisor sign-offs all qualify.

Is a skills matrix mandatory under ISO 9001?

No. The standard requires retained documented information as evidence of competence but prescribes no format. A skills matrix is simply the most auditable common option because it shows required competence, actual competence, and gaps in one document.

How do you prove training effectiveness to an auditor?

Show a defined evaluation method applied within a defined timeframe. The strongest packages combine a competence check (an observed demonstration or a test with a pass threshold, an assessor, and a date) with before and after performance data such as scrap or first-pass yield. Attendance sheets alone will not satisfy 7.2 c).

Ready to put objective production data behind every competence record? Book a Fabrico demo and see how real-time OEE, scrap, and maintenance history turn training effectiveness from a claim into evidence.

Latest from our blog

Încă te întrebi?
Verificați singuri!
Încă te întrebi?

Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!

By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy și Cookies Declaration