How to run an F1 25 league
Most F1 leagues don't fold because of bad racing. They fold because the admin gets heavy: results in a spreadsheet, sign-ups in a form nobody checks, rules buried in a pinned message, and an argument after every incident.
This guide covers the decisions to make before round one and the weekly routine that keeps a season running — whether you run twelve drivers on a Sunday night or three tiers across two time zones.
Pick a format before you open sign-ups
Drivers choose a league by its race slot and its format, so settle these first and put them in your sign-up post.
- Race day and time.One weekly slot for the whole season, written with a time zone (“Sundays 20:00 UK”). Pick a slot that suits where most of your drivers live.
- Season length. Eight to twelve rounds is long enough for a title fight and short enough that drivers stay committed. Keep one or two spare weeks for postponements.
- Race distance. 25% races fit into about an hour with qualifying; 50% races reward tyre strategy but need closer to two hours. Use one length all season.
- Qualifying. One-shot qualifying keeps race nights short and is easy to steward. Short qualifying gives more running but takes longer.
- Car performance. Equal car performance makes driver skill the deciding factor. Real team performance makes team choice matter, so you need a fair way to assign seats.
- Platforms. If your drivers are on different platforms, say up front whether lobbies are cross-platform or each tier sticks to one.
With Pole Apex: The season calendar and race slot live on your public league page, and drivers see each race in their own time zone.
Write rules drivers will actually read
Short, numbered rules beat a long essay. Cover at least:
- Lobby settings: allowed assists, collisions, ghosting, corner-cutting stringency, parc fermé, car damage, safety car and weather. List the exact settings so any staff member can host.
- Points: most leagues copy the real F1 system — 25-18-15-12-10-8-6-4-2-1 for the top ten. Decide up front whether there is a fastest-lap or pole bonus.
- Attendance: how much notice a driver gives before missing a race, how many absences are allowed, and what happens after that.
- Reserves:whether a reserve's points count for the reserve, for the team, or both.
- Disconnects: for example, restart if it happens on lap one, otherwise the race stands.
- Conduct: behaviour on track and in Discord, and who to contact with a problem.
Version your rules (“v1.2, changed 14 March”) so nobody argues about which version applied to which race.
With Pole Apex: Publish your rules as text or a rulebook PDF, next to the points system and allowed assists for each tier.
Place drivers into fair tiers
Tiers keep races close. A two-second pace gap ruins the racing at both ends of the grid, and it's the fastest way to lose new drivers.
- Benchmark: ask for a time trial lap on a fixed track and set tier cut-offs from the spread of times you receive, not fixed numbers.
- Grid size: keep tiers even and as close to a full grid of 20 cars as you can.
- Promotion and relegation: decide before the season how many drivers move between tiers (for example the top two and bottom two), so moves are earned on track, not argued in DMs.
With Pole Apex: Each tier gets its own standings, points system and allowed assists, under one league.
Run driver sign-ups
Ask for what you need to place and contact a driver, and nothing else:
- In-game name or EA ID, and platform
- Availability for your race slot
- Time trial lap for tier placement
- Preferred tier and whether they'll race as a reserve
- Previous leagues, if any
Reply to every application within a few days, accepted or not, and post the lineup once teams are assigned. Fast answers are what turn applicants into regulars.
With Pole Apex: Application forms with your own questions. Applicants verify their email before the request reaches your join requests.
Run race night the same way every week
- Check-in: ask drivers to confirm attendance by a deadline, such as 24 hours before the race, so you can call up reserves in time.
- Lobby: open it 15 minutes early and check the settings against your rules before anyone joins.
- Race director: one staff member in Discord handles restarts, disconnects and questions during the race.
- Broadcast: if you stream, give commentators the grid and the current standings before lights out.
With Pole Apex: The driver check-in module sends email reminders before each race, and the broadcast module adds live overlays and team radio.
Post results and standings the same night
Enter results straight after the race while the screenshots are fresh: finishing order, retirements, and any in-game penalties. Then publish the updated driver and constructor standings with the race result.
Same-night results keep drivers talking about the race all week. Results that appear on Thursday don't. Update the calendar too, so the next round is always obvious.
With Pole Apex: Enter qualifying and race results; standings recalculate for every tier, and you can export results and standings as images for Discord.
Set up stewarding before the first incident
- Report window: incident reports within a fixed time after the race (24 hours is common), with a clip, the lap and the drivers involved.
- Panel:stewards who weren't involved in the incident, and at least two for each decision.
- Penalty guidelines: a published scale — warning, time penalty, grid drop, race ban — applied the same way every time. Penalty points that build up over a season deter repeat offenders.
- Decisions: publish every decision with a short reason. Drivers accept penalties they can follow.
- Appeals: one appeal per decision, to a different steward, with a deadline.
With Pole Apex: The penalty tickets module lets drivers upload incident videos and stewards issue decisions with PDF reports.
Pre-season checklist
- Race slot with time zone, season length and calendar published
- Lobby settings, points system and versioned rules published
- Tier cut-offs and promotion and relegation rules decided
- Sign-up form live, asking for platform, availability and a time trial lap
- Check-in deadline and reserve policy set
- Incident report process and penalty guidelines published
- A named staff member responsible for results and standings
Want the admin side handled? See what Pole Apex does for league owners, or browse leagues already running on it.