A race weekend in Stintsmith is four surfaces stitched together: Races (you schedule it), Stint Planner (you decide how to spend the fuel and the tyres), Pit Wall (you run the race from the phone), and the lap review (you find what to fix). The point of this guide is the seam between them — what you do on each surface, in what order, so the next race feels like a process rather than a panic.
Everything below assumes the Companion is installed and paired, you have at least one teammate on the roster, and you have run a handful of practice laps at the track so the system has something to anchor a stint plan on. If any of that is missing, the surface nudges you back to it; nothing here is destructive.
Schedule the race
Open Races → New race and the form is intentionally short: a name, a track and layout, a car class, a start time, and a duration. Pick whichever stint length the league mandates. Save, and the race lands on the team timeline in the locked state scheduled. From here the team can RSVP — every driver gets a small RSVP card on the Pit Wall, and the captain’s race detail page shows the in/out counts in real time.
If you are running an endurance race, set the duration to its real length (six hours, ten hours, twenty-four) rather than the number of laps. The planner reasons in clock time, not lap count, because that is how fuel windows actually decompose. A 24-hour race with the wrong wall-clock value will produce a stint plan that lies politely.
Build the stint plan
Open the race’s Stint Planner tab. The planner shows a stint Gantt across the duration of the race, with a parameter block above it. The parameters are iPredictor-style — manual numbers you can paste in if you already know them, with a one-click auto-fit button that lifts them out of practice telemetry once the Companion has captured eight or more clean laps at the track.
The four parameters that actually move the plan:
- Base lap (dry / wet). The lap time you can hold on green tyres, a low fuel load, race traffic. Conservative beats heroic — the planner derives the stint window from this, and an over-optimistic base lap fuels you short.
- Fuel per lap. Litres burned per green lap, measured at race pace. Pull from practice unless the car has a known fuel-mode shift between qualifying and race.
- Tyre degradation. Seconds added per lap as the tyre falls off. Once the curve is steeper than the cost of an extra stop, the planner will offer a shorter stint shape. Trust it; the maths is more honest than the heat-of-the-moment instinct to double-stint.
- Pit-stop loss. The total wall-clock cost of a stop on this layout — pit-lane delta plus the fuel and tyre service inside the box. The default is the published Le Mans Ultimate baseline for the layout; bump it if your team is slow on the stop.
With the parameters set, drag stint boundaries on the Gantt. Each stint inherits a driver, a tyre compound, and a fuel load. The planner colours warnings inline — short on fuel, tyres past their cliff, driver over the per-stint cap — and a Limited data badge appears next to any number the system was not confident in. Save a variant when you are happy with it; you can save several and bring two side-by-side into the debrief.
Run the race
Once the race starts, the Pit Wall card becomes the room. On the phone, the race’s live card shows the current stint, the projected pit window, the gap to the cars ahead and behind in class, and a small live timing strip. The card updates from the Companion stream — your live telemetry is feeding the same data the strategist sees, so when someone says box, box, both of you are looking at the same numbers.
On the desktop, the captain or strategist opens /strategy/<raceId> and gets a four-panel live view: stint plan on the left with the active stint highlighted, a fuel and tyre projection on the right, a deltas-to-rivals stack across the bottom, and the live track map on top. The view edits in place — if a safety car upends the plan, drag the next stint shorter and the Pit Wall card on the driver’s phone updates immediately.
Debrief
When the chequered flag drops, the race page collects everything: results, every lap from every stint, the variant you actually ran versus the variants you planned, and the telemetry traces from each driver. The lap list lets you pull two laps into the Lab — the in-app comparison tool — to find the corner that costs you, or to drop a note on the lap that finally got it right. Save the notes against the lap, not against the race; that way they live with the data that produced them and resurface the next time the team practises this layout.