Run the between-session turnaround

Generated from content/lms/race-car-mechanic-reference/07-manage-the-trackside-window/01-run-the-between-session-turnaround.md; edit the source file, not this page.

Source path: content/lms/race-car-mechanic-reference/07-manage-the-trackside-window/01-run-the-between-session-turnaround.md

Course: Service the race car that has to finish

Module: Manage the trackside work window

Estimated duration: 45 minutes

A between-session turnaround is not a panic break. It is a short, disciplined loop that turns a hot car, a fresh driver report, and whatever data you captured into a safer, better next session. The job is not to fix everything. The job is to protect the car, protect the driver, preserve evidence, and choose the next objective before the next green flag.

The principle is simple: safety and reliability first, evidence second, performance third. If you reverse that order, you can waste the window chasing lap time while missing a pressure, temperature, voltage, cooling, or driveline clue that decides whether the car finishes the day. Sergers gives the order clearly in data-analysis terms: download whenever the car comes in, start with vital channels, listen to the driver, observe what the car did, and only then try to understand why it did it. That is the backbone of the turnaround.

This lesson is written for the mechanic, crew chief, or serious club racer who has only a few minutes between sessions. You may have one helper, a driver who is still wearing a helmet, a hot engine bay, tires losing pressure as they cool, and a schedule board that does not care about your workload. The answer is a repeatable sequence. You do the same first checks every time, gather the same evidence every time, and only make changes that are justified by the symptoms, records, or data.

The outcome you want is a car that goes back out with known vital signs, a driver who trusts the team, a written record of what changed, and one or two clear objectives for the next session. Van Valkenburgh points out that driver confidence depends partly on believing that the owner, engineer, and mechanics know their business and care about finishing races and driver health. That confidence is not created by speeches. It is created by visible, competent routine.

The turnaround has seven phases. First, receive the car and stabilize the situation. Second, capture the driver report while it is still fresh. Third, preserve evidence before it disappears. Fourth, check the vital signs and obvious mechanical risks. Fifth, review the data in the right order. Sixth, choose repair, adjustment, or no change. Seventh, brief the driver and record the next objective. You can compress this into a ten-minute club-racing window or stretch it into a longer test-day debrief, but the order should remain recognizable.

The first phase begins before the car stops. Assign arrival roles if you have even one helper. One person receives the driver and hears the first report. One person handles pressures, temperatures, or quick visual inspection. One person downloads data if the system allows it. If you are alone, your checklist matters even more because it prevents the loudest stimulus from taking over. The car is hot, the driver is animated, and the next session is approaching. That is exactly when you need the calmest process.

When the car arrives, resist the temptation to diagnose from the first sentence the driver says. Listen, but do not surrender the sequence. Sergers warns that even if the driver is standing nearby saying the car is not drivable, the analyst should begin with vital channels before moving into performance analysis. In the paddock, that means you take the report seriously while still checking the things that can end the day: temperatures, pressures, voltage, fluid loss, brake condition, tires, wheel security, and obvious damage.

The driver report should be short, structured, and immediate. Ask what changed from the previous session, when it happened, where on track it happened, and whether it repeated. Do not let the driver describe the whole lap from memory unless you have unlimited time. You are hunting for location, phase, repeatability, severity, and trend. Was the issue in braking, turn-in, mid-corner, exit, straight-line acceleration, upshift, downshift, or cooldown? Did it get worse as the session went on? Did it follow traffic, curbing, heat, fuel level, or a setup change? Those questions keep the report useful.

This is where Bentley's debrief method helps a mechanic. He recommends using a track map and noting what the car is doing in the braking zone and at entry, middle, and exit of each corner. For a between-session turnaround, use the same structure but keep it fast. Put a mark on the map where the driver felt the problem. Write the phase beside it. If the car pushed only at the entry of Turn 3, that is different from pushing from apex to exit. If the brake pedal was long only after two fast laps, that is different from a long pedal leaving pit lane.

