Skip to content

What Race Engineer and TeamManager do today

Race Engineer runs on the driver's PC. TeamManager is where the team prepares and follows the race. I am building both, and both are in Alpha.

A local engineer for the driver.

Ask by push-to-talk, without taking your hands off the wheel. Race Engineer answers from your live iRacing data and is built to say when it has none, instead of guessing. It is in a closed Alpha.

  • Fuel left and needed, laps, lap times, position, gaps, flags, weather and the forecast
  • Advisory pit and tire answers, and fuel to save per lap for an extra lap
  • Automatic calls: cars alongside, flags, low fuel, position changes and close fights
  • Pit service by voice, only after a read-back and your "yes"
  • Push-to-talk on a wheel button or key
  • Race Engineer checks pit commands on your PC before they reach iRacing
  • Works without TeamManager
  • Opt-in Voice Cloning, recorded or imported on your PC
Race Engineer on the Race Ready page: the recent radio exchanges and the readiness checks.
Demo data

Prepare the race in the browser.

TeamManager is in early Alpha: usable today, with rough edges, and open to approved Alpha testers. It holds your events, driver availability and stint plans, adds the league field from published results, and shows the race live on the Pitwall.

  • Overview: your iRacing profile, statistics and race history (needs a connected iRacing account)
  • Planning: an event list, and one tabbed workspace per event for setup and strategy, drivers, the stint schedule, notes and weather
  • League planning with opponent pace and favorite drivers
  • Pitwall: a read-only live view with timing and your car's observed fuel use per lap
  • In the app: release history with notes, and settings for your iRacing connection and display preferences
  • Next: a plan that updates with fuel use
TeamManager event workspace: stops, laps per stint and expected finish, with the six-stint plan.
Demo data

Ask in your own words.

Race Engineer understands everyday wording as well as fixed phrases. The installer includes a small on-device model (about 23 MB) that recognises what you asked. If it cannot load, Race Engineer falls back to fixed rules. The model does not write the answers. Each answer starts with the fact and its value, and says when data is unavailable.

  • Understands what you mean and asks back when unsure
  • Says so when it has no data
  • Simulator commands need a clear, complete request and your confirmation
  • In the app's Advanced tab you can customise what the engineer says and which phrases it understands

Share live data with Relay.

TeamManager Relay is a small read-only Windows tray app (download) that sends your live iRacing race data to TeamManager so the team can watch it on Pitwall. It is not Race Engineer and cannot control the simulator.

  • You do not need Relay if you run Race Engineer. Once it is connected to TeamManager, Race Engineer sends the same live telemetry itself.
  • Relay is only a telemetry sender. It has no voice, no radio and no fuel or pit advice.
  • Read-only: it cannot control the simulator.
  • It sends live data only while a planned event matches your session, after you accept a short data notice on your PC.
  • You can stop sharing at any time.
Race Engineer desktop app on the Race Ready page: readiness checks for iRacing, telemetry, speech and TeamManager, the recent radio exchanges and the current session. (opens the full-size image)
Race Engineer · Race ReadyDemo data
TeamManager Telemetry: two laps of a demo circuit overlaid on synced speed, pedal and delta charts, next to the track map. (opens the full-size image)
TeamManager · Telemetry analysisDemo data
TeamManager team event workspace: a stint plan with drivers, stints and the fuel and strategy figures for the race. (opens the full-size image)
TeamManager · Team event planningDemo data

What can I ask Race Engineer?

Ask in your own words. Open a card to see example questions. Answers come from your live iRacing data; when Race Engineer has none, it says so.

Fuel

6 examples
  • "How much fuel do I have left?"
  • "How many laps of fuel?"
  • "How much fuel do I need to finish?"
  • "How much fuel should I save each lap to get an extra lap?"
  • "How much fuel should I add?"
  • "How much fuel for a 60 minute race?"

Without live data, your practice history can answer duration questions. Those answers are labeled advisory.

Pace and session

5 examples
  • "What was my last lap?"
  • "What's my best lap?"
  • "Fastest lap in the session?"
  • "How many laps are left?"
  • "How much time is left?"

Position and opponents

5 examples
  • "What position am I?"
  • "Who is ahead?"
  • "What's the gap to the car ahead?"
  • "Who is P3?"
  • "What's my safety rating?"

Flags and weather

4 examples
  • "Current flags?"
  • "Do I have a penalty?"
  • "How many incidents?"
  • "Is the track wet?"

Weather forecast

2 examples
  • "Will it rain?"
  • "Rain forecast"

