What is a competency framework? A guide for regulated manufacturing

What is a competency framework?Copied

A competency framework is the structured, organization-wide set of competencies that roles require, each defined with the levels at which it can be held and the evidence that demonstrates each level. It is the requirements side of competency management: the answer to “what does this role need to be able to do, and how would we know?”

It is a document, or a data structure. It is not a record of people. That distinction is where most of the confusion starts, and it is the reason the framework sits underneath everything else in competency management rather than alongside it.

Competency framework vs model vs matrix vs scaleCopied

Four terms, used interchangeably in most articles, that mean four different things in practice. Getting them straight is not pedantry. Each one is built on the one below it, so an error at the bottom propagates all the way up.

A competency framework is the whole structure: every competency the organization defines, grouped and leveled.

A competency model is the subset that applies to one role or role family. The management competency model is a model; the framework is what it is drawn from. Some organizations reverse these two terms, and it genuinely does not matter which convention you adopt, as long as the whole-structure layer and the per-role layer stay separate.

A competency matrix is people against the framework: who holds which competency, at which level, as of when. The competency matrix is the tracking artifact, and its columns come from the framework.

A proficiency scale is the level definitions themselves, the difference between “can perform under supervision” and “can train others”. The competency proficiency scale covers the common four- and five-level schemes.

The layering explains a failure that looks mysterious when it happens. A plant discovers its matrix is wrong, rebuilds the matrix, and finds it wrong again six months later. The matrix was never the problem. It was inheriting an error from a framework nobody had looked at since it was written.

What’s the difference between skills and competencies?Copied

A skill is a discrete ability to perform a task: operate the CNC lathe, read a P&ID, perform a lockout. A competency is the demonstrated capacity to apply skills, knowledge and judgment to a role’s requirements at a defined standard. Skills are the units. Competency is the assessed combination.

What are competences covers the definitional ground in more depth, and competency vs proficiency covers the level question. For a frontline framework the working rule is the one in the table. Define skills at the task level and competencies at the role level. Never let one stand in for the other.

What makes a competency framework hold up in regulated manufacturing?Copied

Five design rules, each of which exists because generic HR frameworks fail audits in the same five predictable ways. None of them is about writing better competency descriptions.

It is derived from the process, not the org chart. Start from the procedures, equipment and quality-critical steps, and ask what competence each one requires. ISO 9001 clause 7.2 asks three things of the organization. Determine the competence needed for persons doing work that affects the quality management system. Ensure they are competent on the basis of education, training or experience. Retain documented information as evidence of it. IATF 16949 adds clause 7.2.2, which requires on-the-job training for anyone with new or modified responsibilities affecting quality, explicitly including contract and agency personnel. A framework that lists “teamwork” but omits “visual inspection to acceptance criteria SP-114” satisfies neither.

The FDA position changed recently and is worth stating precisely, because the old citation is still circulating. As of February 2026, 21 CFR Part 820 operates as the Quality Management System Regulation and incorporates ISO 13485 by reference. Device-maker competence requirements now run through ISO 13485 clause 6.2 rather than the retired section 820.25. Pharmaceutical manufacturers sit under a different part entirely. 21 CFR 211.25 requires each person to have the education, training and experience to perform their assigned functions. The training has to cover the particular operations they perform.

Levels map to authorization. Each level in the scale should correspond to something operational: trained, assessed, authorized to perform unsupervised, authorized to train others. If a level does not change what the person is allowed to do, it is a development label rather than a competence level, and it belongs in a different framework.

Every competency has an evidence type. Observation against a checklist, written assessment, certificate, supervised runs. The framework states which one counts for each competency. This is what turns a matrix entry from an assertion into a record. How that evidence is gathered is covered in competency assessment.

Every competency has a currency rule. Competence lapses. The framework states how long each one stays valid and what re-verification looks like: a refresher assessment every 24 months, a supervised run after six months away from the task. Frameworks that omit currency produce matrices that are technically complete and practically wrong.

The framework is versioned. When a procedure changes, the competency changes, and everyone assessed against the old version needs re-assessment against the new one. A framework without version control cannot tell an auditor which definition a person was assessed against on a given date. This is the rule most spreadsheets cannot follow, and the one that most often produces a finding.

How to build a competency framework in six stepsCopied

Six steps, in this order. The order matters more than the content of any single step, because roles defined before processes produce a framework that describes the org chart rather than the work.

• Inventory the processes, equipment and quality-critical steps per site. Not roles. Roles come later.
• Write the competencies each one requires, with a name, a one-line definition and the evidence type. Keep the language operational: verbs and objects, not adjectives.
• Attach a level scale, and for each competency state what each level authorizes the holder to do.
• Assign a currency rule to every competency. Default to annual review where no regulation specifies otherwise.
• Group competencies into role models. A role is a bundle of competencies at required levels, and a person in that role is assessed against the bundle.
• Set governance. Who owns the framework, how changes are proposed, how versions are recorded, and what triggers re-assessment.

Two mistakes to avoid. Copying a published framework wholesale, because the competencies that matter are the ones specific to your own procedures, and a generic list buries them under fifty that do not apply. And starting from a spreadsheet template, because the structure above needs relationships between competency, evidence, currency and version that a flat sheet cannot hold.

Free competency matrix templates are useful for the matrix layer once the framework exists. They are a poor place to design the framework itself.

What a competency framework demands of your softwareCopied

A framework designed as above cannot live in a spreadsheet for long, and the reason is structural rather than a matter of convenience.

The software has to hold competencies with their evidence types and currency rules attached. It has to derive role models from them and compute each person’s status against the current definition. And it has to hold the assessment record with assessor, date and evidence. It has to do that across sites from one shared library. And it has to produce the record an auditor asks for: this person, this competency, this version, this evidence, this date, without somebody assembling it overnight.

Which tools do that is covered in competency management software. How it differs from an LMS, which stores completions rather than competencies, is in competency management system vs LMS.

Where AG5 fits in competency managementCopied

AG5 holds the competency framework as structured data rather than as a document. Competencies carry their evidence type and expiry rules, every assessment records who signed it, when, and on what evidence, and role models are drawn per site from one shared library. A change to the framework re-scores everyone it touches, so a definition change surfaces immediately instead of waiting for a quarterly review.

Manufacturers in pharma, medical devices, food, automotive and aerospace use it to keep the framework and the evidence in the same place. “Was this person competent on that date” then becomes a lookup rather than an investigation. The competency management system page shows how the framework is set up.

If the current framework is a Word document and the current matrix is an Excel file that does not know the framework changed, that is the gap it closes.

FAQs Copied

Author Copied

Rick van Echtelt

Rick van Echtelt is the Co-Founder and CEO of AG5, where he leverages over two decades of experience in entrepreneurship and developing skills management software.

Read author profile