Check the local overlay before you commit

Generated from content/lms/race-class-rules-and-categories/01-read-the-rules-before-the-build/03-check-the-local-overlay.md; edit the source file, not this page.

Source path: content/lms/race-class-rules-and-categories/01-read-the-rules-before-the-build/03-check-the-local-overlay.md

Course: Choose the race class that fits your car and goals

Module: Read the rules before the build

Estimated duration: 45 minutes

Principle: the local overlay is binding, not background reading.

You already know that a race car is not built against vibes. It is built against rules. The skill in this lesson is narrower than building the whole rulebook stack: before you register, buy parts, weld tabs, change safety gear, load the trailer, or decide that a car is ready for a specific weekend, you check the local overlay for that weekend. In SCCA Road Racing language, that overlay is mainly the Supplemental Regulations. In Race Experience language, the same idea appears as Event Information and Supplementary Regulations. The name changes, but the operating principle is the same: the base rules tell you the sport, the car category, the safety floor, and the general conduct system; the local overlay tells you what this event, this track, this host region, and this weekend require on top of that.

For an intermediate driver, the danger is not ignorance of the main book. The danger is confidence. You have read enough GCR sections to feel oriented. You know your car class. You have done tech before. You may have run the same facility in a track-day context. That familiarity can make the local overlay feel like paperwork instead of a control document. The bonded rules material does not support treating it that way. Supplemental Regulations establish event-specific conditions, differ from event to event, and often carry track-specific information you need before arrival. Event Information and Supplementary Regulations also govern driver conduct, tech compliance, and event operations in the Race Experience framework. When you enter the event, you are not merely agreeing to race in a general series. You are agreeing to the base rules and the event overlay together.

The mechanism is simple. A race weekend is a managed system, not a private test day. Registration, paddock placement, tech inspection, grid, fuel, timing and scoring, medical support, drivers meetings, officials, results, and trophies all have event-specific procedures. On track, flags are the communication system between officials and drivers. Pit road speed limits, racing room expectations, reentry after an off, and pass responsibility are controlled by the event rules and the general racing rules. Tech inspectors certify cars and driver gear against the current rules and event Supplementary Regulations. Race Directors conduct the event under the Race Experience Rules and Event Information or Supplementary Regulations. Driver Coaches may talk with drivers who have been black-flagged or need correction. If you skip the overlay, you are not just risking an administrative annoyance. You are entering a managed system without its local operating instructions.

That matters before the build because many race-car choices become expensive once they are physical. A bracket is welded. A seat is mounted. A harness date is accepted in your mind. A helmet is packed or left home. A spare wheel, fuel quantity, transponder plan, or logbook binder is either on the truck or still in the garage. The local overlay is the last check before those choices become commitments for this particular event. It may not replace the GCR, class specifications, or safety rules, but it can change what you must bring, where you must go, who must sign off, when you must present the car, and what conduct standard will be enforced when the green flag drops.

Use a three-layer mental model. Layer one is the permanent rulebook: GCR sections, class specifications, conduct rules, penalties, protest and appeals process, and any sanctioning-body code you are actually racing under. Layer two is the car-specific or class-specific rule material: production specifications, accepted modifications, safety equipment, and classification boundaries. Layer three is the local overlay: event Supplemental Regulations, host-region web information, event information packet, driver meeting notes, and any official bulletin or instruction for that weekend. This lesson is about layer three. Do not let it duplicate the sibling lesson on building the rulebook stack. Your job here is to catch the event delta: the local fact that changes what you do for this weekend.

The technique: run an overlay-to-commitment pass.

Do the pass before the point where changing plans becomes costly. A clean sequence is: first, identify the event and sanctioning body; second, collect the base rules and the local overlay; third, translate the overlay into decisions; fourth, decide whether the car, driver, crew, paperwork, and schedule are ready. Do not read the overlay like a novel. Read it like a preflight checklist for a race operation.

Start with document identity. Confirm which rule system governs the event. For SCCA Road Racing, the GCR is the central document, with Supplemental Regulations added for the specific event. Older instructional material points out the same broader habit: learn the club publication, get the GCR, use the production-car specifications when those apply, and track official regulation changes through the official publication. If you race outside SCCA, the named book changes. IMSA has its code; international rules point toward FIA material. The lesson is not that one book is universal. The lesson is that you must know which authority governs this weekend before you treat any build or entry decision as settled.

