Standard 3 — Personnel & Competence
Criteria in this standard
3.2 — Competence Reassessed on a Schedule
3.3 — Orientation Before First Independent Shift
3.4 — Training Records Tied to Specific SOPs
3.5 — Adequate Staffing for Safe Operation
Documented Qualification Before Independent Work
Non-Negotiable
In plain terms: Nobody works alone on a specific test until someone has actually checked they can do that specific test correctly — a degree alone doesn’t count as that check.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A medical laboratory science degree demonstrates general competence, not proficiency in a specific instrument, a specific SOP, or a specific laboratory’s particular workflow. A newly hired technologist with years of prior experience elsewhere can still make procedure-specific errors on their first unsupervised shift in a new environment. Documented, procedure-specific competence assessment is what actually confirms readiness, not the credential that got someone hired.
What good looks like
- A documented competence record exists for every procedure performed unsupervised.
- Assessment is performed by someone other than the staff member.
- The actual competence-confirmation date is recorded, separate from the hire date.
Common failure modes
- A degree or certificate is treated as sufficient on its own.
- Staff self-certify their own readiness.
- Hire date is recorded as if it were the competence confirmation date.
Worked example
If you are starting from zero — do this first
- Check whether current staff have documented, procedure-specific competence records.
- Build a simple checklist per major procedure if none exists.
- Require sign-off by someone other than the staff member being assessed.
Self-assessment questions
Evidence: Competence assessment record
Evidence: Assessor signature on record
Evidence: Dated competence record
Common reasons for a PARTIAL answer
- Experienced hires skip formal assessment based on assumed competence.
- Records exist but lack a distinct competence-confirmation date.
Implementation plan
| When | What |
|---|---|
| Week 1 | Audit current staff competence records for gaps. |
| Week 2 | Build procedure-specific competence checklists. |
| Week 3 | Complete assessment for any staff member currently missing one. |
| Ongoing | Require competence sign-off before any new hire works unsupervised, regardless of prior experience. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Competence record check | Selects a staff member at random and verifies procedure-specific, independently signed competence records. |
Evidence base
Competence Reassessed on a Schedule
Non-Negotiable
In plain terms: Competence gets checked again regularly, not just once when someone started — and especially after a long break or whenever a procedure changes.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Skills genuinely can lapse — a procedure performed rarely, a long parental or medical leave, months away from a specific instrument. Treating the initial hiring-stage competence confirmation as permanent ignores this reality entirely. Reassessment triggered specifically by absence, procedural change, or a performance concern catches exactly the situations where competence is most likely to have genuinely changed.
What good looks like
- A fixed reassessment interval is actually met, verifiable by dates.
- Return from extended leave triggers reconfirmation before independent work resumes.
- A performance concern triggers targeted reassessment promptly, not at the next routine cycle.
Common failure modes
- A stated annual cycle that hasn’t actually happened in two years.
- Staff resume work immediately after extended leave with no reconfirmation.
- A known performance concern waits months for the next scheduled review.
Worked example
If you are starting from zero — do this first
- Set a specific, fixed reassessment interval — not “as needed.”
- Define what counts as an “extended absence” triggering reconfirmation.
- Build a process to flag performance concerns for targeted, prompt reassessment.
Self-assessment questions
Evidence: Reassessment schedule and records
Evidence: Return-to-work reconfirmation record
Evidence: Targeted reassessment record
Common reasons for a PARTIAL answer
- The stated interval exists on paper but is routinely missed in practice.
- No specific trigger exists for extended-absence reconfirmation.
Implementation plan
| When | What |
|---|---|
| Week 1 | Define a specific reassessment interval and extended-absence threshold. |
| Week 2 | Check current staff against the new schedule for overdue reassessment. |
| Week 3 | Complete any overdue reassessments. |
| Ongoing | Trigger reconfirmation automatically after any qualifying absence. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Reassessment record review | Checks reassessment dates against the defined interval and verifies any recent return-from-leave reconfirmation. |
Evidence base
Orientation Before First Independent Shift
Core
In plain terms: Before anyone works alone, they’ve genuinely been shown how this specific lab works — not just handed paperwork to sign.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
General HR onboarding — benefits paperwork, facility tour, policy acknowledgment signatures — is necessary but is not the same thing as safety and quality orientation. A new staff member who has signed a stack of forms may still have no genuine understanding of this laboratory’s specific hazard points, emergency procedures, or quality expectations. The distinction matters most in the first unsupervised shift, when there is no one immediately present to catch a gap in understanding.
What good looks like
- A signed orientation record is dated before the first unsupervised shift.
- Safety procedures are covered specifically, not folded into general HR content.
- A recently hired staff member can describe what orientation actually covered.
Common failure modes
- Orientation record is signed retroactively, after work has already begun.
- Orientation is entirely administrative, with no safety-specific content.
- A new staff member can’t recall any specific content from their orientation.
Worked example
If you are starting from zero — do this first
- Separate safety-and-quality orientation from general HR onboarding.
- Build a specific checklist covering the actual hazards and procedures of the role.
- Require sign-off dated before the first unsupervised shift.
Self-assessment questions
Evidence: Signed orientation record
Evidence: Orientation content checklist
Evidence: Staff interview
Common reasons for a PARTIAL answer
- Orientation is administrative only, with no safety-specific content.
- The signed record predates actual content delivery, or follows it.
Implementation plan
| When | What |
|---|---|
| Week 1 | Build a safety-and-quality-specific orientation checklist. |
| Week 2 | Pilot it with the next new hire. |
| Week 3 | Refine based on what the pilot revealed as unclear. |
| Ongoing | Require completion before every new hire’s first unsupervised shift. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Recent-hire interview | Asks a recently onboarded staff member to describe specific orientation content without prompting. |
Evidence base
Training Records Tied to Specific SOPs
Core
In plain terms: The lab can say, for any staff member right now, exactly which version of which procedure they’re actually trained and cleared to perform.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A training record reading “trained on specimen handling” tells a Monitor almost nothing — which version, which specific steps, how recently. When an SOP is revised, the gap between the revision date and the actual retraining date is exactly where staff can continue following an outdated procedure in good faith, genuinely unaware anything has changed.
What good looks like
- Records name the specific SOP and version trained on.
- Retraining follows every SOP revision before the new version takes effect.
- Current qualification status is retrievable for any staff member on request.
Common failure modes
- Training records only name a general subject area, not a specific SOP version.
- An SOP is revised with no corresponding retraining record.
- Qualification status must be reconstructed manually from scattered files.
Worked example
If you are starting from zero — do this first
- Check whether current training records name specific SOP versions.
- Build a rule linking every SOP revision to a tracked retraining requirement.
- Test retrievability: ask for one staff member’s complete current qualification list.
Self-assessment questions
Evidence: Training record with SOP version reference
Evidence: Revision-linked retraining record
Evidence: Current qualification list
Common reasons for a PARTIAL answer
- Training records exist but don’t reference specific SOP versions.
- SOP revisions aren’t systematically linked to a retraining requirement.
Implementation plan
| When | What |
|---|---|
| Week 1 | Redesign training record format to name specific SOP and version. |
| Week 2 | Build the revision-to-retraining linkage into the document control process. |
| Week 3 | Backfill current records to the new format. |
| Ongoing | Trigger retraining automatically whenever an SOP is revised. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Qualification retrieval test | Requests a specific staff member’s current SOP qualification list and checks it against the master document register. |
Evidence base
Adequate Staffing for Safe Operation
Core
In plain terms: There are always enough qualified people on shift to do things safely and on time — including when someone calls in sick.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Understaffing rarely causes a dramatic, single failure — instead, it causes a slow accumulation of skipped steps, delayed quality control checks, and shortcuts taken by an already-stretched single staff member with no one to catch an error. Laboratories, particularly smaller ones, often operate for extended periods on minimum viable staffing with no documented plan for what happens when even that minimum is unavailable.
What good looks like
- A documented minimum staffing level exists for each operating shift.
- A real absence-coverage plan exists, not reliance on an already-stretched remaining staff member.
- Understaffing-driven shortcuts, where they occur, get logged as quality events.
Common failure modes
- Staffing levels are informal, “we manage,” with no documented minimum.
- Unplanned absence routinely leaves a single staff member working alone.
- Shortcuts taken under understaffing pressure go unrecorded.
Worked example
If you are starting from zero — do this first
- Document the actual minimum staffing level needed for each shift to operate safely.
- Build a real, usable absence-coverage plan, not an assumption that staff will manage.
- Create a way to log when understaffing actually forces a shortcut or delay.
Self-assessment questions
Evidence: Staffing policy
Evidence: Absence coverage plan
Evidence: Quality event log
Common reasons for a PARTIAL answer
- No documented minimum exists, only informal expectation.
- A coverage plan exists on paper but has never actually been tested.
Implementation plan
| When | What |
|---|---|
| Week 1 | Document the actual minimum staffing level needed per shift. |
| Week 2 | Build a real absence-coverage arrangement. |
| Week 3 | Create a mechanism to log understaffing-driven shortcuts. |
| Ongoing | Review staffing adequacy whenever volume or service scope changes. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Staffing policy and log review | Checks for a documented minimum staffing level, coverage plan, and any logged understaffing events. |