CNL common mistakes
CNL · Understand the traps and how to avoid them.
On "what should the CNL do next" items, choosing the immediate bedside intervention (reassess the patient, call the provider, reposition) rather than the action the CNL takes at the microsystem level (review unit-level data, convene the team, standardize the process).
Most practice items candidates have encountered are written from a staff-nurse frame, so the instinct to act on the patient in front of them feels safest; CNL items instead reward system-level assessment and leadership action, and candidates answer before identifying which role the stem is asking about.
What to do instead
Before answering, identify who the stem says is acting ("as the CNL") and what level of the system is named (individual, unit, population, process). If the stem describes a pattern or a group, eliminate options that treat only one patient; the first move is usually to verify or measure the problem and engage the team, not to intervene on a single case.
Assigning first-time patient teaching, initial assessment, triage, or evaluation of an intervention to assistive personnel or to a licensed staff member whose scope excludes it, justified by efficiency or by "they've done it before."
Candidates choose the delegate by who has time or by past practice rather than by which tasks require nursing judgment, and familiarity with a task is mistaken for authority to delegate it.
What to do instead
Apply a two-part test to every task: does it require nursing judgment/assessment or teaching a new skill (not delegable), and is the delegate's scope and documented competency a match? Delegate only tasks with a predictable outcome in a stable patient; keep assessment, initial teaching, and evaluation with the RN; document the delegation and follow up on the outcome.
When a patient's needs cross settings, answering "notify the provider" or "refer to case management" as if that were the complete action, without naming the specific service that owns the need or who is accountable for follow-through.
Notification feels like action, and "case management" gets used as a generic bin, so the item's actual test - matching the need to the discipline with that expertise - goes unrecognized.
What to do instead
Classify the need first (clinical, functional, financial/psychosocial, educational, equipment), then match it to the discipline that owns it (social work for finances, placement, or abuse; pharmacy for regimen complexity; rehabilitation for functional goals; home health for skilled need at home). State who is accountable and what closes the loop. Reserve provider notification for needs requiring a medical order or clinical decision.
Placing discharge teaching, medication reconciliation, and follow-up scheduling at the end of the stay, so a question about the first action gets answered with "teach the patient" or "give the discharge instructions."
Discharge feels like an event rather than a trajectory, and the visible tasks cluster in the final 24 hours; candidates see "discharge" in the stem and jump to discharge-day activities.
What to do instead
Anchor on the principle that transition planning begins at admission: identify the likely discharge destination and barriers on day one, involve the patient and family in goal-setting, and reconcile medications at every transition (admission, unit transfer, discharge). When the stem asks for the first action, choose the earliest-in-the-trajectory option.
Treating a referral, transfer, or handoff as finished once it has been sent or communicated, with no confirmation of receipt, no scheduled follow-up, and no verification that the patient or caregiver can act on the plan.
Sending feels like completing, and stems often stop at the moment of sending, so candidates do not look for the "confirm/verify/close the loop" option because it reads like a minor detail.
What to do instead
For any handoff, look for a closing action: confirmed receipt by the receiving clinician, a specific follow-up appointment with date and time, a warm handoff or teach-back with the patient/caregiver, and documented reconciliation of medications and pending tests. An option that verifies the transition actually occurred usually outranks one that only initiates it.
Stopping at the screening score - documenting a fall or pressure-injury risk number - without completing the assessment, matching interventions to the specific modifiable risk factors, or reassessing after a change in condition or a transfer.
The tool and the number are concrete and easy to recall, so the score feels like the answer; candidates also misapply instruments, using a fall-risk scale for skin risk or a tool not validated for the population in the stem.
What to do instead
Separate the four steps: screening (who is at risk), assessment (which factors are modifiable), intervention (a bundle matched to those factors), reassessment (scheduled and after any change or transfer). Match the tool to the risk and population, and when a score is high, select the option that addresses the identified factor and re-evaluates rather than one that only documents the score.
Ranking a single randomized controlled trial above a systematic review or meta-analysis, treating patient preference and clinical expertise as optional extras, or choosing "provide a staff in-service" as the entire plan for adopting an evidence-based practice.
Candidates memorize "RCT is the gold standard" without the level above it, and education is the most familiar implementation tactic even though it rarely changes practice on its own.
What to do instead
Order evidence as systematic review/meta-analysis of RCTs, then RCT, then cohort/case-control, then descriptive, qualitative, and expert opinion, weighted for quality, consistency, and applicability to your population. The decision must also incorporate patient values and local context. For implementation, pair education with standardization (protocol or order set), reminders, audit and feedback, and a measure of adoption.
Choosing a solution in a quality-improvement scenario (new checklist, staff education, add a nurse) before a baseline measure and a specific, measurable aim have been established.
Candidates want to fix the problem quickly, and solutions are more memorable than measurement steps; the measurement phase feels like delay when a fix is obvious.
What to do instead
In any QI sequence, the order is: define the problem with data, establish baseline, write a specific aim (how much, by when, for whom), analyze causes (fishbone, Pareto, flow map), then test the change on a small scale with PDSA, measure, and spread only after improvement is demonstrated. Eliminate options that implement before baseline unless the stem already supplies baseline data.
Reporting process or activity counts as if they were outcomes - "95% of nurses completed the training" or "the protocol is now used on all 30 beds" offered as evidence that care improved.
Activity data are easier to collect and rise quickly, so they feel like proof, and the structure/process/outcome distinction blurs under time pressure.
What to do instead
Classify each measure before choosing: structure (resources, staffing, EHR capability), process (whether the right care was delivered - hand hygiene, medication reconciliation completed), outcome (what happened to the patient - fall rate, readmission, infection rate). If the stem asks whether care improved, only outcome measures qualify; add balancing measures (length of stay, staff workload) to detect unintended consequences.
Reacting to a single elevated data point or a month-to-month wobble as though it were real change - ordering an investigation, re-educating staff, or announcing success - instead of applying run-chart or control-chart rules to separate common-cause from special-cause variation.
Candidates read a graph the way they read a trend line, without the rules that define a signal (a shift of six or more consecutive points on one side, a trend of five or more, a point beyond the control limit), so "it went up, so our change worked" feels like valid inference.
What to do instead
Ask whether the variation is common cause (stable and inherent to the system - change the process) or special cause (a signal - investigate that specific event). Apply run-chart rules and require enough data points before declaring improvement, and attribute system-level problems to the process rather than to individual staff.