Then isolate the local overlay. Do not bury it inside your general rulebook notes. Open a separate event sheet with seven gates: credentials and entrant, car and driver gear, paddock and facility logistics, schedule and required meetings, on-track conduct, officials and escalation, and commitment risks. Each gate gets a simple result: clear, question, or stop. Clear means you know what the event requires and the car/driver plan satisfies it. Question means a named official or event contact must answer before you commit. Stop means the requirement can keep you from running, getting a tech sticker, staying in good standing, or finishing the licensing objective.

Gate one is credentials and standing. The SCCA guide says you must bring a proper competition credential to drive at a Road Racing event: a Novice Permit, a Full Competition License, or a license from a recognized sanctioning organization where accepted. It also explains that the entrant is the person submitting registration, often the driver but not always, and that only the driver or entrant has standing for certain administrative purposes at an event. That is not theory. Before you commit, decide who the entrant is, whether that person will be present, whether the credential is current, and what happens to it at registration. A novice permit may be retained by registration and forwarded to the steward or require delivery to the right official. Your responsibility includes getting it back at the end of the weekend. If that surprises you at the track, you have already failed the overlay pass.

Gate two is car and gear tech. The overlay pass asks what you must present, not what you assume tech will ask for. The new-driver guide says that before going on track you must visit scrutineers, usually tech, to obtain a tech sticker. You need the car logbook. You may need your helmet depending on the Supplemental Regulations. At the first event each year, you also need to present personal safety gear. The Race Experience rules assign Technical and Safety Inspection the job of certifying that competition vehicles and required driver gear comply with current Race Experience Rules and event Supplementary Regulations. That means the local overlay is not outside the tech lane. It is one of the documents tech can enforce.

Gate three is paddock and facility logistics. The overlay pass should let you arrive already knowing where the car goes and how the day flows. The SCCA guide explicitly sends you to the Supplemental Regulations and host region website for paddock information. It also tells you to find grid entry, fuel, timing and scoring, medical assistance, drivers meeting locations, stewards, results, and trophy location. Those details sound humble, but they decide how much of your attention is available for driving. If you are wandering the paddock looking for fuel, grid, or the drivers meeting while your group is forming, the overlay failure is already taxing your driving.

Gate four is schedule and attendance. A local overlay is often where the event tells you when registration opens, when tech is available, where a driver meeting will happen, and whether any novice or race-experience classroom session applies. The bonded chunks do not give a universal schedule format, so do not invent one. Instead, treat every time and place in the event packet as a commitment that competes with car prep, crew arrival, fuel, tire pressure, warm-up, and driver briefing. If your arrival plan cannot satisfy the overlay schedule without rushing, the plan is not clear. It is a question or a stop.

Gate five is on-track conduct. This is where many intermediate drivers get lazy because conduct feels familiar. The Race Experience material is blunt: drivers are expected to follow rules for flagging, pit road speed limits, racing etiquette, and event-specifics outlined in Event Information or Supplementary Regulations. Failure can mean black flags, penalties, mistrust from competitors, a poor finish, and not being invited back. The same material defines expectations around car control, track limits, racing room, overtaking, blocking, squeezing, spins, offs, and contact. The SCCA guide points toward GCR Section 6, with flags as the only communication from officials to drivers and close-car conduct covered by the racing rules. Your overlay pass must turn conduct rules into driver behaviors before the first session.

Gate six is officials and escalation. You do not need to memorize every official's biography, but you must know the functional map. Registration handles credentials and outstanding items. Tech issues stickers and checks cars and gear. Stewards operate the event and adjudicate disputes. Race Directors handle the general conduct of Race Experience events. Driver Coaches observe, correct, debrief, and speak with drivers who have been black-flagged or who need coaching. Local volunteer systems differ across tracks, and the science-of-motorsport material emphasizes that procedures differ across venues. So the overlay pass asks: if I have a credential issue, a tech question, a paddock question, a conduct question, or a black flag conversation, where does that go at this event?

Gate seven is the commitment decision. When all six previous gates are clear, you can commit: register, travel, bring the car, run the event, or finalize a build decision for that event. When a gate is a question, you do not solve it by hoping. You ask the correct official or event contact, record the answer, and keep that answer with the event paperwork. When a gate is a stop, you either fix the requirement before commitment or choose a different event. This is where the local overlay protects your money and reputation. It is cheaper to find an event-specific tech requirement before travel than at the tech shed with the car already unloaded.

Sub-skill one: separate permanent rules from event delta.

