Close the loop after every run

Generated from content/lms/tires-and-brakes-engineering/05-control-heat-across-a-session/04-close-the-loop-after-the-run.md; edit the source file, not this page.

Source path: content/lms/tires-and-brakes-engineering/05-control-heat-across-a-session/04-close-the-loop-after-the-run.md

Course: Engineer tire and brake grip that lasts

Module: Control heat across a session

Estimated duration: 60 minutes

Closing the loop after a run is the skill of turning a hot, fading, noisy, emotional session into one clean next-session objective. You do it while the car, your body, and the data are still telling the same story. If you wait until dinner, the details blur together. If you jump straight to lap time, you miss the mechanism. If you only trust feel, you may protect a false memory. The loop is closed when your notes can answer three questions: what changed during the run, why do you think it changed, and what exactly will you do differently next time out.

This lesson sits after the warm-up and repeatability lessons in the heat-control module. The earlier lessons teach how to plan the warm-up, map the heat cycle, and protect brake repeatability. This lesson starts when you come off track. You are not trying to relive the whole session. You are trying to preserve evidence before it cools off: the tire feel, the brake pedal, the steering load, the sounds, the visual cues, the lap-to-lap consistency, and the traces that either support or challenge your memory.

The principle is simple: a post-run debrief is useful only when it connects sensation, behavior, and evidence. Sensation is what you felt, heard, and saw. Behavior is what the car and driver actually did corner by corner. Evidence is what the notes, video, data, segment times, GPS line, and control traces show. Any one of those by itself can mislead you. Together, they give you a defensible hypothesis for the next session.

Start with the driver, not the laptop. Ross Bentley emphasizes debriefing after each session and describing what you heard, what you felt, and what you took in visually. That order matters because your sensory memory fades quickly. Before you look at a graph, write down the things that were alive in the car. Did the steering get lighter or heavier as the tires approached their limit? Did the tires chatter or vibrate? Did your body feel the same lateral load in the middle of the run as it did at the beginning? Did the brake pedal stay high and firm, or did you begin to search for it? Did the car begin to skate, push, rotate, or put power down differently as laps accumulated?

For this module, your first filter is heat. A tire and brake session is not a single state. It has a beginning, a working middle, and a late-run condition. The first laps may be about getting the tires and brakes to operating temperature. Later laps may reveal whether the heat is useful, insufficient, uneven, or excessive. Your debrief should keep those phases separate. A car that understeers on lap one and understeers again on lap seven may be doing two different things for two different reasons. The first may be a cold or not-yet-ready condition. The second may be front tires overused, brake management, driving inconsistency, or a setup direction you need to test only after you can repeat the driving.

Do not write vague heat notes. A vague note says the brakes were bad late. A useful note says the pedal was normal for two laps, then travel increased after repeated heavy stops, and by the last third of the session I had to brake earlier and carry the same entry speed over a longer period. That points to a brake-temperature problem and gives you something to compare against the next run. A vague tire note says no grip. A useful note says the front tires accepted the first steering input on laps three and four, then began to chatter in the same 100-mph turn, and my steering trace likely grew while minimum speed fell. That points to front tire use, not a general mood.

The core method is a six-step loop. First, capture the session context. Note the session number, weather trend if you know it, traffic level, whether you had clean laps, and whether the opening laps were normal or interrupted. Second, capture sensory evidence before data. Third, split the evidence into tires, brakes, and driver inputs. Fourth, cross-check with available channels: brake pressure, throttle, steering, RPM, gear, segment times, fastest rolling lap, theoretical fastest lap, G-sum, GPS line, total steering angle, throttle histogram, video, or whatever your system provides. Fifth, ask why until the explanation reaches a controllable action. Sixth, set one next-session objective that can be checked after that next session.

The first step, context, keeps you from blaming the wrong thing. A run in traffic does not produce the same evidence as a clean practice run. A first pace lap or first practice lap has a different job than a late green-flag lap. Bentley notes that the first priority on the first pace lap, and also the first lap of practice or qualifying, is to get tires and brakes up to operating temperature. That means you should not evaluate the first lap as if it were a normal hot lap. Your post-run note should identify where the car first felt ready, where it felt best, and where it began to degrade if it did. That becomes the map you carry into the heat-cycle lesson.

