Build a baseline you can tune from

Generated from content/lms/vehicle-dynamics-and-setup/04-making-setup-changes/04-baseline-sheets-and-feedback.md; edit the source file, not this page.

Source path: content/lms/vehicle-dynamics-and-setup/04-making-setup-changes/04-baseline-sheets-and-feedback.md

Course: Vehicle Dynamics & Setup

Module: Making Setup Changes

Estimated duration: 60 minutes

Principle: a baseline is the thing you tune against

A setup change only teaches you something if you know what the car did before the change. The baseline is that before state, recorded clearly enough that you can come back to it, compare against it, and stop guessing. It is not just a setup sheet. It is the linked record of the car, the track, the conditions, your driving plan, your feedback, the lap or segment result, and any data channels you can trust.

At the intermediate level, the biggest setup mistake is usually not the wrong bar hole, wing angle, or damper click. It is tuning from a memory that is too vague to test. You finish a session and remember that the car pushed, or felt nervous, or seemed slow on the straight. Those impressions can be real, but by themselves they are not yet a baseline. A baseline has enough context to answer the next question: compared with what?

The mechanism is simple. The tires are the only parts of the car that actually transmit the forces that accelerate, brake, and turn the car. They also carry much of the information you feel through the chassis, steering, brake pedal, and seat. Because the driver receives so much sensory information through the tire contact patches, driver feedback is valuable, but it is also vulnerable to confusion. A driver can feel a balance problem, a line problem, a surface problem, a speed change, an aero change, or a tire-deterioration change as one blended impression. The baseline sheet separates those impressions into evidence.

That is why a useful baseline has two jobs. First, it captures what happened. Second, it preserves the conditions under which it happened. If the track gets hotter, if it rains, if the tires deteriorate, if you drive a different plan, or if you compare a flyer to a poor lap, the apparent setup answer can move even though the car setting did not. A baseline is how you notice that movement before you spend practice time chasing it.

This lesson is not the one-change rule. That sibling lesson teaches how to isolate a single adjustment. This lesson comes one step earlier. You are building the reference point that makes any later one-change test meaningful. It is also not the lesson on naming understeer or oversteer. You still need to name the balance, but here the skill is recording the balance in enough context that the name becomes useful.

What the baseline must answer

A working baseline answers five questions.

First, what was the plan for the session? A good driver has a plan at each meaningful point on the racetrack: where to brake, where to shift, where to turn in, where to apex, how to apply power, and where the car should reach the exit edge. Your baseline starts before the session because the car's behavior only means something relative to the job you asked it to do. If you change your braking point, apex, or power timing every lap, the setup sheet cannot tell you much.

Second, what track and conditions did you run in? The record needs the date, car, weather, best lap, and a useful reference for pace if one exists. Conditions are not decoration. Weather and track state can change the baseline, and tire deterioration can change it even in a session that seems otherwise consistent. If you do not write the conditions down, you may come back to the same track later and treat a different problem as the same problem.

Third, what did the car do, and where? The feedback should locate the behavior by phase and speed: braking, entry, middle, exit, faster corner, slower corner, straight line, or transition. In aero work, the distinction between lower speed and higher speed corners is especially important because mechanical grip and aerodynamic load do not dominate in the same way everywhere. For many average racing corners, mechanical grip remains the basis of balance, while aero download adds to it. That means a baseline that only says push everywhere is too blunt to tune from.

Fourth, what was changed or not changed? You do not need a complicated form to start, but you do need a record of the car state you might later alter. If the relevant knobs are wings or spoilers, record the front and rear settings. If the session is a general setup baseline, record the settings your program actually treats as adjustable. Bentley's point about driver records applies to setup records too: if the person making changes does not keep notes, the program is not learning efficiently.

Fifth, what evidence backs the feedback? Lap time matters, but it is not enough by itself. Segment times, higher speed corner entry, apex, and exit speeds, straight-line speeds, throttle trace, brake pressure shape, steering, RPM, gear, GPS line, G-sum, total steering angle, throttle histogram, fastest rolling lap, and theoretical fastest lap can all help you find what changed. The point is not to stare at every channel every time. The point is to use the available channels to check the story your hands and feet are telling you.

