Tell Players When an Event Time Changes

When an event time changes, speed matters less than consistency. A fast message with the wrong time creates more work than a careful update that gives everyone one current answer.

Confirm the change before announcing it

Settle the new date or time, venue, check-in requirement, refund or withdrawal options, and anything that remains unchanged. Identify who approved the decision so staff do not reverse it after the first message.

For a weather delay, say when the next decision will be made if the replacement time is not final.

Update the source players can revisit

Change the event page, registration record, or other authoritative source first. Add a dated note that states the old arrangement, the new arrangement, and what the player needs to do.

Avoid sending only an image. Forwarded screenshots remain in chats after the source changes again.

Match the message to the consequence

A small change well in advance may need an email or event notification. A same-day cancellation should also reach registered players directly through the contact details they supplied.

No channel reaches everyone. Use more than one route when missing the update would cause travel, cost, or a lost place. Keep the wording identical and link back to the current source.

Prepare the front desk

Give staff the exact message and the list of affected groups. Record who still needs a direct call, especially juniors, visiting teams, or players without confirmed digital contact.

Smash lets clubs update a published event and send an optional notice to followers who can receive it. Followers are not the same as registered participants, so urgent changes may still require direct contact.

After the event, review who missed the update and why. The lesson may be a missing phone number, an outdated registration list, or too much reliance on one chat. Fix that before the next schedule change.