Moving a campout to shelter can be the right call. The communication can still fail when one leader sends a text, another repeats the old location, and a third leaves out the new arrival time. Families then make practical decisions from three different versions of the plan.
Treat a change as a short publishing job. Decide through the unit’s approved process, update one current record, send the affected audience a pointer, and close the loop when the plan is settled. The protocol below gives an event chair and communications volunteer a shared sequence for cancellations, delays, location moves, and all-clear updates.
Follow current Scouting America weather safety guidance, venue rules, local emergency instructions, and your unit’s established safety process when making the actual decision. This article covers only how to communicate that decision, not weather, medical, legal, or emergency-management advice.
Name the decision owner and the message owner before the forecast changes
For each event, write down two roles:
- Decision owner: the person or group authorized by your unit and event plan to decide whether the activity proceeds, changes, delays, or ends.
- Message owner: the person who updates the current event details and sends the family-facing notice. Name a backup who can do the same job.
They may be the same person for a den meeting. For a campout, the event lead might make the call through the unit’s approved process while the communications chair publishes it. This prevents an early guess from becoming the family plan.
Before departure day, agree on the answer to four questions: who decides, where the current event details live, which audiences might need separate notices, and which channel is reserved for urgent changes. The Scout communication channel guide can help keep an official update distinct from conversation and routine reminders.
Use one decision tree
Copy this into the event plan. Replace the bracketed fields before the event opens.
CHANGE-DECISION TREE
1. A changed condition is reported or observed. -> Notify [decision owner] through [approved contact path].
2. Is a decision required now under current official guidance, venue rules, local instructions, or the unit's event plan? -> No: monitor through the approved plan. Do not send speculative notices. -> Yes: [decision owner] confirms the action and effective time.
3. What changed? -> Cancel: publish that the event will not occur and what happens next. -> Delay: publish the new decision/check-in time and when another update is due. -> Relocate: publish the new location, arrival instructions, and route/parking changes. -> Continue with a change: publish the changed condition and the current event details.
4. Update the authoritative event record first. -> Retire or clearly mark the old location, time, or instruction.
5. Notify only the affected audience. -> Use the unit's established urgent path when travel or immediate action is involved. -> Use a durable announcement or regular event reminder when the change can wait.
6. Confirm receipt when the travel, pickup, attendance, or safety impact makes it necessary. Record only the confirmation your unit actually needs.
7. Close the loop. -> Send an all-clear, final cancellation, or next-decision time. -> Keep the final event record available; do not leave competing versions active.The decision tree prompts leaders to wait for the authorized decision and supporting information before sending a message.
Put five details in every change notice
The message can be short when it answers the questions a family must act on:
- What changed? Say cancel, delay, relocate, or continue with a changed plan.
- Which event and audience? Name the activity and who the message affects.
- When does it take effect? Give a date and time, not “later” or “this afternoon.”
- What does the household need to do? Travel later, use a new entrance, stay home, or wait for another update.
- Where is the current detail? Point back to the event record and give the next update time when the final answer is still open.
For example, “Tonight’s 7:00 p.m. den meeting is moving to the library community room. Arrive at the east entrance at 6:55 p.m. The current location and parking note are on the event record. We will confirm whether the outdoor game is rescheduled by Friday at noon.”
That message tells families what to change and where to find the answer without creating another version of the plan.
Match the communication method to the disruption
Match each update to its impact. A changed craft supply list can wait for a normal reminder. A changed pickup location while families are already traveling needs the unit’s established urgent path and a quick confirmation plan.
| Change | Best communication pattern | Key consideration |
|---|---|---|
| Meeting moves before the school day ends | Update the event record, then send a concise family notice | Can affected households reasonably see the change before leaving? |
| Campout departure moves by two hours | Update the event record and send the defined urgent notice to attendees | Which traveling households need a direct follow-up? |
| Rain changes the service-project task, not the location | Update the current event instructions and use the next event reminder | Does anyone need to bring something different or skip the trip? |
| Event is canceled | Mark the event canceled, send the final notice, and state the next decision | Do families need a make-up date or a separate RSVP later? |
Do not require acknowledgements for every ordinary reminder. Ask for confirmation when it helps prevent a real travel, attendance, pickup, or other approved event-planning problem. Use the unit’s existing process for official attendance, transportation, health, safety, or emergency records.
Publish the update, then retire the old version
A clean change can still become messy as it spreads across channels. An event lead moves a Saturday hike to a pavilion. The calendar is updated, but an old group post still says “meet at the trailhead.” A parent screenshots that post on Thursday, drives to the original location, and calls another volunteer who has heard only the old instructions.
Avoid that loop with a two-minute publishing check:
CHANGE NOTICE CHECKLIST
[ ] The decision owner confirmed the action and effective time.[ ] The authoritative event record now has the current time, location, and instructions.[ ] The old detail is removed, canceled, or visibly marked as superseded.[ ] The notice names the event, change, effective time, household action, and current-detail link.[ ] Only affected groups received the notice; unrelated families were not unnecessarily notified.[ ] Direct confirmation is assigned only if travel or another real impact warrants it.[ ] A final all-clear, cancellation, or next-update time is scheduled.For a location move, add the new entrance, parking, and arrival window. For a delay, state whether families should wait at home or still arrive at the original meeting point. For a cancellation, say whether the next step is “nothing further,” “watch for a rescheduled date,” or “complete a new RSVP.”
Copy and adapt these four messages
Replace bracketed text, then remove anything a recipient does not need.
Cancellation
[Event] on [date] is canceled. Do not travel to [location]. The current event record is marked canceled at [link]. [Next step or reschedule details]
Delay
[Event] will begin at [new time] on [date]. [Arrival or departure instruction.] The current details are at [link]. We will send another update by [time] only if the plan changes again.
Relocation
[Event] is moving to [new location] for [date/time]. Use [entrance, parking, or arrival instruction]. The event record now has the current details: [link]. Please do not use the previous [old location] instructions.
All-clear or final confirmation
[Event] is proceeding as currently posted. The latest time, location, and preparation details are at [link]. [Any one action the household still needs to take.] See you at [arrival time].
Keep the final plan visible after the message is sent
Once the immediate update is out, leave the durable event detail in a state a family can use without rereading every message. For an event day with several handoffs, pair this protocol with the Scout event day run sheet so the event lead, setup lead, and family-facing contact have the same live plan. For the earlier planning work, the Scout event planning checklist helps define the owner, alternate location, and change channel before the first forecast watch.
Where Woggle can support the protocol
A unit using Woggle can keep an Event as the current home for its time, location, and practical details. An Announcement targeted to the Unit or appropriate Groups can carry the short change notice back to that Event. A message in the appropriate Channel can handle conversational follow-up, while reminders point attendees to the current information. Woggle supports this coordination alongside official safety guidance, local emergency instructions, Scoutbook, approved records, and a unit’s established urgent-response process.
Before the next outdoor event, assign the decision owner and message owner, then run one low-stakes location-change practice. If a family can find the current plan in under a minute, the protocol is ready to use when a real change arrives.