Race Engineer uses the forecast iRacing published for your race slot. For hosted and league sessions, TeamManager needs to have that forecast.

Track state

2 examples
  • "Track state"
  • "How much rubber is down?"

Pit and tires

4 examples
  • "When should I pit?"
  • "When is my stop?"
  • "How are the tires?"
  • "Where will I rejoin?"

Pit and tire answers are advisory.

Radio and app

8 examples
  • "What can I ask?"
  • "Say again"
  • "Stop talking"
  • "Spotter off"
  • "Mute traffic"
  • "What is muted?"
  • "Gaps every two laps"
  • "What is 3.45 times 12?"

Under Engineer › Each announcement, every call has its own level, and you can switch calls off by voice, for example "mute traffic" or "blue flags off". Safety calls always stay on: yellow and black flags, low fuel and penalties.

Pit service by voice

5 examples
  • "Set fuel to 42 litres"
  • "Add 15 litres"
  • "Change all four tires"
  • "Change to wet tyres"
  • "Set left front to 27 psi"

Calls without a question

10 calls
  • Cars left, right and alongside
  • Flags, with a clear call when they clear
  • Low fuel, with a countdown at 3, 2 and 1 laps left
  • The pit countdown, from 10 seconds out: "5, 4, 3, 2, 1, box now"
  • Trouble ahead, such as "Car off ahead" or "Car stopped ahead", with a short follow-up on how far ahead and the car's position
  • Your position changes and close fights with the cars around you
  • A tire check when you are in the pit box (set it to High under Engineer › Each announcement)
  • In races, rain expected in about 3 laps (or minutes), with one reminder shortly before
  • Rain no longer expected, once the forecast clears
  • The gap to the car ahead and the car behind with its trend, every 1, 2, 3 or 5 laps (off by default)

Race Engineer prepares urgent calls when you get Race Ready, so they play without delay.

Race Engineer always asks before it acts, and nothing is sent to iRacing until you say "yes". Fuel, tire, pressure, fast-repair and tear-off requests are read back first. Say "no" or "cancel", or wait 30 seconds, and nothing is sent. Race Engineer does not carry out requests that mix several actions or ask for impossible values. Voice commands cover fuel, tires and pressures, fast repair and tear-off. Tire compound: say for example "change to wet tyres"; Race Engineer checks the car has that compound, reads it back and waits for your yes.

With an event selected and linked in TeamManager, Race Engineer reads the accepted plan at the start. Ask "briefing" or "read the plan", or "who drives next". It does not control the camera, setup or driver swaps.

What works today, and what comes next.

No promised dates.

In Alpha testing

  1. Local Race Engineer

    Answers about fuel, pace, gaps, opponents and pit stops from your live iRacing data.

  2. Push-to-talk questions

    Press a wheel button or key and ask. Answers come back over the radio.

  3. Ask in your own words

    Race Engineer understands what you mean, asks back when unsure, and says so when it has no data.

  4. Fuel and pit strategy

    How much fuel to save per lap to gain a lap or skip a stop, and when your pit window opens.

  5. Spotter calls

    Calls for cars alongside, flags, race control and hazards ahead, such as a car off or stopped on track.

  6. Weather forecast

    Race Engineer uses the forecast iRacing published for your race slot and warns in races when rain is coming.

  7. Voice Cloning

    Opt in to make your engineer sound like someone you know. You record or import the sample on your PC.

  8. Team planning

    Events, driver availability and stint plans in one shared workspace, plus an Overview of your iRacing profile and race history once your account is connected. Usable today, with rough edges.

  9. Sharing live data

    TeamManager Relay, a small read-only tray app on the Downloads page, sends your live race data to TeamManager so the team can watch it on Pitwall. It has no voice, gives no advice and cannot control the sim.

  10. Pitwall

    A read-only live view with timing, the track map, a class board and save-or-stop fuel advice. Early Alpha, incomplete.

  11. League planning

    League sessions and field context from published results, with favorite drivers. Early Alpha.

  12. Rejoin prediction

    Race Engineer estimates where you rejoin after a stop.

  13. Plan vs race

    The Pitwall plan table compares planned and actual stints, fuel and stops.

  14. Weather in the plan

    Planning sheets show the iRacing weather and a weather timeline.

Coming next

  1. Team strategy updates

    Fuel and pit numbers from the car keep the shared plan up to date as the race changes.

  2. Strategy options

    Build and compare strategy options before the race.

The FAQ has short answers about the Alpha and your PC.

Want to test it?

Race Engineer is in a closed Alpha. Write to me and I will let you know when there is room.