Check Fastrack before you bolt on the update

Generated from content/lms/platform-specific-spec-miata/07-survive-tech-tires-and-rule-updates/02-track-fastrack-and-obsolete-part-updates.md; edit the source file, not this page.

Source path: content/lms/platform-specific-spec-miata/07-survive-tech-tires-and-rule-updates/02-track-fastrack-and-obsolete-part-updates.md

Course: Race a Spec Miata by the rulebook

Module: Survive tech, tires, and rule updates

Estimated duration: 55 minutes

Principle: in Spec Miata, the update is not legal because it exists, fits, solves a supply problem, or came from a believable shop. It is legal only when the rule authority for your sanctioning body, class, event, and region says it is legal. That is the skill in this lesson: before you install an obsolete-part replacement, tire update, or rule-driven component change, you build a short rule trail and you refuse to confuse testing, rumor, regional habit, or availability with permission.

This matters because Spec Miata is not an open development class. The SCCA Spec Miata language starts from a closed list: the class permits only the listed modifications and required safety items, and even a permitted component may not do a prohibited job. The same rule set also says updating or backdating is not allowed unless the rules specifically authorize it. NASA uses the same basic discipline in different words: modifications, additions, removals, and replacement parts are not allowed unless the rules specify or approve them, and the rules must be strictly followed. The practical result is simple. Your first question is not whether the part is better. Your first question is whether the current rule set has opened a door for that exact part on that exact car in that exact class.

Fastrack matters because the SCCA Spec Miata obsolete-parts rule gives it controlling force. When an update is needed because of reliability, supply, or obsolescence, alternative updated parts may be tested with direction and approval from the Club Racing Board. But that testing status is not the same thing as final legality. The update becomes effective only if the CRB finalizes it and it is published in Fastrack. If the part is merely being tested in sanctioned events, the driver or car must forfeit points. That one distinction is the heart of the lesson. A test part, a proposed update, and a final Fastrack-published update are three different states. Treating them as one state is how a legal rebuild becomes a tech problem.

Your job before bolting on an update is to answer five questions in order. First, what sanctioning body and rule family are you actually racing under? Second, what class variant are you entered in? Third, what is the base rule for the part or tire in that class? Fourth, does Fastrack or a regional rule create an amendment, exception, or final update? Fifth, does the event supplemental regulation add any condition you must obey at this event? If you cannot answer all five, the update is not ready to go on the car for competition.

Start with authority, not the part

The most common mistake is to start with the mechanical problem. You discover that the old part is scarce, unreliable, expensive, or discontinued. A vendor has a cleaner replacement. A paddock friend has already installed it. The car will run better with it. Those facts may explain why an update is being considered, but none of them establishes legality. In a restricted production-based class, the legality path starts with the rule authority.

For SCCA Spec Miata, the base authority in the corpus is the GCR Spec Miata section. It says Spec Miata automobiles must conform to GCR Section 9, and it frames the class as low cost, production based, and limited in modifications. It then locks the car to the correct year and VIN for major identity and parts questions. The firewall VIN takes precedence, and engines and internal components used in rebuilding or refurbishment must have been offered by Mazda in the United States for the correct year and VIN unless the Spec Miata rules say otherwise. Rebuild procedures and dimensions must follow the factory service procedures unless the rules say otherwise. Components may not be added or omitted from the published factory configuration unless the rules allow it. This is why you cannot reason from fitment alone. A part can bolt on, work well, and still be outside the allowed configuration.

For NASA Spec Miata Challenge, the corpus gives the same style of rule posture. The rules are subject to change, revisions are marked, and the series intent is to keep vehicles inside clearly established limits so the contest remains about driving skill. The format section is especially important for your decision process: additions, removals, and modifications are not allowed unless specified or approved. Replacement parts that are not specified by the rules must be OEM or the exact equivalent. That means you do not import an SCCA Fastrack answer into a NASA weekend unless the NASA rule set itself supports that answer. The names are similar, the cars may be similar, and the paddock may overlap, but the authority chain is not interchangeable.

