Close the loop in your logbook

Generated from content/lms/race-car-mechanic-reference/04-diagnose-track-symptoms/05-close-the-loop-in-the-logbook.md; edit the source file, not this page.

Source path: content/lms/race-car-mechanic-reference/04-diagnose-track-symptoms/05-close-the-loop-in-the-logbook.md

Course: Service the race car that has to finish

Module: Diagnose track symptoms into mechanical hypotheses

Estimated duration: 55 minutes

Principle: a closed loop is a learning system

A track logbook is not a diary. A diary records what happened. A closed-loop logbook records what you intended to test, what you actually did, what the car and data showed, what you think that means, and what you will do next. The difference matters because track symptoms are noisy. Your hands, feet, confidence, tire temperature, traffic, weather, fuel load, setup, and memory all get mixed together. If you write only that the car felt bad, you have not preserved enough information to diagnose anything. If you write only that you changed something, you have not preserved enough information to know whether the change helped.

The loop has five parts: objective, plan, run, evidence, next objective. Before the session, you write the objective and the technique or plan you intend to use. After the session, you write the track and conditions, the changes made to the car, the changes you think still need to be made, and the session result. Then you check the simple data channels that can confirm or challenge your first impression. The loop closes only when the next session has a specific objective created from that evidence.

That is the skill in this lesson. You are learning how to make your logbook do diagnostic work. You are not trying to create a perfect engineering report. You are trying to create a trackside record that lets you learn from each race, practice, test, or qualifying session, and that lets you return to the same track or the same driving problem with useful memory already captured.

Why the logbook has to begin before the session

The most common intermediate-driver logbook error is starting the entry after the checkered flag. That feels natural because the session just happened and the impressions are fresh. But if you did not write the objective first, you are reviewing a session that had no declared test. You can still learn something, but you are mostly reconstructing. A useful entry starts before the car rolls.

Before each session, write what you are trying to improve and what driving technique or plan you will use to do it. The objective does not need to be poetic. It needs to be specific enough that your post-session notes and data review can answer it. Bad objective: go faster. Better objective: reduce coasting between brake release and throttle pickup in the two corners where the throttle trace showed hesitation. Bad objective: fix braking. Better objective: make the first brake application more consistent and shorten the long light tail if the brake trace shows you are dragging pressure past the point where the car needs it.

This matters because the logbook is part of practice. Each time you brake, turn, and squeeze the throttle, you are programming technique. If your practice has no written target, you may be programming the same vague habit again. The pre-session note gives your brain a job, gives your data review a question, and gives the mechanic or coach a boundary. It turns the session from laps into a test.

A pre-session note should answer four questions. What is the session context? What is the driver objective? What is the car state or setup change, if any? What data or observation will you use afterward to decide whether the objective worked? The order is important. If you begin with the setup change, you may bias yourself toward wrenching. If you begin with the driver objective and evidence plan, you are more likely to separate your own adaptation from a real car change.

The minimum pre-session entry

Use a small, repeatable format. Write the track, configuration if relevant, session type, and obvious conditions. Then write the car state: tire set, pressures if you are tracking them elsewhere, fuel state if it matters to your program, and any change since the last outing. Do not bury a change inside a paragraph. Put it where you can find it later.

Next, write the driver objective. Keep it narrow enough that you can remember it in the car. If your objective has five unrelated parts, it is not an objective; it is a wish list. The objective can be a driving behavior, a data signature, or a comparison. Examples supported by the data process are throttle hesitation, early throttle followed by a lift, coasting, lifts in fast corners, inconsistent brake pressure, brake trace shape, steering input, gear choice, RPM behavior, GPS line, segment time, fastest rolling lap, theoretical fastest, or total steer angle.