The baseline sheet is a loop, not a form

A form can help, but the skill is the loop. Before the session, write the objective and the plan. During the session, drive the plan consistently enough that the car gets a fair test. After the session, record conditions, changes, results, feedback, and evidence. Before the next session, turn that evidence into the next objective.

If you treat the sheet as paperwork after the fact, it will become a diary. A diary can be interesting, but it does not necessarily make the car faster. A baseline sheet is different. It is a working instrument. It tells you what you are trying to learn before you drive, and it tells you what you actually learned after you come in.

The pre-session objective should be narrow. You might be establishing a no-change baseline for a known setup. You might be confirming whether a fast-corner balance complaint is real. You might be building an aero table. You might be returning to a known track in new conditions and checking whether the old notes still apply. The objective should be clear enough that, after the session, you can say whether the run answered the question.

The plan should be written in driving language, not engineering language alone. At minimum, write the important braking, shifting, turn-in, apex, throttle, and exit ideas for the corners that matter to the test. A baseline is only as clean as the driving plan used to produce it. If you are later comparing a setup change, you need to know whether you drove the same corner in the same way.

The post-session section should separate what you felt from what you know. You may feel medium-speed understeer. You may know that the entry speed was higher than the previous session, or that the throttle trace showed a hesitation, or that the segment time improved even though the straight-line top speed fell. Do not mash those into one sentence. Keep the sensation, the lap or segment result, and the data cross-check separate until you have asked why they agree or disagree.

Draw the track as you drive it

A printed track map is useful, but it is not enough for a driver baseline. Draw your own map because the way you see the track is part of the record. Your map should show the practical reference points you use, not just the geometric shape of the circuit. Mark gears, turn-in points, apex references, exit references, elevation changes, surface changes, passing places if relevant, and the pieces of track that are challenging.

This matters because setup feedback without track location is weak. If you say the car understeers in Turn 4 but your notes do not show whether Turn 4 is approached with a late brake release, a particular surface change, a fast entry, or a compromised exit, the setup answer is easy to overread. The map lets you connect the feedback to the actual job the car was doing.

Your map also protects you when you return to the same track. If you only remember that the car was good here last time, you have not preserved much. If your notes show the date, car, weather, best lap, reference lap, gears, turn-in points, apex references, surface changes, and the exact corner phase where the car was strong or weak, the next event starts from knowledge instead of memory.

Do not make the map pretty. Make it useful. A driver-drawn map with three honest reference points and one clear balance note is worth more than a clean printed map covered with generic comments. The map is your index into the baseline sheet.

Feedback that a setup change can use

Good feedback has a location, a phase, a speed band, an input, a car response, and a consequence. Instead of the car pushed, write that in the faster right-hand corner, after turn-in and before apex, with maintenance throttle, the front would not take the added steering and the minimum speed was lower than the previous baseline. If you have data, add whether the steering angle rose, whether throttle was delayed, whether the GPS line moved wide, and whether the segment time suffered.

That structure is not about sounding professional. It is how you protect yourself from the wrong fix. Understeer during fast-corner entry after a downforce change may point in a different direction from understeer during a slow corner because you entered too fast, coasted too long, or pinched the line. A single balance word cannot carry all of that.

The data channels from a basic logger help most when they expose incongruencies. If the feedback says the car would not rotate, but the throttle trace shows a lift after early power, the next question is whether the car forced the lift or the driver created the balance with throttle timing. If the complaint is poor braking confidence, the brake pressure trace can show whether the initial application, release, trail, or long tail changed. If the car feels slow, segment times and straight-line speeds can show whether the cost is cornering speed, exit speed, or drag.

Use data as a cross-check, not as a replacement for feel. The driver is still sensing the car through the tires and controls. The logger helps you test the story. Look for mismatches, dig into the details, use other channels if available, compare when you can, calibrate the data to your driving, imagine what a better trace would look like, and set the next objective from that evidence.

