Training Records & Competency Tracking: A QC Lab Guide

Training records and competency tracking are the most commonly cited documentation gaps during ISO 17025, CLIA, and FDA laboratory inspections — yet most small and mid-size labs still manage them in spreadsheets or shared drives. This guide gives lab directors and QA managers a practical framework for building a system that holds up under scrutiny.

Why Competency Tracking Fails in Most Labs

The root problem is not effort — it is architecture. Labs typically collect training records as static documents: signed PDFs, email confirmations, or hand-dated sign-in sheets. These satisfy the letter of a requirement on the day they are filed and then quietly become liabilities as time passes.

Three failure modes are common:

• No expiry logic. A competency record from 18 months ago is treated as current indefinitely. When an auditor asks whether the analyst who ran last Tuesday's proficiency panel was currently qualified, the answer requires manual cross-referencing.
• Coverage gaps at the method level. Labs train analysts on instruments but not on specific test methods or SOP revisions. An analyst qualified on a platform in 2022 may never have been formally assessed after a method update in 2024.
• No link to results. Training records live in HR folders. Test results live in the LIMS or instrument software. Auditors increasingly expect a traceable line between the two — who ran this sample, were they qualified to do so, and where is the proof?

Fixing this requires treating competency as a data problem, not a paperwork problem.

What a Defensible Competency Record Actually Includes

A training record is only as strong as what it documents. At minimum, each record should capture:

• Analyst identifier (name, employee ID, or LIMS user ID)
• Specific method or SOP covered, including document version number
• Assessment type — observation, proficiency sample, written exam, or supervised run
• Assessor identity — who evaluated competency, not just who administered training
• Date of assessment and expiry date — most accreditation bodies expect re-assessment at defined intervals, commonly annually
• Outcome — pass, conditional pass, or fail with remediation notes
• Supervisor sign-off with date

Notice what is absent from most spreadsheet-based systems: version-controlled SOP linkage and automatic expiry flagging. Without those two elements, a training record is a snapshot with no mechanism to stay current.

Setting Reassessment Intervals That Match Your Risk Profile

Not every method warrants annual reassessment. A practical tiering approach:

Tier 1 — High-risk methods (annual reassessment minimum): Methods tied to regulated decisions, release testing, or reportable values. Examples include potency testing in a cannabis QC lab, sterility testing in a contract pharmaceutical lab, or any method where an out-of-specification result triggers a recall or hold.

Tier 2 — Moderate-risk methods (reassessment at SOP revision or every 24 months): Standard operating procedures for sample prep, instrument maintenance, or internal QC checks where errors are catchable before results are reported.

Tier 3 — Administrative or safety procedures (reassessment at policy update): Lab safety orientation, waste disposal protocols, chain-of-custody procedures.

Document your tiering rationale in your quality manual. Auditors under ISO 17025 clause 6.2 expect to see that competency requirements are defined, not just that training happened.

Building the Link Between Training Records and Sample Results

This is the step most labs skip and the one that creates the most audit exposure.

Consider a concrete example: Greenfield Analytical, a mid-size environmental testing lab, ran a batch of drinking water samples for heavy metals in March. During a state regulatory audit in August, the auditor pulled three sample reports and asked to see competency records for the analyst listed on each. The records existed — but they were filed by analyst name, not by method. Locating them took 40 minutes. The auditor noted the delay as a finding.

The fix is not faster searching. It is linking records at data entry. When an analyst logs into the LIMS and is assigned a test batch, the system should already know — and record — whether that analyst holds a current competency qualification for that method. If the qualification is expired, the assignment should trigger a warning before the work starts, not a scramble after the audit begins.

LIMS platforms like Aliquora can enforce this linkage natively by tying analyst qualifications to method assignments and surfacing gaps in real time, rather than leaving QA managers to maintain parallel spreadsheets.

Structuring Your Competency Assessment Program

A competency assessment is not the same as a training session. Training is instruction. Assessment is verification. Your program should include both, in sequence.

Initial Qualification

Before an analyst runs samples independently:

1. Assign and document training on the current SOP version.
2. Conduct a supervised practice run with a qualified analyst or supervisor observing.
3. Run a blind proficiency sample or known-value control. Document the result against acceptance criteria.
4. Have the assessor sign off with specific criteria noted, not just a generic approval.

Ongoing Competency

At each reassessment interval:

• Repeat the proficiency sample or a direct observation of the analyst performing the method.
• Review any OOS results, instrument flags, or repeat analyses the analyst generated since the last assessment. Patterns matter.
• Update the competency record with the new expiry date and assessor sign-off.
• If the SOP changed since the last assessment, re-initiate the initial qualification sequence for the affected steps.

Handling Failures and Remediation

A failed competency assessment is a quality event, not a personnel event — at least in how it should be documented. Record the failure against the method, assign remediation (additional supervised runs, retraining on specific steps), set a re-assessment date, and document the outcome. Avoid vague notes like "additional training provided." Specify what was covered and who conducted it.

Making Training Records Audit-Ready Without Extra Work

The practical goal is a system where the records are current by default, not by effort. Four structural choices that support this:

1. Use status fields, not just completion dates. Every competency record should display a current status — Active, Expiring Soon, Expired — rather than requiring a manager to calculate from a date field.
2. Automate expiry notifications. The QA manager should receive a 30- and 60-day warning before any qualification expires, not discover the gap during an audit or when assigning a batch.
3. Version-lock SOP references. When an SOP is revised, the system should flag which analysts need re-assessment for that specific method. This is not possible if training records reference a method name rather than a document version.
4. Keep records where the work lives. Training documentation stored in a separate HR system or file share will always lag behind operational reality. When the record is part of the same platform that tracks samples, assignments, and results, the audit trail is coherent without manual reconciliation.

---

Frequently Asked Questions

What is the difference between training records and competency records?

Training records document that instruction occurred — an analyst attended a session, read an SOP, or completed an online module. Competency records document that the analyst can perform the task correctly, typically verified through observation, proficiency samples, or examination. Accreditation bodies require both; relying only on training records is a common audit finding.

How long should laboratory training records be retained?

Retention requirements vary by accreditation standard and regulation. ISO 17025 requires records to be retained for at least five years. FDA-regulated labs often operate under 21 CFR requirements that mandate longer retention. A defensible baseline for most labs is retaining competency records for the duration of employment plus five years, but verify against your specific accreditation body and any applicable regulatory requirements.

How often does analyst competency need to be reassessed under ISO 17025?

ISO 17025 clause 6.2.5 requires laboratories to monitor competency but does not mandate a specific reassessment interval. In practice, most accredited labs use annual reassessment for high-risk or reportable methods and document their rationale for any longer interval. Accreditation body guidance documents often provide additional specificity — review your AB's policy directly.

What happens if an analyst runs samples while their competency qualification has expired?

This is a non-conformance event. Depending on your accreditation body and the nature of the work, it may require customer notification, result review, or a formal CAPA. The exposure is significantly lower if you catch the lapse before the work is run. Automated expiry flagging within a LIMS is the most reliable way to prevent this scenario.

Can training records be stored electronically, and do they need a wet signature?

Electronic records are accepted by ISO 17025, CLIA, and most FDA programs provided the system meets applicable electronic records requirements — in FDA contexts, that typically means 21 CFR Part 11 compliance for audit trail integrity and access controls. Most modern LIMS platforms satisfy these requirements. Wet signatures are generally not required if the electronic system captures a verifiable, timestamped approval with user authentication.