Stop me if you’ve heard this before. A new instrument has arrived. Staff get trained in it. Testing begins. Results get reported. Everything works.
Months later, an inspector asks for competency assessment records for that test system. And the lab discovers that what happened during onboarding was training but not competency assessment. These are two things that feel similar in the moment and are treated very differently under CLIA.
This gap is one of the most common and most avoidable findings in laboratory compliance, and it happens because training and competency assessment get conflated at exactly the moment when the distinction matters most.
Why Training Isn’t Assessment
Training is the process of teaching someone how to perform a procedure in a repeatable way. Competency assessment is the documented verification, using the six required CLIA elements, that they can perform it correctly and consistently. A staff member can complete thorough training and never have their competency formally assessed. During the weeks immediately following a new instrument rollout, those two things look almost identical.
The senior technologist who walks a colleague through the new workflow is transferring knowledge, not documenting direct observation, intermediate result review, and problem-solving evaluation in a form that would satisfy an inspector.
When a new test system goes live, there are specific points at which training needs to be transitioned into a formal, documented competency assessment. One is within the first thirty days, and another is as a second assessment within the first year, mirroring the standard timeline for new testing personnel. That transition gets missed more often than it should, because the lab is focused on getting the instrument operational, not on running a parallel compliance process.
Why This Gap Is Easy to Miss
New test system rollouts create a unique blind spot because everyone involved is focused on the same urgent priority: getting the instrument validated, staff comfortable with it, and testing underway with minimal disruption. Competency assessment, in that context, can feel like a secondary administrative task to handle once things settle down.
The problem is that “once things settle down” often means after the thirty-day window has already closed, and the formal assessment that should have happened during onboarding gets retroactively impossible to document. You can’t observe a staff member’s first attempts at a procedure after the fact. You can’t document problem-solving evaluations that should have happened during the early learning period once that period has passed.
This is also a gap that compounds across staff. A new instrument typically gets rolled out to multiple testing personnel around the same time, which means a missed assessment is a pattern affecting everyone who was trained during that rollout window rather than an isolated incident.
Building the Assessment Into the Rollout Plan
The fix needed is structural rather than procedural. Competency assessment for a new test system needs to be built into the implementation timeline from the beginning, not treated as a follow-up task. That means identifying, before the instrument goes live, who will conduct the assessment, what the six required elements will look like for this specific test system, and when each staff member’s assessment will be completed and documented.
It also means treating the vendor training and the competency assessment as sequential, related, and distinct activities. This means assessments that are scheduled to follow training closely enough that the early-use period, when problem-solving and technique observation are most meaningful, are not missed.
What Inspectors Are Actually Looking For
When an inspector asks about a relatively new test system, they’re checking whether the records reflect assessment that happened during the appropriate window which is early enough to capture genuine learning-period observation, structured around the six required elements, and documented in a way that’s distinguishable from training records.
A lab that can produce that documentation cleanly has handled the rollout correctly. A lab that can only produce training records, however thorough, has a finding, albeit a preventable one.
New instrument rollouts move fast. Competency assessment shouldn’t be the thing that gets left behind. Schedule a 30-minute overview with our team to see how StaffReady keeps assessment scheduling built into every new test system implementation.
