Write a tire and brake handoff spec people can run

Generated from content/lms/tires-and-brakes-engineering/07-validate-and-handoff-a-working-spec/04-write-the-handoff-spec.md; edit the source file, not this page.

Source path: content/lms/tires-and-brakes-engineering/07-validate-and-handoff-a-working-spec/04-write-the-handoff-spec.md

Course: Engineer tire and brake grip that lasts

Module: Validate and hand off a working spec

Estimated duration: 60 minutes

The job of the handoff spec

A tire and brake handoff spec is the document that turns a test result into a runnable next action. It is not the test matrix. The matrix decides what you will compare. It is not the paper test. The paper test checks whether the proposed comparison makes sense before the car rolls. It is not the inspection gate. The inspection gate decides whether the tire and brake state is trustworthy enough to use. The handoff spec comes after those steps. It tells the next driver, crew member, engineer, or future version of you exactly what was accepted, exactly what car state produced it, exactly how to run it again, and exactly what would make the result invalid.

The skill matters because tire and brake tests are easy to remember falsely. A lap time can improve while the track is changing. A brake change can feel better because the driver is more committed. A tire can look faster until a control tire shows that the day itself moved. A data logger can collect far more channels than the team has time to analyze. A brake package can be judged without recording lining thickness, fluid, balance-bar setting, or temperature comments, which means the team later cannot say what setting caused what result. The handoff spec is your defense against that kind of paddock amnesia.

The principle is simple: a result is not handoff-ready until it links configuration, comparison, driver task, measurement, and next decision. If any one of those is missing, you do not have a spec. You have a memory. The brake sources in this bond are strict about recording the exact brake-system setup, test duration, track conditions, temperatures, lining thickness before and after, comments, and deceleration information. The tire-testing source is equally strict about control tires because changing ambient conditions and driver variation prevent treating lap time as an absolute value. The data-analysis source adds the final habit: look for incongruencies, dig into detail, check other channels, compare when you can, calibrate against the driver, imagine the target trace, and set objectives for the next session. A useful handoff spec makes those habits visible on paper.

Write the spec as a decision document, not as a diary. A diary says what happened. A decision document says what the team is allowed to do next because of what happened. Start with the accepted claim in one sentence. For example, the spec may say that the current brake balance setting is the best known setting for clean dry running on this surface, that the next session should repeat it with temperature recording, or that the tire comparison is not accepted because the control tire did not repeat. That sentence forces you to separate accepted evidence from interesting noise.

Then write the car state tightly enough that the same car can be rebuilt. For brakes, include lining type, fluid, balance-bar setting or adjustment position, bedding status, beginning lining thickness, ending lining thickness after the run, where the lining was measured, maximum caliper temperature, maximum rotor-edge temperature, maximum hub temperature, maximum lining temperature when those are part of the test, and any recorded comments about performance versus temperature. If deceleration rate is part of the test, the handoff spec needs a place for it. If hard stops are part of the test, record the number of stops and the speed attached to those stops. The reason is not paperwork pride. Brake pads wear on a taper, and the useful wear number depends on measuring consistently and linking wear to the number of hard stops.

For tires, record the tested specification, the control specification, pressures and temperatures when they are part of the available evidence, lap and segment times, and driver comments. The tire-testing source describes control tires of known specification as the benchmark that protects the comparison from weather, track, and driver variation. The handoff spec should therefore say when the control was run, what the control produced, whether the driver was consistent on the control, and whether the test tire result is still meaningful against that control. If a driver produces different lap times and different comments every time on the control tire, the handoff spec should not pretend the tire comparison is settled.

Next, write the conditions as part of the evidence, not as background color. Track surface matters. A dirty or wet surface makes a brake-balance test useless unless you intend to race or drive on a similar surface. Ambient and track changes also limit tire testing because they move the stopwatch. The handoff spec should make the surface, weather, traffic, and timing of the control run visible enough that the next person can decide whether the result still applies. If the best you have is a crude balance attempt on a poor surface, label it that way and record maximum deceleration so the next adjustment can be judged when traction improves.