The second step is sensory capture. Make it concrete. For feel, write the steering load, tire vibration, tire chatter, brake pedal position, brake effort, and the g-force picture your body remembers. For sound, write anything that changed: tire noise, vibration, scraping, ABS cycling if present, or engine RPM cues that did not match your usual reference. For sight, write what you noticed about the track surface, horizon, peripheral view, and any visible tire or car movement you could see. Bentley frames sensory input sessions as a way to become more sensitive to the limit. In this lesson, you use the same idea after the run: you are training yourself to notice heat-related changes before they become obvious failures.

The third step is classification. Ask whether the evidence is mainly tire, brake, driver, or mixed. Tire evidence often shows up through steering load, corner-entry response, mid-corner chatter, skating, wheelspin on exit, or a need for more total steering angle at the same corner. Brake evidence shows up through pedal feel, braking distance, pressure consistency, initial bite, lockup tendency, a need to brake earlier, a longer and lighter brake application, or a pedal that needs attention on the straight. Driver evidence shows up as coasting, hesitant throttle, early throttle followed by a lift, inconsistent brake pressure, a long brake tail that was not intended, or extra steering added after the car already told you it was saturated.

The fourth step is data cross-check. Keep it simple first. The Data for Drivers process names the useful channels: throttle trace, brake pressure trace, steering, RPM, gear, segment reports, fastest rolling lap, theoretical fastest lap, G-sum, GPS line, total steer angle, and throttle histogram. You do not need all of them. You need the few that can confirm or challenge the story you just wrote. If you felt the front tires give up late, check steering angle, speed, lateral g, and throttle in that corner early versus late. If you felt brake fade, check the brake trace shape and whether braking became light and long instead of hard and short. If you felt the car would not put power down, check throttle application and whether early throttle created a lift.

The fifth step is the why pass. Do not stop at the first label. Understeer is not an answer. Brake fade is not an answer. Tire heat is not an answer. Those are headings. Ask why the evidence points there. If a trace shows more steering for less lateral g late in the run, the front tires may have been overused, the entry may have been too fast, the throttle may have been added before the front tires were ready, or the tire condition may have changed. If the brake trace shows inconsistent pressure, you may be responding to a changing pedal, overprotecting the car after one bad stop, or simply missing the same pressure target lap to lap. The loop closes only when the why points to something you can test.

The sixth step is the next-session objective. A good objective is narrow enough that you can verify it. Not drive better. Not save tires. Not fix brakes. Use a sentence like this: in the next session I will compare laps three through six in Turn 5 and look for the same brake pressure shape with less late tail, while keeping entry speed within my normal range. Or: in the next session I will stop adding throttle until the steering wheel is unwinding in the 100-mph turn, then compare total steer angle and minimum speed to the previous run. Or: in the next session I will use the first two laps to bring the car up to operating temperature without evaluating pace, then mark the first lap where the tire and brake feel stabilizes.

The brake loop deserves special attention because brake heat problems can disguise themselves as driving problems. The Going Faster chunk gives a clear pattern for high ambient temperatures and tracks without long straights: brakes can overheat, and the driver may need to brake earlier and more lightly while carrying the same entry speed. It also describes tapping the brake pedal on the straight to make sure the pedal is up, and explains that if the fluid has boiled, the pedal will not return to the same hardness it had at the start. After a run, that gives you a diagnostic language. Did you choose a longer and lighter brake application because you were managing heat, or did the pedal make that choice for you? Did the pedal recover after a cool lap, or was it permanently softer than at the start? Did you pump or tap the pedal as a confidence check? Those details matter more than a generic note about fade.

When you review the brake pressure trace, look at shape before peak number. The Data for Drivers chunk specifically calls out initial application, trail, long tail, inconsistent pressure, and light-long versus hard-short braking. In a heat-control lesson, those are not just style points. They are how you identify whether the system is repeatable under temperature. If the first half of the session has a crisp initial application and clean release, then the last third has a slower rise, a longer dwell, and a long tail you do not remember choosing, the car may be forcing you to adapt. If the trace is different every lap from the start, the first problem may be your repeatability, not the brake system.

The tire loop is similar, but the evidence is usually more distributed. Tires speak through steering load, vibration, chatter, exit wheelspin, and the relationship between steering angle and lateral acceleration. Bentley points you toward the exact sensations: the steering getting lighter or heavier as tires approach the limit, tire vibration or chattering, and the g-forces acting on your body. The Van Valkenburgh chunk includes a simple MoTeC example in a 100-mph turn using lateral g, steering, speed, and throttle, with notes indicating understeer, front tires overused, and throttle on. That is the kind of post-run thinking you want. Do not ask only whether the car understeered. Ask whether the front tires were asked to corner and accept throttle while already at their limit.

