Write the next session before you drive it

Generated from content/lms/data-interpretation-ii-advanced/05-from-data-to-adjustment/02-writing-the-test-plan.md; edit the source file, not this page.

Source path: content/lms/data-interpretation-ii-advanced/05-from-data-to-adjustment/02-writing-the-test-plan.md

Course: Read the data your hands can't feel

Module: Turn findings into session plans that work

Estimated duration: 55 minutes

This lesson is about the moment after analysis and before you strap in again. You have looked at the data. You have seen something that does not match the lap you thought you drove. You may have compared against another lap, another driver, or your own best reference. Now the useful work is not more staring. The useful work is writing the next session before you drive it.

A written test plan is not a setup sheet, a diary entry, or a wish list. It is the bridge between the evidence you found and the behavior you will perform in the car. Ross Bentley is blunt about the driver keeping records: before each session he writes down objectives and the driving techniques or plans needed to achieve them, then after the session he records track conditions, changes, and results. That is the core of this skill. You are not going out to see what happens. You are going out to test one clear driving idea against the track, the car, and the data.

This sits beside three sibling skills in this module. One lesson teaches committing to one objective. Another teaches committing to one change. Another teaches calibrating data against a faster reference. This lesson assumes you have already done that selection work. Here, your job is to turn the chosen objective into a usable session card: what you will do, where you will do it, what you expect to feel, what channels or observations will verify it, and what you will write down afterward.

The principle: analysis only helps when it changes the next lap. Bentley points out that driving cannot be learned only by the book; it must be learned through hands-on experience. He also explains that understanding the theory and picturing it before driving makes you more sensitive to the experience. That is exactly why the test plan matters. The plan gives your hands-on experience a target. It tells your attention where to go before the noise of the session starts.

Data work follows the same pattern. The Data for Drivers process moves from overview, to incongruencies, to details, to checking other channels, to asking why, to comparison, to calibration against your own driving, to imagining the ideal, and finally to setting objectives for the next session. Notice the order. You do not jump from one strange trace directly into a heroic fix. You first make sure you understand what you are seeing, then you decide what action deserves a session.

A useful next-session plan has five parts.

1. The finding: the specific thing the data or debrief showed you.

2. The hypothesis: the driving reason you think caused it.

3. The action: the exact behavior you will perform in the car.

4. The check: the data channel, comparison, or felt cue that will tell you whether the action happened.

5. The debrief prompt: the question you will answer immediately after the session.

Keep those five parts short enough that you can carry them in your head. The point is not to create paperwork. The point is to keep the session from dissolving into vague effort. A plan that cannot survive the grid, traffic, flags, heat, and adrenaline is too complicated.

Start with the finding. Do not write a plan from emotion. Write it from evidence. The finding can come from a speed trace, throttle trace, throttle histogram, video, instructor notes, or your own logbook. Data for Drivers tells you to look for incongruencies and dig for details. That means the finding should be narrow. Not I am slow. Not the car feels bad. A better finding is that your throttle trace shows hesitation after the minimum-speed point on two laps, or that your best lap carried more speed into a corner but lost speed later, or that the same corner produced a different steering or throttle pattern than the reference.

Then write the hypothesis. This is where many drivers get sloppy. The hypothesis is not yet the truth. It is the explanation you are testing. Data for Drivers keeps returning to asking why, and that matters because a trace is not a confession. If the throttle opens later, the cause could be entry speed, line, confidence, car balance, vision, traffic, or a setup effect. Your plan should say what you think is most likely and what you will do to test it.

The action must be a driver action, not a mood. Try harder is not an action. Be smoother is not an action. Brake earlier by a small, repeatable amount at the same reference, release with more patience, look earlier to the exit, or commit to a throttle pickup point are actions. They are things you can perform. They are also things you can review after the run.

Keep the action tied to the evidence. If the evidence is in throttle and speed, do not write a plan about every input in the corner. If the issue appears only after a setup change, include the setup note in the debrief, but do not let the car become the whole story. Bentley says understanding chassis and suspension adjustments and what they mean to you as a driver is part of the job. He also frames his driving instruction around what the driver may be doing to cause a problem and how to identify and correct it. So your plan can include the car, but it should still ask what you will do from the seat.

The check is what keeps the plan honest. You decide before the session how you will know whether the experiment worked. Data for Drivers tells you to use other channels if available, compare if you can, and calibrate to your driving. That gives you three kinds of checks. First, a data check: did the speed, throttle, or histogram change in the area you targeted. Second, a comparison check: did the target lap move closer to your own best or faster reference. Third, a driver check: did the action feel like what you planned, and did the car response match the data.