Now write the driver task. This is where many handoffs fail. A setup note that says the brakes are good or the tire is faster is too vague to execute. The driver needs to know what to do at each important point of the test. Going Faster frames the competent driver as someone with a plan: brake at a defined place, shift at a defined place, turn at a defined place, take a specific apex, apply power in a specified way, and use a defined exit. For this lesson, you do not need to write a whole driving manual into the handoff. You do need to write the exact repeatable task that protects the test. If the next run is a brake-balance check, say whether the driver is doing hard straight-line braking, whether balance changes are made from the cockpit, how many laps are allowed before discussion, and what the driver should do if a wheel starts to lock. If the next run is a tire comparison, say whether the driver should run a few laps at a time, what comments to give, and when the control tire appears in the sequence.

The driver task should also separate the braking blocks. The bonded driving chunk breaks corner entry into the throttle-brake transition, straight-line deceleration, and the brake-turn segment. That matters in a handoff because a brake spec may be about pressure build and maximum deceleration, while another may be about how the car behaves as brake is carried into direction change. If you do not say which block the driver is testing, the next run may change the technique and make the result unrepeatable. A handoff for straight-line deceleration should keep the car straight and protect maximum braking evidence. A handoff for brake-turn behavior should say that the driver is evaluating combined deceleration and direction change, not just the peak stop.

After the task, write the measurement plan. Keep it narrow enough that someone will actually use it. The data-analysis chunk lists many possible channels: throttle trace, brake pressure trace, steering, RPM, gear, segment and section times, fastest rolling lap, theoretical fastest, G-sum, GPS line, total steer angle, and throttle histogram. It also warns by implication that the list can keep going. Haney makes the same point more sharply for modern tire testing: cars can carry many sensors, but few teams have enough manpower to analyze all of the data, so much of it is never examined. A good handoff spec does not demand every possible channel. It demands the channels that answer the decision.

For a brake handoff, the high-value channels and observations are usually brake pressure shape, initial application, trail or long tail, inconsistent pressure, light-long versus hard-short use, deceleration rate if recorded, lockup observations, temperatures, and lining wear. Brake pressure shape tells you whether the driver actually performed the requested stop. Temperature and lining wear tell you whether the hardware survived the demand. Observer notes matter because a driver may not be able to tell which end locked without flat-spotting the tires. The spec should assign an observer for hard braking when possible and should tell the driver to ease off the pedal as soon as a wheel starts to lock.

For a tire handoff, the high-value evidence is the control comparison, lap and segment times, pressure and temperature behavior if collected, driver comments, and available accelerometer or GPS evidence that relates to grip. Before on-board data acquisition, tire testing relied on lap times, segment times, tire pressures and temperatures, and driver comments. Data acquisition added accelerometers and many other sensors, but that does not remove the need for a controlled comparison. The handoff spec should say which numbers decide the question and which numbers are only supporting evidence.

Write the invalidation rules before the next run. This is one of the main differences between a handoff spec and a setup note. A setup note says what to do. A handoff spec also says when not to trust the result. Invalidate or downgrade the result if the track surface is dirty or wet and the target use is clean dry running. Invalidate a tire comparison if the control tire does not repeat or if driver comments on the control are inconsistent. Downgrade a brake-balance result if excessive wheel locking flat-spots the tire or forces the driver to abandon the planned stop. Downgrade a data conclusion if the channels disagree and you have not checked the other channels that could explain the incongruity. Downgrade a change if more than one variable moved at once.

The one-change rule belongs in the handoff. Puhn's brake-balance testing guidance is very practical: run only a few laps, make only one change, and then discuss with the observers. That sentence is the backbone of a usable brake handoff. The spec should name the single change permitted in the next session and should freeze everything else that matters. If the next run changes balance-bar setting, do not also change linings, fluid, tire set, pressure target, driver task, and cooling procedure. If the next run changes tire specification, protect the brake setup and driver task. The more variables you move, the less the handoff can teach.

