
Training & Competency Module
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
ExploreDefining what competence means for each role, verifying people have it, and maintaining it as practice and regulation evolve — beyond training-completion-as-proof-of-competence.
Training records prove someone attended. Competency proves they can actually do the work. The gap between training-completed and competent-to-perform is one of the most consistently-cited findings in GMP inspections, because it's where capability actually shows up — or doesn't.

Competency management defines what competence means for each role, verifies people have it before assigning them to perform the work, and maintains it over time through requalification, refresh training, and gap remediation. It treats competence as a managed state — defined, verified, maintained — rather than as an outcome of training attendance.
The discipline goes beyond training records. Training is the activity of conveying knowledge or skill; competency is the demonstrated ability to apply it correctly in the actual work. A trained operator has been through the training; a competent operator has been verified to perform the task correctly. The distinction matters because training completion isn't proof of competence. Inspectors increasingly want to see how competence was assessed, not just that training was attended.
Competency management is regulated explicitly under 21 CFR §211.25, 21 CFR §820.25, EU GMP Chapter 2 §§2.1-2.7, ISO 13485 §6.2, ISO 9001:2015 §7.2, ICH Q10, and WHO GMP. The expectation is universal: personnel performing GxP-relevant work must have demonstrated competence appropriate to the role, with ongoing maintenance.
An attendance log proves someone was in the room. An assessment record proves they can do the work. Inspectors look for both. Programs that confuse the two and present training completion as evidence of competence accumulate findings that are easy to make and hard to defend.
Competency is where the people side of the QMS gets tested. Every other QMS control — deviation handling, CAPA, change control, batch review, audit, supplier qualification — depends on the people performing it being competent. If the underlying competency discipline is weak, every dependent process inherits the weakness, and findings that look like specific process failures often trace back to competency gaps.
Inspectors keep finding cases where the apparent issue was a specific failure — a missed deviation, a poorly conducted investigation, a release decision that shouldn't have been made — and the underlying issue was competency. The person who missed the deviation hadn't been assessed for review competence. The investigator wasn't trained on the RCA method they were using. The QP signing release didn't have the experience the role required. The narrow finding became a systemic one.
Recent guidance has tightened the bar specifically. ICH Q10 emphasises ongoing competence. ICH Q9(R1) (effective January 2023) expects competency-based risk management. PIC/S PE 009-17 (June 2023) explicitly addresses personnel competence. Inspectors increasingly ask not just 'are people trained?' but 'how do you know they're competent?' and 'how do you maintain competence over time?'
Where competency is treated as paperwork — signed training records as proof — the dysfunction is visible in inspector interviews with operators. Do they actually know what they're supposed to do, or did they pass the test on paper? Programs that treat competency as the actual capability to do the work, verified, maintained, and gap-remediated, develop genuine quality capacity. The difference shows up the first time inspectors sit down with the people doing the work.
Inspector perspective: competency assessment is often one of the early questions. Pick a critical task — batch review, OOS investigation, deviation closure — and ask how the people performing it were assessed for competence. If the answer is 'they completed the training', the follow-up is 'how do you know they can actually do it?' The answer to that question tells inspectors whether competency is managed or assumed. Assumed competence tends to fail when sampled.
Competency is regulated across multiple frameworks:
The practices that survive inspection:
The controls that hold up at inspection:
Conflating training completion with competency is one of the most basic and most consistently-cited findings. The training record proves someone attended. The competency record proves they can do the work. Programs that maintain both, with explicit linkage, hold up. Programs that present training records as competency evidence accumulate findings under §211.25, §820.25, and Chapter 2.
Whether people are competent to do the work is your quality team's call, not a software answer. What Complere gives you is a way to run training and competency as connected disciplines — so the training record and the assessment record sit together, and so the people doing the work are the people you've actually verified.
You define what training each role needs; when someone joins a role, the right training is assigned automatically. When you revise a role profile, the right people get reassigned. Competency assessment lives alongside the training, not separate from it. You can run knowledge-based assessments — structured questions with scoring — or task-based assessments backed by observation evidence. The assessment record carries the assessor's identity, the method, the evidence, and the signed conclusion. Your auditor can read it back and see how you decided someone was competent, not just that they attended a class.
The link between your SOPs and your training is the part that closes the most common gap. When you revise an SOP, training is reassigned to the affected people, and competency requalification can be triggered on the same change. People can't be marked current on the new version until training — and, where applicable, reassessment — is complete. The "trained on the obsolete revision" problem your inspector watches for stops appearing.
Requalification runs on the interval you set per role. People due for requalification surface in the workflow; managers and your quality team see who's coming due and who's overdue. Trigger-based reassessment — after an SOP change, after a performance event, after an extended absence — can be kicked off against just the affected people.
When an event names someone who was performing the work, the event can reference that person's training and competency status at the time. Investigators looking at whether competency was a contributing factor have the answer in front of them rather than having to hunt for it across spreadsheets.
What stays with your team: the competency profiles themselves (what does competence actually mean for this role), the assessment methods you use (appropriate to the task), the assessor selection (independent where it needs to be), the depth of the assessment (real rigour rather than rubber-stamp), and the discipline of remediating gaps when they show up. Complere makes that discipline easier to operate and easier to evidence. Competent people are still your quality work.
Common questions about Competency Management sourced from regulatory references and inspection patterns.
It's the structured discipline of defining what competence means for each role, verifying people have it before assigning them to perform the work, and maintaining it over time through requalification, refresh training, and gap remediation. It goes beyond training records: training proves attendance, competency proves capability. Modern regulators expect both, with explicit linkage between role requirements, training delivered, competency assessed, and ongoing maintenance.
Training is the activity of conveying knowledge or skill. Competency is the demonstrated ability to apply that knowledge or skill correctly in the actual work. A trained operator has been through the training; a competent operator has been verified to perform the task correctly. The distinction matters because training completion isn't proof of competence. Inspectors increasingly want to see how competence was assessed, not just that training was attended.
Yes, explicitly. 21 CFR §211.25 requires personnel to have the education, training, and experience to perform their assigned functions; 21 CFR §820.25 requires the same for medical device personnel. EU GMP Chapter 2 §§2.1-2.7 establishes personnel competence as a foundational PQS element. ISO 13485 §6.2 requires the organisation to determine necessary competence, ensure persons are competent on the basis of education, training, skills, and experience, and evaluate effectiveness. ISO 9001:2015 §7.2 mirrors. ICH Q10 expects ongoing competence as part of the quality system.
Methods are matched to task criticality and type. Knowledge-based: written or oral examination. Practical: observed performance, supervised execution, demonstration. Behaviour-based: peer evaluation, supervisor assessment over time. Quantitative: performance metrics (error rates, output quality, audit findings). Audit-based: independent verification that the person performs to procedure. Higher-criticality tasks typically require multiple methods; lower-criticality may need only one.
Each role in the organisation has a defined competency requirement: what knowledge, skills, training, experience, and qualifications are needed to perform the role correctly. Operator roles, supervisor roles, QA reviewer roles, QP roles, lab analyst roles, equipment operator roles. The definition is the basis for hiring, training assignment, competency assessment, and requalification. Undefined competency requirements is one of the most basic findings — if the firm can't say what the role needs, it can't verify anyone has it.
Risk-based and role-dependent. Critical roles (QP, qualified person, lead investigator, batch reviewer) typically requalify annually or biennially. Operator roles after significant SOP changes, after extended absence, after performance issues, or on schedule (often annually for high-criticality tasks). Lab analyst competency requalifies when methods change or annually depending on assay risk. The principle: competency degrades over time without practice, and methods and regulations change, so periodic reassessment is needed.
Identification triggers remediation: retraining, supervised practice, role reassignment, or formal CAPA if the gap is systemic. Letting an identified gap persist while the person continues to perform the work is non-compliant — it's a conscious decision to allow incompetence. Programs that identify gaps through assessment but don't address them tend to produce findings that combine the original gap with the failure to remediate, which is worse than the original.
Reliance on training records alone with no competency assessment; undefined role competencies; no requalification or expired qualifications; identified gaps not remediated; competency assessment performed but not documented; assessment methods not appropriate to task criticality (paper-only assessment for hands-on tasks); supervisor performing both work and assessment; SOP changes not triggering competency reassessment; competency records not retrievable. §211.25 and Chapter 2 cited consistently.
Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.

Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
ExploreWalk through Complere's training and competency workflow — role-based assignment, competency assessment, requalification scheduling, and the training-to-SOP-effective-date discipline that ties everything together.