The debrief prompt must be written before you drive because after the session your memory will be noisy. You will remember the pass, the slide, the flag, or the lap that felt good. You may forget the quiet detail that mattered. Bentley recommends writing comments after each session on track and conditions, car changes made and needed, and the results. That is the debrief loop. If you know the prompt beforehand, you can collect the right memory while it is fresh.

A strong debrief prompt is specific. Did I pick up throttle earlier at the same place, and did the car accept it. Did I release the brake in a way that let the car rotate without forcing me to wait. Did the setup change alter the problem, or did my input pattern remain the same. Did the track condition change enough to explain the result. These questions are useful because they can be answered. They also tell you whether to keep the same test, refine it, or move on.

The mechanism behind the skill is simple: you are converting open-ended practice into a controlled learning cycle. The corpus repeatedly points toward learning through use, records, practice, preparation, and returning to material as a reminder. Data analysis can reveal useful information, but only if you extract what is worthwhile and make it practical. A written plan makes the data usable in the cockpit.

There is a second mechanism: the plan protects attention. The cockpit is not a calm office. You cannot analyze every channel while braking, turning, looking, feeling grip, and sharing the track. If you try to carry five theories into the run, you will drive none of them well. The written plan narrows attention to the one behavior that matters in that session. That does not mean ignoring safety, traffic, or flags. It means your performance attention has a preassigned job.

There is a third mechanism: the plan separates testing from judging. Intermediate drivers often look at data and immediately grade themselves. That creates emotion, not learning. The plan asks a better question: what should the next session test. The result might prove the hypothesis wrong. That is not failure. That is a useful result. If the throttle pickup did not move, you know the planned action did not happen or the cue was not strong enough. If the throttle pickup moved but the speed did not improve, you know the cause was probably elsewhere. Either way, you learned.

Use this session-card template.

Finding: what did the data, video, comparison, or logbook show.

Why I think it happened: what is the likely driver or car reason.

Next-session action: the exact input, reference, or attention target.

Where: the segment, corner type, or repeated situation where you will apply it.

Success check: the data signature, felt cue, or comparison that will count as evidence.

Debrief prompt: the question you will answer as soon as you get out.

Conditions note: track, weather, traffic, tires, fuel, setup, or anything that could explain the result.

That last line matters because the same session does not happen twice. Bentley specifically includes track and conditions in the post-session record. If you ignore conditions, you may credit the plan for a gain caused by track improvement, or blame yourself for a loss caused by heat, traffic, or a car change. You are not trying to write a laboratory paper, but you are trying to avoid fooling yourself.

For an intermediate driver, the hardest part is usually making the action concrete enough. A good test-plan action sounds almost boring. It might be one braking reference, one release shape, one throttle pickup, one line cue, or one comparison point. It does not sound like a whole new personality. The plan should tell you what to do on lap three when the tires are in, what to do again on lap four, and what to notice if it works.

Before you write the plan, complete a quick evidence pass. First, take the overview. What is the broad difference in lap, segment, or behavior. Second, find the incongruity. What does not match your memory or expectation. Third, dig into the details. Zoom into the area that matters. Fourth, check another channel if you have one. Speed alone can mislead; throttle, brake, steering, video, or gear position may explain more. Fifth, ask why. Sixth, compare if possible. Seventh, calibrate to what you actually did in the car. Eighth, imagine the ideal trace or behavior. Ninth, write the objective.

Do not skip the calibration step. It is tempting to treat the data as separate from you, as if the trace is the driver and you are just reading it. The process says to calibrate to your driving. That means you connect the line on the screen to your memory of what you did with your feet, hands, eyes, and timing. When the trace says you waited on throttle, ask what you were waiting for. Grip. Rotation. Vision. Confidence. Space. If you do not connect the trace to an actual in-car cause, the plan becomes generic.

Do not skip the ideal step either. Imagining the ideal does not mean fantasizing a perfect lap. It means forming a practical picture of what better would look like. Bentley says picturing the theory clearly before you start driving makes you more sensitive to the experience. If you can picture a cleaner throttle pickup, a more deliberate release, or a calmer steering trace before you leave the paddock, you have a better chance of recognizing it when it starts to happen.

There is also a limit to the plan. The plan does not guarantee speed. It guarantees a better question. Winning and improvement come from work, determination, skill, practice, preparation, and continued analysis. The session plan is one tool in that chain. It will not replace seat time, instruction, mechanical understanding, or judgment. It makes those things line up.

Here is what improving at this skill feels like. Your pre-session notes get shorter and sharper. Your debriefs get more factual. You stop writing that the car was bad and start writing what the car did, where, under what input, and after what change. You stop saying the data is confusing and start saying what you need to check next. You become less attached to being right about the cause and more attached to running the next useful test.