The handoff spec also needs a logistics section. This can feel beneath the level of an engineering lesson until it ruins a session. The brake handbook chunk is blunt about test preparation: make copies of blank data sheets, keep a notebook or similar record system, bring a clipboard, keep the notebook with you during tests and races, make lists of tools, supplies, instruments, maintenance items, repair items, and spare parts, organize parts and supplies into labeled boxes, and assign a pit crew member to keep track of things when possible. In handoff language, that means the spec should not only say what to measure. It should say what form, tool, part, and person are required to get the measurement.

For an intermediate driver, the easiest working format is seven fields. Field one is the decision: accepted, repeat, provisional, or rejected. Field two is the exact setup: tire, brake, fluid, balance, pressures, bedding, measurements, and anything else that defines the car. Field three is the comparison: control tire, baseline run, prior setting, or previous session. Field four is the driver task: the points, the number of laps, the speed or gear reference when relevant, and the specific braking or tire behavior being tested. Field five is the evidence plan: times, comments, temperatures, thicknesses, data channels, and observers. Field six is the invalidation rule: surface, control inconsistency, lockup, missing measurement, multiple variables, or channel conflict. Field seven is the next objective: what the next session is supposed to prove or protect.

Do not bury the next objective. Data for Drivers ends the analysis process by setting objectives for the next session. That is exactly what a handoff spec should do. The objective should be concrete enough that a driver can leave pit lane with it in mind. Examples are: repeat the accepted balance setting on a clean surface and record temperatures; rerun the control tire before accepting the new tire; keep the brake pressure trace hard-short rather than light-long; record lining thickness at the same pad locations after a known number of hard stops; compare segment times only after confirming the same GPS line. These are not generic hopes. They are instructions tied to evidence.

A good handoff also names what not to decide. If the bond does not support a conclusion, the spec should not smuggle it in. If you did not collect brake temperatures, do not claim the lining temperature margin is proven. If you did not measure lining thickness before and after, do not claim wear per stop. If you did not return to the control tire, do not treat a changing day as a tire gain. If a driver was learning the braking zone during the test, do not claim the hardware alone produced the lap-time change. Refusing to decide is not failure. It is how you keep the next test honest.

The handoff spec is especially important because tires and brakes interact with driver confidence. A driver who expects more brake may brake later. A driver who expects more front grip may enter faster. A tire that feels better may change throttle timing. Data for Drivers points you toward throttle hesitation, coasting, early application leading to lift, lifts in fast corners, brake pressure shape, inconsistent pressure, and long tails. Those are not just driver-coaching details. They are evidence that the driver task changed. The handoff should tell the analyst to check them before accepting a hardware conclusion.

The same principle applies to line and segment evidence. Segment times can help, fastest rolling and theoretical fastest can help, GPS line can help, and G-sum can help, but only if they answer the question. If a tire looks faster in lap time but the GPS line changed, the handoff should flag the conclusion as partly driver-line evidence. If a brake setting looks better but the driver used a different brake-pressure shape, flag it. If throttle traces show a lift in a fast corner after an early application, do not treat that lap as clean tire evidence. A good handoff teaches the next reader how to trust the result, not just where to find the file.

Use comments correctly. Puhn says recorded comments on brake performance versus temperatures are vital. Haney includes driver feedback as one of the original tire-test data streams. The handoff spec should ask for comments that tie sensation to evidence: pedal feel as temperatures rise, lockup tendency during hard braking, consistency of pressure application, confidence on the control tire, and whether the car repeated the same behavior across the few-lap run. Vague comments are not useless, but they need structure. The driver should not simply report that the car felt good. The driver should report what the car did during the planned task.

