A step-by-step manual for getting Spin for SIM™ running — and keeping it running — across your unit and your trust. Not how to facilitate a scenario; how to make it stick.
This toolkit is written for the person leading the rollout — a trust lead, educator, or facilitator champion. Work through it in order the first time, then dip back into the chapter you need. Everything here pairs with the free posters, emails and kit on the Resources page.

Teams are expected to manage high-acuity, low-occurrence (HALO) emergencies flawlessly — the rare moments when coordinated multidisciplinary working matters most. Yet the chance to rehearse those moments together is often the first thing squeezed out of a busy week.
Traditional simulation is valuable but hard to sustain: it tends to be infrequent, resource-heavy, booked away from the clinical area, and dependent on faculty, kit and protected time. It can also feel high-stakes — a test to be passed rather than a chance to learn — which quietly excludes the very people a real emergency would need in the room.
Spin for SIM is low-fidelity, high-frequency, in-situ simulation. Short (around 10 minutes), opportunistic, and run where care actually happens. A spinning wheel picks the scenario at random, so nobody prepares in advance and everyone — including the facilitator — shares the same uncertainty. That randomness flattens hierarchy, and the deliberately informal, low-tech set-up keeps the stakes low and the focus on teamworking, communication and escalation.
Done regularly, it stops being an event and becomes a habit — a continuous cycle of Spin → Scenario → Team → Debrief → Learning → Repeat woven into the working day. The goal isn't a perfect performance; it's a team that's more confident, communicates more openly, and escalates more safely when it counts.

You don't need much to start — but a little groundwork makes the difference between a launch that fades and one that sticks. Aim to have these five in place before your launch date.

Give your launch a name and a bit of fanfare. Spin for SIM™ Week cupcakes with wheel toppers, stickers and a team photo turn “another training thing” into an event people remember — and want to repeat. Bake them, badge them, and celebrate the teams taking part.
Exactly what happens, day by day. Keep each action small. The aim of week one is simply to prove it's possible, visible, and enjoyable — not to hit a numbers target.
If a planned session can't happen because the unit is too busy, that's fine — defer it. A brief or partially completed session still counts as a win in week one.

The first week is the easy bit. These four habits are what carry Spin for SIM™ from a launch into a culture. Pick the ones that fit your unit — you don't need all four to start.

Almost every objection has a small, practical answer. When something stalls, reach for the fix — don't abandon the model.
Record little, but record it every time. Most of this is captured automatically when participants scan the QR codes — keep the manual bits to a quick note. The golden rule: every session is tagged with your trust code, so it lands on the right dashboard.
Once every three months, share your trust's psychological safety pulse with the whole team — a short, anonymous, seven-item check (adapted from Edmondson) plus a quick "how many Spin for SIM™ sessions have you done this month?". Run it at launch for a baseline, then quarterly. It's one standing QR code (find it on your dashboard); responses bucket themselves by quarter automatically, so there's nothing to set up each time — you just re-share the same link. Your dashboard then shows psychological safety by quarter, and how it compares between people who have and haven't been taking part.
Resist the urge to collect more. Light-touch data that's actually recorded beats a detailed form nobody fills in.

Confidence change is a great outcome — but on its own it won't tell you whether Spin for SIM™ has actually embedded. Implementation is about behaviour and reach. Watch these eight signals instead.