Staff coordination

How to keep drift event staff handoffs clear

The short answer

Give each decision an owner and make the next step clear. Shared information reduces repeated questions, but staff still need to know when they can act on it.

1. Give each decision one owner

Agree who manages the run order, confirms the result and controls the broadcast. One person may cover several jobs, but each handoff should still be clear.

Use a simple signal for when a result is ready and when the next driver may be called. Do not make the producer infer a final decision from an unfinished staff conversation.

2. Keep everyone on the same event information

Point staff to the same current run order and results. Copying values into several private lists makes it harder to tell which version is correct after a change.

When handing over a role, state the active stage, the next action and any unresolved issue. The replacement should know what is waiting for a decision before touching the controls.

3. Let confirmed information feed the repeated outputs

Live Judging gives judges and operators a shared Sheet for qualifying and battles. Broadcast Overlays uses that data to update the show without someone retyping every result.

In-Game Announcer uses the live workflow for driver calls and supported result messages. Staff retain the decisions; the connected tools reduce the repeated copying and announcement work that follows them.

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 a small team need separate people for every role?

No. One person can cover several jobs. Make the responsibilities and order of actions clear so nothing depends on an unspoken assumption.

Will connected tools make the judging decision?

No. Judges and staff make the decisions. The tools record inputs and update supported outputs from the configured workflow.