Build the first baseline without tuning

The first baseline run should be boring on purpose. Your job is not to fix the car in the first session. Your job is to learn what the current car does when driven to a known plan. If the session is safe and the car is mechanically sound, avoid making a setup change before you have a usable record of the starting point.

Drive enough representative laps to know whether the feedback repeats. In a formal aero comparison, the cited method ran each wing configuration over five laps, averaged the lap times, and discarded abnormal highs or lows. You do not have to turn every HPDE session into a race-team test, but the principle applies: one weird lap is not a baseline. A baseline is a repeatable pattern.

After the session, do not start with the adjustment. Start with the record. What was the objective? What did the car do? Where did it do it? What did the lap, segment, or channel evidence say? What conditions might have changed? What would you need to repeat to verify it? Only after that do you decide whether a change is warranted.

This is where intermediate drivers often have to slow themselves down. Tuning feels productive. Writing feels passive. But a written baseline saves track time later. If you return to the same track and already know how the car behaved, what settings produced balance, and what conditions were present, you can spend the next session learning the track or refining the driver instead of rediscovering the same starting point.

Mechanical baseline before aero baseline

If the car has meaningful aerodynamic devices, build the aero baseline only after you have a reasonable mechanical baseline. The reason is not that aero is unimportant. It is that the foundation of vehicle balance is still the tire and mechanical grip, and aero download adds to that foundation. The average racing corner is often below the speed where aerodynamic download dominates the whole problem, and even when aero matters, it does not erase the need for a car with good mechanical grip.

That means you should not use wing changes to hide a basic mechanical balance problem before you have identified it. If the car is inconsistent in lower speed corners, if the driver plan is changing every lap, or if the basic setup is not recorded, an aero change can make the notebook look scientific while the test is still confused.

Once the mechanical baseline is known well enough, aero testing becomes much cleaner. Traditional on-track aero testing can record lap times, sector times, higher speed corner entry, apex, and exit speeds, and straight-line speeds. The driver feedback should focus on aerodynamic handling balance, especially in medium and high speed corners where the downforce change should show up more clearly. The data logger may record much of the speed and time evidence, but the driver still needs to add notes and context.

The practical boundary is not perfect. The source material acknowledges that there is not always time to separate mechanical from aerodynamic balance tuning. When time is short, at least use the track layout intelligently. Low speed corners help you watch mechanical behavior. Higher speed corners help you watch aero behavior. The baseline sheet should say which part of the track you used for which question.

Worked example: building an aero balance table

Suppose you have fitted front and rear downforce aids and want a baseline that will help at more than one event. A conservative starting point is to create a stable medium and high speed understeer condition. Set the front device at minimum downforce and set the rear device high enough that you expect the rear to outperform the front. If that means starting the rear at maximum downforce, do it.

Now go out and test the car. If the car understeers in the faster corners, you have the stable direction you wanted. Back off rear downforce until the car balances, or if rear minimum still leaves understeer, increase front downforce until the understeer is gone. Record the front and rear settings, the balance feedback, lap or run times, and any useful speed data.

That gives you the first balanced aero point. Then raise rear downforce again, run the car until the understeer appears, and adjust the front until the car is balanced again. Repeat the process from minimum practical downforce toward maximum practical rear downforce. The result is not just one setup. It is a reference table of balanced settings across the usable downforce range, with times attached.

The table is valuable because it avoids future guesswork. You can compare cornering speeds, straight-line speeds, segment times, and lap or run times across the balanced points. You can also see whether the setup with the biggest top speed is actually the quickest. The source material is explicit that the aero setup that gives the highest top speed will rarely be the one that gives the best lap time. A baseline table keeps your ego away from the wrong metric.

Worked example: five-lap wing comparison without fooling yourself

A second useful baseline situation is a direct comparison between two wing configurations. The disciplined version is simple. Run one configuration for five laps. Change only the wing configuration. Run the other configuration for five laps. Average the lap times and discard laps that are abnormally high or low. Then look at the handling balance and sector performance, not just the final lap number.

