1. Decide what can change and until when
Tell drivers where to request an entry change and who can approve it. A registration deadline is easier to operate when staff also know how to handle a withdrawal or replacement.
Use the event’s published rules to decide the request. Avoid treating a Discord message or a new form submission as automatic permission to join a group already in progress.
2. Check the impact of the approved change
Confirm the correct driver and event, then review the entry record, group assignment and server access that may be affected. Tell the relevant staff what changed before making the next call.
If fees or refunds are involved, handle that decision under your stated policy. Keep the entry decision clear even when another staff member handles the payment follow-up.
3. Rebuild the repeated pieces from the corrected records
Applications & Event Registration holds driver profiles and event entries. Role Sync updates competition roles from Live Judging once the group information is correct.
Server Preset Manager prepares supported stage presets from the required competition and registration data, with a preview before deployment. It can reduce repeated preset edits; your operator still checks and deploys the intended change.
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
Can registration automatically approve a late entry?
A submission is not the decision. Staff apply the event’s rules and confirm whether the driver can join.
Does changing an entry update every other tool immediately?
Do not assume that. Group roles follow the configured Live Judging data, and server preparation and deployment remain operator-controlled steps.