The second phase is evidence capture. Evidence starts evaporating as soon as the car stops. Tire pressures and temperatures move. Brake temperatures fall. Fluids drip, burn off, or spread. Driver memory gets contaminated by lap times, other drivers, and paddock opinions. Data can be overwritten or forgotten. Johnson's record-keeping advice is blunt: from the first time you go out, keep complete records of the car and performance. For a turnaround, that means every change, pressures out and in, shock settings, plugs when relevant, oil and water temperature, revs, gear ratios, and lap times should land in the record.

Do not treat record-keeping as office work to do later. Later is when you forget which pressure was hot, which corner had the rub mark, which shock click was changed, or whether the driver complained before or after you adjusted the bar. The notebook or digital run sheet is part of the repair process. It prevents the team from starting over at the same course next year, and it prevents the team from starting over after lunch on the same day.

A practical run sheet should capture the session number, track conditions if known, tire set, starting pressures, ending pressures, temperatures or observed wear when available, fuel load if relevant, driver comments, data availability, mechanical findings, changes made, and next-session objective. It does not need to be beautiful. It needs to be fast, consistent, and complete enough that a future you can reconstruct what happened.

The third phase is the physical inspection. Begin with vital signs and high-consequence items. Sergers names engine and driveline temperatures, pressures, and battery voltage as the vital channels in data. In the paddock, the matching physical checks are coolant and oil signs, leaks, belt or hose problems, brake fluid and pedal condition, tire condition, wheel and lug condition, battery or charging clues, and anything loose, rubbing, cracked, melted, or smoking. Performance adjustments wait until the car is known to be safe enough to continue.

The inspection must be both standardized and symptom-led. Standardized means the same quick scan happens every time: tires, wheels, brakes, fluids, engine bay, underbody glance when possible, cockpit controls, harness and safety items, data logger, and fuel. Symptom-led means the driver's report and data tell you where to look harder. If the driver reports vibration under braking, you do not skip the general scan, but you give extra attention to wheels, tires, brake hardware, steering, suspension, and anything that could create a speed-dependent vibration.

The fourth phase is data preservation and first-pass review. Download the logger every time the car comes in if you have one. Sergers notes that even warm-ups and rollout laps can provide relevant information. That matters in club racing because the session you ignore may contain the first clue: low voltage before the misfire, rising temperature before the warning, a brake-pressure change before the driver calls the pedal long, or a speed trace showing the driver lifted because of traffic rather than because the setup got worse.

Once the data is available, do not jump straight to the fastest lap. Sergers warns against focusing only on the fastest lap and recommends looking at all laps for consistency and inconsistency. This is critical between sessions because your decision may depend less on the peak lap and more on the trend. A single slow lap may be traffic. A steady loss of straightaway speed may be heat, engine, aero drag, driver confidence, or traffic. A brake trace that lengthens lap by lap may point to confidence, pedal feel, tires, or hardware. The pattern matters.

Use the speed trace as the first performance map. Sergers describes the speed graph as the place that shows where time is gained or lost. A stopwatch tells you whether the lap was slow or quick; the speed trace tells you where. In a between-session window, that means you use speed to locate the event, then use other channels to explain it. If speed drops early before a corner, check brake pressure, throttle release, traffic, gear, and driver comment. If speed is lower on a straight, check throttle, RPM, gear, temperatures, pressure, voltage, and whether the driver was impeded.

The Data for Drivers process gives a useful performance checklist: look at throttle for coasting, hesitant application, early throttle leading to lift, and lifts in fast corners. Look at brake pressure for initial shape, trail, long tail, inconsistency, and light-long versus hard-short application. Look at steering, RPM, gear, segment reports, fastest rolling lap, theoretical fastest, g-sum, GPS line, total steer angle, and throttle histogram as needed. The point is not to stare at every channel every time. The point is to have a known menu so you do not confuse curiosity with diagnosis.

