Learn / Setup & Driver Feedback / The setup sheet, baseline philosophy and back-to-back testing
L2 · Practitioner

The setup sheet, baseline philosophy and back-to-back testing

A setup is only as good as its documentation. Keep a complete setup sheet and run log, work from a known baseline, evaluate changes back-to-back with controlled conditions, and check whether a lap-time difference is statistically real before believing it.

The setup sheet, baseline philosophy and back-to-back testing: L1 Foundation explanation

The setup sheet is the single source of truth for the car's configuration. It records every adjustable: tyre pressures (cold set, hot achieved), ride heights, corner weights, camber, toe, caster, springs, ARBs, packers/bump rubbers, damper clicks, wing/flap positions, brake bias, diff settings, electronics maps (TC, ABS, engine), gear ratios, fuel load and ballast. Alongside it, the run log records conditions (track/air temp, wind, time), tyre set and age, fuel, the driver's comments and lap times.

Baseline philosophy. Every event starts from a baseline: a known, validated setup the team trusts (from the last visit, simulation, or the manufacturer's recommendation). Changes are evaluated relative to it. If the weekend goes wrong, you can always go back. Never start "from scratch".

Back-to-back testing. To know whether a change helped, compare it with the baseline under conditions as similar as possible: same driver, same tyre state, similar fuel, close together in time. The cleanest method is A–B–A: baseline, change, baseline again. If the second A matches the first, conditions were stable and the B result is believable.

Is the difference real? Lap times scatter by 0.1–0.3 s even for a consistent pro driver. A 0.1 s improvement on one lap means nothing. You need several laps per configuration and you must compare the difference with the scatter.

Key formulas

Standard error of a lap-time difference
SEΔ=sA2nA+sB2nBSE_{\Delta} = \sqrt{\frac{s_A^2}{n_A} + \frac{s_B^2}{n_B}}
s
lap-time standard deviation per configuration (s)
n
number of clean laps per configuration
Laps needed per configuration (α = 0.05, power 80%)
n≈2(2.8 σΔ)2n \approx 2\left(\frac{2.8\,\sigma}{\Delta}\right)^2
σ\sigma
lap-time scatter (s)
Δ\Delta
difference to detect (s)

Trackside takeaways

  • Document everything, every run: measured values, conditions, driver words, your interpretation, next action.

  • Always start from a validated baseline; re-run it to detect drift.

  • Use A–B–A (or ABBA) to cancel track evolution and driver adaptation.

  • A lap-time difference is real only if it clearly exceeds ~2× its standard error.

  • Prefer lower-noise metrics (segment times, min speed, gated understeer angle, roll gradient) to judge small changes.

  • Correct for fuel, tyre degradation and track evolution before comparing.

On your car

Multi-driver line-ups: log which driver drove each run; compare like with like. Data sharing across sister cars helps build baselines.

Check yourself

Question 1 / 4L1 · Foundation

What is the main purpose of running the baseline again after testing a change (A–B–A)?

Further reading
  • Milliken & Milliken – Race Car Vehicle Dynamics — Ch. 11 Testing and Development
  • Milliken & Milliken – Race Car Vehicle Dynamics — Ch. 12 Chassis Set-up
  • Segers – Analysis Techniques for Racecar Data Acquisition — §17.1–17.3 Metrics and run charts
  • Segers – Analysis Techniques for Racecar Data Acquisition — §9.6 Suspension Troubleshooting