Keep the spec portable. It should make sense at the race shop, in the paddock, and months later. That is why the brake handbook wants a notebook or record-keeping system that collects test plans, test-data sheets, parts lists, supply lists, and technical information. The handoff spec is one page of that larger record. It should reference the forms and logs that contain raw detail, but it should also stand alone as the instruction for the next run. If someone cannot prep the car from the spec, or cannot tell which data sheet proves the claim, the spec is not finished.

There is a useful tension here. The spec must be complete enough to run, but not so broad that no one reads it. Resolve that tension by separating required evidence from optional evidence. Required evidence is what the next decision depends on: exact brake setup, tire spec, control run, surface condition, driver task, temperatures or thicknesses if the decision depends on them, and the specific traces or times you will compare. Optional evidence is useful if available but not allowed to block a clean session. This keeps the handoff simple without becoming shallow.

The best calibration cue is that the next session produces fewer questions, not more. A strong handoff lets the driver know the objective before leaving pit lane. It lets the crew know what hardware state to build. It lets the observer know what to watch during hard braking. It lets the analyst know which channels matter first. It lets the team reject a tempting result when the control, surface, driver task, or data channels do not support it. When that happens, the spec has done its job.

You are improving when your handoffs start to catch problems before they become arguments. A repeated control tire that does not repeat tells you not to accept the tire comparison. A dirty surface note prevents a false brake-balance conclusion. A lining-thickness record turns pad wear from a guess into a per-stop estimate. A brake-pressure trace that shows a different shape tells you the driver changed the test. A tool and parts list prevents a missing instrument from wasting the session. These are the signatures of a driver who is moving from trying parts to running controlled development.

The last habit is to write the handoff immediately while the details are still alive. Do not wait until the end of the weekend and reconstruct the test from memory. Fill the sheet, mark the decision, attach or reference the data, and set the next objective. If the result is incomplete, say so. If it is accepted only for similar conditions, say so. If the next run must repeat before a permanent spec change, say so. The handoff spec is not there to make the test look successful. It is there to make the next decision better.

Worked example: adjustable balance-bar brake handoff

You have a race car with a balance bar that can be adjusted from the cockpit. The previous session was a brake-balance test. The handoff should not say only that the balance is close. It should say what the car was, what the brake system was, what the driver did, what the observers saw, what the measurements showed, and what the next run is allowed to change.

Start the spec with the decision. The current balance setting is provisional for a clean dry surface, and the next session is a repeat with temperature recording and observer notes. Then write the exact brake state: lining type, fluid, balance-bar setting, whether the linings are bedded, beginning lining thickness at the middle and corners, and the intended ending measurement locations. Include the test duration field: laps, number of hard stops, and stop speed if you have it. If deceleration rate is part of the plan, add the deceleration form rather than leaving the analyst to improvise.

Now script the run. The driver will run only a few laps. Only the balance setting may change. Observers will watch hard braking and record what happens. The driver may change the balance to feel the effect, but the handoff should preserve each setting as a separate run note. If a wheel starts to lock, the driver eases off immediately; excessive locking risks flat-spotting the tire and makes the test expensive. The spec does not ask the driver to identify the locked end by feel alone because the source warns that this is difficult without damaging the tires. Observer notes are part of the evidence.

The invalidation rules are clear. If the track is dirty or wet and the target condition is not similar, the balance result is not accepted as the final dry setting. If the driver changes more than the balance setting, the result is downgraded. If lining thickness is not measured at matching locations before and after, the wear conclusion is not accepted. If the driver flat-spots a tire, the test stops being a clean balance test and becomes a damage-control note. The next objective is equally clear: repeat the best-known setting on the target surface, record temperatures and comments, then decide whether the setting becomes the working race or HPDE handoff.

Worked example: control-tire benchmark handoff

The tire test handoff begins with a different risk. The stopwatch is the primary measuring device, but the stopwatch is not an absolute truth. Ambient conditions and driver variation move lap times. The handoff therefore has to protect the control tire.

