To document the steps you use to spin a random name picker wheel, write down four things for every draw — the list source, the names entered, the draw mode (with or without replacement), and the winner — so anyone reading your record can replay or audit the exact spin. Documenting a wheel workflow is less about the tool itself and more about capturing the inputs, settings, and outcome in a way that survives the moment the tab is closed. Because the Random Name Picker Wheel runs locally in your browser and nothing is stored on a server, your documentation also doubles as the only persistent evidence that a particular draw happened. A clean record typically takes the form of a short entry in a shared doc, an SOP page, or a printed handout: a one-line list source, the full pasted roster, the option chosen for repeats, a timestamp, and the highlighted winner shown below the wheel after the spin. Once you adopt that format, the same template works for a classroom cold-call list, a company giveaway, a raffle at a community event, or a team standup where you need a fair "who goes first" decision. The rest of this guide walks through what to capture, the three actual steps to spin the wheel, a reusable template, and where to keep the record so it remains useful long term.
What "Documenting the Steps" Means for a Random Name Picker Wheel
Most readers who ask how to document steps for a random name picker wheel are not asking how to spin the wheel — they already know the gist. They are asking how to turn a quick, in-the-moment click into a record that someone else (or future-them) can read, verify, and repeat. A spin feels like a single action, but behind the click sit four distinct decisions: where the names came from, what was entered, which draw mode was used, and who came out as the winner. Each of those decisions is worth capturing, because a winner chosen in front of a classroom or a livestream audience is only as trustworthy as the record of how the names got onto the wheel.
Think of the documentation as a short audit log rather than a manual. You are not writing a tutorial for the tool; you are writing the equivalent of a meeting minute that says exactly what list was used, what was clicked, and what result came out. Done well, the record takes a minute to write and answers any future question in seconds, and it scales from a teacher's class roster to a company-wide giveaway without changing its structure.
What Belongs in a Documented Spin Workflow
Four categories cover almost every random name picker wheel draw worth recording. Capture them in the same order every time, and your entries will line up cleanly when you scroll back through them weeks later.
- Inputs. Where the names came from (a class roster sheet, a Slack channel export, a Google Form response list, a typed-in list at the venue) and the exact roster as it was pasted into the wheel. Blank lines are ignored automatically, so the recorded list should match what you actually loaded.
- Settings. Which draw mode was active. By default the same name can come up again; ticking "Remove winner after each pick" switches the wheel to draws without replacement, which is the right choice for ordered running lists or ranked prizes.
- Actions. Who clicked Spin and when. A simple timestamp plus the name of the person at the keyboard is enough — useful when several people take turns running draws at the same event.
- Output. The name highlighted below the wheel once it stops, plus any subsequent draws if remove-after-pick was on. A short note like "Winner: Priya" is fine; a screenshot is better if the draw is publicly auditable.
If your draw is sensitive — a real student list, a real employee raffle, or a contest with a paid prize — add a fifth line: a privacy note confirming the draw was run locally and the page was closed afterward. The Random Name Picker Wheel processes everything client-side, so that note is genuinely true and worth recording as evidence.
Using a Random Name Picker Wheel: The Three Core Actions
The three core actions of the wheel are short enough to fit on a sticky note, and that brevity is exactly what makes them easy to document. Each step is a single observable event, which means each one also has a clean place in your written record.
- Type or paste your names into the box, one name per line. Blank lines are ignored automatically, so you do not need to clean them up before pasting. If your roster lives in a spreadsheet column or a Google Doc, copy a single column straight in — each line becomes one entry on the wheel. Duplicate names are kept if you want to give someone extra chances.
- Click "Spin the wheel." The wheel spins and eases to a stop on a random winner, which is then highlighted in the result area directly below the wheel. Write the highlighted name down immediately, or capture a screenshot if the draw is being recorded for an audience.
- Optionally tick "Remove winner after each pick," then keep spinning. With the box ticked, each winner drops off the wheel automatically, letting you keep clicking Spin to draw a full running order, a tournament bracket, or a ranked list of prizes without ever repeating a name. Unticked, the wheel resets to the full list each spin.
For a deeper walkthrough of why those three actions are designed the way they are, the guide Wheel to Pick a Random Winner From Any List covers the same flow in more detail. What matters here is that the three steps translate directly into the three lines of your documentation: load, spin, record the result.
A Reusable Template for Recording Each Draw
Once you have settled on what to capture, the easiest way to keep documentation consistent across many draws is to reuse the same template every time. The following table is a starting point you can copy into a shared doc, a Notion database, or an LMS lesson plan.
| Element | What to record | Why it matters |
|---|---|---|
| Draw purpose | Cold-call, giveaway, raffle, running order, tie-breaker | Context for replay and review |
| List source | Spreadsheet column, Google Doc, sign-up form, typed at the venue | Reproducibility of the input |
| Full name list | Names exactly as pasted, one per line | Audit trail of who was eligible |
| Draw mode | With replacement / without replacement | Affects whether repeats are possible |
| Timestamp | Date and local time of the spin | Chronological ordering across draws |
| Spinner | Person who clicked Spin | Accountability for who triggered the draw |
| Winner | The highlighted name below the wheel | The recorded result |
Treat each row as a single field. If you keep the template as a database row, every draw becomes one row you can filter by date, event, or person. If you keep it as a flat document, copy the headings once and fill them in for each new draw. Either way, the same fields cover classroom cold-calls, internal giveaways, and livestreamed raffles without modification.
Where to Keep Your Documented Steps
Storage location matters almost as much as the content itself. A perfect record in a place nobody can find is not much better than no record at all. The right home depends on who needs to read it and how often the draws happen.
| Storage format | Best for | Trade-off |
|---|---|---|
| Shared Google Doc or Notion page | Teams that run weekly draws and need to search history | Easy to edit; needs a permission setup |
| Printed SOP binder | Classrooms and venues without reliable wifi | Always available; harder to search later |
| Screen-recorded walkthrough | Training new facilitators in person | Shows the click visually; bigger files |
| README in a project repo | Giveaways tied to software releases or community events | Version-controlled; less accessible to non-technical readers |
| LMS lesson plan entry | Teachers documenting classroom draws alongside attendance | Sits next to grade records; visible to admins |
Pick one home as the system of record, and stick to it. Mixing formats silently — a Google Doc for one event, a sticky note for the next, a Slack message for a third — is the fastest way to lose the audit trail. Once the home is set, link to it from any related calendar event so future-you knows where to look.
Keeping the Record Useful Over Time
A documented workflow ages well only if it is revisited. Spinning a wheel is a stable operation, but the things around it — the roster source, the event format, the people who run it — change every term or quarter. Build a five-minute review into your routine so the record keeps matching the draw.
Three habits make the difference. First, update the template whenever a new setting appears or a draw mode changes; if you ever add a second wheel or a custom label, record the change in the same place. Second, note deviations explicitly. If you removed a late-arriving entrant after the first spin, write that down; an unexplained gap in the recorded list is the first thing challengers will point to. Third, capture a screenshot for any draw that is publicly visible — a livestreamed raffle, a recorded meeting, or a school assembly — and store it next to the entry. Text describes the result; a screenshot proves it.
Finally, keep a one-line privacy note with each entry. Because the wheel runs client-side in JavaScript and nothing is transmitted to a server, your roster never leaves the page, and the same is true of every draw you run through it. Recording that fact once per entry is enough to answer the question that always gets asked later: "Did the names get sent anywhere?" For a longer read on exactly what the tool does and does not upload, the guide Does a Random Name Picker Wheel Upload Names You Enter? walks through the privacy mechanics in detail.