Heat interpretation also needs the warm-up mechanism. Bentley notes that race tires heat quicker from hard acceleration and braking than from weaving alone, and that brake-pad heat transfers through rotors, hubs or uprights, wheels, and the air inside the tire to build temperature in the carcass rather than only the surface. After the run, this helps you interpret the opening laps. If the tires felt awake after aggressive straight-line acceleration and braking, then fell away after hard cornering, write that distinction. If weaving made the surface feel alive but the tire did not stay consistent, do not call the warm-up solved. Your post-run job is not to design the next warm-up in detail; that belongs in the warm-up lesson. Your job is to preserve what the warm-up produced.

The loop also keeps setup thinking honest. Bentley is direct that you cannot do much useful setup development until you know the track well, because if your driving is still improving every lap you cannot know whether a car change helped. He also tells you to make notes on everything about the car and your driving after each session. For an intermediate driver, that means your first post-run setup conclusion should usually be provisional. If you were inconsistent on brake pressure, throttle timing, or line, write the inconsistency first. If the same behavior appears in the same phase of the same corner across several comparable laps, then you have stronger evidence for a car or heat-management issue.

Use corner speed categories to organize your notes. Bentley suggests asking how the car behaves in slow, medium-speed, and fast corners, plus initial turn-in, middle of the corner, and exit power-down. That structure works well after a tire-and-brake session. A brake issue may appear mostly before slow corners with heavy deceleration. A tire-front issue may show up in medium or fast corners where the front tires carry sustained load. An exit problem may show up as too much wheelspin when power is applied. If you write one blended note for the entire lap, you lose that pattern. Split the run by corner type and by corner phase.

Your notes should also separate intended experiments from accidental adaptations. Practice is the time to try things: a taller gear, braking later and carrying more speed, or braking earlier and getting to power earlier. But the post-run loop must label those trials. If you tried a taller gear in one corner, note it so the data does not look like a mysterious RPM or throttle change. If you braked earlier as a planned test, note it so you do not misread it as fear or fade. If you braked earlier because the pedal was changing, note that too. The same trace shape can mean discipline, experiment, heat management, or uncertainty. Your memory supplies the label; the data supplies the check.

The strongest post-run notes are short but specific. They usually have four parts. First, the session phase: early, best, late. Second, the location: corner or section. Third, the sensory cue: steering lighter, tire chatter, long pedal, car skating, wheelspin, more g-force than expected, visual surface change. Fourth, the evidence to check: brake pressure shape, steering angle, throttle trace, GPS line, segment time, G-sum, RPM, or gear. A note like late-run front push everywhere is weak. A note like laps six through eight, fast right, steering heavier then chatter, likely more steering for less speed, check steering and lateral g, is actionable.

Do not let lap time dominate the loop. Lap time is useful, but it is a summary, not a diagnosis. The Data for Drivers process includes segment reports, fastest rolling lap, and theoretical fastest lap because the lap is made of pieces. A tire or brake heat problem may cost time only in one braking zone or one fast section. A best lap may hide a late-run brake issue because traffic or a better exit elsewhere masks it. A theoretical fastest lap may show that the car had the pieces but you did not assemble them. Use lap time to choose where to look, then use traces and sensory notes to decide why.

Also do not let the data overrule a real safety signal. If the pedal became longer, if you had to tap or pump to confirm it, if the pedal never returned to its starting hardness, or if you were changing braking technique because the car no longer repeated, that is not just a data curiosity. The Going Faster chunk describes why the pedal may not come back after fluid boil. Your post-run objective may be to cool, inspect, change technique, or solve repeatability before chasing pace. This lesson is about learning, but the loop has to protect the next session as well as improve it.

A useful mental model is compare, calibrate, imagine, decide. Compare your best-feeling laps to your worst-feeling laps. Calibrate the data to what you remember feeling. Imagine what a clean version would look like in the trace: earlier readiness, same pressure shape, no unnecessary long tail, smoother throttle, less extra steering, stable segment time. Then decide one objective. The Data for Drivers process uses exactly that flow: look for incongruencies, dig into details, use other channels, ask why, compare, calibrate to your driving, imagine the ideal, and set objectives for the next session.

