Documenting Competency in GMP
In GMP systems, competency is not assumed because training occurred.
It is demonstrated through evidence.
Regulators evaluate competency by examining how organizations document that personnel can perform assigned activities correctly, consistently, and in alignment with approved procedures.
This article explains what regulators mean by competency, how competency is expected to be documented, and why gaps in competency documentation frequently surface during inspections - even when training records appear complete.
What Competency Means in GMP
Regulatory expectations around competency extend beyond training completion. Competency refers to an individual’s ability to perform assigned tasks as required, not merely their exposure to procedures.
In practice, inspectors distinguish between:
Training: confirmation that instruction occurred
Competency: evidence that instruction translates into correct execution
Competency is therefore assessed indirectly - through records, outcomes, and consistency - not through declarations or checkboxes.
Understanding this distinction is essential, because documentation systems that treat training completion as proof of competency often fail under inspection scrutiny.
Training Records vs Competency Evidence
Training records are necessary, but they are not sufficient to demonstrate competency.
Inspectors routinely ask:
How does training translate into correct performance?
What evidence shows that individuals can apply SOPs?
How is competency maintained over time?
When documentation consists solely of “read-and-sign” records, inspectors question whether understanding and application were ever verified. This gap becomes especially visible during interviews, when different individuals describe the same process differently.
How SOPs should be used as training instruments - rather than acknowledgement artifacts - is discussed in How to Train Staff on SOPs.
Types of Documentation Used to Demonstrate Competency
Organizations rely on multiple forms of documentation to demonstrate competency. Regulators assess these collectively, not in isolation.
Common forms include:
SOP training records, linked to current, approved versions
on-the-job training documentation, showing supervised practice
qualification or authorization records, where applicable
periodic reassessment evidence, demonstrating sustained competency
deviation or investigation records, where competency was evaluated
What matters is not the format, but whether documentation provides a coherent narrative showing that personnel are capable of performing their responsibilities.
Poor alignment between these records signals weak control, even if each record appears compliant on its own.
How Inspectors Review Competency Documentation
Inspectors rarely review competency documentation in bulk. Instead, they select individuals and follow evidence trails.
A typical approach includes:
identifying personnel performing GMP-critical activities
reviewing SOPs applicable to those activities
reviewing training and competency records for those individuals
interviewing personnel to assess understanding and execution
Inconsistencies between documentation and explanations prompt deeper review. When competency evidence cannot be traced clearly to roles, procedures, and outcomes, inspectors question whether competency is actively managed or passively assumed.
Common Documentation Gaps Related to Competency
Certain competency-related documentation gaps recur across inspections.
These include:
training records that reference outdated SOP versions
competency evidence that is not role-specific
over-reliance on acknowledgement without demonstration
missing evidence of reassessment following changes or deviations
authorization records that are no longer current
Many of these gaps originate upstream, in SOP clarity and training design. Structural weaknesses that contribute to these patterns are explored in Common SOP Writing Mistakes.
Competency Documentation and Ongoing Compliance
Competency is not static. Documentation must reflect how competency is maintained as systems evolve.
Inspectors expect organizations to consider competency documentation when:
SOPs are revised
new responsibilities are assigned
deviations or investigations identify human error
process or equipment changes affect execution
Failure to update or reassess competency documentation following these events suggests that competency management is reactive rather than controlled.
How Competency Documentation Fits Within Training Systems
Competency documentation sits at the intersection of training, SOP quality, and documentation control.
Clear SOPs support effective training. Effective training supports consistent execution. Consistent execution produces reliable records. When competency documentation reflects this alignment, inspectors see a controlled system rather than disconnected artifacts.
The broader relationship between documentation design and credibility is outlined in GMP Documentation & Data Integrity.
Regulatory Perspective
Regulators do not expect organizations to prove competency through a single record or assessment.
They expect consistent, traceable evidence that personnel can perform assigned activities correctly and continue to do so over time.
Competency is demonstrated through consistent outcomes, not assumed through training completion.
Inspectors look for evidence that personnel can perform assigned activities correctly and continue to do so as systems change.
When competency documentation tells a clear, traceable story, it strengthens inspection confidence.
When it does not, training and qualification records are examined more critically.
Explore more on Documentation & Data Integrity
Browse VerethiQ resources on documentation control, data integrity expectations, ALCOA+ principles, record review, SOP governance, and inspection readiness.