The fifth phase is deciding what problem you are solving. A between-session turnaround can easily collapse into three competing conversations: the driver wants lap time, the mechanic wants reliability, and the data person wants a cleaner trace. You need one priority order. If the car has a safety or reliability question, that is the objective. If the car is healthy but the driver is inconsistent, the next objective may be a driver task. If the car is healthy and the driver is repeatable, a setup adjustment may be justified. If the evidence is muddy, the next objective may be to gather cleaner evidence rather than to adjust.

A useful rule is to separate a repair from an adjustment from an experiment. A repair restores the car to known-good condition. An adjustment changes balance, response, gearing, pressure, or another setting to improve performance or drivability. An experiment is a deliberate test designed to learn something. During a short turnaround, do not hide an experiment inside the language of repair. If you change a shock, bar, pressure, wing, or alignment because you want to test a hypothesis, write the hypothesis and expected channel change. Sergers recommends determining which channels should show differences after a setup change. That keeps the experiment honest.

Carroll Smith's testing guidance is useful here even though it speaks to broader test planning. He argues that a team does not need the freshest race engine or new brake pads for every kind of test, and that basic testing such as engine tuning, cooling, and aerodynamic drag work can be done with worn tires or less expensive venues when appropriate. The lesson for the turnaround is not to be cheap. The lesson is to match the work to the objective. Do not use a scarce between-race window to chase a low-value change when the car still needs cooling confirmation, driveline reliability, or driver familiarity.

Driver familiarity is part of the turnaround, not separate from it. Van Valkenburgh emphasizes getting many miles on a particular race-car setup because familiarity improves control and reduces mistakes. Between sessions, you can support that familiarity by avoiding unnecessary changes. If the driver is still learning the car and the setup is not unsafe or clearly wrong, a stable car plus a clear driving objective may be more valuable than three adjustments that make the next report impossible to interpret.

This is especially important for intermediate drivers. They may be good enough to feel a problem but not yet calibrated enough to separate their own timing from the car's balance. Bentley warns that drivers recalibrate their sense of the limit as they improve. What felt like a 9 or 10 may later feel like a 6 or 7. In the turnaround, that means you do not treat every strong driver statement as proof of a mechanical problem, but you also do not dismiss it. You compare the report with data, physical evidence, previous records, and the next objective.

The sixth phase is the debrief and next-session objective. Bentley's main objective for a debrief is to determine the next session's objectives. The Data for Drivers process ends the same way: compare if you can, calibrate to the driving, imagine the ideal, and set objectives for the next session. A good objective is small enough to execute, measurable enough to review, and connected to the evidence. It might be to verify coolant stability over four consecutive laps, confirm whether the brake-pressure tail shortens after a pad change, test a two-psi pressure split, or ask the driver to eliminate coasting at two named exits.

Avoid sending the driver out with a vague instruction such as go faster, feel it out, or see what happens. Those are not objectives. The next session should have a purpose. If you have a mechanical concern, the objective may be to run an abbreviated session and report immediately if the symptom returns. If you adjusted tire pressure, the objective may be to run three clean laps, avoid major traffic if possible, and come straight in for hot pressures. If the data shows hesitant throttle, the objective may be to focus on two exits and compare throttle traces afterward.

The driver brief should include what you found, what you changed, what you did not change, what to watch for, and when to abort. This supports the driver confidence Van Valkenburgh describes. You are not merely handing the car back. You are telling the driver what the team knows and what the next job is. A driver with faith in the car and team can concentrate on driving; a driver who suspects the crew is guessing will spend mental bandwidth listening for failure.

The final phase is closing the loop after the next session. A turnaround is only as good as its next review. If you changed pressure, check pressure. If you suspected cooling, check temperature trend. If you asked for cleaner throttle, compare throttle. If you marked Turn 4 entry as the issue, go back to that section. If the change did not move the expected channel, do not pretend it worked because the lap time improved in traffic-free air. Sergers specifically warns that traffic can influence lap time, so the lap-time number alone cannot validate the repair or adjustment.

