Pressure-test the spec on paper first
Generated from
content/lms/tires-and-brakes-engineering/07-validate-and-handoff-a-working-spec/02-run-paper-tests-before-track-tests.md; edit the source file, not this page.
Source path: content/lms/tires-and-brakes-engineering/07-validate-and-handoff-a-working-spec/02-run-paper-tests-before-track-tests.md
Course: Engineer tire and brake grip that lasts
Module: Validate and hand off a working spec
Estimated duration: 45 minutes
A paper test is the discipline of making the spec answer hard questions before the car answers them at speed. You are not proving the tire or brake package yet. You are proving that the test idea is coherent enough to deserve a track run. For this module, that means you take the written tire or brake spec, the proposed test intent, the known mechanisms from tire and brake behavior, and the evidence plan, then you look for the failures that can be found while the car is still quiet.
The practical rule is simple: a track test should confirm or reject a prepared question, not discover that the question was never written. Fred Puhn frames brake-system work as carefully planned steps that start with a written statement of what the brake system must do. Paul Haney's tire-development material points in the same direction from the tire side: knowing what questions to ask changes the quality of the technical conversation, and tire work is full of missing information, load effects, pressure effects, temperature effects, driver feedback, and performance data. A paper test is where you make those known complexities visible before they become a confused session.
This lesson sits between the sibling lessons. Build a tire and brake test matrix teaches the run structure. Inspect the tire before trusting results teaches the physical tire-read gate. Write the handoff spec teaches the final transfer of instructions. This lesson is the desk check before all three. It asks whether the spec has enough written criteria, enough known data, enough planned measurements, and enough answerable questions to go to the track without wasting the first run on confusion.
The principle: state the duty, then interrogate the mechanisms.
Start with duty. A brake spec has to say what the system must do for the car and use case. Puhn's brake-design passage separates a race-car brake system from road-car assumptions and warns that brake performance is too critical to compromise. That is not a styling preference. It is a paper-test gate. If the spec cannot say whether the hardware is being asked to serve a racing duty, a street duty, or a hybrid compromise, then the track test is already contaminated. You will not know whether a failure came from the concept, the components, or a duty mismatch.
A tire spec needs the same duty statement. Haney's tire chapters point to load and internal pressure, overloading and underinflation, braking and acceleration forces, bias-ply versus radial construction, street tires versus race tires, tire temperature and pressure, tire testing, driver feedback, and tire performance data. You do not need to solve all of tire science on paper, but you do need to show that the spec has noticed the mechanisms it is about to disturb. If the spec changes pressure but has no plan for temperature, or compares tires but has no awareness of load sensitivity, or asks for driver feedback but has no structure for what the driver should report, the paper test should fail.
Then interrogate the mechanisms. Tires and brakes do not live in separate boxes once the car is moving. The tire is asked for longitudinal force under braking and acceleration, lateral force in a corner, and combined force when those demands overlap. The brake system changes the force demand at the contact patch. Internal pressure changes how the tire supports load. Temperature and speed effects matter to rubber friction. Front and rear fluid-pressure relationships and proportioning become part of whether the car can use available traction. A paper test that treats brake result, tire result, pressure result, and driver comment as unrelated topics is not ready.
The technique: run five written passes.
Pass one is the duty pass. Write the answer the test is supposed to produce in one sentence. The sentence must name the object being judged, such as pad choice, proportioning setting, pressure target, tire construction, or handoff criterion. It must also name the use case. A race car brake system and a street car brake system are not the same paper problem. A street tire and a race tire are not the same paper problem. The duty pass fails if the sentence is vague enough that several different track results could all be called success.
Pass two is the mechanism pass. Under the duty sentence, list the mechanisms that can plausibly affect the result. For a brake paper test, include front and rear pressure relationship, proportioning or balance adjustment if the car uses it, temperature evidence such as temperature-sensing paint when available, and the tire traction condition the brake system is trying to use. For a tire paper test, include load and internal pressure, overloading and underinflation risk, braking and acceleration forces, temperature and speed effects, load sensitivity, rolling radius, spring rate, and self-aligning torque if the data are available. Do not turn this into a textbook outline. Only list mechanisms that can change the answer to the test.
Pass three is the evidence pass. For each mechanism, write what evidence will let you say something useful after the run. Tire temperature and pressure are explicitly part of Haney's tire-performance scope, so a tire paper test should say how those values enter the decision. Puhn's brake material shows temperature-sensing paint and proportioning hardware in the brake-system context, so a brake paper test can plan evidence around temperature marks and front/rear control settings when the car has those features. Haney's tire-testing material includes driver feedback and performance data, so driver comments should be treated as evidence only when the driver has been asked a specific question that matches the duty sentence.
Pass four is the missing-information pass. Haney names missing information directly in the tire-performance-data chapter outline, and the interview passage makes the point that research improves the questions you can ask. On paper, mark every place where the spec depends on a value you do not have: tire spring rate, rolling radius, load sensitivity, self-aligning torque, a pressure recommendation, a brake pressure relationship, a compound temperature check, or a supplier explanation. You are not required to fill every blank before testing, but you are required to know which blanks you are carrying into the test. A known unknown can be managed. An invisible unknown becomes a false conclusion.
Pass five is the contradiction pass. Read the paper test as if you want to stop it. Look for places where the duty statement and the evidence plan disagree. A spec that says maximum deceleration but has no front/rear pressure or traction-condition thinking is not internally clean. A spec that says tire comparison but ignores pressure and temperature is not internally clean. A spec that says racing use but relies on road-car brake assumptions is not internally clean. A spec that asks for driver feedback but never says what the driver should feel for is not internally clean. The contradiction pass is successful when the remaining questions are explicit enough to hand to the person running the test.
The sub-skills.
The first sub-skill is writing a real design criterion. Do not write a wish. Write a duty. A useful brake criterion says what the system must do for the car's use. A useful tire criterion says what the tire choice, pressure choice, or tire-data request is supposed to decide. The criterion is not the full handoff spec; that belongs in the sibling handoff lesson. Here, it is the minimum sentence that prevents the test from drifting.
The second sub-skill is data inventory. Haney's tire-performance-data outline names typical tire data such as spring rate, rolling radius, load sensitivity, and self-aligning torque, along with lab testing and simulation software. Your paper test should ask which of those data types matter to the proposed decision and whether you actually have them. If you do not, you decide whether the track test can still answer a narrower question. For example, you may not have lab tire data, but you may still be able to structure a pressure-and-temperature observation. What you cannot do is pretend the missing lab data do not exist.
The third sub-skill is question drafting. The Haney interview passage is a good reminder that technical answers improve when the question improves. Do not ask a supplier, engineer, or driver for general impressions first. Ask whether the pressure range is appropriate for the load, whether camber or toe could be outside the useful window, whether the compound or brake hardware fits the duty, whether the temperature evidence is adequate, and whether the data you lack would change the interpretation. The point is not to collect opinions. The point is to remove ambiguity before the car runs.
The fourth sub-skill is evidence mapping. Every planned observation should have a reason to exist. Tire pressure and temperature matter because tire performance changes with load, pressure, temperature, speed, and construction. Brake temperature evidence matters because Puhn's brake material places rubbing-surface temperature and temperature-sensing paint inside the brake-system toolkit. Front/rear pressure relationship matters because maximum deceleration depends on the traction condition and brake distribution. Driver feedback matters because Haney's tire-testing outline treats it as part of tire development, but it must be tied to the specific tire or brake behavior you are trying to learn.
The fifth sub-skill is keeping the scope narrow enough to read. Paper testing can become a way to avoid track testing if you let it sprawl. Do not build a full vehicle-dynamics model unless the spec truly requires it and the data exist. The paper test is a gate, not the race car. You are checking that the proposed track test has a duty, mechanism awareness, evidence, known missing information, and no obvious contradiction.
Calibration cues: what improvement looks like.
You are getting better at paper tests when the first track session becomes less surprising in the right way. You may still learn that the spec was wrong. That is normal. What should disappear are avoidable surprises: nobody knows what result would count, the driver gives a useful comment but the sheet has no place for it, a brake-balance change is made without noting the pressure relationship, a tire-pressure change is judged without temperature context, or the team realizes after the run that supplier data were needed.
A good paper test produces a shorter, sharper track conversation. The driver can be told what to notice. The mechanic knows which settings matter. The engineer or lead driver knows which missing data are being carried as risk. The test matrix builder knows which rows are worth running. The handoff writer knows what the spec is trying to preserve. If someone asks what question the next run answers, you can answer without rereading a long document.
You are also improving when your paper test finds reasons not to run. That can feel unproductive, but it is a valid result. If the brake package has no written duty, if a race-use car is still being judged through road-car brake assumptions, if a tire test depends on pressure while ignoring temperature, if the plan requires data you do not have and cannot observe at the track, or if the driver-feedback prompt is too vague to separate tire from brake behavior, the correct paper-test result is to revise before track testing.
Failure modes and recovery.
The first failure mode is track-first thinking. You assume the track will explain the spec. It will not. The track will produce behavior. Without a written duty and evidence plan, that behavior can be overread. Recovery is to stop and write the single decision the test is supposed to make.
The second failure mode is treating tire behavior as simple friction. Haney's table-of-contents fragments alone warn you away from that: rubber friction has adhesion, road-surface effects, load sensitivity, temperature and speed effects, and later tire behavior includes internal pressure, load sensitivity, standing waves, frequency response, combined forces, balance, and control. Recovery is not to become a tire designer. Recovery is to ask which of those mechanisms could change your specific test result and then add evidence or a caveat.
The third failure mode is treating brake choice as a parts preference. Puhn's brake-design material starts with what the system must do and separates race and road use. Recovery is to restate the brake duty before discussing calipers, pads, proportioning, or temperature checks. If the duty changes, the test question changes.
The fourth failure mode is collecting feedback without a prompt. Driver feedback helps develop tires, but only if the driver knows what they are trying to report. Recovery is to give the driver a narrow observation task connected to the spec. Ask for a brake-release feel, a front-tire support feel, a rear-tire stability feel, a temperature-related change across the run, or a balance change after a pressure adjustment only when that matches the test question.
The fifth failure mode is hiding missing information. Haney explicitly calls out missing tire information in the performance-data chapter outline. Recovery is to label the blank. If you do not have tire load-sensitivity data, say so. If you do not know the brake pressure relationship, say so. If supplier guidance is unavailable, say so. A written unknown is safer than a silent assumption.
Cross-references.
After this paper gate passes, move into Build a tire and brake test matrix to turn the question into rows, controls, repeats, and run order. Use Inspect the tire before trusting results when the paper test says tire condition or tire evidence can make the data misleading. Use Write the handoff spec after the paper test and track test agree on what must be preserved for the next driver, mechanic, or event.
Worked example: brake-system paper test for a race car
Suppose the proposed spec says to validate a brake change on a race car. The paper test begins by rejecting the vague version of that sentence. Puhn's brake-design framing says the work starts with what the brake system must do, and his race-versus-road distinction matters here. So the duty sentence becomes narrower: decide whether the proposed race-car brake setup is ready to be track-tested for the intended racing duty without compromising brake performance.
Now run the mechanism pass. The paper test lists front versus rear fluid-pressure relationship, proportioning or balance adjustment if present, traction condition, brake temperature evidence, and whether the hardware assumption is race duty or road duty. The Puhn fragments support proportioning-valve and pressure-relationship thinking, and the cover material shows temperature-sensing paint as part of the brake toolkit. The paper test does not invent a pressure number. It asks whether the test plan can observe or control the relationship that matters.
The evidence pass then asks what the first track run will record. If the car has proportioning hardware, the setting needs to be written down. If temperature-sensing paint is used, the plan needs to say where it will be read and how the result will affect the decision. If the tire traction condition is part of the brake result, the plan cannot ignore the tire state. If the driver will report feel, the driver needs a narrow prompt tied to the brake duty, not a general question about whether the brakes feel good.
The contradiction pass is where this example often fails. If the spec says racing brake validation but the parts or assumptions are still framed as ordinary road-car suitability, revise. If the spec says maximum deceleration but has no way to account for front/rear pressure relationship or traction condition, revise. If the only evidence is a general impression, revise. The paper test passes only when the brake-track test has a written duty, a known hardware context, a planned temperature or setting observation where applicable, and a driver prompt that can actually inform the brake decision.
Worked example: tire-data paper test before a pressure change
Suppose the proposed spec says to try a tire-pressure change. On paper, that is not yet a test. Haney's tire material puts pressure beside load, overloading, underinflation, braking and acceleration forces, tire temperature and pressure, temperature and speed effects, load sensitivity, and typical data such as spring rate, rolling radius, load sensitivity, and self-aligning torque. The first paper-test move is to ask what the pressure change is supposed to decide.
A better duty sentence is narrow: decide whether the proposed pressure direction is worth a controlled track test for this tire and duty. Then the mechanism pass asks what pressure can disturb. It can change how the tire carries load, how the contact patch behaves under braking and acceleration demand, how temperature evidence is interpreted, and how driver feedback should be read. The paper test does not need to produce a tire-company model. It needs to stop you from treating pressure as an isolated number.
The missing-information pass is especially important in this example. If you have tire spring-rate data, rolling-radius data, load-sensitivity information, self-aligning-torque data, supplier pressure guidance, or past tire-testing notes, write them into the packet. If you do not have them, mark them as unknown. Haney's interview material supports doing research so the questions improve, and the supplier-support passage reminds you that technical product suppliers can be useful sources when asked specific questions.
The evidence pass should make temperature and pressure visible. If the run is meant to compare pressure behavior, the paper test should require pressure and temperature recording rather than accepting a driver impression alone. If driver feedback is included, the driver should be asked about a specific balance or support change that the pressure move could plausibly affect. The paper test fails if the proposed pressure change has no temperature context, no statement of the tire behavior being judged, and no known-data inventory.
Drill: the 30-minute no-car paper gate
Do this drill before your next event or before handing a tire or brake spec to another driver. Use one sheet of paper or one plain text document. Set a 30-minute timer. For the first five minutes, write one duty sentence for the tire or brake item you want to test. If it takes more than five minutes, that is the result: the test is not ready.
For the next eight minutes, list only the mechanisms that could change the answer. For a tire question, pull from pressure, load, braking and acceleration force, temperature and speed effects, construction, load sensitivity, rolling radius, spring rate, and self-aligning torque when relevant. For a brake question, pull from race-versus-road duty, front/rear pressure relationship, proportioning or balance hardware, temperature evidence, and tire traction condition. The success criterion is not a long list. The success criterion is that every listed mechanism could change the decision.
For the next eight minutes, build the evidence map. Write one observation beside each mechanism: setting recorded, pressure recorded, temperature recorded, driver prompt written, supplier question asked, or missing data labeled. If a mechanism has no possible observation and no source of supporting data, mark it as a risk rather than pretending it is covered.
For the final nine minutes, run the contradiction pass. Circle any mismatch between the duty sentence and the evidence map. Underline every missing value. Put a stop mark beside any contradiction that would make the first track run unreadable. The drill succeeds when the output gives you one of two clean results: ready for matrix planning, or revise before track testing. It fails when the sheet is full of general intentions but cannot say what the next run is supposed to prove.
Common mistakes
Mistake one is the parts-list test. The plan names pads, calipers, tires, or pressures, but it never states what the system must do. Good looks like a duty statement first and a parts list second.
Mistake two is the single-number tire test. The plan treats pressure as the whole tire decision. Good looks like pressure tied to load, temperature, braking and acceleration demand, and the tire data you have or lack.
Mistake three is the unsourced expert question. You ask a supplier or experienced driver a broad question and get a broad answer. Good looks like a question built from the mechanism pass: pressure range, camber or toe concern, temperature evidence, construction choice, or brake duty fit.
Mistake four is the driver-comment trap. The driver is asked for an overall impression, then that impression is used as if it proves the spec. Good looks like a driver prompt matched to the duty sentence and recorded beside the objective settings or observations.
Mistake five is the invisible unknown. The test depends on tire data, brake pressure relationship, temperature behavior, or supplier guidance that nobody has written down. Good looks like a missing-information list. You can test with gaps, but you cannot honestly interpret a result while pretending the gaps are gone.
Mistake six is the sibling-lesson mix-up. You start building a full test matrix before the paper gate has passed. Good looks like a short gate first: duty, mechanisms, evidence, missing information, contradictions. Only after that should you build the matrix.
When the paper test should stop the track test
Stopping is the right answer when the spec has no written criterion. Puhn's brake-design framing makes the written duty central, and tire testing has the same need for a clear question. If the duty is not written, do not spend the first run discovering it.
Stopping is also right when the planned evidence cannot answer the duty. A brake test that depends on distribution but records no proportioning or pressure-related setting is not ready. A tire test that depends on pressure but records no temperature context is not ready. A driver-feedback test with no driver prompt is not ready.
Stop when a duty mismatch is visible. If the car is being used for racing but the brake assumption is still road-car suitability, revise the spec. If the tire decision is about race use but the paper packet never distinguishes street tire and race tire behavior, revise the spec. If camber, toe, or inflation pressure could be outside the useful range and the plan never asks about them, revise the spec.
Finally, stop when the missing-information list is too central. You can carry unknowns into a track test, but only if the question remains answerable without them. If the missing data are the very thing needed to interpret the result, the paper test has done its job by keeping the car parked until the question is narrower.
Paper-test handoff format
Use a compact handoff so the next person does not have to reconstruct your thinking. Start with the duty sentence. Then list the mechanisms considered. Then list the evidence to record. Then list missing information and supplier or driver questions. End with the gate result: ready for matrix planning, revise spec, or request more data.
Keep the handoff deliberately smaller than the final spec. This is not the sibling handoff lesson and it is not the full test matrix. It is the proof that the test has a real question and a defensible evidence plan. If the paper-test handoff is clear, the track-test handoff becomes easier because the track team inherits a question instead of a pile of parts and hopes.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Brake Handbook Fred Puhn | 3d465707-6601-517e-fe94-f6d03d5b9968 | 89 | 1 | uio_books_raw_v1 |
| 2 | The Racing and High-Performance Tire Paul Haney | c7cd145f-3222-e76b-6637-4d1b3567bb4a | 187 | 1 | uio_books_raw_v1 |
| 3 | The Racing and High-Performance Tire Paul Haney | 221f3474-bd81-b046-beff-b7986be85df8 | 8 | 1 | uio_books_raw_v1 |
| 4 | The Racing and High-Performance Tire Paul Haney | dd27b82c-8a72-819b-19ef-7b9a54d9a2b4 | 6 | 1 | uio_books_raw_v1 |
| 5 | The Racing and High-Performance Tire Paul Haney | 32462b4c-7417-3172-c3bf-6c12636e872e | 7 | 1 | uio_books_raw_v1 |
| 6 | The Racing and High-Performance Tire Paul Haney | 798fa73e-a9d8-c82e-25cc-731fc9112cb9 | 7 | 1 | uio_books_raw_v1 |
| 7 | The Racing and High-Performance Tire Paul Haney | 2fb85dd4-d3c2-33f2-89ca-559fc9aaf180 | 5 | 1 | uio_books_raw_v1 |
| 8 | The Racing and High-Performance Tire Paul Haney | ea0cfc03-c9dc-d850-b4f3-4d2d9520f5f3 | 7 | 1 | uio_books_raw_v1 |
| 9 | The Racing and High-Performance Tire Paul Haney | 66030e95-8de0-33d1-9de0-86cc1395b84b | 19 | 1 | uio_books_raw_v1 |
| 10 | Brake Handbook Fred Puhn | a23c862e-40fa-1107-1fab-10f69cb424e9 | 96 | 1 | uio_books_raw_v1 |
| 11 | Brake Handbook Fred Puhn | 5d3058e5-0d17-72bc-937f-03c85b869759 | 55 | 1 | uio_books_raw_v1 |
| 12 | Brake Handbook Fred Puhn | 024b35e3-7e7c-0378-00c0-d03ae4f1115f | 2 | 1 | uio_books_raw_v1 |
| 13 | Brake Handbook Fred Puhn | 38bb7bb1-423b-110d-a5ed-653d5b172302 | 11 | 1 | uio_books_raw_v1 |
| 14 | The Racing and High-Performance Tire Paul Haney | 106208c3-32c1-09ef-6217-fc5dd4280b65 | 165 | 1 | uio_books_raw_v1 |
| 15 | The Racing and High-Performance Tire Paul Haney | 0528b7f6-a4bf-cd9a-4bfb-b305c71aff39 | 6 | 1 | uio_books_raw_v1 |
| 16 | The Racing and High-Performance Tire Paul Haney | 86614d56-65e8-99dd-0495-d6e4b9ce210f | 5 | 1 | uio_books_raw_v1 |