1. Separate “go now” from “get ready”
Drivers should be able to tell whether a message is calling them to the line or asking them to prepare. Use a consistent current-driver call and a separate next-driver call.
Explain the meaning during briefing. That makes each short message useful without staff repeating a full set of instructions before every run.
2. Keep the run order connected to attendance
A registered driver is not always present when their turn arrives. Keep attendance current so the team is not repeatedly calling someone who is absent.
Give one operator responsibility for selecting the current driver. After a delay or a change of plan, confirm that selection before resuming calls. Everyone should be working from the same run order.
3. Send the calls from the live Sheet
In-Game Announcer follows the driver selected in Live Judging. It sends the current driver to the line and tells the next driver in the same group to stage, skipping drivers marked absent.
It also posts qualifying scores, battle winners and One More Time results in server chat. Drivers can follow the outcome without staff typing each result separately.
Your operator still chooses when to move to the next driver. The tool handles the messages, so staff can focus on whether the event is ready for the next run.
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
Does entering a score automatically call the next driver?
No. Qualifying selection stays under operator control. The announcer follows the selected driver in the Sheet rather than advancing the run order when a score is entered.
What do we need for in-game announcements?
The module needs Live Judging and compatible AC Server Manager chat access. We confirm the setup before purchase.