Finally, write the plan. The plan is the concrete action you will take, not the result you hope to get. If the objective is to remove throttle hesitation, the plan might be to choose one corner and make one clear decision: either maintain brake release until rotation is complete, or begin one smooth throttle application and commit to it without a corrective lift. If the objective is brake consistency, the plan might be to focus on the first brake pressure rise and the release shape, then review whether the trace is consistent lap to lap.

Notice what is not in the pre-session entry: a final diagnosis. Before the session, you can have a hypothesis. You cannot yet have proof. A closed-loop logbook protects that distinction.

The post-session entry: facts first, interpretation second

After the session, write before the details evaporate. You are trying to capture the record while the sensations, track state, and session flow are still available. Start with facts: track and conditions, traffic, notable interruptions, what changes were made, what results you observed, and whether anything changed during the run. If you adjusted something, write what changed and when. If the track changed, write it. If the session was compromised by traffic or a flag, write it. These facts are not clutter. They are the difference between learning and guessing when you look back later.

Then write the driver report. Keep it separate from the facts. The driver report can include feel: where the car felt reluctant, where you hesitated, where the car seemed better, where it seemed worse. But do not let feel become diagnosis too quickly. The sentence the car is loose everywhere is less useful than the rear moved on entry when I released the brake, and the brake trace needs review for a long tail or inconsistent pressure. The first sentence is a label. The second sentence gives the next review step.

After the feel report, write the evidence. This is where the logbook connects to data. You do not need to analyze every channel after every session. In fact, one of the data-process lessons is to keep it simple and focus on the basics. But you do need to check the channel that matches your objective. If the objective involved throttle discipline, look at throttle trace and, if available, throttle histogram. If the objective involved braking, look at brake pressure shape, initial application, trail, long tail, pressure consistency, and whether the stop was light and long or hard and short. If the objective involved line or corner use, GPS line and segment or section times may help. If the objective involved overall pace, fastest rolling and theoretical fastest can help you see whether the issue is one corner, one segment, or general inconsistency.

The evidence section is not a place to prove yourself right. It is a place to look for incongruencies. If the driver report says the car would not accept throttle, but the throttle trace shows early application followed by a lift, the logbook should not jump to a setup change. It should record that your application may be creating the problem you feel. If the driver report says the car was inconsistent on entry, and the brake trace shows inconsistent pressure lap to lap, the logbook should record that driver input is still a live suspect. If the data and feel disagree, that disagreement is valuable. It tells you where to dig.

Closing the loop: the next-session objective

A logbook entry is incomplete until it creates the next objective. This is the step many drivers skip. They write what happened, maybe paste in a lap time, maybe list a setup change, and then leave the next session to whatever feels urgent. That is an open loop. It wastes the previous session because the learning does not become a controlled next action.

The next objective should be built from the evidence. If the data shows coasting, the next objective might be to reduce the coast phase in one corner and check the throttle trace afterward. If the brake pressure trace shows a long light tail, the next objective might be to make a cleaner release and see whether corner entry speed, balance, or segment time changes. If GPS line shows you are not using the available track, the next objective might be to run the intended line and check whether the outside tires are consistently near the edge where appropriate. If the fastest rolling or theoretical fastest report shows one segment has the biggest gap, the next objective might be to isolate that section instead of chasing the whole lap.

A strong next objective has three parts: the behavior you will attempt, the evidence you will review, and the condition under which you will accept the result. For example: In session three, focus on the brake release in Turn X; afterward compare brake pressure shape and segment time to session two; accept the change only if the trace is more consistent and the car did not create a new problem on exit. You can adapt the exact words to your car and track, but the structure should stay stable.

Why data belongs in the logbook, not beside it

Data is not a separate hobby from the logbook. The logbook gives data a question, and data gives the logbook discipline. Without the logbook, you can spend an evening staring at squiggly lines and never decide what to do next. Without data, you can spend an evening writing confident stories that the car may not support.

The useful data process starts wide and narrows. Begin with the overview. Look for incongruencies. Dig for details. Use other channels if available to check the story. Ask Why? Compare if you can. Calibrate the data to your driving. Imagine what the better version would look like. Then set objectives for the next session. That process is a loop, and your logbook is where the loop becomes visible.