Once you know the sanctioning body, identify the actual class variant. In the regional rules chunk, ordinary Spec Miata, Spec Miata T, Spec Miata Southeast T, and Spec Miata Southeast are not treated as one undifferentiated bucket. Some are tied to the SCCA GCR Spec Miata category specifications, some have a tire-rule exception, and some are reviewed or modified through regional meetings. A driver who says the Spec Miata rule allows it may still be wrong if the entry is in a regional variant with a specific overlay. Conversely, a regional tire allowance for one variant does not become a universal allowance for every SM entry.

Then identify the part category. Tires, obsolete replacement parts, safety equipment, ballast, interior removals, pedals, windows, and radios are not governed by one general permission. The GCR chunk shows that even allowed areas are narrow. Ballast has required location, fasteners, bolt size, lock nuts, washers, and allowed mounting holes. Door windows must be fully down. Safety equipment is required by referenced GCR sections. Pedal modifications are allowed for comfort and accessibility. These examples are useful because they show the class logic. Permission is usually specific. If the rule tells you where the ballast goes and how it is fastened, you should not assume another component update is free just because it seems harmless.

The Fastrack decision tree

Use this decision tree when you are considering a part update because the old part is hard to find, unreliable, or has been superseded.

Step one: name the old rule. Write down the base class rule that controls the original part. If it is an engine or internal component in SCCA SM, the starting point is the correct year and VIN, Mazda US availability, standard dimensions, and factory service procedures unless the rules create an exception. If it is a non-engine component, the starting point is the authorized-modifications list and the prohibition on updating or backdating unless specifically authorized. If it is a NASA car, start with the rule that additions, removals, modifications, and unspecified replacement parts are not allowed unless specified, approved, OEM, or exact equivalent.

Step two: name the reason for the update. The SCCA obsolete-parts path is not a general performance path. The corpus names reliability, supply, or obsolescence as reasons that can put an alternative updated source into testing with CRB direction and approval. If the reason is that the part is faster, lighter, easier to tune, or more convenient, you need a different specific permission. Do not dress a performance preference in obsolete-parts language.

Step three: separate testing from final legality. If a part is being tested during sanctioned events, that status carries a points consequence in the GCR chunk. That tells you testing is an exceptional status, not normal competition legality. If your plan depends on keeping points, do not use a test-status part unless you have verified the consequences and accepted them. If your plan depends on a championship result, you need final published legality, not a testing rumor.

Step four: look for final CRB action and Fastrack publication. The SCCA chunk is explicit that obsolete-parts updates become effective only when finalized by the CRB and published in Fastrack. Do not treat a draft, conversation, vendor note, social media post, or paddock consensus as a substitute for that final action. Your working rule should be: no final publication, no competition installation.

Step five: check the event layer. The new-driver guidance reminds you that supplemental regulations are additions to the GCR and are different for each event. That means the event can carry track-specific or event-specific information you need before arriving. For a rule update, the event layer can matter in two ways. It can point you toward the controlling rule package for that weekend, and it can affect what you must present at registration, tech, or impound. The rule may be legal nationally and still need documentation at this event because the scrutineers are the ones who issue the tech sticker.

Step six: prepare your evidence before tech asks. At the track, you need to visit tech before going on track, present the car log book, and sometimes present your helmet or safety gear. Once a year, the car itself must be inspected. That process is not the place to discover you cannot explain the update. Bring the current rule material, the relevant Fastrack reference if SCCA, and your car identification support such as the factory shop manual access required by the GCR. The factory manual is not just a shop convenience; in the GCR chunk it exists to help scrutineers identify parts and the configuration of the automobile.

Step seven: know who has standing. The new-driver guide says the entrant is the person submitting the event registration, and only the driver or entrant will be recognized for some administrative purposes. If a rule question becomes an official disagreement, do not let a crew member with no standing be the only person who understands the evidence. The driver and entrant need to know what changed, why it is legal, and where the documentation lives.

What good looks like

Good does not mean you can recite every rule in the GCR. Good means your update decision is traceable, narrow, and current. Traceable means you can show the base rule, the update rule, and the event overlay. Narrow means you can explain exactly which car, year, class, part, and event your answer applies to. Current means you checked the active rules, Fastrack if it controls the update, regional class rules if the class uses them, and supplemental regulations for the event.

