Endurance sim-racing · Driver scheduling
A driver rotation.
Not another spreadsheet.
Plan around your team's availability and timezones. Generate a starting schedule, see each driver's time, and spot coverage gaps before race day.
Race setup is free. Sign in to save your plan.
Make the handoff clear
- Who can drive?Bring availability into the plan, not a separate chat thread.
- Whose local time?Review the same schedule in a driver's timezone.
- What needs attention?Check driving totals and warnings, then adjust individual stints.
Three hours. Two drivers. One shared clock.
A fictional race and roster, not a live session. All schedule times below are on in UTC (UTC+00:00).
Saturday endurance practice
Fully covered in this example- Green flag · UTC
- Checkered · UTC
- Total driving
- 2h 58m 5s
- Uncovered
- 0m
- 01
Alex
Double · two fuel runs
- Start · UTC
- End · UTC
- Driver total
- 2h
Includes one 30-second refuel. Then allow 1m 25s for the change from Alex to Sam.
- 02
Sam
Single · one fuel run
- Start · UTC
- End · UTC
- Driver total
- 58m 5s
No in-stint refuel. This shorter final stint reaches the checkered flag.
The arithmetic: 2h 58m 05s driving + 30s in-stint refuel + 1m 25s driver change = 3h. Normal service counts toward coverage, but not driving totals.
Session start is 17:50 UTC, with a 10-minute green-flag offset. Each fuel run allows up to 60 minutes of driving. Both drivers are available throughout; the race uses a double-stint preference, no total driving cap, and no minimum-time target.
Same race, local clocks. The 18:00–21:00 UTC race window is 18:00–21:00 for Alex in Europe/London and 13:00–16:00 for Sam in America/New_York on this date.
A starting point, not equal-time optimization. The preference gives Alex a double; Sam gets a shorter single at the end. Review the totals against your team's needs.
From race window to reviewed rotation.
- 01
Set the race window
Add a race name, track, session start, and duration. Duration runs from green to checkered; use the green-flag offset if the session starts earlier.
- 02
Add drivers & availability
Add at least two drivers, their timezones, and when they can or cannot drive. No availability records means available for the whole race.
- 03
Generate a starting schedule
Generate around availability, stint preferences, and driving limits. The generator is a deterministic heuristic, not a guarantee of equal time or complete coverage.
- 04
Review & adjust
Check the timeline, per-driver driving totals, and coverage warnings. Edit a stint's driver, type, start, or end, or delete a stint without replacing the rest.
Changing race settings or availability does not automatically rerun generation. Review the stored schedule after changes. If you regenerate, the new schedule replaces it and discards manual edits.
Move one stint. See what it leaves uncovered.
Suppose Sam needs to start ten minutes later. Edit only Sam's start time, keeping the 21:00 end and Alex's stint unchanged. The edit can be saved, but the gap needs your attention.
Before · Sam · UTC
20:01:55 → 21:00:00
58m 05s driving · no uncovered time
After · Sam · UTC
20:11:55 → 21:00:00
48m 5s driving · 11m 25s uncovered
Coverage warning: 11m 25s internal gap before stint 2.
Alex ends at 20:00:30. The interval until Sam's new start at 20:11:55 is 11m 25s, longer than the allowed 1m 25s driver change. The report therefore marks that whole interval as an uncovered gap, not normal service. Coverage is now 2h 48m 35s of 3h; Alex still has 2h of driving.
Review a different handoff or driver assignment to close the gap. The report updates after the edit and remains consistent on refresh; the app does not silently repair the rotation.
What to know before you plan.
Does it work with my simulator?
StintManager is a standalone driver-scheduling tool for endurance sim racing. You can use it to plan events in iRacing, Assetto Corsa Competizione (ACC), Le Mans Ultimate (LMU), or another simulator. It does not connect to those simulators and is not affiliated with them.
It is for preparation, not live race tracking, telemetry, fuel-strategy optimization, or enforcing your event's rules.
How do availability and timezones work?
Enter the session start in your browser's local timezone. Give each driver their own timezone and enter availability in that driver's timezone. On the schedule page, choose a driver's timezone to view the same stored instants on a familiar clock.
No availability records means available throughout. Adding available windows limits the driver to those periods; not-available windows subtract time. If you add only not-available windows, the rest of the race stays available. Daylight-saving repeated hours require an explicit occurrence choice when changed.
Can my teammates help?
The race owner can invite teammates by email with view, edit, or admin access. They must accept before gaining access. Editors and admins can adjust the race and schedule; a linked driver can update their own availability even with view access.
A permanent race unlock covers every collaborator. Only the owner can use the account's free race or a purchased credit; admin access does not transfer ownership.
What is free, and when would I pay?
Race setup, drivers, and availability are free. When billing applies, an owner who has not used their account's first-free-race allowance can use it on successful schedule generation. Later locked races need a purchased race credit. The race page shows the applicable unlock option, and prices are shown before payment.
A successful generation unlocks that race permanently, including regeneration and access for its collaborators under their assigned permissions. Failed or empty generation does not use the allowance or a credit. Deleting an unlocked race does not restore it. Already-unlocked or exempt races do not need another payment; billing availability and exemptions determine which terms apply.
Start with your next race.
Set the window, add your drivers, and turn the availability conversation into a schedule you can review together.
Already planning? Open your races or sign in.