Do not overcomplicate the first pass. If the symptom is throttle-related, the first useful channels are often throttle trace, speed, and maybe throttle histogram. You are looking for coasting, hesitation, early application leading to lift, or lifts in fast corners. If the symptom is braking-related, the first useful channel is brake pressure trace. You are looking at shape, initial application, trail, long tail, inconsistency, and whether the stop is light and long or hard and short. If the symptom is line-related, GPS line and total steer angle may help. If the symptom is pace-related, segment times, section times, fastest rolling, and theoretical fastest may help.

The important word is related. Do not review every channel just because the software can show it. The logbook should tell you which channels answer the objective. That is how you keep the review short enough to do at the event and specific enough to matter.

Sub-skill 1: objective writing

Objective writing is the ability to turn a vague desire into a testable session target. Going faster is not testable enough. Better braking is not testable enough. A testable objective names the behavior and the place or condition where it will happen. It also names the evidence you will use afterward.

At the intermediate level, the objective should usually be a driver behavior before it becomes a car change. That does not mean the car is never wrong. It means the driver is part of the system, and the logbook should not let your first impression erase that fact. If the brake trace is inconsistent, you cannot fairly judge a setup change for entry balance. If the throttle trace shows hesitation or early application followed by lift, you cannot fairly decide the car simply lacks exit drive. If the GPS line moves around lap to lap, you cannot fairly decide that a corner needs a chassis change.

Good objective writing creates a fair test. It gives the driver one thing to attempt and gives the mechanic or coach one thing to evaluate. It also protects the baseline, because you are less likely to make an unrelated adjustment just to feel productive.

Sub-skill 2: condition capture

Condition capture is the habit of writing the context that could explain the result. Track and conditions are part of the post-session record because they affect how you interpret the session later. A note that says the car was better is weak if it omits the conditions and the change history. A note that says the car was better in a cooler session with less traffic and no setup change is more useful. A note that says the car was better after a setup change but the driver also changed braking technique is more honest.

Do not try to record everything in the world. Capture what you will need when returning to the same track or when the same problem appears again. If you cannot imagine using the detail later, it may not belong. If you can imagine arguing about it later in the paddock, write it down now.

Sub-skill 3: change trace

Change trace is the ability to follow what changed between sessions. In a diagnostic context, this is critical. Your logbook should make it easy to answer three questions: What changed on the car? What changed in the driver's plan? What changed in the result?

The mistake is mixing those into one emotional paragraph. Instead, keep them visible. Car change: what was adjusted. Driver plan: what you attempted. Result: what happened. Evidence: what the data showed. Next: what you will do. When the next session starts, you should not have to remember this structure. You should be able to read it.

This is also where the logbook prevents false credit. If a segment improved after you changed both the car and your brake release, you do not yet know which one mattered. That does not make the session useless. It means the next objective should isolate the remaining question. The logbook is not there to make every answer simple. It is there to keep you honest about what you know.

Sub-skill 4: data triangulation

Triangulation means using more than one channel or observation to check the story. If the throttle trace shows hesitation, speed may show whether that hesitation cost momentum. If the brake pressure trace shows a long tail, speed and segment time may show whether the entry is being over-slowed. If GPS line shows a different path, total steer angle may help show whether you are adding steering instead of using the track. If a segment report shows the loss is concentrated in one section, you can stop treating the entire lap as the problem.

Triangulation does not mean drowning in channels. It means using the other available channels to check a claim. The data process specifically calls for incongruencies, details, other channels, comparison, calibration to your driving, and imagining what the better version would look like. Put that in your logbook. You can write a simple line: feel says entry instability; brake trace shows inconsistent release; GPS line also varies; next test is driver consistency before setup.

Sub-skill 5: comparison