The key is the word only. If you change the wing and also change the way you drive, the result becomes cloudy. If the track changes, weather changes, or tires deteriorate, the result can drift even without a real setup improvement. That is why the source emphasizes returning to the baseline setup periodically during the session, especially when conditions change.

The baseline return is not wasted time. It tells you whether the reference itself moved. If the original configuration is now slower than it was earlier, you cannot simply credit or blame the new wing. Tire deterioration or changing conditions may have moved the comparison. If the original configuration comes back close to its earlier behavior, your comparison is stronger.

This example also shows why driver feedback belongs beside the data. The average lap time may say one configuration is faster, while the sector report shows where it gained and where it lost. The driver may report that one configuration made the car balanced in higher speed corners but cost straight-line speed. That is useful information. The baseline lets you decide whether the trade is worth lap time, not whether it merely feels different.

Worked example: returning to the same track in rain

The payoff for baseline work often appears later, when track time is limited. Imagine you tested at a venue in dry conditions and built a balanced aero table from minimum to maximum downforce. Later you return to the same track and it is raining. Without the table, you may spend precious practice time searching for a wet balance. With the table, you can look up the front setting that balanced the maximum rear setting, install that combination, and use the session to learn the wet track.

That is the practical meaning of baseline before tuning. The old record does not drive the car for you, and the wet surface is still a new condition. But the table prevents you from starting from zero. You already know which front setting matched the rear maximum in your previous test. Now your attention can go to rain line, grip changes, visibility, and driver adaptation instead of blind aero hunting.

This example also shows why notes and times belong with the settings. A table of front and rear wing positions is better than memory, but a table with balance notes, lap or run times, cornering speeds, straight-line speeds, and segment times is far more useful. It tells you what the setting did, not just what the setting was.

Worked example: the driver logbook as setup evidence

A non-aero baseline can be just as valuable. Before a practice session, write the objective, the track conditions, the car, and the specific plan for the corners you care about. Draw your map. Mark gears, references, surface changes, elevation changes, and difficult sections. After the session, record the result, the best lap, the fastest reference lap if available, the weather, and the exact feedback.

Now imagine you come back to the same track months later. Instead of remembering only that the car was loose or tight, you can see the plan you drove, the conditions, the references, the lap time, and the balance note. You can tell whether you are dealing with the same complaint or a new one. You can also see whether the problem was tied to a particular reference point, corner phase, or condition.

That is how a driver logbook becomes setup evidence. It is not only about personal improvement. It gives the car record context. If you later ask whether a setup change helped, you can compare against a real description of the baseline lap rather than a mood from the paddock.

Calibration cues: how you know the baseline is getting better

A better baseline makes you faster at learning, not always faster on the next lap. The first cue is that your notes become reusable. When you return to a track, you can quickly recover the plan, references, conditions, and previous balance. You are not relearning the same thing twice.

The second cue is that your feedback becomes more specific. Instead of saying the car was bad, you can say which phase, which speed band, what input, what response, and what consequence. That is the kind of feedback a setup change can act on.

The third cue is that your data review gets shorter and sharper. You stop opening every channel in hope of finding an answer. You start with the complaint, check the channels that can confirm or challenge it, look for incongruencies, ask why, and set the next objective.

The fourth cue is that you can separate speed from feeling. A car can feel faster because the straight-line speed is higher, while the lap is worse because cornering and segment times suffered. A car can feel calmer but be slower if it gives away too much in the wrong part of the track. A useful baseline keeps the lap, segment, corner speed, and driver feedback in the same conversation.

The fifth cue is that you can return to baseline without drama. If weather, track, or tire state changes, you know what to reinstall and what comparison to make. You are not emotionally attached to the latest change because the baseline is a tool, not a verdict.

Common mistakes

The first mistake is the memory baseline. You come in, talk for five minutes, and decide the car needs a change based on the loudest sensation you remember. Good looks like writing the objective before the session and recording conditions, feedback, changes, and results immediately afterward.

