How many judges does a drift competition need?

Three is common because it gives a clear majority in battles. Smaller events can run with fewer, but a single judge makes decisions harder to trust.

What software do I need to host an Assetto Corsa drift event?

An Assetto Corsa server (Content Manager's server manager or dedicated community server software), a judging sheet, Discord for communication and OBS for streaming. Tools like Event Toolkit connect these so updates happen automatically.

How long does a drift competition take?

Plan for several hours: briefing, practice, qualifying, a break to build the bracket and switch servers, then battles. Bigger brackets take longer.

Should I charge an entry fee?

That's up to you. If you do, publish your refund and withdrawal rules before entries open and keep payments linked to each driver and event.

How to Run Your Own Assetto Corsa Drift Competition

Running a drift competition means coordinating drivers, judges, servers and a stream at the same time. Here is what's involved and where most of the work goes.

Key takeaway

Write your format and rules first, build a small crew with clear roles, and automate the repeated updates.

1. Decide your format

Start with the basics, and write them down before anything else:

Single events or a season? A season keeps drivers coming back but needs a points system and tiebreakers.
Qualifying: how many runs per driver (two is common) and how ties are broken.
Bracket size: Top 16 or Top 32 are common, with a plan for byes when fewer drivers qualify.
Car rules: open cars or a standard physics set, and how cars are inspected.
Who can enter: open sign-up, applications or invitations.

2. Publish clear rules

Most disputes come from rules drivers didn't know about. Publish, in plain language: the event format, judging criteria, car requirements, start procedure, what happens on disconnects and restarts, conduct expectations, and how drivers can ask about a decision afterwards. EFVD's Competition Guide and Judging Guide are a full example; Event Toolkit has a free guide on writing clear drift competition rules.

3. Build your crew

Role	Responsibilities
Organizer	Schedule, entries, servers and final decisions.
Judges	Score qualifying and decide battles, ideally three for a clear majority.
Marshals	Call drivers, manage the start line and Discord voice.
Inspectors	Check car files before the event.
Broadcast	Stream, overlays, replays and commentary.
Social media	Announcements, grid reveals and results posts.

4. Take entries and payments

Collect each driver's name, Steam ID, Discord account and car in one place. If you charge an entry fee, connect each payment to the right driver and event, and write down your refund rules before entries open. Manual spreadsheets work for a few drivers but get error-prone quickly.

5. Check cars

Car files cause many event-day problems. Set a submission deadline, check physics, file structure, textures and optimization, and give drivers clear feedback early enough to fix issues.

6. Prepare servers

You'll typically need a practice server and a competition server, often reconfigured between qualifying and battles. Content Manager includes a server manager, and many organizers use dedicated community server software. Build your server entry list from your confirmed entries so the right drivers and cars are allowed in.

7. Run the judging

Give judges a shared scoring sheet and agreed criteria, and make sure scores flow quickly into qualifying results and the bracket. Read our guide to drift judging for the standard criteria.

8. Keep drivers informed on Discord

Drivers need to know when their group is up, who's next and what the result was. Discord roles for qualifying and battle groups, targeted group calls and live leaderboards cut down on repeated messages.

9. Broadcast the event

A stream makes your event worth watching and attracts new drivers. OBS overlays showing the current drivers, scores and battle results, plus replays, make it much easier to follow, but updating them by hand during a live event is a full-time job.

10. Rehearse, run, review

Do a short rehearsal before your first event to test the handoffs between judging, announcements and the stream. After each event, pick one improvement for next time. Then share results, highlights and driver graphics to keep the community engaged.

What to automate

Most of the work above is repetitive: copying scores into overlays, updating the bracket, changing Discord roles, rebuilding server entry lists, matching payments and posting results. That's where organizers lose the most time, and where mistakes creep in during a live show.

Event Toolkit is a modular set of tools for exactly these jobs, built from the tools that run EFVD's own championship: live judging, broadcast overlays, replays, registration and payments, car checks, server presets and Discord automation. It runs on your own accounts, so you keep your data. Its free organizer guides go deeper into each step.

Frequently asked questions

How many judges does a drift competition need?: Three is common because it gives a clear majority in battles. Smaller events can run with fewer, but a single judge makes decisions harder to trust.
What software do I need to host an Assetto Corsa drift event?: An Assetto Corsa server (Content Manager's server manager or dedicated community server software), a judging sheet, Discord for communication and OBS for streaming. Tools like Event Toolkit connect these so updates happen automatically.
How long does a drift competition take?: Plan for several hours: briefing, practice, qualifying, a break to build the bracket and switch servers, then battles. Bigger brackets take longer.
Should I charge an entry fee?: That's up to you. If you do, publish your refund and withdrawal rules before entries open and keep payments linked to each driver and event.

How to run your own drift competition