Build a session log that survives the season
Generated from
content/lms/race-car-engineering-and-operations/05-debrief-and-continuous-improvement/02-session-note-keeping.md; edit the source file, not this page.
Source path: content/lms/race-car-engineering-and-operations/05-debrief-and-continuous-improvement/02-session-note-keeping.md
Course: Run the paddock like a race engineer
Module: Close the loop every session
Estimated duration: 55 minutes
A session log is not paperwork. It is the memory system that lets you turn one session into the next session instead of starting over every time you buckle in. At the intermediate level, you already know that speed comes from repetition, preparation, and honest review. The problem is that most drivers do not lose lessons because they were lazy. They lose them because the lesson was never written in a form that could survive heat, noise, lap-time emotion, car changes, and the six-week gap before they return to the same track.
The principle is simple: every session note must connect five things in one chain. What were you trying to do? What were the track and weather conditions? What did you or the crew change on the car or in the driving plan? What happened? What will you do next? If one of those links is missing, the note may still be interesting, but it is not yet useful. A useful log lets you look back before a later race, practice, test, or qualifying session and recover the decision you made, the reason you made it, and the evidence that supported it.
This lesson sits beside the debrief and experiment lessons in this module, but it is narrower. A debrief is the conversation that turns a run into a plan. Treating a weekend as experiments is the discipline of changing one thing and looking for the result. The session log is the durable artifact that lets those habits survive the season. Without it, the best debrief evaporates. Without it, experiments become scattered guesses. With it, your season becomes a connected body of evidence.
Why the log matters more than memory
Ross Bentley's records guidance is blunt about the purpose: a driver should keep a log for every race, practice, test, or qualifying session and use it when returning to the same track or when struggling with a specific part of the driving. That is the first design requirement. Your log is not only a diary of what happened today. It is a tool for the next time you face this track, this car behavior, this corner type, this brake-release problem, or this weather pattern.
The second design requirement is that the log has to protect you from relearning the same lesson. Bentley compares the driver to a car engineer who keeps no notes on changes. That engineer would be ineffective because nobody could know which change caused which result. The same applies to you. If you change your brake release, your reference point, your tire pressure, your gear choice, or your setup language and then write only that the session felt better, you have not preserved the reason. A month later, better will be too vague to act on.
The third requirement is that the log must connect driver learning with data. The data chunks in this bond do not say to drown yourself in channels. They repeatedly point the other way: start with an overview, look for incongruencies, dig for details, use other channels when available, ask why, compare when you can, calibrate the data to your driving, imagine the ideal trace, and set objectives for the next session. That is the rhythm of a season-proof log. You do not need a perfect engineering report after every session. You need enough structured evidence that your next objective is not a guess.
The fourth requirement is humility. The corpus keeps returning to learning: keep learning, keep it simple, focus on the basics, ask why, and keep learning again. Bentley also frames driving as something you learn through hands-on experience faster when you understand the theory before you drive. A good log sits between theory and experience. It turns a vague impression from the seat into a specific question, then turns data or comparison into the next piece of practice.
The page layout that works
A season-proof session page needs a stable shape. Do not redesign the form every weekend. The point of the template is that you can compare entries across time. Use whatever medium you will actually maintain: notebook, tablet, spreadsheet, Tracky logbook, or printed sheets in a binder. The medium matters less than the fields. The fields matter because they force the right questions.
Start with the event header. Record the date, track, car, session type, best lap time, fastest car's lap time if you know it, and weather conditions. Bentley specifically calls for date, car, best lap, fastest car, and weather. Those details are not filler. They explain why the same lap time may mean different things on different days. They also let you separate a driving improvement from a weather shift, car change, or field comparison.
Next, record the pre-session objective. Before each session, Bentley writes down the objective and the driving techniques or plans needed to achieve it. That is the heart of the system. An objective is not a wish to go faster. It is the behavior you intend to practice. A useful objective might be to release the brake earlier and cleaner in one corner, stop coasting before throttle pickup, use a specific turn-in reference, or compare third gear against fourth gear through a section. The plan names what you will do with your hands, feet, eyes, or decision timing to achieve that objective.
Keep the objective small enough to remember in the car. The data guidance says keep it simple and focus on basics. If you give yourself six objectives, you have written a menu, not a plan. Your page may contain many observations, but the pre-session target should be narrow. One primary objective and one secondary watch item are enough for most sessions. The log's job is to make progress traceable, not to prove that you thought about every possible thing.
Then record the expected evidence. This does not have to be a formal hypothesis, but it has to say what will make the session readable afterward. If the objective is cleaner brake release, your evidence may be the brake pressure trace shape, whether the long tail is reduced, whether the car rotates more predictably, and whether segment time improves without losing exit speed. If the objective is earlier confident throttle, your evidence may be the throttle trace, coasting time, early application followed by lift, or section time. If the objective is a reference-point change, your evidence may be whether the car reaches the same apex and exit with less steering correction. This is how the log connects plan to review.
The driver-drawn track map
Bentley recommends drawing your own track map at each track, not only using a printed map. The reason is important: you need to draw the track as you see it, not necessarily as it really is. That line should change how you use maps. A printed map is good reference material, and you can keep one for comparison, but your own map captures the driver's job: what the corner looks like from your seat, where your eyes go, what reference matters, and where the car's behavior changes.
On the map, mark the gears used in each turn. Mark your turn-in references, apex references, and exit references. The corpus examples include turn-in at a crack in the pavement and apex at the end of the curbing. You do not need to use those exact references; you need references at that level of specificity. Mark elevation changes and surface changes, because those alter the way the car feels and the way you should interpret a session. Mark good places to pass. Mark any especially challenging part of the track and why it is challenging.
This is not art. A useful map can be ugly. It only needs to recover your perception later. The next time you arrive at the same track, that map should help you remember where the car got light, where you ran out of confidence, where the pavement changed grip, where you missed the apex when you looked too late, or where a pass is realistic. Bentley's track-personality point matters here: every racetrack has its own personality, and even similar layouts feel different. Your map records that personality in the language of your own driving.
The after-session download
After each session, record track and conditions, changes made, changes that need to be made, and the result of the session. That sequence is straight from the records guidance, and it gives you the minimum complete after-session download.
Track and conditions come first because they frame everything else. Was the track green, rubbered-in, damp, hot, cold, windy, or changing? Did traffic shape the run? Was the session a practice, test, race, or qualifying run? The bond does not provide a detailed weather model, so do not invent one. Record the conditions plainly enough that your future self understands the context.
Changes made come next. This includes both car changes and driver-plan changes. If tire pressure changed, write it. If bar, damping, alignment, or ride-height language enters the conversation, write what was changed and why. Bentley states that understanding chassis and suspension adjustments and what they mean to you as a driver is a critical part of the job. The log does not need to become a chassis textbook, but it must preserve the adjustment and the driver-facing reason. If you do not understand the change, write the question and ask someone to explain it.
Then record the result. Result does not mean only best lap. It includes whether the objective was attempted, whether the behavior changed, whether the car felt better or worse in the target area, whether a new problem appeared, and what the data or timing showed. A best lap with no explanation is fragile. A slower lap with a clean behavior change may be valuable. A fast lap with an early throttle application followed by a lift may be less stable than it looks. Your log should make those distinctions possible.
Finally, record what needs to be done next. This is where the log becomes a plan rather than a scrapbook. The Data for Drivers process ends with setting objectives for the next session. That is not an afterthought. It is the point. If the next objective is not written, the next session begins with whatever feeling is loudest in your head. If it is written, you can use the next run to continue the work.
How to use data without drowning in it
Data belongs in the log, but not as a giant dump. The process in the bonded data chunks is disciplined: overview, incongruencies, details, other channels, why, comparison, calibration, ideal, next objective. Use that order.
Start with the overview. What does the lap or session say at a high level? Is the time loss concentrated in one segment? Is the issue repeated lap-to-lap or only on one lap? Does the fastest rolling lap or theoretical fastest suggest that your best pieces exist but are not connected? Segment and section reports can help here. So can a simple comparison to a better lap if you have one. The point is not to admire squiggly lines. The point is to find the one question that matters next.
Then look for incongruencies. An incongruency is a mismatch between what you thought happened and what the evidence shows. You thought you were early to throttle, but the trace shows coasting. You thought you were decisive, but the throttle trace shows hesitant application. You thought earlier throttle helped, but the trace shows early application leading to a lift. You thought the car was flat through a fast corner, but the trace shows a lift. You thought the brake zone was consistent, but brake pressure shows inconsistent initial pressure or a long, light tail. Those mismatches are where learning lives.
Dig for details only after the overview points you there. For throttle, the bonded prompts are clear: look for coasting, hesitant application, early application leading to a lift, and lifts in fast corners. For braking, look at the shape of the brake pressure trace: initial application, trail, and whether there is a long tail. Look for inconsistent pressure. Compare light and long braking against hard and short braking when that question fits the corner. Other channels can help check your interpretation: steering, RPM, gear, section times, GPS line, G-sum, total steer angle, and throttle histogram.
Use channels to check each other. If the throttle trace shows hesitation, check whether steering angle was still high. If brake pressure has a long tail, check whether throttle starts late. If GPS line shows you missed the apex, check whether the turn-in reference on your map matches what you actually drove. If RPM or gear choice changed, make sure you know whether the time gain came from driving technique or from gearing. The data guidance says use other channels if available to check. That is how you avoid building a story around one trace.
Calibrate the data to your driving. That phrase matters. A trace is not the car by itself; it is the trace of you driving the car in those conditions. The log should preserve what the data meant from the seat. Write the data observation and the driver observation together. For example: throttle trace shows a pause before pickup; from the seat, I was waiting because the car felt wide at apex. Or: brake pressure has a long tail; from the seat, I was using brake to finish rotation. That pairing makes the data teachable.
Imagine what ideal would look like, but keep it grounded. Ideal does not mean fantasy. In this context it means a trace and lap shape consistent with the objective. If you are trying to stop coasting, ideal may be a cleaner transition from brake release to throttle pickup. If you are trying to reduce a lift in a fast corner, ideal may be a steadier throttle trace and a line that does not require correction. If you are working on braking, ideal may be a more repeatable pressure shape. Write the ideal in practical terms, then set the next objective.
Worked example: returning to the same track after a gap
Imagine you are returning to a track you drove earlier in the season. You have not been there for months. Without a log, your first session becomes a memory hunt. You remember that one corner was awkward, that the car felt nervous somewhere, and that you found a passing spot late in the day. That is not enough.
With a season-proof log, your first session starts before you arrive. You open the track page. The header tells you the car you drove, the date, weather, best lap, and fastest car's lap. The map shows the gears you used in each turn. It marks a turn-in reference, an apex reference, an elevation change, a surface change, a passing area, and a corner you labeled as challenging with the reason. The previous after-session note says what changed and what needed to change next.
Your pre-session objective writes itself from the old evidence. You do not need to solve the whole track. You choose the one section that the old page shows was still unresolved. The plan names the driving technique you will use. The expected evidence names the trace or observation that will prove whether the work improved. After the session, you update the same track map and compare the new result to the earlier note. That is how a log survives the season: it lets an old lesson become the first step of the next event.
Worked example: the throttle hesitation that is really a brake-release problem
Now imagine a practice session where your note says the car will not drive off a corner. The lazy version of the log would say poor exit, need more throttle. That may be true, but it does not tell you why. The data-review process gives you a better path.
Start with the overview. The segment report says the time loss is in the section after the corner, not at the braking marker. Your best rolling or theoretical fastest suggests you have made good speed elsewhere, so this is a targeted issue. The throttle trace shows coasting before pickup, then a hesitant application. On one lap, it shows early application followed by a lift. The brake pressure trace shows a long tail into the same corner. Steering angle is still significant when throttle starts.
Now the log can hold a useful diagnosis without pretending to know more than the data supports. The issue may not be courage with the throttle. It may be that the brake release is late or messy, keeping the car from being ready to accept throttle. The next objective should not be simply get to throttle earlier. It should be something like finish brake release cleaner at the target reference, let the car take a set, and pick up throttle once steering is unwinding. The evidence will be a shorter or cleaner brake tail, less coasting, less hesitant throttle, and better section time without an early lift.
This example uses the log properly because it connects seat impression, data channels, why, and next action. It also protects you from the common false fix of adding throttle to a car that is not yet prepared to use it.
Worked example: the setup change that disappears without notes
A driver reports that the car was better in the afternoon. The team changed something. The driver also changed a reference point. The track temperature changed. Traffic was lighter. If nobody writes the chain down, the conclusion is almost useless. The next event will begin with a story, not evidence.
A season-proof log handles the same session differently. The pre-session objective says what the driver intended to change. The car-change field records what was adjusted and why. The condition field records the weather and track state. The result field records the lap time, the target-section behavior, and any data observation. The next-action field separates car follow-up from driver follow-up. If the car engineer analogy from Bentley makes you uncomfortable, that is useful. A driver who keeps no notes about driver changes is doing the same thing as an engineer who keeps no notes about car changes.
Calibration cues: how you know the log is improving
The first cue is that your next-session objectives become easier to write. If every after-session page ends with a specific next action, you should not need to invent a plan in the grid. You already have one.
The second cue is that your map gets more driver-specific. Early maps may show only the track shape. Better maps show gears, references, surface or elevation changes, passing areas, and hard sections with reasons. The best maps let you return to a circuit and remember how you saw it from the seat.
The third cue is that your data notes get shorter but sharper. At first you may copy too many channels. As you improve, the log should say which trace answered which question. Throttle hesitation, coasting, early throttle followed by lift, brake-pressure shape, gear choice, segment time, and GPS line each belong in the note only when they help answer the session objective.
The fourth cue is fewer repeated mistakes. Bentley's objective is that you should not have to make the same mistake twice or learn the same thing twice. You will still make mistakes. The improvement is that the log catches them, names them, and turns them into a plan instead of letting them reappear as vague frustration.
The fifth cue is better debrief language. Instead of saying the car felt weird, you can say the car would not accept throttle at the target corner, the brake trace still has a long tail, steering is still high at pickup, and the next session should focus on cleaner release. That is the difference between complaint and diagnosis.
Common mistakes
The first mistake is the diary page. It has a lot of feeling and no decision. It says the session was fun, frustrating, loose, crowded, or better. Those words may be true, but they do not survive the season by themselves. Good looks like attaching the feeling to objective, conditions, change, result, and next action.
The second mistake is the lap-time-only page. Lap time matters, and Bentley specifically includes best lap and fastest car's lap in the record. But lap time without conditions, car, objective, and result can mislead you. Good looks like recording the lap time as context, then explaining what produced it or what prevented a better one.
The third mistake is the data dump. This driver pastes in charts or writes every channel name but never asks why. The bonded data process is not more channels for their own sake. It is overview, incongruency, detail, cross-check, why, comparison, calibration, ideal, and objective. Good looks like one or two data observations that change the next plan.
The fourth mistake is the orphan setup change. A pressure, bar, damper, alignment, or other chassis change gets made, but the log does not record why or what resulted. Good looks like writing the change, the driver problem it was meant to address, the condition it was tested in, the result, and whether the next session needs more car work or more driver work.
The fifth mistake is the printed-map-only habit. A printed map is useful, but Bentley's point is that your own map records the track as you see it. Good looks like drawing your own version and marking gears, references, elevation, surface changes, passing places, and difficult pieces with the reason they are difficult.
The sixth mistake is the objective pileup. The driver writes everything they want to fix, then cannot remember any of it at speed. The data guidance says keep it simple and focus on basics. Good looks like one primary objective, one watch item if needed, and a defined piece of evidence.
The seventh mistake is the answer without the question. The driver looks at a throttle or brake trace and declares the fix before asking what problem the session was testing. Good looks like starting from the pre-session objective, then using the trace to confirm, challenge, or refine it.
The drill: three-session season-proof log builder
Run this drill at your next event over three sessions. The total time cost is about ten minutes before each session, fifteen minutes after each session, and one twenty-minute data review after session two or session three if data is available.
Before session one, create the page header and draw a simple track map from memory or from a printed outline. Add gears and two references you already trust. Choose one objective and write the driving technique or plan you will use. Do not write more than one primary target. After the session, fill in track and conditions, changes made, result, and next action. Add at least one map note about a surface, elevation, reference, passing area, or difficult section.
Before session two, read only your own session-one note before writing the objective. The goal is to prove that the log can drive the next plan. Choose the next objective from the prior result. After the session, review one data area if available. If your objective was throttle application, look for coasting, hesitation, early application leading to lift, or lifts in fast corners. If your objective was braking, look at initial application, trail, long tail, consistency, and light-long versus hard-short shape where appropriate. Add one data-backed observation and one question beginning with why.
Before session three, write the objective from the session-two evidence. Add expected evidence before you drive. Afterward, update the map and write the next action. The success criterion is not a lap-time number. The drill succeeds if all three pages connect objective, conditions, change or technique, result, and next action; if the map is more useful after session three than before session one; and if at least one next-session objective came from evidence rather than memory.
When this principle breaks down
The session log is not a substitute for live coaching, engineering judgment, or safety decisions. If the car has a safety issue, stop treating the log as the main tool and deal with the car. If you do not understand a chassis or suspension adjustment, Bentley's guidance is to go back to good sources or ask someone to explain it. The log can preserve the question, but it cannot replace understanding.
The log also breaks down when you confuse correlation with proof. If three things changed at once, the log should say that three things changed. Do not promote the nicest story into a conclusion. Write what happened, what evidence supports it, what remains uncertain, and what you will test next. That keeps the season honest.
The log breaks down when it becomes too big to use. If you need half an hour to fill it out after every short run, you will stop using it. The Data for Drivers guidance to keep learning, keep it simple, and focus on basics is the antidote. The right log is extensive in the season view, not bloated on every page. Each entry should be complete enough to drive the next decision and short enough that you will actually maintain it.
Cross-references
Use this lesson as the written backbone for the sibling lesson on running a debrief that produces a plan. The debrief conversation should draw from the same fields: objective, conditions, changes, results, evidence, and next action. Use the sibling lesson on treating the weekend as a series of experiments when you decide what to change and how many variables to move. Use data-interpretation lessons when the trace question becomes deeper than this log can answer. Use chassis and setup lessons when the log shows repeated car-behavior patterns that require more than a driver technique change.
The standard to hold yourself to
At the end of a weekend, your log should let a future version of you answer practical questions. What did I try? What did the car do? What changed? What did the track and weather do? Which corner or section mattered? What did the data confirm or challenge? What should I do first when I come back?
If your notes can answer those questions, they will survive the season. If they cannot, they are only memories with dates on them.
Worked example: returning to the same track after a gap
A season-proof log turns a return visit into continuation instead of rediscovery. Before the first session back, you open the prior track page and recover the date, car, best lap, fastest car's lap, weather, gears, references, surface or elevation notes, passing areas, and the section marked as difficult. Your pre-session objective comes from that old evidence. After the run, you update the same map and compare the new result against the earlier note. The skill is not remembering everything; the skill is writing the previous event clearly enough that it can coach the first session of the next one.
Worked example: a throttle hesitation that is really a brake-release problem
A driver note that says poor exit, need more throttle is not yet useful. The log becomes useful when it connects the seat impression to the trace. The segment report points to time loss after the corner. The throttle trace shows coasting and hesitant application, with early application followed by a lift on one lap. The brake pressure trace shows a long tail, and steering remains high at throttle pickup. The next objective should not be simply more throttle. It should be cleaner brake release and throttle pickup when the car is ready to accept it, with evidence from brake shape, coasting time, throttle hesitation, and section time.
Worked example: the setup change that disappears without notes
If the car is better in the afternoon but the driver changed a reference, the crew changed the car, the track changed, and traffic cleared, an unwritten conclusion is weak. The log preserves the chain: the driver objective, the car change and reason, the condition, the result, the data observation, and the next action. This follows Bentley's engineer comparison. A driver who keeps no notes about driver changes is as exposed as an engineer who keeps no notes about car changes.
Common mistakes
The diary page records feeling but no decision. The lap-time-only page records outcome but not context. The data dump collects channels without asking why. The orphan setup change records that something was adjusted but not the reason or result. The printed-map-only habit misses the driver's view of the track. The objective pileup creates a plan too large to execute. The answer-without-question error reads a trace without tying it back to the session objective. Good looks like objective, conditions, change or technique, result, evidence, and next action on every page.
Drill: three-session season-proof log builder
Run the drill over three sessions at the next event. Spend about ten minutes before each session and fifteen minutes after each session, plus one twenty-minute data review if data is available. Session one builds the header, map, single objective, plan, and after-session result. Session two uses the first page to create the next objective and adds one data-backed observation. Session three uses the second page's evidence to set the next plan and updates the map. The drill succeeds if all three pages connect objective, conditions, change or technique, result, and next action, and if at least one objective came from evidence rather than memory.
When this principle breaks down
The log is not a substitute for safety judgment, live coaching, or real engineering understanding. If the car has a safety issue, stop and fix the car. If you do not understand a chassis or suspension change, preserve the question and ask someone who can explain it. The log also breaks down when it turns correlation into proof after several variables changed at once, or when it becomes too large to maintain. Keep it complete enough to drive the next decision and simple enough that you will actually use it.
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 | Speed Secrets Professional Race Driving Techniques Ross Bentley | a009c9a4-cb8d-b3b5-063d-33e44ea0b5cb | 76 | 1 | uio_books_raw_v1 |
| 3 | Data for Drivers | cabda699642b26311b0a7ef998da2c71 | 15 | 1 | uio_books_raw_v1 |
| 4 | Data-for-Drivers-PRINT | bbb02386-778f-20ec-ad16-b9c016921743 | 16 | 1 | uio_books_raw_v1 |
| 5 | Data-for-Drivers-PRINT | b80dc634-a0a7-d6de-d470-353aed47e2a6 | 17 | 1 | uio_books_raw_v1 |
| 6 | Data for Drivers | 27ec1aea-60bb-f052-9a1a-294b72597f55 | 17 | 1 | uio_books_raw_v1 |
| 7 | Ultimate Speed Secrets - Ross Bentley | 0237a5bd-e2d4-724e-bc2e-ba13db924f66 | 11 | 1 | uio_books_raw_v1 |
| 8 | Ultimate Speed Secrets - Ross Bentley | 47f6de8d-9d56-5b6d-547a-f1e7bb92faaf | 152 | 1 | uio_books_raw_v1 |
| 9 | Speed Secrets Professional Race Driving Techniques Ross Bentley | 26bc8e35-76a6-4f72-ea86-df10ba43a636 | 14 | 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 | Going Faster Mastering the Art of Race Driving - Carl Lopez | fa01ec16-aace-9079-2afa-de127b8272a9 | 300 | 1 | uio_books_raw_v1 |