A clean pre-event rule trail fits on one page. At the top, write the event, sanctioning body, class, car year, VIN-relevant configuration, and entrant. Then list the component. Under that, list the base rule. Under that, list the update authority. For SCCA obsolete parts, the update authority must include CRB finalization and Fastrack publication if you are relying on the obsolete-parts pathway. Under that, list any regional overlay, especially if the class is a regional variant. Under that, list any supplemental regulation that affects the event process. At the bottom, write the decision in plain language: install, do not install, install only as a test with points consequence, or hold until clarification.

The important part is the last line. You are not collecting rules to feel prepared. You are making a yes-or-no decision before the wrench touches the car. Intermediate drivers often lose discipline here because they know enough to find some rule language but not enough to force the language into a decision. If the trail does not produce a clear decision, the honest decision is hold.

The difference between national, regional, and event rules

The regional tire chunk gives you a compact example of why this hierarchy matters. It says the SEDIV Spec Miata tire rule for all SEDIV series races is the same tire as listed in the GCR for the Spec Miata National or Majors race class with any amendments in Fastrack. That sentence links the regional rule to the national rule and to Fastrack amendments. But the same chunk then describes Spec Miata T and Spec Miata Southeast T with a specific tire-rule exception: Toyo Proxes RR in size 205x50x15, all four tires the same manufacturer and model, with Toyo RA1 allowed but recommended only for wet conditions. It also states that the regional rule can only be modified at the Annual Meeting in January or the Mid-Year Meeting.

That creates three lessons. First, the national rule can be the base without being the whole answer. Second, Fastrack can amend the national-linked answer. Third, a regional class variant can have a specific exception that you must not generalize beyond its class. A driver who reads only the GCR may miss the regional exception. A driver who reads only the regional exception may apply it to the wrong class. A driver who reads a last-season version may miss a change window.

Supplemental regulations are a different layer. The new-driver guide calls them additions to the GCR and says they are different for each event. They often contain track-specific information you need to know. For this lesson, treat supps as the final event wrapper. They may not rewrite the class specification, but they tell you how this event is being run and what administrative expectations apply. If you are counting on a rule update, the supps help you know where registration, tech, results, stewards, and other officials fit into your weekend. That matters because rule trouble is partly a documentation problem and partly a process problem.

How to read the rule language without fooling yourself

There are several phrases in these chunks that should change your behavior.

Only modifications permitted means silence is not permission. In an open class, you might ask whether the rules prohibit a part. In Spec Miata, you usually ask whether the rules permit it. If the update is not in the permitted list, the class spec, the Fastrack-finalized update, or another controlling rule, it is not safe to install for competition.

Except as specifically authorized means the exception has to be specific enough to cover your case. A broad conversation about obsolete parts is not specific authorization for your year, component, and class. A regional tire exception for SMT and SMSE-T is not specific authorization for a different Spec Miata entry. A NASA approval pathway is not specific authorization for SCCA unless the SCCA authority says so.

Testing with direction and approval means somebody else may be gathering data, but you still need to understand the competition consequence. The SCCA obsolete-parts chunk says testing in sanctioned events requires forfeiting points. That is a major difference between a no-points test weekend and a points race. The part can be present at the event under a test arrangement and still be the wrong choice for your championship objective.

Finalized and published means the update has crossed the line into effective rule text. Do not skip those words. They are what separate a future rule from a current rule. If you cannot find finalization and Fastrack publication for an SCCA obsolete-part update, you have not finished the job.

Rules subject to change means last season's answer is not automatically current. The NASA chunk marks the rule version and notes revision colors. The regional rules list revision and review dates. The new-driver guide points you to current GCR, supps, and event procedures. The habit you are building is not one-time knowledge. It is a pre-event check.

Technique: the 20-minute pre-install audit

Do this before you order the part if possible. If the part is already on your bench, do it before installation. If the part is already on the car, do it before you enter the next event.

Minute 0 to 3: define the decision. Write one sentence: I am deciding whether this exact update is legal for this exact car in this exact class at this exact event. Include year, class variant, sanctioning body, and whether the event is points-bearing. This prevents the classic mistake of answering a nearby question instead of your actual question.

