Comparing two drivers and coaching with data
Comparison is the heart of driver development. Use a structured process – speed and delta first, then inputs, then line – and deliver it in a way the driver can absorb, acknowledging that car balance and driver technique are intertwined.
Comparing two drivers and coaching with data: L1 Foundation explanation
Two pitfalls (Segers §14.1):
- Driver and chassis are intertwined. What looks like a driver error may be an unbalanced car – and vice versa. Always combine the driver's comments with data.
- Drivers are human. Even well-founded, tactful criticism can dent confidence. Often the best approach is to guide drivers to discover the issue themselves.
Make drivers data-literate. Drivers should be able to use the analysis software, understand basic techniques, and have enough vehicle-dynamics knowledge to relate their driving to the car's behaviour. Give them the data quickly, while the laps are fresh in their memory.
A basic driver template: speed, throttle, front brake pressure, gear, RPM, steering, with delta time to a reference lap.
Four characteristics to evaluate (Segers §14.2):
- Performance – results: minimum corner speeds, peak lateral g, peak deceleration, shift times, lap time.
- Smoothness – inputs that don't upset the car (throttle, brake release, steering).
- Response – delays between actions: throttle-off to brake-on, brake-off to throttle-on; responses to slides.
- Consistency – repeatability of all the above.
Comparing two drivers and coaching with data: L2 Practitioner explanation
A structured comparison process.
- Same conditions: same car (or identical cars), same session or similar track state, similar tyre age and fuel. Otherwise you compare conditions, not drivers.
- Speed + delta time vs distance: find the 2–3 places where most time is lost (steep delta slope). Ignore small, random losses.
- Inputs at those places: brake point and peak, release, throttle pickup and full-throttle point, gear choice, steering. Use per-corner metrics (brake point, min speed, throttle acceptance, coasting).
- Line: curvature/radius channels, GPS lines from the same session, synced onboard video.
- Explain with physics: e.g., "you reach full throttle 25 m later because the car is still turning at the exit; try a later turn-in and get the rotation done before the apex".
- Make it actionable: one or two concrete references per corner (brake board, kerb, gear), not ten observations.
- Verify next run: did the metric move? Did lap time follow?
Driver aids from data: shift lights per gear from logged RPM/power data, predictive lap timing against a reference lap, virtual sector times, lock-up and wheelspin indicators on the dash, brake-balance display.
Delivering feedback. Structure: observation (fact in data) → effect (time) → suggestion → check. Start with what was good. Use the driver's own best laps as reference where possible ("your lap 7 did this, lap 12 didn't") – self-comparison is far less threatening than comparison with a team-mate. In Pro-Am, the Pro's lap is the natural benchmark, but present it as a target, not a verdict.
Comparing two drivers and coaching with data: L3 Advanced explanation
When the "faster driver" reference misleads.
- Different styles can be equally fast. One driver brakes later and rotates the car aggressively (V-style); another carries more minimum speed. Copying one element (a later brake point) without the rest of the technique usually makes the junior driver slower.
- Confidence and car setup. A Pro may tolerate a nervous rear that an Am can't. A coaching gain of 0.5 s may be available just by setting the car up for the slower driver (more stable rear, less entry rotation) – often the better team decision in shared-car series.
- Tyre and fuel states differ. Compare like-for-like stints or fuel-correct.
Quantitative driver comparison at scale. Build per-corner tables for both drivers over many laps: brake point (m), peak pressure (bar), time-to-peak (s), minimum speed (km/h), pickup distance after apex (m), throttle acceptance (%), coasting time (s), corrections count. Show distributions (box plots) rather than single laps; a difference is real only if it exceeds the within-driver scatter.
Left- vs right-foot braking. Left-foot braking removes the throttle-to-brake transition time, allows deliberate throttle/brake overlap (balance, turbo boost) and, on manual-blip gearboxes, isolates braking from blipping (smoother pressure during downshifts – ECU auto-blip makes this last point largely irrelevant), but some drivers lose sensitivity. Data shows it clearly: overlap of throttle and brake, near-zero transition and very stable release.
Prioritise by lap-time value. Rank coaching items by expected gain (from delta slope and repeatability) and by learning difficulty. Two easy items worth 0.2 s each beat one hard item worth 0.3 s in a 30-minute practice. Track progress with run charts of the corresponding metrics across a weekend and a season.
Key formulas
- reference driver speed (m/s)
- V
- driver speed (m/s)
Trackside takeaways
Compare under the same conditions: car, session, tyre age, fuel.
Speed and delta first, inputs second, line third – then explain with physics.
Give one or two actionable references per corner, not a list of faults.
Use the driver’s own best laps as references to protect confidence.
Sometimes the fastest coaching is a setup that suits the slower driver.
On your car
Pro-Am line-ups: overlays of Am vs Pro are the daily tool; ABS and TC differences (map choice) must be equal before comparing.
Check yourself
What is the best first step when comparing two drivers’ laps from the same session?
- Segers – Analysis Techniques for Racecar Data Acquisition — §14.1 Improving Driver Performance
- Segers – Analysis Techniques for Racecar Data Acquisition — §14.2 Driving Style Evaluation
- Segers – Analysis Techniques for Racecar Data Acquisition — Ch. 3 §3.3 Comparing Laps