Blog · ISO 9001 Made Simple

What Does "Competence" Actually Mean When Everyone Wears Multiple Hats?

Published 6 September 2026 · 4 min read

Ask a five-person business what "competence" means under ISO 9001, and the word alone can sound like it belongs to a company with an HR department and a training budget. It doesn't. Clause 7.2 is one of the most misunderstood requirements in the whole standard, not because it's complicated, but because the word "competence" sounds like it's asking for something a small business doesn't have. In reality, it's asking for something every small business already half does, it just needs to be written down properly.

What Clause 7.2 actually requires

Stripped of the formal language, Clause 7.2 asks a business to do four things: work out what knowledge, skills, and experience a role actually needs, check whether the person in that role currently has it, close the gap if they don't, and keep some kind of record showing all of that happened (source: Core Business Solutions' explainer on Clause 7.2). That's the whole requirement. Nothing in it demands a formal training department, a learning management system, or annual performance reviews.

Why this feels harder for a business where everyone wears multiple hats

In a five or ten person business, almost nobody has one job. The person who quotes jobs also manages the schedule and sometimes does the work themselves. The office manager also handles invoicing, customer complaints, and health and safety. That's not a barrier to Clause 7.2, but it does mean the clause has to be applied per function, not per person.

According to the same guidance, competence needs to be defined and evidenced separately for each responsibility a person holds, not once for the person as a whole. A team member who quotes jobs, manages a small crew, and handles safety inductions genuinely holds three sets of competence requirements, even though it's one person wearing three hats. Treating it as one blurry "they're good at their job" assessment is the most common way this clause gets done badly.

What actually counts as evidence of competence

This is where most small businesses relax once they see the real list. "Competence" doesn't mean a formal qualification. It can be demonstrated through any credible combination of the following, and most small businesses already have some of this sitting around without realising it counts:

• Formal qualifications or licences, where the role genuinely requires one (a trade licence, a first aid certificate, a forklift ticket).
• On-the-job training, documented as simply as a signed note saying who trained whom, on what, and when.
• Years of hands-on experience in the role, particularly for skills that were never formally taught but were clearly learned by doing the work.
• Evidence the training actually worked, a supervisor sign-off, a short competency check, or simply the absence of repeated errors in that area since the training happened.

A simple way to actually do this without overbuilding it

The practical approach for a small business is to build one short table per role or function, not per person. List what the role needs to know or be able to do, note how the current person meets that (qualification, experience, or training), and note the date. When someone changes roles, or a new person joins, the same table tells you exactly what to check and what to close a gap on. That's the entire system. It doesn't need software, a policy manual, or a training calendar, it needs an honest half hour spent thinking through each function properly.

The bottom line

Clause 7.2 isn't asking a five-person business to behave like a corporation with an HR department. It's asking for something most small businesses can build in an afternoon: a clear, honest record of what each function actually needs, and evidence that the person doing it can actually do it, however that competence was built. Once it's written down properly, it stops being a compliance worry and becomes a genuinely useful record for onboarding, for covering someone who's away, and for proving to an auditor, or a bigger client, that the business knows exactly who can do what.

Source: Core Business Solutions — Clause 7.2 ISO 9001:2015 Explained