The permanent rulebook tells you the general competition structure. The local overlay tells you what changes at this event. Intermediate drivers often blur those together. They remember that a car passed annual inspection, then assume the weekend has no gear presentation requirement. They remember a prior host region's paddock plan, then assume the same grid or fuel location. They remember a track-day passing rule, then carry it into a Race Experience event with wheel-to-wheel conduct language. The correction is to ask, at each gate, whether the answer came from the base rulebook or from this weekend's overlay. If the answer came from memory, last year's event, or a friend's paddock note, treat it as unverified until the local overlay or an event official confirms it.

Sub-skill two: translate text into physical objects.

A rule you cannot turn into an object or action is easy to forget. Credential requirement becomes license or permit in the folder. Entrant designation becomes a registration choice and a person who knows they carry standing. Tech requirement becomes logbook, helmet, personal safety gear, and any event-specific item packed together. Paddock guidance becomes an arrival plan. Fuel location becomes a fuel plan. Driver meeting location becomes a calendar alarm and walking route. Flag and racing-room language becomes a session intention. The point is not to admire the overlay. The point is to change what goes in the trailer, what goes in your pocket, what goes on the schedule, and what goes through your head before grid.

Sub-skill three: plan around the first at-track tasks.

The SCCA guide presents a predictable early sequence: registration, paddock, tech, then the rest of orientation before going on track. That sequence should be reflected in your arrival plan. You do not want registration to become your first reading of the event. You do not want the paddock location to be a guess. You do not want tech to be your first discovery that the helmet or gear must be presented. If the first at-track activity is resolving only outstanding items and collecting credentials, you are using the overlay correctly. If the first at-track activity is learning the event, you are late.

Sub-skill four: turn conduct rules into restraint, not bravado.

Race rules are not only there to punish people after mistakes. They shape the driving standard before the mistake. Race Experience rules place the primary burden of a pass on the overtaking driver because that driver has the best visibility, while also making the overtaken driver responsible for awareness and not impeding. They prohibit more than one defensive move and deliberate squeezing beyond the track edge. They define racing room as enough marked racing surface for a driver to maintain control in close quarters. If you read that only after contact, you have missed the point. The overlay pass should produce a driving agreement with yourself: leave room, keep control, reenter safely, obey flags, respect pit speed, and do not convert confusion into assertiveness.

Sub-skill five: protect the licensing and learning objective.

Johnson's driver-training discussion is useful here because it reminds you that early racing is not only about peak pace. Your attitude is watched, your ability to learn matters, the car must be dependable, and finished races count toward licensing while DNFs do not. That is an overlay lesson because local event commitments can either support or sabotage that objective. If your car barely runs, if your paperwork is uncertain, if your crew does not know the schedule, or if you burn attention on logistics, you reduce your chance of completing the weekend cleanly. The local overlay helps you preserve the real goal: run, learn, finish, and remain a driver the officials and competitors can trust.

Calibration cues: how you know the skill is working.

The best cue is boring registration. You arrive with the correct credential, entrant designation settled, and only normal outstanding items to resolve. If you are on a novice permit, you know whether it will be retained, where it goes, and how you get it back. The conversation is short because you did the event-specific reading before the event.

The second cue is boring tech. You know whether the car logbook, helmet, and personal gear are required at that point. You can answer which rule set and event overlay the car is being presented under. If the tech inspector asks for something the overlay already mentioned, you do not look surprised. The car either receives the sticker or the issue is a genuine mechanical or compliance problem, not an avoidable reading failure.

The third cue is paddock calm. You know where to park or how to ask for help. You know where grid, fuel, timing and scoring, medical assistance, drivers meetings, stewards, results, and trophies are located, or you know where the event told you to find them. Your crew is not pulling you away from driving focus with basic facility questions.

The fourth cue is cleaner on-track behavior. You obey flags because you reviewed them as the official communication system. You respect pit road speed and event-specific etiquette. You can race close without treating racing room as optional. If you are passed by a faster car or you are the faster car, you apply the burden and awareness rules rather than improvising from ego. You do not collect black flags for conduct rules you could have read.

The fifth cue is social trust. The Race Experience rules make clear that rule failures cost more than position; they damage competitor trust and can affect whether you are invited back. When the overlay skill is working, competitors do not have to guess what you will do, officials do not have to repeatedly correct the same avoidable behavior, and coaches can spend their time on driving quality rather than event literacy.

Recovery when you find a local-overlay issue late.

