A backup date is a plan, not an announcement that the event has moved. Once the organizer makes a change, publish the complete new date and time together and replace the old arrival instructions.
Say whether the backup is conditional or activated
Keep the organizer's decision separate from a weather forecast. A coordinator may prepare a replacement notice in advance while the original event remains scheduled. That preparation does not justify publishing “rescheduled” before the responsible organizer has made the decision.
The City of Falls Church's 2027 egg-hunt page, checked November 13, 2026, illustrates why a complete backup matters. It lists a Saturday morning hunt and a conditional weather fallback on Monday, March 29 at 4:30 p.m. Both the day and time change. This published contingency is not evidence that the move has actually been announced.
| Actual situation | What the notice should communicate |
|---|---|
| Original event still scheduled; backup prepared | Current plan, conditional backup and where to check for a decision |
| Organizer announces a postponement | Old arrangement no longer applies; full confirmed replacement details |
| Organizer cancels without a replacement | Cancellation and any confirmed next step; no invented new date |
| Decision not yet available | What remains unresolved and the maintained update route |
A changed date needs a changed arrival message
Fictional communication example: Sunbreak has an original Saturday hunt with a Monday backup. The following messages demonstrate the difference between a contingency and an actual change. They are training copy, not real invitations.
Before a decision: The Saturday hunt remains scheduled. A Monday alternative is prepared if the organizer postpones the event. Check the organizer's current event update before traveling.
The actual public version must contain the confirmed original date and time and a working update destination. If the backup details are published, mark them as conditional next to those details rather than relying on a distant footnote.
After an announced change: The organizer has postponed the Saturday hunt. The hunt will now take place on Monday, March 29, 2027 at 4:30 p.m. Use the updated arrival instructions on the current event page. The old Saturday morning arrival instruction no longer applies.
In this fictional example the editor receives the decision, replaces the scheduled-date notice and checks the new date, weekday and time together. The venue and entry route are confirmed separately; the editor does not assume they stay unchanged. If activities surrounding the hunt have a revised schedule, those receive their own confirmed details.
Finish the update across the channels people actually use
Assign one editor to the current announcement and one reviewer to compare it with the organizer's decision. The editor then checks four working surfaces: the event information page, any direct participant message the organizer uses, approved paper placements and the staff briefing. A social post alone will not correct an old paper notice at a shop.
For Sunbreak, the reviewer finds that the website is current but one indoor notice still shows Saturday. The team replaces that notice through its normal process, confirms that staff have the Monday wording and records the update time. A colleague then checks the visitor's route from the paper notice to the current event page. That closes the fictional update; it does not claim that a real event ran or that visitors received a message.
Keep the replacement date and start time together wherever either appears. Avoid “same time, different day” unless the organizer has confirmed exactly that. Keep old versions identifiable in your records while preventing them from remaining the visitor-facing instructions.
Do not fill an unresolved field with a guess
When the organizer has not provided a decision time, state the current update route rather than promising a cutoff. Read event-specific instructions in context; office hours or unrelated program information cannot establish the hunt's decision deadline.
Separate a communications update from decisions about weather conditions, site use, admission or refunds. Those belong to the responsible operator and its current policies. If a visitor asks about a detail the update does not settle, route that question to the organizer without adding a new promise to the notice.
Use a stable update route on optional printed information
A dry indoor information-card option
These custom rack cards for event update information list 3.74 × 8.27-inch paper cards, 14pt as the default and a minimum allowed quantity of 50. The small image is an AI artwork concept.
Compare custom rack cards for event information or discuss the actual artwork with DecentCustom. Keep the maintained update destination readable; this ordinary paper card is not a weatherproof outdoor sign or a live status display.
Existing digital information and replaceable paper may already cover the job. New print should serve a verified distribution need, with someone responsible for keeping its destination current.
Official event information and the linked product checked November 13, 2026. Sunbreak and its completed update workflow are fictional. Real changes require the actual organizer's announcement; this guide does not assess weather or establish a cancellation, refund or attendance outcome.