Comparison turns a single session into learning. Compare if you can: session to session, lap to lap, driver to driver where appropriate, or current track notes to the last time you were here. The Speed Secrets logbook idea is not only to write records but to learn from them by looking back when returning to the same track or when a specific driving problem appears. That is why your notes should be findable.

The comparison must be fair enough to help. A clean lap and a traffic lap may not answer the same question. A cold track and a later warm session may not tell the whole story. A lap where you tried a new brake release should be compared with the previous version of that same corner, not with a random lap chosen because the time was convenient. Perfect comparisons are rare at HPDE and club-racing level, but disciplined comparisons are possible.

Sub-skill 6: the why ladder

The useful question after a symptom is Why? Ask it more than once, but do not use it to invent certainty. If the car felt slow off the corner, why? Because the throttle trace shows hesitation. Why did you hesitate? Because the car was not settled when you wanted throttle. Why was it not settled? The brake trace may show a long tail, the steering trace may show extra input, or the GPS line may show you were not in the place you expected. Each answer tells you what to check next.

The why ladder is how a logbook entry becomes a next-session objective instead of a complaint. It also tells you when to stop. If you have no channel or observation to answer the next why, write that the cause is unconfirmed. That is not failure. That is honest diagnosis.

Sub-skill 7: useful simplicity

The bonded data process ends with a paddock-friendly warning: keep learning, keep it simple, focus on the basics, and get your hands dirty with the data. For this lesson, that means your logbook format must be usable when you are tired, hot, distracted, or waiting for the next session call. A beautiful format you never complete is worse than a plain format you use every time.

A practical page can be short. Pre-session: objective, plan, car state, evidence to check. Post-session: conditions, changes, result, feel, data check, next objective. If you can complete that consistently, you have the loop. Add detail when the problem requires it. Do not add detail to avoid making a decision.

Calibration cues: how you know the logbook is working

You are improving at this skill when your notes become predictive. Before returning to a track, you can read the prior event notes and know which corners or behaviors deserve attention. When a symptom appears again, you can find the earlier entry and compare what changed. When you open the data, you already know which channels matter because the objective named them. When you talk to an instructor or mechanic, you can separate what you felt, what changed, what the data showed, and what you want to test next.

The lap-time signature is not always immediate whole-lap improvement. Sometimes the first sign is a cleaner segment report, a smaller loss in the section you targeted, a more consistent throttle trace, a more repeatable brake pressure shape, or fewer lap-to-lap variations. Theoretical fastest and fastest rolling can help you see whether your best pieces are improving even when traffic or mistakes hide the whole-lap result. Treat those as evidence, not ego.

The driver-feel signature is also specific. You should feel less surprised after each session because the session had a target. You should feel less tempted to explain everything at once because the logbook captured the next question. You should feel more willing to leave a setup change alone when the driver data is inconclusive, and more willing to make a setup change when the driver inputs and conditions are stable enough to give the change a fair test.

Where this lesson connects to the surrounding module

This lesson does not replace symptom mapping. If the feedback is fuzzy, use the symptom-map lessons to turn it into track-specific observations. It does not replace checking simple data before you wrench; it gives that check a home. It does not replace preserving the baseline; it helps you record what the baseline was and what changed from it. It does not replace separating the driver from the change; it gives you a repeatable way to keep those two suspects visible.

The close-loop habit is the binder for those skills. Without it, each session becomes a fresh argument. With it, each session becomes part of a chain of evidence.

Worked example: the throttle problem that looks like a car problem

Suppose you come in convinced that the car will not drive off a corner. Do not turn that sentence directly into a chassis change. Close the loop.

The pre-session note for the next run should name the suspected behavior and the evidence. For example, your objective is to improve throttle commitment in that corner, and your evidence will be throttle trace, speed, and segment time. Your plan is to avoid an uncertain pickup: no long coast, no hesitant application, and no early stab that creates a lift.