The data signature improves too. You should see fewer random experiments inside the same session. The targeted channel should show whether you attempted the planned behavior. If the plan was earlier throttle pickup, the throttle trace should answer that. If the plan was a different approach to an oversteer problem, your notes and available channels should show whether your input changed before you blame the car. If the plan was to compare against a reference, the next review should have a narrower comparison instead of a new pile of unrelated observations.

The instructor signature is just as clear. A good instructor reading your log should be able to understand what you intended, what happened, and what you want to test next. They may disagree with your hypothesis, but they should not have to guess what the session was for. If your coach has to ask what you were trying to accomplish, the plan was not written clearly enough.

Finally, remember that records become more valuable when you return to the same track or problem. Bentley specifically says to learn from records by looking back when returning to the same track or when having a problem with a specific area of driving. That means the test plan is not only for the next twenty minutes. It is future evidence. Months later, you want to know what you tried, what changed, and what the result was. A vague memory will not give you that. A short session card will.

Worked example: from throttle trace to next-session behavior

You review two laps and the useful evidence is not your emotion about them. It is the comparison. The corpus describes a throttle histogram comparing the percentage of throttle openings for two laps, plus speed and throttle position over the course of a lap. That is enough to build a clean test plan.

Finding: in the target segment, one lap shows a later or less committed throttle pattern than the lap you want to match. The speed trace gives you the result, and the throttle trace gives you one likely cause.

Hypothesis: you may be waiting because the car is not pointed, because you carried a different entry, or because your eyes and confidence are late. You do not know yet. You only know that the throttle behavior is worth testing.

Action: on the next session, choose the same segment and make the first throttle pickup a deliberate event rather than a hopeful squeeze after the car is already settled. Your job is not to floor it blindly. Your job is to arrive at the planned pickup point with enough car balance and vision that the throttle can begin there.

Check: after the session, compare the throttle position and speed in the same segment. If the throttle pickup moved earlier but speed did not improve, the action may have exposed another limiting factor. If the pickup did not move at all, the plan was not executed or the cue was too vague. If the pickup moved and the speed trace improved without a control problem, the plan deserves another session or a refined version.

Debrief prompt: what was I waiting for at throttle pickup. Answer that immediately, while you can still remember whether it was grip, line, rotation, traffic, or confidence.

Worked example: oversteer that may be driver-created

A driver comes in saying the car oversteers. That may be true, but it is not yet a useful test plan. Bentley frames his driver instruction around identifying what the driver may be doing to cause oversteer and how to correct it. The data process also tells you to ask why and use other channels if available. So the plan begins by refusing to jump straight to a setup conclusion.

Finding: the car rotates more than you want in one repeated situation. You may have data, video, instructor notes, or only a reliable driver log.

Hypothesis: before changing the car, you will test whether your entry, release, steering, or throttle timing is contributing to the oversteer. If there was a chassis or suspension adjustment, you note it, because understanding adjustments and what they mean to you is part of the driver job. But you still write a driver action.

Action: pick the repeated situation where the oversteer appears and change only the input you believe is most responsible. If you believe the issue is caused by an abrupt release, the action is a more deliberate release. If you believe the issue is caused by asking for throttle before the car accepts it, the action is a cleaner pickup. If you believe the issue is caused by steering demand, the action is a calmer, smaller request.

Check: after the session, record track conditions, what changed on the car if anything, what input you changed, and what result followed. If the same oversteer remains with a confirmed input change, the next hypothesis may involve setup or another driver input. If the oversteer changes when your input changes, you have found useful driver leverage.

The important part is not proving that the car was innocent. The important part is writing a test that separates car behavior from driver contribution.

Worked example: first oval session after road-course habits

Bentley gives a useful learning example: road racers he coached became strong oval racers because they had little oval experience, received coaching early, and developed the right habits before bad habits formed. For this lesson, treat that as a session-planning example rather than an oval technique lesson.

Finding: the situation is unfamiliar, and your normal road-course habits may not transfer cleanly. You need a plan that helps you learn the new situation rather than drive it with old assumptions.

Hypothesis: the fastest learning will come from entering the session with a small number of intended habits instead of trying to interpret everything at speed. This matches the broader idea that picturing the theory before driving makes you more sensitive to the experience.

Action: write one habit for the first session. It might be a visual habit, a steering habit, or a patience habit, depending on what your instructor and data indicate. Do not write a plan to master the whole discipline. Write a plan to avoid installing the wrong first habit.

Check: after the session, do not only record lap time. Record what you saw that was new, what habit you actually used, and what surprised you. The Performance Driving Illustrated chunk shows the driver asking what is present that has not been seen before; that is a useful attitude for an unfamiliar segment or track type. The next plan should come from what you learned, not from defending the habit you arrived with.

Drill: three-card next-session progression

Do this drill over three sessions at your next event. The count is three written cards, one per session. The duration is five minutes before each session and five minutes immediately after each session. The success criterion is that each card produces one clear answer that affects the next card.