The decision field might say that the new tire is not yet accepted because the control tire did not repeat, or that the new tire is accepted provisionally because the control tire repeated within the team's usable range and the driver comments were consistent. The configuration field names the control tire of known specification and the test tire. It records pressures, temperatures if collected, lap times, segment times, and driver comments. If accelerometer or other data is available, the spec names which channel will be used for grip-related support rather than opening every possible trace.

The run script is simple and strict. The driver runs only a few laps at a time. Tires are changed between runs. The control tire appears occasionally to validate the day. The driver comments after each run using the same prompts. The handoff should say whether the driver knows which tire is on the car if that matters to the test. In the professional tire-test model described in the source, only the tire engineers know which tires are installed, and the control runs expose whether the driver is producing usable repeatability.

The invalidation rule is the heart of the handoff. If the same driver produces different lap times and different comments every time on the control tire, the handoff must not declare the new tire better or worse. The right conclusion is that the test driver, conditions, or method did not produce a trustworthy comparison. If the control tire repeats but the new tire gains only where the GPS line changed, the spec should mark the result as a driver-line question rather than a clean tire result. If the team collected more sensor data than it can analyze, the spec should identify the few channels that decide the next run and leave the rest as archive material.

Common mistakes

Mistake one is the configuration orphan. This is a handoff that says the brakes worked or the tire was faster but does not list lining type, fluid, balance-bar setting, bedding status, tire specification, control tire, pressures, temperatures, or measurement locations. Good looks different: the next person can rebuild the exact tested state without asking the original driver what was on the car.

Mistake two is stopwatch worship. A faster lap is treated as proof even though ambient conditions, track condition, and driver variation were moving. Good is a control-aware handoff. For tire work, that means a known control tire appears in the sequence. For brake work, that means the surface and task are recorded and poor-surface results are labeled as crude or provisional unless that surface is the target.

Mistake three is the multi-change fog. The handoff changes balance, pads, tires, pressure, and driver task in the same run, then tries to name one cause. Good is a one-change session with a short run and a discussion after the run. The spec should freeze the rest of the test environment as much as the paddock allows.

Mistake four is unmeasured wear. The team talks about pad life but never measures lining thickness before and after or never records the number of hard stops. Good is a measurement plan that uses the same locations on the lining and ties wear to stops, laps, or miles.

Mistake five is driver-task drift. The hardware comparison is accepted even though the driver changed brake pressure shape, coasting, throttle timing, GPS line, or lift behavior. Good is a handoff that names the requested task and checks the driver channels before accepting the hardware conclusion.

Mistake six is data hoarding. The car collects many channels, but nobody knows which trace answers the question. Good is a small evidence set chosen before the run: brake pressure shape for a braking task, control comparison and segment times for a tire task, temperatures and lining thickness for a brake durability task, and comments tied to the planned behavior.

Mistake seven is logistics denial. The spec requires a temperature label, micrometer, clipboard, spare parts, or observer, but nobody is assigned and the tool is not in the paddock. Good is a handoff that includes the needed forms, tools, supplies, instruments, and ownership before the session starts.

Drill: the two-session handoff rehearsal

At your next event, run this as a two-session drill. The count is two driving sessions and one paddock review between them. The duration is the length of the first session, twenty minutes in the paddock, and the second session. The success criterion is that another person, or you after a break, can read the handoff and describe the next run without asking what the setup was, what the comparison was, or what would invalidate the result.

Before session one, choose one narrow tire or brake question. Do not choose a full development program. A useful beginner version is brake pressure consistency with the current pads, or whether a known tire pressure target still gives repeatable driver comments. Prepare a blank handoff with the seven fields: decision, exact setup, comparison, driver task, evidence plan, invalidation rule, and next objective.

During session one, drive the planned task only. If it is a brake task, keep the braking behavior you promised to test and avoid adding extra setup changes. If it is a tire task, protect the comparison and record comments immediately. After the session, fill the handoff before you get pulled into other paddock work. Record what you know and mark what you do not know. If you skipped a measurement, write that the conclusion is downgraded.