First, classify the issue. If it touches safety gear, car compliance, credentials, or anything tech must certify, treat it as a possible stop. Do not rationalize it as a minor administrative point. Tech's role includes certifying compliance with current rules and event Supplementary Regulations. A local tech requirement can be the difference between running and not running.

Second, find the right official path. Registration issues go through registration. Tech compliance questions go to tech. Conduct or black-flag matters belong with the appropriate Race Director, steward, or Driver Coach structure for the event. Paddock and facility questions may be answered through the host region, event information, or paddock staff. Do not ask the most confident person in the paddock when the overlay identifies a real official channel.

Third, preserve the answer. This lesson sits next to Preserve the paper trail for a reason. If an official clarifies an ambiguous local requirement, keep the clarification with the event file. You are not building a courtroom case in the paddock; you are preventing memory drift. The next time the same question appears, you want evidence of what you were told and by whom.

Fourth, adapt without drama. Some overlay misses are not fatal. A fuel location you did not mark can be fixed by adjusting the schedule. A driver-meeting location can be added to the crew plan. A paddock uncertainty can be solved by asking for help. The key is to adapt before the miss steals attention from driving or creates avoidable pressure at grid.

Cross-references.

Use Build your rulebook stack before the build for the permanent document set: GCR, car specifications, sanctioning-body codes, and official update streams. Use Separate safety, eligibility, and allowances before you build when the issue is what type of rule you are reading. Use Preserve the paper trail when you ask a region, steward, tech inspector, or event official for clarification. This lesson is the event-layer skill: take the local overlay seriously before you commit to the weekend.

Worked example: SCCA novice road race weekend

You are entering an SCCA Road Racing weekend on a Novice Permit. The wrong move is to read only the general racing rules, load the car, and assume registration will tell you the rest. The overlay method starts before registration. You collect the GCR sections that matter to you and the car, then you open the event Supplemental Regulations and host-region information as the local overlay.

Gate one asks whether your credential and entrant plan are clear. You confirm that the Novice Permit is the competition credential you will bring, and you decide whether you or a separate entrant will submit the registration. If a family member, car owner, or prep-shop representative is the entrant, that person must understand that only the driver or entrant has standing for certain administrative purposes. That changes the crew briefing. It is not just a registration convenience.

Gate two asks what registration will do with the permit. The SCCA guide says the Novice Permit may be retained by registration and forwarded to the steward for your run group, or you may be told where to deliver it. It also says getting the permit back at the end of the weekend is your responsibility. So your event sheet has a permit line with three blanks: who receives it, where it is after registration, and how you retrieve it. That small note prevents a Sunday-afternoon licensing scramble.

Gate three is tech. You know you must present the car logbook for the tech sticker. You check the Supplemental Regulations for whether the helmet must be presented. If this is your first event of the year, you pack personal safety gear for inspection. You also know that the annual car inspection requirement is separate from the event tech sticker. The local overlay does not replace the annual inspection rule, but it can change what you must physically carry to tech on this weekend.

Gate four is facility orientation. Before leaving home, your crew should know the likely paddock plan, where to ask for help if the facility is unfamiliar, how to enter grid, where fuel is available, where timing and scoring sits, where medical help is located, where drivers meetings happen, and where stewards or results can be found. If the Supplemental Regulations or host-region website gives those answers, you mark them. If not, your first paddock task is to ask deliberately, not wander.

Gate five is on-track conduct. You re-read the flag section because flags are the official communication system from corner and race control to the driver. You also review close-car conduct before you are close to anyone. The result is a specific first-session plan: obey every flag station, leave racing room, avoid thoughtless blocking, and treat uncertainty as a reason to create margin. For a novice permit driver, this is not timid. It is how you become the kind of driver the steward can sign off.

The success condition for this weekend is not that you look clever in the paddock. It is that registration is routine, tech is routine, the crew knows where to go, you attend the required meetings, you drive inside the conduct rules, and you finish the races that count toward the license path. The overlay made that possible before the trailer moved.

Worked example: Race Experience overlay and the black-flag conversation

Now take a Race Experience event. The local overlay is not only class paperwork. The Race Experience rules explicitly point drivers to Event Information and Supplementary Regulations for flagging, pit road speed limits, racing etiquette, and other event-specifics. If you treat that packet as optional, the event has several ways to make the lesson expensive: black flags, penalties, lost competitor trust, poor finishing position, and possibly not being invited back.

