1. Make the hold clear
Say which part of the event is paused and whether drivers should stay ready or wait for another call. Give an update point you can keep, even if the restart time is still uncertain.
Choose one staff member to communicate the current plan. Different estimates from several channels make it harder for drivers to know which message to follow.
2. Confirm the next action before restarting
Check the active group, the next driver and any outstanding decision with the people responsible. Avoid making several schedule changes while different staff are still working from the old plan.
Tell drivers when the hold ends and what they need to do. A server change or on-screen graphic alone may not explain a revised schedule.
3. Resume the routine calls from confirmed information
Live Judging keeps the run order and competition state in one Sheet. In-Game Announcer uses the selected driver to make routine server-chat calls.
Discord Group Announcer can post the group call when a configured server group changes. Staff still explain the hold and confirm the restart; the tools reduce the repeated announcements once the event is ready to continue.
Before your next event
Readiness checklist
Tick these as you prepare, or print a copy for your team. This site does not save your ticks.
Keep the checklist
A simple copy for your team, ready to open in Google Sheets or Excel.
Common questions
Will the announcers detect an event delay?
No. They follow configured competition or server state. Staff need to coordinate those inputs and explain any hold or schedule change.
Should we keep changing the estimated restart time?
Share a restart time when you can support it. Otherwise give a clear next update point and tell drivers whether they should remain ready.