The loop is closed only when it produces behavior. A note that says front tires overused is not closed. A note that says delay throttle until steering begins to unwind in the 100-mph turn, then compare steering angle and lateral g, is closed. A note that says brake fade is not closed. A note that says brake five car lengths earlier for two laps to test whether a longer and lighter application keeps the pedal consistent, then inspect whether the pressure trace stabilizes, is closed. A note that says warm-up bad is not closed. A note that says first two laps produced only surface feel, then car stabilized after harder straight-line acceleration and braking, so next session I will mark readiness by pedal and steering feel rather than lap time, is closed.

For intermediate drivers, the most important discipline is one objective per next run. The corpus gives you many possible channels and questions. That does not mean you should chase all of them in one session. If your main heat problem is brake repeatability, focus on brake pressure shape, pedal feel, and the braking zones where the problem appears. If your main issue is tire-front overload, focus on steering angle, lateral g, throttle timing, and the corner phase where the front tires complain. If your main issue is sensory weakness, run a sensory input session and debrief what you heard, felt, and saw. A narrower objective gives you cleaner evidence.

Use another person if you can. Bentley suggests describing the session to someone because being forced to explain what you heard, felt, and saw pulls more detail out of you. That person does not need to be a pro engineer. They need to ask simple questions and stop you from skipping the mechanism. Where did it start? Which lap? Which corner type? What changed in the pedal? What did the steering do? Did the same thing happen in slow, medium, and fast corners? What channel will you check? What will you do next session? If no one is available, ask yourself those questions out loud or write them as prompts.

Your exit standard for this lesson is practical. After a run, you should be able to produce a post-run note that another instructor could understand without having ridden with you. It should name the phase of the run, the car behavior, the sensory cue, the evidence channel, the suspected mechanism, and the next-session objective. If you cannot do that, the loop is still open. If you can, you have turned one session of tire and brake heat into the next session of learning.

Worked example: High ambient session with a soft pedal

You come in after a session on a hot day at a track without much straightaway cooling time. Early in the run, the pedal is normal and the braking points feel familiar. By the late laps, you are braking earlier and using a longer, lighter application to carry about the same entry speed. On the straight, you tap the pedal because you want to know it is up before the next braking zone. After the run, the key is not to write slow late laps. The useful loop is more specific: the brake system changed during the run, the driver adapted by lengthening the brake zone, and the next check is whether the pedal returned to its starting hardness or stayed soft.

The data pass starts with brake pressure shape. Compare an early clean lap, a middle lap, and the late lap where the pedal got your attention. Look for the initial application, peak pressure, release, and whether the trace became light and long. Then compare entry speed. If entry speed stayed similar while the brake zone grew longer, your driving adapted to the brake condition. If pressure is inconsistent from lap two onward, you may have a repeatability issue before you have a heat diagnosis. The next-session objective should be narrow: monitor the same braking zone across the first six laps and decide whether the system stays repeatable, rather than trying to set a best lap.

Worked example: The 100-mph turn with front tires overused

The Van Valkenburgh chunk describes a simple data screen with lateral g, steering, speed, and throttle in a 100-mph turn, annotated for understeer, front tires overused, and throttle on. That is an ideal after-run loop because it forces you to connect the driver input to the tire complaint. You come in feeling that the car pushed late in a fast corner. The lazy note is the car understeered. The useful note is late-run fast corner, front tires chattered, steering input increased, throttle was already being added, check steering angle, lateral g, speed, and throttle timing.

In the data, do not look for one magic number. Compare early and late laps at the same corner. If the late lap shows more steering angle with no matching gain in lateral g, the front tires are not giving you more cornering for the added steering. If throttle begins while the front tires are already saturated, the driver may be asking the front tires to finish cornering while the car is also being asked to accelerate. The next-session objective is not simply carry more speed. It is to delay throttle until the steering begins to unwind, then compare whether total steering angle drops and the car holds or improves minimum speed.

Worked example: Opening-lap heat that fooled the debrief

You start a practice session focused on getting the tires and brakes up to operating temperature. You use acceleration and braking in a straight line, and the car begins to feel alive. Later, you remember that the first fast lap felt good, but the middle of the run felt better, and the last laps had front chatter. Without a loop, you might call the warm-up successful because the first timed lap was not terrible. With a loop, you separate surface readiness from working temperature and late-run behavior.

