The LPN Example NCSBN Uses to Explain Assignment

NCSBN publishes one concrete example of the assignment and delegation distinction, and almost nobody reads it. It is a short scenario about an LPN or VN caring for a client with diabetes. It settles a question that four different study guides will answer four different ways.

The example, as NCSBN presents it

The scenario appears in the National Guidelines for Nursing Delegation, published by NCSBN and the American Nurses Association in the Journal of Nursing Regulation in April 2016.

An LPN or VN is caring for a client with diabetes. The tasks are taking vital signs, checking blood glucose, monitoring intake and output, documenting the care, and reporting findings to the registered nurse.

NCSBN calls that an assignment. Not delegation. The document is explicit about it.

Why those tasks are assignment and not delegation

The reasoning is a single test, applied to each task. Is this activity already inside the person's authorized scope and basic education?

Every task on that list is taught in a standard LPN and VN program. Glucose monitoring is in the curriculum. Intake and output is in the curriculum. Documentation and reporting are in the curriculum.

Nothing on that list asks the nurse to step outside their existing role. That is the whole reason it is an assignment.

Delegation is the other case. It means allowing someone to perform a specific activity that sits beyond their traditional role, and it requires additional validated competency for that specific activity. The definitional split itself belongs to delegation versus assignment, the line that decides answers.

So the deciding word is not who. It is whether.

The curriculum and scope test in practice

You can run this test on almost any answer option in under ten seconds. Ask whether the activity was taught as core content in that person's own program. If yes, and the client's condition allows it, you are looking at an assignment.

Ten seconds is not an exaggeration either. Once the comparison is familiar, most who-does-what options sort themselves before you have finished reading them.

The trap is that the test feels too easy, so students reach for a memorized task table instead. There is no such table in the NCSBN guideline. The document is a process framework and it says as much.

There is a second reason the table does not exist. Scope varies by state.

NCSBN states plainly that jurisdictions have different laws and rules about delegation, and that every licensed nurse is responsible for knowing what their own state practice act permits. Whether an LPN or VN may pass a task to unlicensed personnel at all is one of those state-conditional questions, taken up in can an LPN or VN delegate to a UAP, your state decides.

What still applies even though it is an assignment

Calling it an assignment does not remove the nurse's obligations. Two things carry over.

Accountability does not transfer. The nurse who assigned or delegated the work keeps overall accountability for the client, while the person performing the task is responsible for that task itself. That split is why an answer option ending the RN's involvement is so often wrong.

The client's condition still governs. If the client's status changes, the expectation is that the person performing the task reports back and the nurse reassesses. The full set of requirements, in NCSBN's own wording, is in the five rights of delegation applied to a stem.

Neither obligation depends on which word the stem used.

Who counts as unlicensed personnel is a separate definition with its own list of job titles, and it is covered in what UAP means and which roles it covers.

Three stems where the example does the work

First stem. An LPN is asked to obtain vital signs on a client admitted overnight who is stable this morning. That is the worked example almost word for word, so it is an assignment, and the item is really about what gets reported afterward.

Second stem. An LPN is asked to perform the admission assessment on a newly arrived client. Assessment is nursing judgment, and judgment is the one thing the guideline says can never be handed off. The task itself is the problem here, not the person.

Third stem. An LPN is asked to check blood glucose on a client who became diaphoretic and confused ten minutes ago. The task sits inside the curriculum, but the client is no longer stable. Stability is a condition on moving any task, so this one changes too.

Same list of tasks, three different answers, and the difference is never the job title.

Reusing the example on stems that look different

The value of a worked example is that you can transplant it. When a stem gives you a task and a person, run the same comparison.

Ask three things in order. Was this taught in that person's basic program. Is the client stable enough for the task to move. Does the option keep a reporting loop open.

If all three hold, the option is defensible. If the first fails, you are in delegation territory and the stem needs to tell you competency was verified. If the second fails, nothing moves anywhere yet.

That is the whole method. It is short on purpose.

Why this one example is worth keeping

Most delegation content you will read is somebody's interpretation. This is the source document's own illustration, in the source document's own words, which means an exam item built on the same distinction will behave the same way.

Keep the scenario in your head as a reference point. Vital signs, glucose, intake and output, documentation, reporting to the RN. Assignment.

When a stem hands you something outside that pattern, you now have a comparison rather than a guess, and that is usually enough to eliminate two options immediately.

Where this family sits relative to prioritization items, and how the two get combined inside case studies, is mapped in prioritization and delegation questions, decoded.