The second mistake is the top-speed trap. You chase the setup that gives the biggest number at the end of the straight. Good looks like comparing lap time, segment time, higher speed corner entry, apex and exit speed, and straight-line speed together. The fastest straight-line setup may not be the fastest lap setup.

The third mistake is the mapless complaint. You say the car understeers, but the sheet does not say where, at what phase, or against which reference. Good looks like a driver-drawn map with the practical references and the balance note attached to a specific part of the corner.

The fourth mistake is changing the car and the test at the same time. You alter a setup item, drive a different plan, and call the result tuning. Good looks like preserving the driving plan tightly enough that the car gets a fair comparison. The sibling lesson on changing one thing builds directly on this.

The fifth mistake is data drowning. You open throttle, brake, steering, GPS, G-sum, histograms, segment reports, fastest rolling, and theoretical fastest all at once, then leave with no decision. Good looks like starting from the complaint, checking the channels that matter, looking for incongruencies, and setting one objective for the next session.

The sixth mistake is forgetting that the baseline can move. Weather, track condition, and tire deterioration can shift the reference during a test. Good looks like returning to the baseline setup periodically when conditions change, especially in a comparison session.

The seventh mistake is tuning aero before you know the mechanical car. Good looks like understanding the mechanical baseline first, then using higher speed corners and speed data to study aerodynamic changes. If there is not time to fully separate mechanical and aero effects, at least record which corners you used to judge each.

Drill: the baseline packet drill

At your next event, run this as a two-session drill. The count is two complete on-track sessions, plus a five-lap subset in any session where traffic and event rules make five representative laps realistic. The duration is the full length of those two sessions; do not shorten the driving to serve the form. The work is in how you prepare and debrief.

Before session one, write a one-sentence objective. Draw your own track map. Mark the important gears, braking or turn-in references, apex references, exit references, surface or elevation notes, and one or two challenging sections. Record the car, date, weather, current setup state you care about, and the plan you intend to drive.

During session one, do not tune. Drive the plan. Your job is to produce a repeatable picture of the car. If you have data, mark the laps that best represent the plan. If you do not have data, rely on the map and immediate notes.

After session one, write the feedback in the form phase, speed band, input, car response, consequence. Add lap time, segment time, or speed evidence if available. Check at least one channel or one observable result that could challenge your first impression. Then set the objective for session two.

Before session two, decide whether you are still baselining or whether you have enough evidence to test one change. If you change the car, keep the driving plan as stable as you can. If conditions have shifted enough to make the comparison questionable, repeat the baseline instead of forcing a conclusion.

The success criterion is not a lap time. You pass the drill if, by the end, you can answer these questions without guessing: what was the objective, what plan did you drive, what did the car do, where did it do it, what conditions were present, what evidence supports the feedback, and what is the next objective? If you can answer those, you have a baseline you can tune from.

When the principle gets messy

Real track days and race weekends are not laboratories. You may not have enough time to separate mechanical balance from aerodynamic balance. You may not get clear laps. Weather may change. Tires may deteriorate. The logger may give you more channels than you can use between sessions. None of that cancels the baseline principle. It just means your baseline has to record the uncertainty.

If the test is messy, say so in the sheet. Write that conditions changed, that the comparison was limited, that the higher speed corners suggested one thing while lower speed corners suggested another, or that the data needs another run. A baseline with honest uncertainty is useful. A confident but unsupported conclusion is dangerous.

The practical rule is this: never let the sheet imply more certainty than the session earned. If you know only that the car understeered in faster corners after an aero change, write that. If you know the segment improved despite lower top speed, write that. If you know the baseline moved because the tires deteriorated, write that. The purpose is not to look decisive. The purpose is to make the next decision better.

How this connects to the rest of the module

Once the baseline exists, the sibling lessons take over. Change one thing and learn what happened depends on this record because a one-change test needs a known starting point. Change one thing, then prove what happened depends on the lap, segment, channel, and feedback evidence you saved. Name the balance before you tune it depends on the phase and speed language in the feedback. Work the setup stack in order depends on knowing whether the complaint is mechanical, aero, driver-plan, or condition related. Make setup changes like a test driver depends on the discipline of objective, run, evidence, and next objective.

