
Training & Competency Module
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
ExploreThe controlled process for qualifying personnel to perform their assigned GxP tasks.
Training records sit on the audit trail right next to product records. If the person who released the batch wasn't trained on the current procedure, that's not a training finding — it's a release finding.

Training management is the controlled process for qualifying personnel to perform their assigned GxP tasks. It covers identifying who needs what training based on role and task, delivering the training (read-and-understand, classroom, on-the-job, or assessment-based), confirming competency, retaining records for the predicate-rule period, and re-training when something changes.
In a regulated environment, training isn't an HR function. It's a quality function. The training record is the documented evidence that the specific person who performed the specific task was qualified to do so before they did it. That link — role → document → training → person → activity — is what inspectors trace.
The principal regulations all carry the same expectation in different words: personnel performing GxP tasks must have the education, training, and experience to do them, and the records must exist to prove it.
Owning training in HR creates a structural problem: HR optimizes for completion, QA needs evidence of competency. Strong programs put training assignment, qualification, and effectiveness in QA's accountability, even if delivery sits elsewhere.
When an inspector questions a batch release, a deviation investigation, or a method run, one of the first questions is: was the person doing this trained on the current procedure? The training record either supports the activity or contradicts it.
A training record that names the person, the document, the version, the date trained, and the competency outcome supports the activity. A record that's missing one of these pieces — typically the document version — creates a gap the inspector will pull on. Documents revised six months ago with no new training records is one of the most common findings, because the people doing the work are using a procedure they were never trained on.
Inspector note: When I look at a training file, I want to see three things matched up: the role this person holds, the documents that role requires training on, and the dates those trainings happened relative to when the documents took effect. If a document was revised in March and the person performed the activity in April with no training record for the new version, that's a finding I can write before I leave the room.
Training expectations appear in every major GxP framework and are reinforced by 21 CFR Part 11 for electronic training records:
Training in a mature program moves through a recognizable sequence:
Programs that hold up at inspection share consistent technical and procedural controls:
An operator's training file shows training on SOP rev 5. The current effective version is rev 7. The operator performed the activity last week. That's the most common training-related finding pattern. The fix is in the system, not in retraining one person: automated triggers from document revision to training assignment, with effective-date gating for high-risk changes.
Training in Complere is built around the linkage your inspectors trace — role, document, training, person, activity. The system doesn't treat training as a side calendar that HR keeps; it sits inside the same quality workflow your team uses for documents, change, and CAPA, so the evidence stands up the same way every other regulated record does.
When someone joins a role, takes on a new responsibility, or moves between departments, the training that role requires shows up on their list without anyone hand-curating it. Your team defines what each role needs once; the matrix takes care of the rest. When a controlled procedure changes, Complere triggers training tasks for everyone the change affects, and for high-risk changes your team can hold the new effective date until those trainings are complete. The "trained on the old version, working on the new one" pattern stops being a thing you have to chase.
Delivery handles the mix that real operations need. Read-and-understand acknowledgements are captured with an electronic signature that names the person, the moment, and the meaning of the signature — the same signature controls Complere applies to a document approval or a CAPA closure. For tasks that need real competency, your team can attach assessments with question banks, capture attempt history, and require a passing score before training is marked complete. For classroom and on-the-job training, offline-user support records signed attendance and attributes the training to the right person so it shows up in their file when an inspector pulls it.
The training record for any person names the document, the version they were trained on, the date, the type of training, the assessor when one applies, and the outcome. Coordinator responsibilities for delivery and follow-up sit on defined groups rather than named individuals, so the program survives staff turnover. Every action — assignment, completion, re-assignment, lapse, signature — is on the audit trail with identity and timestamp. Dashboards by role, department, and document show where training is overdue, and escalations route through the same notification system the rest of your quality work uses.
The Vendor Validation Package for the LMS module — requirements, IQ/OQ/PQ evidence, and a traceability matrix — ships with Complere, so your team isn't starting from scratch when validating the training records system for Part 11 use.
What stays with your team: defining the role-to-training matrix, deciding which procedures warrant assessment versus read-and-understand, judging when a competency check has gone deep enough for the task, and reviewing the program's effectiveness through internal audits and management review. Complere runs the workflow, captures the evidence, and produces the inspection-ready records; the training program around it stays yours.
Common questions about Training Management sourced from regulatory references and inspection patterns.
GxP training is the documented evidence that a specific person was qualified to perform a specific task before they performed it. The record names the person, the controlled document or procedure they were trained on, the version of that document, the date of training, the type (read-and-understand, classroom, on-the-job, assessment), and the outcome (passed, failed, observed). The link from role to document to training to person to activity is what inspectors trace, and the training record either supports the activity or contradicts it.
It depends on the task and the risk. Read-and-understand is acceptable for low-risk awareness or procedural updates that don't involve a new skill — for example, training on a revised approval flow in an SOP the person already operates under. For technical tasks (aseptic processing, instrument operation, deviation investigation, validation testing), read-and-understand alone is not sufficient: competency needs to be demonstrated through assessment, observation, or qualified-observer sign-off. The choice between read-and-understand and competency-based training is itself a documented decision.
The principal triggers are: a controlled document is revised; the person moves to a new role; a defined lapse period passes without performing the task (typical for high-risk activities like aseptic processing); a regulatory or guidance change reframes the task; a CAPA action identifies a training gap; an audit finding implicates training. The mature program automates the first three triggers from the system rather than relying on a coordinator to spot them.
Personnel performing GxP tasks before their training was complete; SOPs revised without corresponding training-on-change records; training records that don't pin the document version (so the inspector can't tell which version the person was trained on); competency assessment missing for technical tasks; classroom or external training without signed attendance evidence; and the gap between trained-on-rev-5 and working-on-rev-7 — the most-cited single pattern.
Anyone performing GxP tasks needs documented qualification, regardless of employment status. Contractors, consultants, and temporary staff performing the same tasks as employees need equivalent training records. 21 CFR §211.34 makes this explicit for drug consultants; EU GMP Chapter 7 carries the same expectation for outsourced activities. Visitors are different — they typically don't perform GxP tasks and instead require induction on facility access, hygiene, and area-specific behaviour, with the level matched to where they're going and what they'll observe.
Per the predicate rule that governs the activity the training supports, not by a separate 'training records' rule. For drug manufacturing under 21 CFR §211.180(a), at least one year past the batch expiration date of any batch the training supported. For device records under 21 CFR §820.180, the longer of the expected device lifetime or two years from date of release for distribution. The training record stays linked to the role and the activity it qualified, so the retention is driven by the underlying work.
Training is the activity — delivering the material, the procedure, the standard, the assessment. Competency is the verified ability to perform the task to standard. A person can complete training without being competent; a competent person can demonstrate the ability without recently completing training. Most regulators expect both for non-trivial tasks: training records as evidence the qualification was delivered, and competency records (assessment scores, observed performance, qualified-observer sign-off) as evidence the qualification stuck.
Yes. Electronic training records under a predicate rule fall within Part 11 scope. §11.10 controls (validation, audit trail, access control, secure records) apply to the training system; §11.50 and §11.70 apply to the electronic signature that captures the training completion — the signer's identity, the moment, and the meaning (training completion / competency confirmation) need to be captured together and bound to the record. A read-and-understand acknowledgement is an electronic signature under Part 11 if the underlying activity is predicate-rule-required.
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 how Complere operationalizes this concept inside a validation-ready quality system.