There is a deep trap here: speed can improve for the wrong reason and lap time can get worse for the right reason. A driver may run slower because of traffic while the car's cooling problem is fixed. A driver may run faster because of clear track while the brake issue is worsening. That is why the turnaround uses multiple evidence streams: driver report, physical inspection, vital channels, speed trace, throttle, brake, RPM, gear, sector times, and written records. One piece of evidence starts a question. Several pieces pointing the same way support a decision.

You should also be careful with theoretical fastest or fastest rolling laps. The Data for Drivers checklist includes both as useful tools, but in a between-session mechanic window they are secondary. They help show potential, but they do not prove the car is safe or the setup is correct. Use them after vital signs and obvious inconsistencies. If the car is overheating, the theoretical lap is not the most important line on the screen.

A strong turnaround feels almost boring from the outside. The car arrives. The driver gives a short report. Pressures and visual checks happen. Data is pulled. Vital signs are reviewed. The map is marked. The team decides whether to repair, adjust, or hold. The change is written down. The driver gets one objective. The car leaves. The calmness is the point. Racing creates enough randomness without the crew adding more.

The skill is not knowing every possible fix. The skill is managing the trackside window so that the right fix, the right non-fix, or the right evidence-gathering plan can happen before the next session. You are building a chain of custody for the car's condition. You know what came in, what you heard, what you measured, what you changed, and what you expect to see next. That is what lets you improve without guessing.

Worked example: the driver says the car will not brake

The car comes in after Session 2 and the driver says the brake pedal went long. You have twelve minutes before the next call. The wrong move is to start debating brake bias, trail braking, or driver confidence while the car sits hot and undocumented. The correct sequence is reception, preservation, vital signs, then diagnosis.

First, ask for location and trend. Was the pedal long leaving the pits, after several laps, only after a long straight, or only after traffic forced extra brake use? Did it recover on the cooldown lap? Was the car still stopping but with more travel, or did the driver have to reduce pace? Mark the affected corner or braking zone on the track map. Bentley's debrief structure of braking zone, entry, middle, and exit keeps this report from becoming a general complaint.

Second, capture the physical evidence. Check fluid level, visible leaks, pedal feel, pad condition if accessible, rotor condition if visible, wheel and tire condition, and anything rubbing or loose. Take hot pressures if that is part of your routine before they drift. Record the driver's words and the session number. Johnson's record-keeping approach matters because a brake problem without a record becomes folklore by the afternoon.

Third, pull the data. Start with vital channels if available, including voltage and temperatures where relevant. Then use the brake-pressure trace. The Data for Drivers checklist asks whether the brake trace has a normal initial shape, whether pressure is inconsistent, whether the driver is light and long or hard and short, and whether there is a long tail. Compare more than the fastest lap. Sergers recommends analyzing all laps and looking for consistency and inconsistency. If brake pressure starts strong and grows longer or less repeatable across the session, that supports the driver's report. If the trace is unchanged but speed is lower because of traffic, that points elsewhere.

Now decide. If the physical inspection shows a safety issue, repair or park the car. If the hardware looks healthy but the trace shows the driver braking earlier and longer every lap, the next objective may be a confidence or technique check, not a setup change. If you change pads, bleed brakes, adjust bias, or change cooling tape, write exactly what changed and what you expect to see in the next data: shorter brake zones, more consistent pressure, stable pedal report, or stable temperatures. Then brief the driver on the abort condition. The car does not go back out merely because the clock is running.

Worked example: the lap time fell off, but the car may not be slower

After Session 3, the driver is frustrated because the best lap is eight tenths slower than the morning. The car feels flat, but the driver also mentions traffic. This is a classic between-session trap. A stopwatch says the lap is slower, but it does not say why. Sergers makes the distinction: the stopwatch identifies slow or quick, while the speed graph shows where time is gained or lost.