Minute 3 to 7: pull the base rule. For SCCA SM, start with the Spec Miata class rules and the authorized-modifications framework. If it is an engine or internal component, include the correct-year and VIN-based Mazda availability rule. If it is a non-engine component, identify whether the rules expressly allow the update, repair method, or replacement. For NASA, start with the format rule and the OEM or exact-equivalent replacement rule. If the base rule already says no and you have no exception, stop.

Minute 7 to 11: pull the update authority. For an SCCA obsolete-part update, look for the CRB and Fastrack path. The update must be finalized and published in Fastrack before it is effective. If the language only supports testing, write testing only and note the points forfeiture consequence. For a tire rule in the regional context, look at whether the rule points to the GCR tire, Fastrack amendments, or a specific regional exception.

Minute 11 to 14: pull the event overlay. Read the supplemental regulations for the event. You are looking for registration, tech, class grouping, and any rule-administration information that changes what you need to bring or do at the track. The supps are not a substitute for the GCR, but the new-driver guide treats them as an addition to it, and they can carry details you need.

Minute 14 to 17: assemble the tech packet. Put the rule trail where you can reach it. The driver and entrant should both know where it is. If the factory manual helps identify the part or original configuration, have that access ready because the GCR requires the entrant to possess a Mazda factory shop manual for the specific make, model, and year, and it is intended to help scrutineers identify parts and configuration.

Minute 17 to 20: make the decision. Use only four outcomes. Legal to install for this event. Not legal to install. Legal only under testing status with points consequence. Unclear, hold and seek official clarification before use. Do not create a fifth category called probably fine. Probably fine is the mental state that gets expensive in tech.

How this saves you at the track

At-track rule trouble costs attention first. The new-driver guide already gives you a full checklist for the weekend: registration, paddock, tech, grid entry, fuel, timing and scoring, medical, drivers meetings, stewards, results, and trophies. You also need to know the rules of the road, flags, and close-car conduct before you drive onto the track. That is a lot to manage. If you arrive with an unresolved parts question, it competes with the work that actually keeps the weekend smooth and safe.

The tech process is not hostile, but it is structured. You need a tech sticker before going on track. You present the log book, and depending on the event you may present helmet and personal safety gear. Once a year the car must be inspected. If a scrutineer asks about the update and you answer from memory, you are asking that official to trust your summary. If you hand over the rule trail, you have turned the discussion from a paddock debate into a documentation question.

The same is true if a disagreement becomes formal. The new-driver guide explains that procedures for disagreements appear in GCR Section 8 and that time limits usually begin 30 minutes after the session. The written form and fee requirement for protests means you cannot casually unwind a bad assumption after the race. You need documentation before the session, not a scramble after results are posted.

Sub-skills you are building

The first sub-skill is authority sorting. You learn to separate SCCA from NASA, national from regional, class from class variant, and GCR from supps. This is not paperwork trivia. The rules are part of the competition surface. A legal SCCA answer may not be a legal NASA answer. A regional SMT tire answer may not be a general SM answer. An event supp may not change the part's legality, but it can change how the event expects you to manage documentation.

The second sub-skill is exception discipline. Restricted classes are built from exceptions. You are allowed to remove spare wheels and trunk carpeting. You are allowed to make pedal modifications for comfort and accessibility. You are required to run both front door windows down. Ballast is allowed only under detailed mounting requirements. These examples train your eye: every permission has boundaries. When you read an update rule, ask what boundary it creates.

The third sub-skill is status recognition. Proposed, testing, finalized, published, reviewed, amended, and event-specific are not synonyms. The obsolete-parts chunk gives you the most important split: testing may happen with CRB direction and approval, but effectiveness comes only after CRB finalization and Fastrack publication. Regional tire language gives another split: a rule can be reviewed as experience is gained but modified only at specific meetings. Do not upgrade a rule's status in your head because you want the part on the car.

