Clinical judgment is a chain of decisions made with incomplete information: what to assess first, when to escalate, which order to question. High-fidelity simulation teaches that chain well — but most programs can only give each student a few hours of lab time per semester. The thinking part of simulation, where a student commits to a decision and watches the patient respond, does not actually require a manikin.
A branching scenario is the low-cost complement: a short interactive case where the student reads a handoff, chooses what to do next, and sees the consequences play out — vitals that keep trending down if they delay, a charge nurse who asks pointed questions if they escalate without data. ScenarioSplice is a no-code tool for building these. You write the case, tag each outcome as correct, incorrect, or partial, and send students a link. They play it in any browser, on any phone, with no account.
This page covers what nursing cases look like as decision trees, example premises you can adapt, and how to build one in an afternoon.
A branching clinical case has four kinds of pages: a situation page (the handoff — patient, history, current status), a decision page with two or three realistic actions, consequence pages that show what happens next, and a debrief page that consolidates the takeaway. The structure mirrors the clinical judgment cycle: notice, interpret, act, reflect.
Because the Next Generation NCLEX puts so much weight on clinical judgment, this format doubles as decision practice in the same spirit — not a question bank, but repeated reps at prioritization and next-best-action under realistic pressure.
The quiet deterioration. A 68-year-old is post-op day one after a hip replacement. Blood pressure has drifted from 128/76 to 102/60 over the shift, and she is newly confused. Students decide what to do first — focused assessment, the PRN analgesic charted for tonight, or an immediate call to the surgeon — and each choice plays out the next thirty minutes of the shift.
Who do you see first? Students take handoff on four med-surg patients: one due for discharge teaching, one two hours post-transfusion, one with new-onset shortness of breath, one asking for pain medication. They choose an order of rounds, the scenario plays out what each delay costs, and the debrief walks through a prioritization framework.
The pediatric escalation. A 7-year-old in the ED has had two nebulizer treatments with minimal improvement, and retractions are worsening. Students choose between continuing the current plan, escalating to the provider now, or repositioning and reassessing in fifteen minutes — and see how each choice changes the next set of observations.
Paper cases and lecture vignettes give the answer away on the next slide. The student never commits, so nothing is at stake when the answer appears. In a branching scenario the student must choose before they can continue — and the case responds. Delay the assessment and the vitals worsen. Call the surgeon without numbers and the surgeon asks for them. That felt consequence is what makes the debrief stick.
It is also safe failure. A student can take the wrong path, watch it go badly, back up, and try again — repetitions a sim lab schedule can never afford.
Every new scenario opens as a decision-tree template — intro, decision, outcomes, debrief — so you edit pages rather than face a blank canvas. Tag each outcome correct, incorrect, or partial for color-coded feedback students see as they play; use info pages for labs and vitals. Paste an image URL for a rhythm strip or wound photo, keep debrief prompts in private facilitator notes, run validation to catch orphan pages, then click Assign and paste the link into Canvas or your course email. The full walkthrough is in how to create a branching scenario.
No. Students open the assign link in any browser — phone, tablet, or laptop — and play anonymously. Only authors sign in (with Google) to build.
No, and it is not meant to. It is a complement: use branching cases as pre-briefing before lab time, or as spaced decision practice between sim days. The manikin work stays where it belongs.
Not yet. Learners play anonymously today; a per-learner gradebook with CSV export is on the roadmap. Many instructors pair a scenario with a short written reflection as the graded artifact.
Yes — paste an image URL on any page, with alt text for accessibility. One-click image upload is on the roadmap.
Building and sharing scenarios is free, with no cap on how many — what students see carries a small "Made with ScenarioSplice" line. Professional replaces that with your program’s own logo and colors. For most nursing faculty the free tier is the whole story; branding tends to matter more to people delivering training commercially. Professional is $19/month and you can start it today.