How to Run an iRacing League

To run an iRacing league, decide on a format and ruleset, build a season schedule of rounds, open driver registration, and pick a scoring system. On race day you run sessions and apply flags or penalties, then after each race you import the iRacing results, publish official standings, handle any protests, and communicate with your drivers.

That is the whole loop, and it repeats every week. The hard part is not the racing — it is the administration around it. Below is how to do each piece well, and where a platform like Racey does the bookkeeping for you so you can focus on the community.

Plan your league and ruleset

Before you create a single calendar event, decide what kind of league you are running. The three questions that shape everything else:

Discipline and car class. Road, oval, dirt, endurance, or multiclass. Pick one to start. A focused single-class series is far easier to fill and run than an ambitious multiclass grid you cannot populate.
Skill level and culture. Open-entry casual, or invite-only competitive? This sets your code of conduct, your stewarding strictness, and the kind of driver you attract.
Cadence. Weekly is the most common and the most sustainable. A fixed night ("Tuesdays, 8pm ET") becomes a habit drivers protect.

Then write a real ruleset. At minimum it should cover: minimum incident/safety expectations, qualifying and race format, pit and tire rules if any, the penalty ladder stewards may draw from, and the protest process. Drivers behave better when the rules are written down and applied consistently — ambiguity is what turns a clean league into a Discord argument.

In Racey, the code of conduct and custom rules live on the league itself, and drivers must accept the code of conduct when they register, so there is a clear record that everyone agreed to the terms. The full setup walkthrough is in the League Admin Guide.

Build the schedule

A season is a series of rounds, each with a track, a date and time, and a format. When you build your schedule, keep these things in mind:

Commit to dates early. Drivers plan their week around your calendar. Publishing all rounds up front, even if some details change later, dramatically improves attendance.
Mix familiar and fresh. A schedule of all-time-favourite tracks is safe but stale; one or two wildcard rounds keep things interesting without alienating regulars.
Account for endurance specials. If you run a longer feature event, decide in advance whether it carries extra championship weight.

Racey's schedule builder lets you add each round with its track, date/time, and configuration details, and reorder or edit rounds any time before they are completed. Because the schedule is structured data rather than a pinned Discord message, your standings, broadcast overlays, and driver notifications all stay in sync with it automatically.

Driver registration and rosters

Stop running registration through direct messages and a spreadsheet. A self-serve registration flow saves you hours and removes the "did you get my sign-up?" back-and-forth.

When you open a season for registration, drivers apply through your league's season page. Each application captures:

Car number — checked for conflicts so two drivers cannot claim the same number in one season
Car class — for multiclass seasons
Team assignment — if you run teams
Code of conduct acceptance
Entry fee payment — if you have configured one

You (or a delegated race director) then approve, deny, or waitlist each application, and drivers are notified of the outcome. You can also bulk-invite a roster from last season by email so returning drivers do not start from scratch.

Linking iRacing identities

This is the step that makes automated results possible. Each driver saves their iRacing Customer ID on their profile. Later, when you import a results CSV, the platform matches finishing rows to the right drivers by that ID — no manual name-matching.

One honest note on iRacing integration: today the connection is manual Customer ID linking plus CSV import. Automatic profile sync and direct session import are built around iRacing's OAuth access, which is paused industry-wide while iRacing is not issuing new OAuth client access. So the reliable workflow that works for every league right now is Customer ID linking and CSV import, covered in detail below.

Choose a scoring system

Your scoring system is the spine of the championship. Get it right and the title fight stays alive to the final round; get it wrong and someone clinches with three races to spare.

A few principles:

Reward finishing and consistency, not just winning. A points curve that is too top-heavy punishes the entire midfield for one driver's dominance.
Drop weeks keep people in it. Excluding each driver's worst one or two rounds means a single disconnect or a stewarding penalty does not end someone's season — which keeps grids full late in the year.
Bonuses should reflect your values. If you care about clean racing, a clean-race bonus (zero incidents) literally pays drivers to race cleanly.

Racey ships with scoring presets modelled on real series — F1, NASCAR (with stage points), IndyCar, IMSA/WEC multiclass, GT3 Sprint, Oval Weekly, Road Weekly, and Heat + Feature — available on every plan. On the Pro plan you can build fully custom configurations: any position-points array, bonuses (pole, fastest lap, most laps led, most positions gained, clean race), drop weeks, stage points, multiclass scoring, team scoring, and automatic half-points for shortened races.

Whatever you choose, the important thing is that points are computed the same way every single week. Every point Racey awards is logged with a full breakdown showing exactly how it was calculated, so when a driver asks "why do I have 47 and not 48," you have the receipt instead of re-checking a spreadsheet formula.

Race-day operations (race control)

Race day is where leagues either feel professional or feel improvised. The difference is having a single source of truth for the session state instead of a flurry of Discord messages.

Good race-day operation means one person — a race director or clerk — is responsible for:

Calling the session through its phases (formation, green, yellow, safety car, red, finish)
Logging incidents the moment they happen, with the driver, lap, and what occurred
Issuing any in-session penalties (drive-through, stop-and-go, time penalty, grid drop)
Posting clear, timestamped messages to drivers