The fourth sub-skill is evidence packaging. A legal answer that you cannot present quickly is weaker than it should be. You need the base rule, update authority, event overlay, and identification support in a compact format. The driver and entrant both need to understand it. The factory manual requirement exists partly because scrutineers need a way to identify parts and configuration. Help that process.

The fifth sub-skill is timing. You check before ordering when possible, before installing if you already bought the part, and before entering if the part is already installed. Waiting until tech converts a cheap rule check into a weekend problem. Waiting until after a session converts it into a protest-timing problem. The guide's 30-minute protest window is a reminder that race administration moves on a clock.

Calibration cues

You are improving when your rule answers get shorter and more precise. Early on, your answer may sound like a story: the part is available, several people run it, the old one is obsolete, and somebody said it was coming. A better answer sounds like a decision: SCCA SM, this year and VIN, this component, final CRB action published in Fastrack, no conflicting regional or supp language, install for this event. Or: SCCA SM, testing status only, points forfeiture applies, do not install for a points weekend.

You are improving when you stop saying current rules in a vague way and start naming the rule layer. Current GCR. Current Fastrack amendment if SCCA obsolete-parts or tire language depends on it. Current regional rule if your class is under a regional overlay. Current supplemental regulations for the event. The word current should always point to a document.

You are improving when your tech packet gets thinner. This sounds backward, but it is not. A weak packet is a pile of pages. A strong packet is a small trail with the relevant lines already identified and the decision written plainly. Scrutineers do not need your entire research history. They need the controlling rule and enough context to see why it applies to your car.

You are improving when you can explain the same decision to three different people: your prep shop, your entrant, and a scrutineer. The prep shop needs the mechanical instruction. The entrant needs the administrative risk. The scrutineer needs the rule basis. If your explanation only works for one of those audiences, you probably have not separated the technical change from the legal authority.

You are improving when hold becomes an acceptable outcome. Intermediate racers often treat uncertainty as a problem to talk themselves out of. In rule compliance, uncertainty is information. If the authoritative trail is not complete, holding the update is a disciplined decision.

Cross-references inside this module

This lesson sits next to the tire-rule lesson. Do not duplicate that work by treating every tire choice here. Use this lesson for the process of checking whether Fastrack or a regional rule has changed the answer before you buy or install. Use the tire-rule lesson for the narrower task of verifying the tire itself before purchase.

It also connects to the recovery-point and audit lessons. The recovery-point idea is mechanical and logistical: make it obvious what you will do if the car fails, a part mismatch appears, or tech finds a problem. The audit lesson is the broader pre-tech sweep. This lesson is the specific upstream habit that keeps obsolete-part and update decisions from becoming audit failures. If the update cannot pass this Fastrack and authority check, it should not reach the final tech audit as a surprise.

The rule of thumb to keep

Bolt-on work is satisfying because it feels decisive. Rule work feels slower because it is reading, comparing, and documenting. In Spec Miata, the reading is part of the build. A part update becomes race-ready only after the authority chain says it is race-ready. For SCCA obsolete parts, that chain runs through CRB finalization and Fastrack publication. For regional variants, it may run through the GCR, Fastrack amendments, and the regional rule. For NASA, it runs through the NASA rule set and its specified or approved modifications. For every event, supplemental regulations tell you the final event conditions.

If you remember only one sentence, make it this: do not let availability outrun authority. The old part being hard to find explains why you are asking the question. It does not answer the question.

Worked example: SCCA obsolete replacement part before a points weekend

You have an SCCA Spec Miata and a component on the car has become difficult to source in the original form. A supplier offers an updated alternative and tells you the issue is an obsolete-parts situation. You are entered in a points weekend, so the decision matters.

The wrong way is to ask whether the updated part is reasonable. It may be reasonable. The GCR obsolete-parts language already recognizes that reliability, supply, and obsolescence can create a need for alternative updated sources. But the question for your weekend is not whether the need exists. The question is whether the update is effective for competition.

You start with the base SCCA SM rule. The car is a restricted production-based class car with limited modifications. Updating and backdating are not allowed unless specifically authorized. If the part is engine-related, the correct-year and VIN-based Mazda availability rule raises the bar further unless another rule creates the exception. This tells you the default answer is no.

