A Scout event run sheet should fit on one page and answer one question: when the plan moves from one person to another, who owns the handoff?
That is enough to cover a campout departure, derby check-in, service-project arrival, banquet doors, or troop outing pickup. It is not a minute-by-minute script and it is not the place for every policy, packing detail, permission, or private contact. It is the small operating view that lets volunteers see the next immovable moment, the person responsible, the condition that has to be true, and the update families need if the plan changes.
Use the template below after the larger event plan is complete. It will make the day easier to run even if your unit keeps it on paper or in a shared document.
Give the sheet only the jobs it can do well
A run sheet is for live operations. Put the things that have to be found, decided, or handed off during the event on it:
- arrival window, opening time, departure time, pickup window, or another immovable moment;
- a named owner and a backup for a handoff;
- the dependency that determines whether the next step can happen;
- a communication trigger that changes what families or volunteers need to do; and
- a closeout confirmation before people leave.
Keep the detailed event description, gear list, registration or permission process, budget, training records, and private contact information somewhere appropriate to each of those jobs. The Scout event planning checklist is the larger planning view; the event description template is the family-facing view. A run sheet links those decisions on the day without duplicating everything.
For Scouting America activities, use the current SAFE Checklist and any applicable program, council, and unit guidance for the safety plan. Its assessment guidance calls for activity-specific risk planning, contingency planning, and communication with participants, parents, and emergency services. This template does not replace those requirements or become a safety, medical, transportation, or compliance record.
Build around the moments that cannot slide
The most useful times are not necessarily the most frequent. Start with the points where a delay would create a new decision.
For a Saturday service project, those might be the 8:30 arrival check, the 9:00 tool and area briefing, the noon water-and-count check, and the 12:45 site sweep. For a Pinewood Derby, they might be doors open, weigh-in closes, racing starts, awards begin, and the last track component is checked back in. For an overnight departure, the anchors might be the meet window, final roster lock, vehicle departure decision, destination arrival confirmation, and the family pickup update.
Between those anchors, resist filling every blank with a task. A sheet with 27 lines is hard to scan during a busy check-in. A sheet with six to ten meaningful moments lets an event chair see the next handoff without treating every volunteer like a stage manager.
Name owners, backups, and triggers—not just jobs
“Set up check-in” is a task. “Avery opens check-in; Morgan covers if Avery is handling a family question” is an operating instruction.
The same distinction applies to dependencies. “Food arrives” is vague. “Snack table opens after the allergy-aware items are placed and the food lead confirms the count” tells the next person what they are waiting for. Use roles or first names your team recognizes, but do not publish private phone numbers or sensitive information in a broadly shared version.
Each family-facing update needs a trigger. A useful trigger is a change in the family’s next action, not merely an internal milestone. For example:
- If rain moves the service project indoors, the communications owner posts the new entrance and start location.
- If derby weigh-in runs 20 minutes late, the owner posts the revised race-start expectation before families arrive for it.
- If the pickup window changes, the owner names the new window and points families to the current event details.
This keeps the run sheet from turning every normal check-in into a stream of messages.
Copyable one-page Scout event run-sheet template
Copy this into a shared document or print it. Trim rows that do not create a live decision.
EVENT AND OWNERSHIP
Event / date:
Event lead:
Backup lead:
Family-facing source of truth:
Current safety, program, council, and unit guidance checked by:
DAY-OF RUN SHEET
Time / window | Moment or handoff | Owner / backup | Must be true before it starts | Family or volunteer trigger
------------- | ----------------- | -------------- | ----------------------------- | ----------------------------------
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
CHANGE RULE
1. The event lead confirms the decision with the owner responsible for the affected work.
2. Update the family-facing source of truth first.
3. Send one concise message only if the decision changes what families or volunteers need to do.
4. Record the new owner, time, or next check on this sheet.
CLOSEOUT
[ ] Participant flow, equipment, and site check complete.
[ ] The person responsible for any remaining item is named.
[ ] Families received the one update they need before leaving.
[ ] The lead and backup know where the final event notes belong.Filled example: pack service project
Here is a small version for a park cleanup. It is deliberately not a full project plan; it only covers the day’s handoffs.
| Time / window | Moment or handoff | Owner / backup | Must be true before it starts | Family or volunteer trigger |
|---|---|---|---|---|
| 8:15–8:30 | Arrival and check-in | Jamie / Priya | Check-in sign and group meeting point are ready | None; families already have the arrival window |
| 8:35 | Safety and area briefing | Priya / Lee | Activity guidance and site boundaries are confirmed | If the meeting area moves, post the new entrance |
| 9:00 | Work groups begin | Lee / Jamie | Each group has a leader and its assigned area | None |
| 11:40 | Weather and progress check | Jamie / Priya | Conditions are still suitable and cleanup plan is clear | If ending early, post the revised pickup time |
| 12:00 | Families pick up | Priya / Lee | Each group is back at the meeting point | Post only if the pickup window changes |
| 12:15 | Site sweep and tool return | Lee / Jamie | Groups have departed and tools are counted | Tell volunteers who owns any remaining item |
The sheet does not list each tool, participant, or safety rule. Those belong in the relevant plan and approved process. Its value is that, when weather changes at 11:40, everyone knows who decides, who communicates, and what needs to happen before pickup.
Plan for the handoff that breaks first
The realistic failure mode is a quiet gap in ownership. At a derby, the volunteer running check-in steps away to solve a bracket question. The next family arrives with a car that still needs inspection. The person at the table assumes someone else has the decision, and the line grows while three leaders offer slightly different answers.
The recovery is not a bigger group chat. The event lead uses the sheet: the backup takes check-in, the inspection owner makes the call, and the communications owner sends an update only if the public timing has changed. Afterward, change the next version of the run sheet so the backup is explicit before the doors open.
Keep the durable plan connected in Woggle
If your unit uses Woggle, the run sheet can remain a printable or shared working document while the durable coordination stays attached to the activity: use an Event for the current details, Household RSVPs for attendance context, volunteer roles for the specific open jobs, and an Announcement for the few changes families actually need to see. Household-aware RSVPs are especially useful when a day-of count needs to reflect the people a family has said are attending.
That does not make Woggle a project scheduler, a run-sheet feature, or an official record system. It gives the handoff plan a clearer place to point when the day changes.
On your next event, use the template for only the six moments most likely to create confusion. After closeout, keep the one row that prevented the most scrambling and remove the one nobody used.