During the twenty-minute review, read the handoff as if you were the next person. Circle every vague instruction. If the spec says record temperatures, name which temperatures. If it says compare data, name the channels. If it says repeat the run, name how many laps and what surface condition matters. If it says the car felt better, rewrite the comment so it ties to the planned task.

For session two, run only the next objective from the handoff. Do not improve the experiment in three directions at once. After the session, score the drill. You pass if the car state was repeatable, the driver task was clear, the required measurements were gathered or explicitly marked missing, and the result ended as accepted, repeat, provisional, or rejected. You fail if the second session raises basic questions the handoff should have answered.

Handoff spec template

Use this template when the paddock is busy. Decision: accepted, repeat, provisional, or rejected, followed by the tire or brake claim in one sentence. Exact setup: tire specification, control tire if used, pressures and temperatures if used, lining type, fluid, balance-bar setting, bedding status, beginning measurements, and any setup item needed to rebuild the car. Conditions: track, surface, weather, traffic, timing of control run, and anything that limits comparison. Driver task: number of laps, braking block or tire behavior being tested, speed or gear reference if needed, points on the track if defined, and what the driver must not change. Evidence: lap and segment times, control result, driver comments, brake pressure shape, throttle trace, steering, RPM, gear, GPS line, G-sum, temperatures, lining thickness, deceleration rate, and observer notes as appropriate to the decision. Invalidation rules: poor target mismatch on surface, inconsistent control, excessive lockup, missing measurement, multiple variables, or channel conflict. Next objective: the single thing the next session must prove, repeat, or protect.

The template is intentionally plain. Its strength is not clever formatting. Its strength is that it forces you to write the information that the bonded sources keep returning to: exact setup, controlled comparison, few-lap discipline, one change, useful comments, measured temperatures and wear, observer records, and a next-session objective.

When the handoff should refuse to decide

Sometimes the correct handoff is a refusal. If the track surface was dirty or wet and the target use is clean dry running, do not promote a brake-balance setting to final. If the control tire did not repeat, do not call the new tire faster. If the driver comments changed every time on the same control, do not call the tire test trustworthy. If the driver changed the brake pressure shape or line while the hardware changed, do not assign the gain to hardware alone. If the team collected sensor data that nobody reviewed, do not imply that the data supports the decision.

A refusal is not wasted work. It is a clean next objective. The next handoff can say to repeat on the correct surface, rerun the control tire, reduce the measurement set, assign an observer, measure lining thickness correctly, or run only one change. That is still progress because it keeps the program from building a permanent setup around evidence that was never strong enough to carry the decision.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Brake Handbook Fred Puhn	1f4c39e1-5a16-66d1-a93d-9b20080df111	110	1	uio_books_raw_v1
2	The Racing and High-Performance Tire Paul Haney	11880aec-933e-aa8f-4b04-34e8fbf40f0e	168	1	uio_books_raw_v1
3	Data for Drivers	cabda699642b26311b0a7ef998da2c71	15	1	uio_books_raw_v1
4	Brake Handbook Fred Puhn	b428d525-10b5-f995-e2e9-8a064043d69a	115	1	uio_books_raw_v1
5	Brake Handbook Fred Puhn	e38a4194-d555-2ffd-739b-884f82a25adf	117	1	uio_books_raw_v1
6	Brake Handbook Fred Puhn	eec70339-5799-3a15-184a-c384934cec4d	115	1	uio_books_raw_v1
7	Brake Handbook Fred Puhn	07dade4d-8bb3-cc02-322d-cca272a63945	110	1	uio_books_raw_v1
8	Going Faster Mastering the Art of Race Driving - Carl Lopez	3b70eb1f-e4e3-c70c-1221-c2c8a8e43d83	51	1	uio_books_raw_v1