Your overlay pass begins by identifying who owns conduct at this event. The Race Director is responsible for the general conduct of the event under the Race Experience Rules and Event Information or Supplementary Regulations. Driver Coaches observe, work with the Event Lead and Race Director, speak to black-flagged drivers, and coach drivers who need correction. Technical and Safety Inspection certifies cars and gear against current Race Experience Rules and event Supplementary Regulations. That map tells you where the consequences live. If you break a conduct rule, you are not only arguing with another driver. You are entering an event-management process.

Now translate the local overlay into driver behavior. Pit road speed is not a suggestion. Track limits mean you stay on the marked racing surface unless there is justification, and reentry after an off must be safe and must not create a lasting advantage. Racing room means the other car gets enough marked surface to maintain control in close quarters. If you are overtaking, you carry the primary burden for deciding to pass and completing the pass safely because you have the best visibility. If you are being overtaken, you must be aware and avoid impeding or blocking. More than one defensive move is not allowed, and squeezing a car beyond the track edge is prohibited.

Imagine your first stint. You exit pit lane hot, miss the local pit-speed expectation, crowd a car at corner exit, and then claim you were racing. The Driver Coach conversation will not be about your bravery. It will be about an overlay failure. You had access to the event-specific conduct rules and the general examples before the stint. The correct preparation would have been to write three session intentions on your notes: pit lane discipline, racing-room discipline, and safe reentry discipline. Those are local-overlay commitments, not abstract etiquette.

The worked lesson is this: Race Experience overlays govern behavior as much as paperwork. Checking them before you commit is how you avoid converting an avoidable reading miss into a black flag, a damaged relationship, or an early end to a stint.

Worked example: sprint-race fuel, pit tools, and the overlay plan

Alan Johnson's sprint-race pit guidance gives a useful practical overlay example even though it is not written as a modern event packet. The usual SCCA Regional or National is short enough that a pit stop ruins any serious position result, but a novice still needs to rejoin and be running at the flag if possible. That means the local-overlay check cannot stop at paperwork. It must reach the pit and fuel plan.

Before the event, the SCCA guide tells you to find where fuel is available. Johnson adds the operational standard: the crew should have basic tools ready, including a jack, lug wrench, spare tire with correct pressure, pliers, screwdriver, safety wire, and racer tape. He also warns that needing gas or oil during a sprint race means the pre-race plan failed, and says to carry at least the event fuel requirement plus a small margin. The exact fuel amount is your car and event calculation, but the principle is supported: do the fuel plan before the race, not after the gauge scares you.

The overlay pass turns that into a commitment sheet. You mark the fuel location from the Supplemental Regulations or host-region information. You decide whether fuel must be bought on site or brought in under the event's rules. You assign a crew member to tire pressure, spare-tire readiness, and basic pit tools. You confirm the car has enough fuel for the race plus margin before grid. If a longer race has planned stops, Johnson's guidance pushes you to plan and practice them rather than improvise.

The point is not that every intermediate club racer needs a NASCAR-style pit crew. The point is that local event information and race-operation planning meet before the green flag. If the overlay tells you where fuel is, when grid forms, and what the day requires, and your pit plan turns that into tools, pressure, fuel, and people, you have converted text into readiness. If you ignore it, the first time you think about fuel may be the moment it costs you a finish.

Common mistakes

The national-rulebook comfort trap. You read the GCR, class rules, or permanent code and feel prepared, so you skim the event overlay. Good looks like separating the permanent rules from the event delta. The base rules tell you the sport; the Supplemental Regulations tell you this weekend's local conditions.

The last-event copy-paste. You ran the same track or region before and assume the paddock, fuel, registration, meeting location, and tech expectations are unchanged. Good looks like checking the current event packet and host-region information every time, because supplemental rules differ by event and procedures differ across venues.

The build-shop tunnel vision. You focus on parts, setup, and eligibility while forgetting the objects that get you through registration and tech: credential, entrant information, car logbook, helmet, and personal gear when required. Good looks like packing against the event tech and registration requirements, not just against your memory of annual inspection.

The entrant blind spot. You let someone else register the car without deciding whether that person is the entrant and whether they will be present and informed. Good looks like deliberately choosing the entrant and understanding that the driver or entrant has standing for certain administrative purposes.

The tech-at-track surprise. You assume tech will only inspect what it inspected last time. Good looks like reading whether the event requires helmet presentation, first-event-of-year gear presentation, or any event-specific safety check, then arriving with those items ready.

The conduct-overlay mismatch. You treat Race Experience or club-racing conduct as if it were a casual track day. Good looks like reviewing flagging, pit road speed, track limits, racing room, overtaking responsibility, blocking limits, reentry, and contact expectations before the first session.