The note should identify three points: when the brake pedal first felt ready, when the tire response felt stable, and when degradation began. The mechanism matters because brake heat can transfer through the rotor, hub or upright, wheel, and air inside the tire to build carcass temperature, not only surface temperature. Your next objective is to mark readiness by feel and repeatability, not by eagerness to push. If the first lap feels sharp but the tire behavior changes quickly, you bring that evidence back to the warm-up planning lesson instead of simply adding more weaving or more pace.

Common mistakes

The first mistake is parking the memory. You come in, talk about traffic, check your phone, and only later try to remember what the car did. Good looks like writing sensory notes before the laptop opens: pedal, steering, tire noise, chatter, skating, wheelspin, and any visual surface cue.

The second mistake is treating lap time as the diagnosis. A slow lap does not tell you whether the loss came from brake pressure, throttle hesitation, extra steering, traffic, line, or tire behavior. Good looks like using segment times and traces to locate the loss before naming the cause.

The third mistake is calling every late-run problem setup. Bentley warns that setup development is hard until your driving is consistent. Good looks like checking whether brake pressure, throttle timing, steering, line, gear, and corner entry are repeatable before blaming the car.

The fourth mistake is writing a heat label with no phase. Hot tires, cold tires, and overheated brakes are incomplete notes. Good looks like early, best, and late phase notes, with the corner or section named.

The fifth mistake is ignoring incongruencies. If you felt brave but the throttle trace shows hesitation, believe the trace enough to investigate. If you felt the car was bad everywhere but the segment report shows only one section fell away, narrow the problem. Good looks like using other channels to check the story.

The sixth mistake is carrying a recovery tactic into the next run as if it were normal. If you had to brake longer and lighter, tap the pedal, or pump to get confidence in the pedal, that belongs in the repeatability discussion. Good looks like treating that as evidence to solve, not as proof that you adapted well.

Drill: Three-run closed-loop notebook

Run this drill over three sessions at your next event. The count is three runs. The time cost is four minutes immediately after each run and ten minutes of data or video review before the next run. The success criterion is that each run produces one next-session objective that can be verified by sensation and at least one evidence channel.

After run one, do only sensory capture for four minutes. Write three feel notes, two sound notes if you have them, and two visual notes. Then choose one heat-related question. Example: did the brake pedal change after lap five, or did my braking pressure change first?

Before run two, choose one channel to check that question. It may be brake pressure, throttle, steering, GPS line, segment time, or video. After run two, compare early, middle, and late laps only in the corner or section tied to the question. Write one objective for run three.

Run three is the verification run. Do the objective, then debrief again. You pass the drill if your final note can name the session phase, location, sensory cue, data channel, suspected mechanism, and next action. You fail the drill if your note is only a lap time, only a feeling, or only a generic setup complaint.

When to use the sibling lessons

Use Map your session heat cycle when your debrief shows that the tire or brake behavior changes clearly by lap phase and you need to plot the whole run. Use Protect brake repeatability under temperature when the pedal, pressure trace, braking length, or driver confidence changes as heat builds. Use Plan warm-up without hiding risk when the opening laps feel misleading, when the car feels ready on the surface but does not stay consistent, or when tire and brake readiness arrive at different times. This lesson is the bridge between them: it preserves the evidence after the run so the next lesson you apply is based on what actually happened.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Data for Drivers	cabda699642b26311b0a7ef998da2c71	15	1	uio_books_raw_v1
2	Ultimate Speed Secrets - Ross Bentley	39f78a08-7a9c-ccf1-086b-9dd4e0aa53a4	500	1	uio_books_raw_v1
3	Going Faster Mastering the Art of Race Driving - Carl Lopez	4dfc5860-2f13-09b6-3121-106ac2228185	185	1	uio_books_raw_v1
4	Ultimate Speed Secrets - Ross Bentley	392d0d7b-14e9-290b-a9cb-8696b08e1e97	305	1	uio_books_raw_v1
5	Ultimate Speed Secrets - Ross Bentley	12f4cd2d-5031-a219-7d3f-b35d97a4116e	305	1	uio_books_raw_v1
6	Ultimate Speed Secrets - Ross Bentley	47e12692-bbb7-6e53-8b0e-97e81f1dc537	305	1	uio_books_raw_v1
7	Ultimate Speed Secrets - Ross Bentley	4f8ea99e-c241-7c69-b197-d63882fae51c	513	1	uio_books_raw_v1
8	Race Car Engineering Mechanics Paul Van Valkenburgh	f721fe85-812c-0bdc-d9b3-212cd51c14f7	149	1	uio_books_raw_v1