Then you check the obsolete-parts path. The corpus supports three states. State one is ordinary illegality: the updated part is just a different part with no permission. State two is testing: alternative updated sources may be used in sanctioned events with direction and approval from the CRB, but testing in sanctioned events requires forfeiting points. State three is final legality: the update has been finalized by the CRB and published in Fastrack.

Because this is a points weekend, state two is not a harmless middle ground. If the part is only approved for testing and the car must forfeit points, it does not meet your event objective. Your decision line should read: do not install for this points event unless final CRB action has been published in Fastrack and no event or regional rule conflicts. If the part is already on the car and the trail only supports testing, you either accept the points consequence or remove the part before the event.

Worked example: SEDIV Spec Miata tire update versus SMT tire exception

You are running a SEDIV event and someone in the paddock says the regional Spec Miata tire situation changed. This is exactly where class labels matter.

The regional rules chunk says the SEDIV Spec Miata tire rule for all SEDIV series races follows the GCR tire for the Spec Miata National or Majors race class with Fastrack amendments. For ordinary SM in that regional context, your process is therefore GCR first, Fastrack amendments second, and regional rule third as the rule that points you to that chain. That is a different task from simply copying what another car has mounted.

The same chunk also creates a specific exception for Spec Miata T and Spec Miata Southeast T. Those vehicles must use Toyo Proxes RR tires in size 205x50x15, all four tires must be the same manufacturer and model, and Toyo RA1 is allowed but recommended only for wet conditions. That is a class-specific exception. If you are not entered in SMT or SMSE-T, do not treat that exception as your answer.

Now add timing. The regional rule says the Spec Miata tire rule is continually reviewed as experience is gained, but it can only be modified at the Annual Meeting in January or the Mid-Year Meeting. That means a paddock conversation after a race is not enough. A shop note about what people expect next season is not enough. You need the current regional rule and any Fastrack amendment that the regional rule incorporates. The decision line for ordinary SEDIV SM should read: use the GCR National or Majors SM tire as amended in Fastrack unless the current regional rule for my exact class variant says otherwise.

Worked example: NASA Spec Miata replacement part logic

You are moving between SCCA and NASA weekends with the same car. A replacement part looks legal under one rule discussion, and you want to know whether it carries over.

The NASA chunks tell you not to assume carryover. NASA identifies the rules as subject to change and marks revisions. It states the intent as keeping vehicles within clearly established limits so the contest is about driving skill. Most important for the update decision, the format section says modifications, additions, and removals are not allowed unless specified or approved, and replacement parts not specified by the rules must be OEM or the exact equivalent.

That produces a separate decision tree. You do not ask whether SCCA Fastrack discussed the part unless the NASA rules themselves incorporate that answer, and the corpus does not provide such incorporation. You ask whether NASA specifies or approves the modification, addition, removal, or replacement, or whether the replacement is OEM or the exact equivalent. If the answer is not clear, you hold the update for NASA competition.

This example is not about which sanctioning body is stricter. It is about authority. The same physical car can be subject to two different rule paths on two different weekends. The disciplined driver keeps separate rule trails.

Common mistakes

Mistake one is confusing need with permission. The old part is unreliable or obsolete, so the replacement feels justified. In the SCCA obsolete-parts rule, reliability, supply, and obsolescence explain why alternative sources may be tested. They do not by themselves make the part effective. Good looks like separating the need statement from the legality statement.

Mistake two is confusing testing with approval. A part being tested with CRB direction and approval is not the same as a final Fastrack-published update. The cost can be championship points, because the GCR chunk says sanctioned-event testing requires forfeiting points. Good looks like writing testing only on your rule trail until final publication exists.

Mistake three is importing the wrong rule family. SCCA and NASA both run Spec Miata-shaped racing, but the chunks give separate authority structures. NASA replacement parts must be OEM or exact equivalent unless rules specify otherwise, and SCCA obsolete-parts updates depend on CRB finalization and Fastrack publication. Good looks like making one rule trail per sanctioning body.

Mistake four is applying a class-variant exception to the wrong entry. The SEDIV regional tire chunk treats SM, SMT, SMSE-T, and SMSE differently. Good looks like writing the exact class from your entry before reading the tire or update rule.