Start by protecting the car. Check vital signs before arguing about pace: temperatures, pressures, voltage, fluid signs, tire condition, and obvious mechanical issues. If the engine or driveline data shows something abnormal, performance analysis waits. If the vital signs are clean, move to the session shape.

Do not compare only the best lap from each session. Look across all laps for consistency and inconsistency. Identify laps affected by traffic if the video, GPS line, speed trace, or driver report supports it. Traffic can heavily influence lap time, so a slower lap in traffic does not prove the car got worse. Compare speed at the end of the longest straight, throttle application, RPM, gear, and acceleration shape. If straight-line speed and RPM are consistent with the earlier session but sector time is lost behind another car, the car may be fine. If the throttle trace shows hesitancy or lifts in fast corners, that may be driver confidence or track condition. If straight speed is down on clean laps with full throttle and the same gear, then the flat-feeling report deserves deeper mechanical attention.

The next objective depends on the evidence. If the car is healthy and traffic corrupted the comparison, send the driver with a clean-lap objective rather than changing the car. If the driver was hesitant on throttle at two exits, name those exits and compare traces after the session. If full-throttle acceleration is down despite normal driver inputs, treat it as a mechanical or environmental question and inspect accordingly. The key is that the between-session turnaround does not chase the lap-time headline. It locates the loss, checks the car, and chooses the next evidence-based action.

The seven-step turnaround checklist

Use this as the practical sequence until it becomes habit. Step one is receive the car safely and assign roles. Step two is capture the driver report: what changed, where, when, how often, and whether it got worse. Step three is preserve perishable evidence: hot pressures, obvious temperatures, leaks, wear, damage, and data download. Step four is check vital signs before performance channels: engine and driveline temperatures, pressures, voltage, fluid condition, brakes, tires, wheels, and safety hardware. Step five is locate the issue in data or on the track map: speed trace first for where, then throttle, brake pressure, steering, RPM, gear, GPS line, segment times, and other channels for why. Step six is decide repair, adjust, hold, or gather evidence. Step seven is record the decision and give the driver one or two next-session objectives.

The order matters because it prevents two common failures. The first is performance tunnel vision, where the team studies sector time while a reliability issue is developing. The second is paddock guessing, where the team changes the car because the driver used a strong adjective. The checklist lets you respect the driver report without letting it bypass mechanical safety and evidence.

Common mistakes

The first mistake is chasing the loudest complaint. A driver may be correct that the car feels wrong, but the job is to convert that feeling into location, phase, repeatability, and evidence. Good looks like a short driver interview, a marked track map, and a check against physical condition and data.

The second mistake is studying the fastest lap only. Sergers warns against this because the fastest lap may hide the trend that matters. Good looks like reviewing all laps for consistency, deterioration, traffic effects, and repeatable symptoms.

The third mistake is changing too many things. If you change pressure, shock, bar, alignment, and driving objective at once, you may not know which change mattered. Good looks like one justified change or one clear evidence-gathering plan, with the expected channel or driver response written down.

The fourth mistake is putting performance before vital signs. A lap-time problem is not more important than a pressure, temperature, voltage, brake, tire, or fluid warning. Good looks like vital channels and high-consequence mechanical checks before detailed performance analysis.

The fifth mistake is failing to record the baseline. Johnson's advice on complete records exists because memory is not enough. Good looks like pressures out and in, settings, temperatures, driver report, changes, lap times, and next objective captured while the session is still fresh.

The sixth mistake is giving the driver a vague next instruction. Good looks like a specific task: run three clean laps, report whether the brake pedal changes after lap two, avoid the exit curb at a named corner, verify full throttle from a named apex, or come in immediately if the temperature climbs again.

Drill: three-session turnaround rehearsal

At your next test day or HPDE support day, run this drill over three consecutive sessions. The purpose is not to make the car faster immediately. The purpose is to make your between-session process fast, repeatable, and evidence-driven.

