A surveyor stands at the nurses' station on a Tuesday morning and asks a plain question. Show me that this nurse can safely operate the infusion pump she used on the night shift. The educator opens a binder, finds the right tab, and produces a sign-in sheet: forty names, a date, a room number, and a signature next to each. It is a tidy document, and it proves exactly one thing. Forty people were in a room.
It does not prove that any one of them can program the pump, recognize an occlusion alarm, or clear an air-in-line fault without paging biomed. The distance between those two ideas, attendance and demonstrated ability, is where most competency programs quietly fail. It is also where citations, avoidable errors, and the awkward conversation with a surveyor tend to live.
This article is for the person who has to build the thing that closes that gap: a competency validation program that a facility can stand up, run every year without descending into chaos, and defend line by line when someone asks for evidence. It covers the difference between attendance and observed validation, how to design a skills fair people actually attend, how to meet the annual requirement without a December scramble, what a record needs to survive an audit, and where the preceptor fits.
The cleanest way to see the problem is George Miller's framework for clinical assessment, often drawn as a pyramid. At the base sits knows, then knows how, then shows how, and at the top does. A lecture and a sign-in sheet reach the bottom two levels at best. They confirm that information was delivered and, if you add a quiz, that it was understood. Neither touches the top two levels, which are the only ones a patient experiences.
Competency validation is the deliberate act of moving assessment up to shows how and does. Put plainly, a qualified validator watches the staff member perform the skill against written criteria and records the result. Everything else in a strong program is machinery built to make that single observation reliable, repeatable, and documented.
This is not an optional refinement. The Joint Commission's human resources standards require that staff competence is assessed, demonstrated, and maintained, not merely that education was offered. The federal Conditions of Participation that govern Medicare and Medicaid participation carry the same expectation. A binder of attendance records answers a question no regulator is asking.
The one-line test. For any item in your program, ask: if this staff member never actually performed the skill in front of a qualified observer, would my record still say "competent"? If the answer is yes, you are documenting attendance and calling it validation.
Observed return demonstration is the gold standard, but it is not the only legitimate method, and treating it as such is how programs collapse under their own weight. Donna Wright's widely used competency model makes the point well: different skills are best proven by different kinds of evidence. Direct observation is one. Others include written tests for knowledge-heavy items, review of evidence from daily work, case studies and scenario walkthroughs for clinical reasoning, peer review, and quality monitors that already exist in your data.
The discipline is matching the method to the skill rather than defaulting to a station for everything. A high-risk, low-frequency skill, the kind a nurse performs rarely but cannot afford to fumble, such as managing a massive transfusion or responding to malignant hyperthermia, earns direct observation or high-fidelity simulation. A high-volume routine skill may be adequately evidenced by existing chart audits or a quality monitor you already collect. Reserve your scarcest resource, a validator's attention, for the skills where getting it wrong is both plausible and serious.
Mixing methods is not cutting corners. It is how you make an annual program survivable, because a station-for-everything model needs more validator hours than any facility actually has, which is why it gets abandoned in the fourth quarter.
The skills fair remains the workhorse of competency validation, and it has a deserved reputation for being dreaded. That reputation is a design failure, not an inevitability. Fairs fail for predictable reasons: they run once, on day shift, in a distant conference room; the stations are long and generic; the validators are whoever was free; and the whole thing feels like a compliance tax rather than a professional service.
A fair people attend is engineered differently. Keep stations short and specific, six to ten minutes each, focused on a single validated skill with clear criteria. Run the fair across multiple days and, critically, across shifts, including nights and weekends, so staff are not forced to come in on their own time. Staff each station with a credible validator, someone respected for the skill, because the quickest way to kill a fair is to have a nurse validated by a person she does not believe is qualified to judge her.
Tie it to the schedule, not to goodwill. The single biggest driver of attendance is building validation slots into the staffing schedule as paid, rostered time. Voluntary attendance on unpaid hours produces a rush of the conscientious and a long tail of the missing, which becomes your compliance problem in November.
Give the fair a reason to exist beyond the checkbox. The best fairs double as low-stakes practice, where a nurse can fumble the rarely-used chest tube setup with a coach beside her rather than at 3 a.m. with a real patient. That reframing, from examination to supported rehearsal, is what turns a mandatory event into one staff find genuinely useful, and useful events fill themselves.
Most facilities treat annual competency as a single event, and then spend the last quarter of the year hunting down the staff who missed it. The fix is to stop thinking of competency as annual and start thinking of it as continuous, sampled throughout the year.
Two distinctions do most of the work. The first separates initial competency, proven during onboarding before a nurse works independently, from ongoing competency, confirmed on a schedule thereafter. The second is risk-based selection. You cannot revalidate every skill every year, and you should not try. Prioritize by the intersection of risk and frequency: high-risk, low-frequency skills need frequent deliberate validation precisely because staff rarely practice them, while high-frequency skills are partly self-maintaining and can lean on existing quality data.
Once you have a risk-based list, stagger it. Assign competencies to quarters, tie each nurse's cycle to a fixed anchor such as hire-date month, and let the calendar spread the load rather than concentrating it. A dashboard that shows completion by unit and by month turns the year-end scramble into a routine that is 90 percent done before anyone feels rushed. This is exactly the kind of structure a facility can build once and reuse, and it is a recurring theme across our broader guidance on workforce training for facilities.
A validation that is not documented did not happen, as far as a surveyor is concerned. But most records fail audit not because the validation was weak, rather because the record omits the details that make it defensible. A record that survives scrutiny is specific about six things.
Name the skill and the specific criteria it was measured against, so a reader knows what "competent" meant on that day. Name the validator, not just the department. Name the method, whether observed demonstration, test, or chart review. Date it. State the outcome in unambiguous terms, met or not yet met. And where a skill was not met, show the remediation path and the re-check, because a program that never records a failure is not being trusted by anyone who reads it closely. A file with zero remediation entries does not look flawless to a surveyor. It looks unused.
Keep the criteria for each skill in a single controlled source, so every validator scores the same skill the same way and the record points back to a definition that has not drifted. This is unglamorous, and it is the part that turns a stack of forms into an auditable system.
Facilities routinely conflate two roles that do different jobs. A preceptor supports learning: coaching, modeling, and building a newer nurse toward independent practice, a progression Patricia Benner's novice-to-expert work describes well. A validator makes a judgment against fixed criteria at a point in time. The same experienced nurse can hold both roles, but the roles are not interchangeable, and blurring them weakens both.
The risk in fusing them is obvious once named. A preceptor who has invested weeks in a nurse's growth is not a neutral judge of whether that nurse met the criteria today. Good programs keep the coaching relationship warm and the validation moment clean, sometimes by having a different qualified person perform the final observed validation.
Whoever validates, they must be trained to do it consistently. If two validators watch the same performance and reach different verdicts, your "competent" stamp means nothing, and inconsistency is the flaw a thorough survey will find. Calibrating your validators, so a pass means the same thing at every station and on every shift, is the difference between a program that looks rigorous and one that is. That validator development is precisely the kind of work our team builds into a facility's course and training plans, and it is available as part of our on-site mobile education services.
Coach warmly, judge cleanly. Keep the preceptor's job and the validator's verdict distinct, and calibrate everyone who signs off. A competency stamp is only worth the consistency of the people applying it.
Initial competency must be proven during onboarding, before a nurse practices independently. Ongoing competency is confirmed on a schedule your facility sets, commonly annually, though the standards focus on competence being maintained rather than prescribing a single interval for every skill. The practical answer is to validate each skill as often as its risk and how rarely it is used demand, not to force everything onto one yearly date.
It can anchor the year, but relying on a single event is what produces the December scramble. Run validation across multiple days and shifts, stagger cycles by hire-date month, and use existing quality data for high-frequency skills so the fair is not carrying the entire load. A continuous, sampled approach finishes the year calmly.
They can, but the preceptor and the validator are different roles. A preceptor coaches toward independence; a validator judges against criteria at a moment in time. Because a preceptor is invested in the nurse's progress, some facilities have a separate qualified person perform the final observed validation to keep that judgment neutral. Whoever signs, they should be trained to score consistently.
Specificity and honesty. A defensible entry states the skill and its criteria, names the validator and the method, carries a date, and gives an unambiguous outcome. Records that show remediation when a skill was not yet met read as more credible, not less, because a program that never documents a gap does not look like one that is being used.
It is, if you stop trying to observe everything. The programs that survive are risk-based: they spend scarce validator time on the skills where failure is both plausible and serious, and they use tests, chart audits, and quality monitors for the rest. That triage is the core of a program a stretched facility can actually sustain.
Building competency validation well is operational work: the right methods, a fair staff will attend, a defensible record, and validators who score the same way every time. Wahero can run that program with your team or support the parts you have not yet built, on site and across shifts, so the structure holds up long after the visit is over.
Educational content only
This material is published by Wahero Health Institute for professional and operational education. It describes how competency validation programs are designed and documented, and it is not legal advice, an accreditation ruling, or a substitute for your organization's own policies and the current standards of your accrediting body. Always follow the requirements in force where you operate. See our Terms of Use.