Before session one, write a baseline card. Use one finding from your last data review or last logbook entry. Write the finding, hypothesis, action, check, and debrief prompt. Keep it to one segment or repeated situation. Drive the session with normal safety margins and make the planned action only where appropriate.

After session one, answer the debrief prompt before doing a long data review. Then check the data or available evidence. Mark one of three results: action confirmed, action not confirmed, or action confirmed but hypothesis unsupported. If you cannot mark one, your card was too vague.

Before session two, write the refinement card. If the action was not confirmed, make the cue more concrete. If the action was confirmed but the result did not move, change the hypothesis rather than adding three more actions. If the action and result both moved, repeat once to confirm it was not noise.

After session two, again answer the prompt and check the evidence. Before session three, write the decision card. Your decision is one of three: keep developing this objective, retire it because the target behavior is now reliable, or move to the next objective because the evidence points elsewhere.

This drill is deliberately plain. It trains the habit Bentley describes: write objectives and plans before the session, record conditions and results after the session, and learn from the record when the same track or problem returns.

Common mistakes

The first common mistake is writing a wish instead of a plan. The note says be smoother or go faster, but there is no action. Good looks like a specific behavior in a specific place, with a check you can review afterward.

The second mistake is treating one data trace as the whole truth. Data for Drivers tells you to dig for details and use other channels if available. Good looks like a finding that has been checked against at least one other source when possible: another channel, video, comparison, or your own calibrated memory.

The third mistake is skipping the why step. You see late throttle and decide to force earlier throttle. That may work, but it may also hide the real cause. Good looks like a hypothesis that says why the behavior happened and what the next session will test.

The fourth mistake is blaming setup before writing a driver test. Setup matters, and Bentley says drivers must understand chassis and suspension adjustments. But a setup note is not a substitute for a driver action. Good looks like recording the car change while still asking what input, timing, or decision you will test from the seat.

The fifth mistake is changing the plan mid-session because a lap felt bad. Traffic, conditions, and normal variation can make a single lap misleading. Good looks like staying with the planned test long enough to collect evidence, unless safety or instruction requires you to stop.

The sixth mistake is debriefing too late. If you wait until the trailer is packed or the drive home has started, your memory edits itself. Good looks like answering the debrief prompt immediately, then reviewing data with that fresh memory available.

The seventh mistake is keeping records that cannot be reused. A notebook full of vague comments does not help when you return to the same track or problem. Good looks like a record that names the finding, action, condition, and result clearly enough that future you can restart the learning loop.

Quick checklist before you grid

Read the card once. Can you say the action in one sentence. Can you say where it applies. Can you say what evidence will count afterward. Can you still drive safely if traffic ruins the target lap. If any answer is no, simplify the plan before you leave the paddock.

The best next-session plan feels almost too simple on paper. That is its strength. It leaves enough attention for the real work: driving the car, feeling the result, and bringing back evidence you can trust.

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-PRINT	bbb02386-778f-20ec-ad16-b9c016921743	16	1	uio_books_raw_v1
3	Ultimate Speed Secrets - Ross Bentley	0237a5bd-e2d4-724e-bc2e-ba13db924f66	11	1	uio_books_raw_v1
4	Ultimate Speed Secrets - Ross Bentley	4400491c-451f-86fc-590c-1fa83983aef9	12	1	uio_books_raw_v1
5	Speed Secrets Professional Race Driving Techniques Ross Bentley	3d51ef4c-3272-cfbd-9d7d-5a6a011ef252	6	1	uio_books_raw_v1
6	Speed Secrets Professional Race Driving Techniques Ross Bentley	26bc8e35-76a6-4f72-ea86-df10ba43a636	14	1	uio_books_raw_v1
7	Ultimate Speed Secrets - Ross Bentley	149c4d5c-d228-0358-acc0-8a92ac07ec7c	50	1	uio_books_raw_v1
8	Competition Car Aerodynamics 3rd Edition McBeath Simon	cd94958f-1042-ceff-8d99-06fa06ac633b	504	1	uio_books_raw_v1
9	Data-for-Drivers-PRINT	b80dc634-a0a7-d6de-d470-353aed47e2a6	17	1	uio_books_raw_v1
10	Speed Secrets Professional Race Driving Techniques Ross Bentley	8b546b81-602a-e872-facb-d67640333134	6	1	uio_books_raw_v1
11	Performance-Driving-Illustrated-Ross-Bentley	d03d8129-9884-8385-fe77-b2af5835c3e6	1	1	uio_books_raw_v1
12	Ultimate Speed Secrets - Ross Bentley	7816dd86-ce80-1320-b6ed-b34e005cc98f	16	1	uio_books_raw_v1