Coordinating multi-driver endurance races on iRacing used to mean messy spreadsheets, frantic math in Discord, and mistimed driver swaps. iEndurance emerged to solve this exact headache, offering a specialized web-based stint planner built for long-haul racing. Instead of guessing fuel windows or tracking driver minimum times manually, teams can map out an entire 12-hour or 24-hour event in one unified dashboard.
Understanding how to leverage tools like iEndurance can mean the difference between a podium finish and running out of fuel on the back straight. This breakdown covers core functionality, setup mechanics, and tactical advantages for sim racing teams.
What is the iEndurance Stint Planner?
The platform is a dedicated web utility designed to simplify race strategy for events where timing, fuel consumption, and driver rotation dictate the outcome. Endurance racing requires cars to cover maximum distance with minimal stops. Calculating average lap times, pit lane delta times, and maximum fuel capacities across changing track conditions is notoriously error-prone when done on the fly.
The application functions as a centralized hub where team managers input baseline metrics—such as fuel per lap, tank capacity, estimated lap times, and total race duration—to generate a complete stint-by-stint projection.
Core Features and Strategy Design
Building an effective race strategy requires precise inputs and a clear understanding of how the tool models race progression.
- Fuel Window Calculations: The calculator estimates exact pit stop windows based on consumption rates, helping teams avoid short-fueling penalties or unnecessary splash-and-dash stops.
- Driver Rotation Tracking: Official series have strict rules regarding minimum and maximum driving time. The planner monitors driver stints to ensure compliance and prevent disqualifications.
- Real-Time Adjustments: As track temperatures shift and lap times drop or climb during a race, strategy logs can be updated to recalibrate remaining stints.
Setting Up Your First Race Plan
Configuring a session inside the platform takes only a few minutes if you gather your team data beforehand.
- Input the total race duration (e.g., 6 hours, 12 hours, or 24 hours).
- Enter your car class fuel tank limits and average fuel consumption per lap gathered from practice sessions.
- Assign available drivers and note any mandatory rest or driving time constraints specified by the iRacing Sporting Code.
- Generate the baseline schedule and share the session view with your teammates so everyone knows their expected jump-in times.
Common Mistakes to Avoid
Even with automated planning software, teams often run into avoidable pitfalls during endurance blocks.
- Ignoring Track Evolution: Relying purely on clean-air practice lap times will throw off your fuel windows once traffic and rubber buildup alter grip levels. Always build a safety margin into your fuel calculations.
- Failing to Account for Safety Cars: Full course yellows or safety car periods alter consumption rates drastically. Don't assume green-flag projections will hold true across a chaotic multi-class race.
- Overlooking Driver Fatigue Windows: Scheduling a driver for maximum allowable stints back-to-back often leads to compounding concentration errors in the final hours.
Frequently Asked Questions
Is iEndurance free to use?
The platform offers free core features designed to help teams plan and execute standard endurance races, alongside optional supporter tiers for advanced server upkeep.
How does it handle driver change rules?
You input each driver's availability window and the series' regulatory limits, and the planner maps out legal stint lengths to maintain rule compliance.
Can I update the strategy mid-race?
Yes. As lap times fluctuate due to weather or tire wear, modifying your baseline metrics updates the subsequent stint projections instantly.
Does it integrate directly with iRacing telemetry?
The tool operates primarily as a strategic web planner and calculator rather than an overlay telemetry suite, requiring manual input of practice or telemetry averages.
