Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.
I've been racing with a spotter for two seasons now, and I spent the first season mostly ignoring half the calls. My crew chief would yell "box box" and I'd brake too early. He'd say "clear" and I'd still get turned around by a car I didn't see. The problem wasn't the spotter—it was that I didn't know what information I actually needed to act on in real time.
A good spotter call is like a good setup change: specific, actionable, and timed to when it matters. A bad one is noise that pulls your focus away from the apex. This post is about learning the difference, which calls drive your decisions on track, and how to tune your spotter audio so you can hear what counts.
The Calls That Actually Change Your Braking and Steering
Not every spotter transmission is born equal. Some calls require you to change your line, speed, or both. Others are just situational awareness. The critical ones—the ones that will cost you a position or a crash if you ignore them—fall into a narrow category.
Position and Closing Relative Speed
When your spotter says "car ahead, two car lengths, closing," that's a decision call. You need to know if you're on a collision course or if you have time to set up a move. On a road course like Spa or Suzuka, a car that's closing fast in a high-speed section might force you to lift earlier than your optimal line. On an oval, it tells you whether a pass is possible in the next few corners.
I pay closest attention to relative speed callouts in three-wide traffic or when I'm hunting someone down into a braking zone. "Car ahead, one length, same pace" tells me I'm going to need to wait for a real gap. "Car ahead, closing two tenths a lap" tells me I can be patient and set up a move. That's actionable. The call directly changes my decision-making.
Clear and Blocked
"Clear left, clear right" is the opposite extreme—it tells you that no one is there, not where they are. In iRacing, this call is most useful before a pass attempt or when you're defending and trying to commit to a late apex without worrying about a car you can't see in a blind spot.
"Blocked left" or "blocked right" is a hard stop. If you're about to move out to execute a pass or defend, and your spotter says blocked, you have to trust it and commit to your current line. I've found this call invaluable on narrow tracks like Monza or Long Beach, where side-by-side running is common and visibility is compromised.
- Closing relative speed (forces a line or braking adjustment)
- Clear/blocked (enables or stops a pass attempt)
- Gap size ("one car length" vs. "two lengths") (tells you if a pass window exists)
- Multiple cars ("two cars within a second behind") (changes your defensive strategy)
The Noise That Doesn't Change Anything
Every spotter mod has calls that sound important but don't affect your driving. Learning to filter these out is the second half of this skill.
Weather and Tire Temperature Reports
"Tires warming up" or "track temperature rising"—these are pre-lap information. If you're already racing, your pedal input and lock-up behavior tell you everything you need to know about grip. A call mid-corner about tire temps is late and won't change what you do right now. Save this callout for practice sessions when you're actively learning the car's envelope.
Fuel and Tire Wear Projections
"Fuel mileage looks good" is pit-lane intel. "You're on for a one-stop" is strategy, and it belongs in a pre-race briefing, not mid-race calls. If your pit crew hasn't told you a pit window before the race starts, you can't act on lap 23 when your spotter suddenly mentions fuel. I mute or ignore these unless I'm in an endurance race where fuel strategy actually changes in real time.
Encouragement and Vague Warnings
"Nice one!" and "stay focused" feel good, but they don't improve your lap time. "Be careful, there's traffic" is too broad—traffic where? If your spotter can't point you left or right, you still have to figure it out. I appreciate the effort, but I'd rather have a silent spotter than one that fills dead air with noise.
Check your crew chief mod settings. Most spotter packs (including the default crew chief) let you toggle which calls are active. Disable weather, fuel, and encouragement callouts. Keep only position, gap, and clear/blocked. Your audio bandwidth is limited when you're concentrating.
Timing: When the Spotter Message Arrives Relative to Your Action
A perfect spotter call at the wrong moment is useless. The delay between what the spotter sees and when you hear it, plus the delay between hearing and reacting, can be 0.5 to 1.5 seconds depending on your setup.
Braking Zone Calls
"Car ahead, closing, into the chicane"—this call needs to come at least two seconds before the braking zone. If your spotter calls it as you're entering the corner, you can't safely adjust your speed. On my rig with a ~9 N·m MOZA R9, I'm already committed to my brake pressure by the time most audio reaches my ears. The best spotters call threats two corners ahead.
Mid-Corner Calls
"Car left, car right" mid-corner is the worst timing. You can't change your steering input safely. These calls only work if they come on the straightaway before the corner or deep into the exit. A good spotter knows the track layout well enough to call threats with enough runway to react.
Straight-Line Calls
"Clear left" or "car right" on a DRS zone or acceleration zone is perfect timing. You have time to adjust your line without losing braking stability, and you can commit to a pass or defense with confidence.
Setting Up Your Crew Chief Audio for Maximum Signal, Minimum Noise
The default crew chief in iRacing works, but it treats all calls as equal importance. I've spent time tuning my setup to make critical calls stand out.
- Open the crew chief settings panel (press Ctrl+M in iRacing with crew chief loaded).
- Reduce the call rate. Set spotter calls to "cautious" mode if available—fewer calls, more meaningful ones.
- Disable messages you don't need: fuel, tire wear, weather, encouragement, setup feedback.
- Enable only: position calls, gap calls, clear/blocked calls, and incident warnings.
- Test your audio levels. Your spotter should be audible but not so loud that it startles you into a mistake.
- In multiplayer, consider voice comms over spotter calls if you have a real human spotting. Live human calls are faster than any AI.
I use the default crew chief on ovals (where position calls matter most) and disable it entirely in road-racing practice sessions where I'm learning the track solo. Once I'm comfortable with the lines, I re-enable it for traffic and racing.
Practice: How to Learn Which Calls Matter for Your Driving Style
The best way to learn which spotter information improves your performance is to test different modes. I did this over a few weeks and it changed how I listen.
- Week 1: Race with all spotter calls enabled. Pay attention to which calls actually change your driving. Log which ones you reacted to.
- Week 2: Disable half the calls (start with weather, fuel, and encouragement). Lap in practice and note your pace. Is it the same?
- Week 3: Keep only position, gap, and clear/blocked calls. Race a few events and compare your incident rate and positions gained.
- Week 4: Fine-tune based on your results. If you're still getting surprised by cars, ask for earlier position calls. If pace is dropping, the spotter might be distracting you.
After this cycle, you'll know exactly which calls your brain needs and which ones are just noise. Every driver is different. Some drivers thrive on constant audio feedback. Others—including me—race better with minimal calls and maximum visual focus.
One More Thing: The Spotter vs. Raw Visual Scanning
A spotter is a tool, not a substitute for awareness. Even with a perfect spotter, you still need to develop the habit of checking mirrors, glancing left and right before a move, and scanning the brake zone for unseen cars. The spotter fills gaps in what you can see from your fixed camera angle, but it's not omniscient. On my fixed rig, I still miss traffic sometimes even with crew chief enabled, because I'm focused on my own line.
The best drivers I've raced against use the spotter to confirm what they already suspect from mirrors and visual scanning, not as their primary source of threat detection. If your spotter is surprising you every lap, you're probably not checking your mirrors enough.
Practice "active listening" to your spotter. After each session, mentally replay which calls helped you and which ones you didn't need. Over time, your brain will filter the signal from the noise automatically.
- MOZA R9 Direct Drive Wheelbase — 9 N·m direct drive — the base bolted to my rig right now
Some links are affiliate links — I may earn a commission at no cost to you.
Watch it, don't just read about it
I stream and upload iRacing races on my MOZA R9 rig — real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.
▶ Subscribe on YouTubeFAQ
Should I use a spotter in every race, or only in certain series?
I use a spotter in multiplayer racing where traffic is frequent and visibility is limited (road courses, ovals with tight fields). In solo practice or offline testing, I disable it because I'm focused on learning the car and track, not defending position. In league racing, I keep it enabled—the extra safety information is worth the minor distraction.
What's the difference between the default crew chief and third-party spotter mods?
The default crew chief is solid and works out of the box with no setup. Third-party mods like Crew Chief Community or AC Spotter offer more customization, voice variety, and sometimes better timing. I use the default because the customization options I mentioned (disabling fuel, weather, encouragement calls) give me what I need. If you want a more human-sounding voice or track-specific callouts, try a third-party mod.
Can a bad spotter call actually hurt my performance more than it helps?
Absolutely. If your spotter is calling threats that don't exist (false positives) or calling too late to act on (after you've committed to a move), it will make you hesitant and nervous. This is why the filtering and testing cycle I described matters. A spotter that makes you second-guess yourself is worse than no spotter at all.
How do I know if my spotter is accurate, or if it's hallucinating cars that aren't there?
Compare what the spotter says to what you see in the mirror or on your telemetry map. If the spotter says 'car left' and you check the mirror and there's nothing there, disable that call type temporarily. Also check the spotter mod's settings—sometimes it flags cars that are several positions back rather than immediate threats. Accuracy varies by mod and track complexity, so test it in practice before trusting it fully in races.