After the session, write the facts first. Track and conditions. Any car changes. Traffic. Then write the driver report: where the car felt reluctant and whether you felt yourself waiting, squeezing, or lifting. Then look at the throttle trace. The bonded data process gives you specific patterns to look for: coasting, hesitant application, early application leading to lift, and lifts in fast corners. If the trace shows early throttle followed by a lift, the logbook should not close with the car needs more exit grip. It should close with a driver-input test: next session, delay the pickup until the car can accept one smooth application, then review whether the lift disappeared and whether the segment improved.

If the trace instead shows a clean throttle pickup and the speed still falls compared with your reference, the question changes. Now you may compare GPS line, steering, and segment timing. You still have not proven a setup fault, but you have earned a sharper next question. That is the discipline: each loop narrows the problem without pretending the first feeling was proof.

Worked example: the brake trace that explains a slow first half of the corner

The Going Faster material describes data showing a speed difference between two drivers on the same section of race track, with one driver slowing too much in the first half of the corner. Use that as a logbook model.

Your driver report might be simple: the car felt safe but slow in the first half of the corner. The open-loop version of that note is to say you need to brake later. The closed-loop version asks what the brake trace and speed trace actually show. Look at the initial brake application. Look at whether the pressure is consistent lap to lap. Look at whether the brake trace has a long tail. Look at whether the stop is light and long or hard and short. Then compare the segment or section time.

If the data shows a long, light brake phase that continues after the car should be ready to turn, the next objective is not simply brake later. The next objective is to change the shape of the brake event and review the result. You might target a cleaner initial application and a more deliberate release, then compare speed at the first half of the corner and the segment time. If the trace gets cleaner but the car becomes less stable, you have learned something else: the release shape and balance need more work before you blame the car. If the trace gets cleaner and the section improves, the logbook can record the behavior that helped.

This is how the logbook protects you from a common intermediate trap. The symptom was slow first half of the corner. The first story was maybe I should brake later. The evidence may show that the real target is not a heroic later brake point but a more useful brake pressure shape.

Worked example: different cars, same loop

The bonded material names Formula Dodge, Showroom Stock, and Indy Cars as examples of specific race cars whose handling, tire choices, chassis adjustments, and driving modifications can be analyzed from real-world data. That matters because a logbook habit must survive different cars.

Do not copy a conclusion from one car category to another just because the words sound similar. A note that helped in a Formula Dodge does not automatically tell you what a Showroom Stock car wants, and neither automatically tells you what an Indy Car wants. But the loop is the same. Before the session, write the objective and plan. After the session, write the conditions, car changes, result, and evidence. Use the relevant channels to check the story. Compare where the comparison is fair. Set the next objective.

The discipline is transferable even when the answer is not. That is why the logbook format should be stable: it lets you adapt the diagnosis to the car without changing the thinking process every weekend.

Common mistakes

Mistake 1: writing a memory dump instead of a loop. A memory dump says the car was bad, the driver was frustrated, or the lap time was disappointing. Good looks like objective, plan, conditions, changes, result, evidence, and next objective.

Mistake 2: starting after the session. If there was no pre-session objective, the review has no target. Good looks like writing the objective and the technique plan before the car goes out, then judging the session against that plan.

Mistake 3: treating feel as proof. Feel is valuable, but it is not the whole diagnosis. Good looks like recording feel separately from evidence, then checking the related channels: throttle trace for throttle problems, brake pressure trace for braking problems, GPS line and segment times for line or section problems.

Mistake 4: using too many channels to avoid deciding. Data software can show steering, RPM, gear, GPS line, G-sum, total steer angle, throttle histogram, segment reports, fastest rolling, theoretical fastest, and more. Good looks like choosing the channels that answer the objective and leaving the rest for later.

Mistake 5: ignoring incongruencies. If the driver report and data disagree, that is not an annoyance. It is the next useful clue. Good looks like writing the disagreement directly and setting the next objective to resolve it.

