Building a Competency Program When You’re Starting from Scratch

A researcher in a lab coat carefully examines a test tube, symbolizing scientific discovery and research.

Inheriting a lab without a functioning competency program, or being tasked with building one from nothing, is one of the more daunting situations a lab manager can face. The regulatory requirements are extensive, the documentation volume is significant, and the work must be done without disrupting ongoing operations.

The good news is that building a competency program doesn’t require doing everything at once. It does, however, require a structure and doing the right things in the right order.

Start With the Regulatory Framework

Before designing anything, be clear about which regulatory requirements apply to your lab. CLIA requires competency assessment for all testing personnel performing moderate or high-complexity tests, with a defined set of six assessment methods that must be used. CAP adds specificity through discipline-specific checklists. If your lab also operates under TJC or another accrediting body, those requirements layer on top.

Understanding the full regulatory picture before you begin designing the program can preclude building a program that satisfies one framework while inadvertently creating gaps in another.

Inventory Your Staff and Their Testing Responsibilities

It’s important to remember that at their core, competency programs are inherently human-centered. A competency program is built around people and the tasks they perform. Before you can design assessments, you’ll need a clear picture of who is performing what testing, at what complexity level, and on what schedule.

This inventory is more complex than it sounds. Staff who rotate across departments or specialties need competency documentation for every area they work in. Staff who are new to a role are subject to different assessment timelines than established personnel as well as training in their new responsibilities. Staff who perform testing infrequently need the same documentation as those who perform it daily.

Build the inventory before you build the program. It will shape every subsequent decision about assessment design, scheduling, and documentation and ultimately remove much of the decision fatigue you may face as a manager.

Design Assessments That Match the Work

CLIA’s six required assessment methods — direct observation, monitoring of test recording and reporting, review of intermediate results, observation of instrument maintenance, proficiency testing, and evaluation of problem-solving skills — are a static framework, not a list of potential options. All six must be used, but how they’re implemented depends on the specific testing being assessed.

Direct observation of a manual differential requires a different assessment design than direct observation of an automated chemistry panel. Problem-solving assessment for a microbiology bench looks different than for a point-of-care glucose program. Designing assessments that reflect the actual work increases their validity and makes them more defensible during an inspection. By connecting assessments to relevant work and tasks, you also deepen the learning and relevance for the employees being evaluated.

 

Build the Schedule Before You Need It

Competency assessment timelines are regulatory requirements. New testing personnel must be assessed at least twice in their first year. Established personnel must be assessed annually. Building the assessment schedule from the beginning and assigning ownership of each assessment prevents the calendar drift that causes most competency programs to fall behind.

A schedule that exists only in someone’s head or as a reminder on a personal calendar is not a program. It’s a plan that will fail the first time the person who owns it changes roles or goes on leave.

Document Everything from Day One

The documentation discipline you establish at the beginning of the program sets the standard for everything that follows. Every assessment completed, every finding identified, every remediation undertaken needs to be documented in a way that is retrievable, specific, and legible to someone who wasn’t present when it happened.

Starting with good documentation habits is significantly easier than retrofitting them onto a program that has been running informally. The inspectors who look at your program in two years will be reading the records you create today.

 

Building a competency program from scratch is easier with the right infrastructure behind it. Schedule a 20-minute walkthrough with our team to see how StaffReady supports the full build.

Related Blog Posts