For Session 1, your count is one complete baseline turnaround. Before the car goes out, write starting tire pressures, known settings, fuel state if relevant, and the objective. When the car comes in, give yourself ten minutes. Capture the driver report in four questions: what changed, where, when, and did it repeat. Take hot pressures or your normal perishable measurements. Download data if available. Check vital signs first. Mark one track-map note. Write the next objective. Success means you have a complete record and no undocumented change.

For Session 2, your count is one symptom-led turnaround. Before the session, choose one thing to watch, such as brake feel, coolant temperature, throttle hesitation, or straight-line speed. After the car comes in, follow the same order, but spend your analysis time only on channels or checks that bear on that symptom. Success means your decision is repair, adjust, hold, or gather more evidence, and you can state why in one sentence.

For Session 3, your count is one closed-loop turnaround. Compare the result against the Session 2 objective. Did the expected physical sign, driver report, or data channel change? If yes, record it. If no, record that too and do not pretend the change worked. Success means the next decision follows from the evidence rather than the lap-time headline.

The standard is not perfection. The standard is discipline under time pressure. If you can run this drill without losing the order, you are building the same habit you will need when the car has a real problem and the next session is already being called.

Calibration cues

You are improving when the turnaround produces fewer surprises. The driver report becomes more specific because your questions train the driver to speak in locations and phases. Your notes become useful later because pressures, settings, changes, and symptoms are recorded in the same format. Your data review gets faster because you begin with vital channels, then speed, then the channels that explain the speed trace. Your setup changes become easier to judge because you wrote what you expected to see.

A good lap-time signature is not always immediate improvement. Sometimes the correct result is a stable temperature trend, a consistent brake trace, fewer driver lifts in fast corners, or a cleaner explanation for why traffic ruined the comparison. A good instructor or crew chief would notice that your next-session objectives are becoming smaller and clearer. That is a sign that the team is learning instead of guessing.

The driver's behavior is another cue. Van Valkenburgh connects driver confidence with belief that the team knows its business and cares about finishing and safety. When your turnaround is calm and evidence-based, the driver should leave with less mental clutter: what was checked, what was changed, what to watch, and when to come in. That confidence is not a substitute for inspection, but it is one of the products of good inspection.

Cross-references inside the module

This lesson sits between three related skills. Diagnose like an emergency mechanic is the deeper skill when a symptom threatens safety or reliability and you need a fault tree under pressure. Decide repair, adjust, or park is the decision skill when the evidence says the car may not be fit to continue. End the event with better evidence is the longer-horizon version of the same record-keeping discipline Johnson describes: you do not want to return to the same course and begin again as if you have never been there before.

The boundary is important. The between-session turnaround does not replace emergency diagnosis, repair judgment, or end-of-day analysis. It feeds them. It captures the evidence, protects the car, and chooses the next objective while the clock is still running.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Analysis Techniques for Racecar Data Acquisition (Jorge Sergers)	bf8c23f5b9988c507f2659b9ce0f63e4	5	1	uio_books_raw_v1
2	Ultimate Speed Secrets - Ross Bentley	46de7230-2886-08d9-b78e-62d135637158	533	1	uio_books_raw_v1
3	Driving in competition None Johnson Alan 1935- None	6f8ef047-2945-22d3-9b91-8be0ec5487ef	42	1	uio_books_raw_v1
4	Data for Drivers	cabda699642b26311b0a7ef998da2c71	15	1	uio_books_raw_v1
5	Data-for-Drivers-PRINT	bbb02386-778f-20ec-ad16-b9c016921743	16	1	uio_books_raw_v1
6	Race Car Engineering Mechanics Paul Van Valkenburgh	706b6084-0052-a3ba-4f63-34d81ab8ff4c	112	1	uio_books_raw_v1
7	Ultimate Speed Secrets - Ross Bentley	392d0d7b-14e9-290b-a9cb-8696b08e1e97	305	1	uio_books_raw_v1
8	Tune To Win Carroll Smith	a8fe019e-2cca-7195-3ccd-e9b67806de4e	163	1	uio_books_raw_v1