Racey's Race Control panel (included with Pro) gives you exactly this surface. The session moves through an enforced state machine — illegal jumps (like reopening a finished session back to green) are rejected, so the live race state stays trustworthy. Incidents you file carry their context straight into stewarding. In-session penalty points roll up to the championship ledger automatically. And every flag, penalty, and message is written to an immutable event log, so after the race you can resolve a dispute from the actual sequence of events instead of someone's memory.

If you are not on Pro, you can still run race day the manual way — the key habit to build is writing incidents down as they happen, because nobody remembers Lap 14 accurately by the time the protest comes in.

Stewarding and protests

Stewarding is the single biggest reason drivers quit leagues. When people feel the calls are unfair or arbitrary, they leave — and they tell their friends. A structured process fixes this.

The principles worth borrowing from real motorsport:

Independence. Stewards should not be the same people racing for the win that night.
Anonymity in deliberation. When stewards see driver names, reputation bias creeps in — the fast, popular driver gets the benefit of the doubt.
A fixed penalty ladder. Define the possible penalties before the season so outcomes are predictable.
Consistency. Similar incidents should get similar penalties, week to week.

Racey includes a stewarding system built on these ideas. Basic stewarding — filing protests, issuing rulings, and applying penalties — is available on every plan. On Pro you also get blind review (stewards see "Driver A" and "Driver B," not names), independent voting so panelists do not anchor on each other, an appeals process routed to a separate reviewer, and penalty-points tracking. The system also flags conflicts of interest when you assign a panel, like a steward who shares a team with an involved driver.

A practical recommendation: appoint three to five stewards so you can field a panel without overloading any one person, and choose people who can be objective and write a reasoned decision. The full role walkthrough is in the Steward Guide.

Publishing results and standings

After the race, get the results in and make them official. With iRacing this is a CSV workflow:

Export the session results CSV from iRacing.
In your league's Results section for that round, upload the CSV.
The platform matches finishers to drivers by their linked iRacing Customer ID. Any unmatched rows are flagged for you to resolve manually.
Review, then publish the round as official.

When you publish, championship standings recalculate automatically, drivers are notified, your Discord post fires if you have that configured, and broadcast overlays update with the new data. Results move through clear states — pending, reviewed, official, locked — and every correction after publishing is tracked with what changed, who changed it, and why.

This is the part that most obviously beats a spreadsheet: you never hand-compute a points table again, and you cannot accidentally ship a standings page with a broken formula. For the step-by-step on file formats, column mapping, and resolving unmatched drivers, see the Results CSV Import Guide.

Broadcasting (OBS overlays)

A broadcast turns a private race into content that grows your league. You do not need a production studio — you need OBS and clean on-screen graphics.

Racey provides six professional OBS browser-source overlays (on the Pro plan):

Timing Tower — live positions and gaps
Championship Standings — the title table as a lower third
Driver Card — an intro graphic with a driver's stats
Battle Tracker — gap analysis on the closest on-track fight
Fastest Lap — a highlight when the fastest lap changes hands
Incident Ticker — a live feed of stewarding notices

Each overlay is a web URL you add to OBS as a Browser Source at 1920x1080 — no plugins, no extra software. They update in real time over Server-Sent Events, so as soon as you publish results or a position changes in Race Control, the graphics reflect it. For private leagues you can protect overlay URLs with a signed token so only your broadcaster can load them.

Broadcasting tip: even a basic stream with a timing tower and a standings overlay looks dramatically more legitimate than a raw screen capture, and that perceived professionalism is what convinces new drivers to sign up.

Collecting entry fees

Entry fees fund prize pools, cover costs, and — honestly — increase commitment, because drivers who paid show up. The problem has always been the chasing: Venmo screenshots, PayPal notes, and a spreadsheet column nobody keeps current.

Racey handles this with Stripe Connect (on the Pro plan). You connect your own Stripe account, and entry fees are charged to drivers at registration and land directly in your account — Racey takes zero commission and never touches the money. You pay only Stripe's standard processing fees. You can set per-season fees, add coupons or early-bird pricing, track who has paid, and issue refunds through your connected account when needed.

Because payment is collected as part of the registration flow, "did everyone pay?" stops being a question you have to ask.

Growing the league

The operations above keep a league alive; growth is what makes it thrive.

Make your league public and easy to find. A public league page that shows your schedule, standings, and roster is a far better recruiting tool than a screenshot in a Discord server.
Be consistent. Same night, same format, results published promptly, stewarding applied evenly. Reliability is underrated — drivers stay where they know what to expect.
Broadcast and clip. A short highlight from last week's last-lap pass does more recruiting than any amount of "we're recruiting!" posting.
Reduce friction for new drivers. Self-serve registration, a clear ruleset, and a welcoming code of conduct lower the barrier to that first race.

Retention beats acquisition every time. A league that runs cleanly and fairly, week after week, grows mostly by word of mouth — which is exactly why getting the operations right is the growth strategy.

Start your league

You can run a real iRacing league on Racey's Free plan today — one league, unlimited drivers and seasons, the scoring presets, standings, CSV import, and basic stewarding, with no trial and no credit card. When you want custom scoring, Race Control, blind-review stewarding, OBS overlays, Stripe Connect entry fees, and unlimited leagues, Pro is $4.99/month. See the full breakdown on the pricing page, or jump straight into the admin feature tour and create your first season.

Run the racing. Let the platform run the bookkeeping.