Mistake 6: logging changes without results. A note that lists a car change but not the session result cannot teach you much later. Good looks like recording what was changed, what happened, and what still needs to be changed or tested.

Mistake 7: never looking back. The logbook earns its keep when you return to the same track or the same problem. Good looks like reviewing prior entries before the next event and carrying forward the unresolved objective instead of starting from zero.

Drill: three-session close-loop progression

Run this drill at your next event for three consecutive sessions. The count is three sessions. The time budget is five minutes before each session, ten minutes immediately after each session, and twenty minutes at the end of the day. The success criterion is three complete loops, each with an objective, plan, conditions, changes, result, evidence check, and next objective.

Before session one, choose one driver behavior from the basic data list: throttle hesitation, coasting, early throttle followed by lift, inconsistent brake pressure, long brake tail, line variation, or segment loss. Write the objective, the plan, and the channel you will inspect. Do not choose the whole lap.

After session one, write conditions and changes first. Then write the feel report. Then inspect only the channels tied to the objective. Close the entry with a next objective for session two.

Before session two, copy the next objective into the pre-session box. This is the part that closes the loop. Run the session with that target. Afterward, repeat the same review. Compare session two with session one if the conditions and traffic make the comparison useful.

Before session three, choose whether to continue the same target or move to the next question. Do not move on just because you are bored. Move on only if the evidence says the question is answered enough for today. At the end of the day, read all three entries and write a two-sentence summary: what improved, and what the next event should begin with.

You pass the drill if another driver, instructor, or mechanic could read your three entries and understand what you tested, what evidence you used, and what the next track session should try.

When to refuse a conclusion

Do not close the loop with a confident conclusion when the evidence is incomplete. If the session had heavy traffic, say so. If the channel you needed was unavailable, say so. If the driver changed technique at the same time the car changed setup, say so. If the throttle trace and driver report disagree, say so. If the brake trace is inconsistent, do not pretend a chassis change received a clean test.

A disciplined logbook can end with unresolved. That is better than inventing certainty. The next objective can be to gather the missing evidence, repeat the test in cleaner conditions, compare against a better reference lap, or simplify the problem to one corner and one behavior. Honest unresolved notes are part of the loop because they stop you from wrenching on a guess.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Speed Secrets Professional Race Driving Techniques Ross Bentley	a009c9a4-cb8d-b3b5-063d-33e44ea0b5cb	76	1	uio_books_raw_v1
2	Data for Drivers	cabda699642b26311b0a7ef998da2c71	15	1	uio_books_raw_v1
3	Data-for-Drivers-PRINT	b80dc634-a0a7-d6de-d470-353aed47e2a6	17	1	uio_books_raw_v1
4	Data for Drivers	27ec1aea-60bb-f052-9a1a-294b72597f55	17	1	uio_books_raw_v1
5	Going Faster Mastering the Art of Race Driving - Carl Lopez	4285b990-c3e7-880e-5596-99af145b469c	300	1	uio_books_raw_v1
6	Speed Secrets Professional Race Driving Techniques Ross Bentley	3aa22935-d523-f6c2-00af-f6db3831cbe9	64	1	uio_books_raw_v1
7	Ultimate Speed Secrets - Ross Bentley	4400491c-451f-86fc-590c-1fa83983aef9	12	1	uio_books_raw_v1
8	Speed Secrets Professional Race Driving Techniques Ross Bentley	8b546b81-602a-e872-facb-d67640333134	6	1	uio_books_raw_v1
9	Advanced Automotive Fault Diagnosis. Automotive Technology. Vehicle Maintenance and Repair Tom Denton	cc59f603-84a8-dcb9-5da5-5cc6797ecbe8	39	1	uio_books_raw_v1
10	Ultimate Speed Secrets - Ross Bentley	536ffcb0-b4fd-90e0-b1a6-b29d29b9de0f	217	1	uio_books_raw_v1