Mistake five is arriving at tech with a memory instead of evidence. The guide says you need tech before going on track and may need log book, helmet, and personal safety gear, with annual inspection requirements for the car. Good looks like having the base rule, update authority, event supps, and factory-manual access ready before the car is in the tech line.

Mistake six is assuming the driver can delegate the whole rule problem. The new-driver guide says the driver and entrant should understand officials and that only the driver or entrant has standing for some administrative purposes. Good looks like the driver and entrant both understanding the update decision, even if a shop did the mechanical work.

Drill: three-event Fastrack and update audit

Run this drill across your next three events or test weekends. The goal is not to create paperwork for its own sake. The goal is to make rule-source checking automatic before parts choices become expensive.

Event one is the baseline audit. Choose one component on the car that was replaced, updated, or commonly questioned in your paddock. Spend 20 minutes building the rule trail: sanctioning body, class variant, base rule, update authority, regional overlay, and event supps. Success criterion: you can write one decision line that says legal, not legal, testing only with consequence, or unclear hold. If you cannot produce the decision line, the drill has found a weakness.

Event two is the tech-packet audit. Use a different component or a tire-rule question. Build the same trail, then reduce it to one page. Include only the controlling rule points and the decision line. Success criterion: your entrant or crew chief can read the page and explain the decision back to you without your commentary. If they cannot, your packet is too vague.

Event three is the pressure audit. Do the process before registration closes or before the car goes to tech. Add the event supplemental regulations and identify where tech, registration, stewards, results, and drivers meetings are handled for the weekend. Success criterion: if a scrutineer asks why the part or tire is legal, you can answer in less than one minute and produce the supporting trail. If the answer depends on memory, rumor, or a future expected change, you hold the update.

After the third event, keep the template. You do not need to redo every line for unchanged parts every weekend, but you do need to refresh it whenever rules are subject to change, Fastrack amendments matter, regional rules have review windows, or you move between sanctioning bodies.

When to stop and ask instead of installing

Stop when the only support you have is that the part fits. Fitment is a mechanical fact, not a class permission.

Stop when the only support you have is that the old part is obsolete. Obsolescence can open a testing and update pathway in SCCA SM, but the update becomes effective only after the required finalization and Fastrack publication.

Stop when the only support you have is another competitor's car. You may not know their class variant, sanctioning body, event objective, testing status, points situation, or whether they are legal.

Stop when the rule trail changes sanctioning bodies halfway through. A NASA approval or exact-equivalent argument is not an SCCA Fastrack publication. An SCCA Fastrack answer is not a NASA rule unless NASA's rules make it so.

Stop when your decision depends on a future meeting, expected review, or anticipated publication. The regional chunk shows review and modification timing, and the SCCA obsolete-parts chunk shows final publication as the effective step. Expected change is not current authority.

Stop when the driver and entrant cannot explain the change. The guide makes the driver and entrant central to event responsibility and administrative standing. A shop may prepare the car, but the driver and entrant live with the event consequence.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	GCR_SM	a2f7aa9cd510712c80997e684860bcc3	12	1	uio_books_raw_v1
2	GCR_SM	8aaac52cf61cfb33dae2abb73f7a7a52	1	1	uio_books_raw_v1
3	2023 Regional Class Rules	63384ad5199ffa8ecc8abca763c50e09	4	1	uio_books_raw_v1
4	New Drivers and Minor Drivers Guide v1.0	52b5e9e8885b461b1b284e754b2db070	1	1	uio_books_raw_v1
5	New Drivers and Minor Drivers Guide v1.0	af3b5e92254e14ffa0dd0dd29497783f	1	1	uio_books_raw_v1
6	New Drivers and Minor Drivers Guide v1.0	a6880e534a9363adadc87d8f0a6f9082	2	1	uio_books_raw_v1
7	2024 NASA Spec Miata Rules	66ac45c14be617ab2977cb35ac9db5f4	1	1	uio_books_raw_v1
8	2024_Spec_Miata_Rules	f486666f0d1f6f61102ddf03fac74a87	1	1	uio_books_raw_v1