The paddock logistics drain. You arrive without knowing where grid, fuel, timing and scoring, medical, drivers meetings, stewards, results, or trophies are. Good looks like using the Supplemental Regulations and host-region information to remove those unknowns before the driver is under time pressure.

The reliability-is-separate mistake. You treat car dependability as a mechanical issue unrelated to rule preparation. Good looks like recognizing that, especially in the novice phase, a dependable car and clean finish support the licensing objective. If the car spends half the weekend in the pits, the paperwork may be perfect but the weekend still fails its purpose.

Drill: the seven-gate local-overlay audit

Do this drill for your next event before you register or before the last date when you can change plans without real cost. It takes about 60 minutes the first time and about 30 minutes once you have a template.

Set a timer for 10 minutes and collect the documents: base rulebook, car or class specifications if applicable, event Supplemental Regulations or Event Information, host-region event page, and any official bulletin or schedule available. The success criterion for this first block is a named document stack, not a folder of random downloads.

Set a timer for 35 minutes and work the seven gates. Gate one: credential and entrant. Write the credential you will bring, who the entrant is, and whether any permit handling applies. Gate two: car and gear tech. Write what must be presented at tech and what item could stop the car from receiving a sticker. Gate three: paddock and facility. Write where to find paddock help, grid, fuel, timing and scoring, medical, meetings, officials, and results, or write the official place you will ask. Gate four: schedule. Write arrival, registration, tech, meetings, and first on-track timing. Gate five: conduct. Write three event-specific driving behaviors you must honor. Gate six: officials. Write who handles registration, tech, conduct, coaching, and steward questions. Gate seven: commitment decision. Mark each gate clear, question, or stop.

Set a timer for 10 minutes and convert every question into an action. Each question gets an owner, contact path, and deadline. Each stop gets either a fix or a decision not to run. Each clear gate gets one physical packing or schedule action where applicable.

Use the drill for two consecutive events. The success criterion is not perfection. It is that no event-specific requirement surprises you at registration, tech, grid, or the first conduct discussion. A strong pass means registration is short, tech is predictable, the crew can answer facility questions without asking you, and your first session has no overlay-caused black flag or missed meeting.

When this principle breaks down

The principle does not mean the local overlay can answer every build question. If you need to know whether a modification is legal, whether a safety item satisfies the main rules, or whether a car belongs in a class, you must go back to the permanent rulebook, class specifications, and the safety-versus-eligibility-versus-allowance split covered in sibling lessons. The overlay tells you the local conditions for the event; it is not a substitute for the underlying class law.

The principle also breaks down when the overlay is missing, late, unclear, or contradicted by another document. That is not permission to invent the most convenient answer. It is a question gate. Ask through the event's official channel, registration, tech, the host region, Race Director, steward, or other named official path depending on the issue. Preserve the answer with your event paperwork.

Finally, the principle has limits when procedures change at the track. Venue procedures differ, volunteers and officials carry local knowledge, and event management may need to respond to conditions. When a real official update changes the plan, adapt to the official update. The skill is not stubbornly clinging to the PDF you printed. The skill is knowing the governing stack well enough to recognize a real local instruction and respond before it becomes a safety, compliance, or trust problem.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	New Drivers and Minor Drivers Guide v1.0	af3b5e92254e14ffa0dd0dd29497783f	1	1	uio_books_raw_v1
2	New Drivers and Minor Drivers Guide v1.0	52b5e9e8885b461b1b284e754b2db070	1	1	uio_books_raw_v1
3	RACE EXPERIENCE RULES	700f781fc620525801fbc4e33e90a5b9	37	1	uio_books_raw_v1
4	RACE EXPERIENCE RULES	c847c14e9bca676ed203ef4dc499e9b2	56	1	uio_books_raw_v1
5	Driving in competition None Johnson Alan 1935- None	5ede8de3-8eee-4c85-6699-e2cedc9cae21	19	1	uio_books_raw_v1
6	the science of motorsport	1ddfa98d-7910-5ba5-8140-a565bbd3749c	229	1	uio_books_raw_v1
7	Driving in competition None Johnson Alan 1935- None	27cc50b4-e42e-372d-7880-855de7ffb799	126	1	uio_books_raw_v1
8	Driving in competition None Johnson Alan 1935- None	5e878120-b2a6-b838-9d99-38888a4e8e8b	114	1	uio_books_raw_v1