The baseline is not glamorous. It is the thing that lets every later setup lesson work. Build it before you tune.

Worked example: building an aero balance table

Start with the front device at minimum downforce and the rear device high enough to create stable medium and high speed understeer. Test the car, then reduce rear downforce or add front downforce until the faster-corner understeer is gone. Record the balanced front and rear settings, the balance feedback, lap or run times, and any speed data. Repeat from minimum practical downforce toward maximum practical rear downforce so the result is a table of balanced settings rather than one favorite setup.

Worked example: five-lap wing comparison

Run one wing configuration for five laps, change only the wing configuration, then run the comparison for five laps. Average representative lap times and discard abnormal highs or lows. Compare sector behavior, higher speed corner performance, straight-line speed, and driver feedback. Return to the baseline configuration periodically if weather, track condition, or tire deterioration may have moved the reference.

Worked example: returning to the same track in rain

If you built a dry aero balance table at the same venue, a wet return no longer starts from guesswork. Choose the maximum rear downforce setting and look up the front setting that previously balanced it. That does not solve the wet track for you, but it saves practice time that would otherwise be spent searching for basic balance instead of learning the wet line and grip change.

Common mistakes

The common errors are tuning from memory, chasing top speed instead of lap or segment time, writing mapless balance complaints, changing the car and the driving plan together, drowning in data channels, forgetting that weather and tire deterioration can move the baseline, and using aero changes before the mechanical baseline is understood. Good looks like pre-session objectives, driver-drawn maps, phase-specific feedback, targeted channel checks, periodic baseline returns, and honest uncertainty when the run did not earn a firm conclusion.

Drill: the baseline packet drill

Run two complete on-track sessions as a baseline drill. Before session one, write the objective, draw your own track map, mark key references, record conditions and car state, and state the plan. During session one, do not tune. Afterward, write feedback by phase, speed band, input, car response, and consequence, then cross-check at least one data channel or observable result. Use session two either to repeat the baseline if conditions shifted or to prepare for a one-change test. Success means you can state the objective, plan, car behavior, location, conditions, supporting evidence, and next objective without relying on memory.

When this principle gets messy

Track time is imperfect. You may not be able to separate mechanical and aerodynamic balance cleanly, and conditions may drift during the test. The answer is not to pretend the run was cleaner than it was. Use lower speed corners to watch mechanical behavior, higher speed corners to watch aero behavior, return to baseline when the reference may have moved, and write the uncertainty directly into the sheet.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Ultimate Speed Secrets - Ross Bentley	1dbf972c-aef7-3111-aa9c-9fec3776319f	567	1	uio_books_raw_v1
2	Data for Drivers	cabda699642b26311b0a7ef998da2c71	15	1	uio_books_raw_v1
3	Competition Car Aerodynamics 3rd Edition McBeath Simon	4adf8cb4-89c7-1b45-bd4d-9bb03634ecf3	345	1	uio_books_raw_v1
4	Competition Car Aerodynamics 3rd Edition McBeath Simon	c0cd0f54-6d9c-7f08-e9af-37c31b3421d3	345	1	uio_books_raw_v1
5	Competition Car Aerodynamics 3rd Edition McBeath Simon	76c2bbb8-7ace-d134-aad7-e2b7ba9841e5	475	1	uio_books_raw_v1
6	Competition Car Aerodynamics 3rd Edition McBeath Simon	80bde176-e318-b515-e3d5-5de74a7cd507	476	1	uio_books_raw_v1
7	Going Faster Mastering the Art of Race Driving - Carl Lopez	3b70eb1f-e4e3-c70c-1221-c2c8a8e43d83	51	1	uio_books_raw_v1
8	Racing Chassis and Suspension Design Carroll Smith	148524fa-62af-201e-6dff-3b729c84477a	8	1	uio_books_raw_v1