Summit GT Racing Series Rulebook

Season 2 Official Rulebook

Version Date: 08/12/2026

Rulebook Revision Control

This rulebook may be updated as needed by Summit GT Racing Series officials to clarify rules, address competitive issues, improve league procedures, or correct errors.

Once the season is underway, rule changes should generally be limited to clarification, safety, race control, conduct, penalty review, or administrative items. Major competition format changes should be reserved for the offseason unless league officials determine that an immediate update is necessary.

All additions, edits, and clarifications should be recorded in the revision log below so drivers can easily identify what has changed.

Revision Log

1.0 League Overview

The Summit GT Racing Series is an organized iRacing road racing league built around competitive, respectful, and professional GT3 and LMP2 competition.

The goal of the series is to provide drivers with a structured championship environment that rewards racecraft, consistency, preparation, and clean competition.

All drivers are expected to understand and follow this rulebook, iRacing rules, event announcements, race-specific procedures, and instructions from league officials.

Participation in the Summit GT Racing Series is a privilege. Drivers are expected to conduct themselves in a way that represents the series, its members, broadcast partners, sponsors, and officials in a positive manner.

2.0 League Officials and Administration

Summit GT Racing Series officials are responsible for managing league operations, reviewing incidents, enforcing rules, issuing penalties, making eligibility decisions, and maintaining the overall integrity of the series.

League officials may include admins, race control, stewards, competition committee members, or any other individuals appointed by league leadership.

League officials have the authority to review incidents, issue penalties, interpret rules, approve or deny protests, rule on appeals, update procedures, and make final decisions related to the series.

2.1 Admin Contacts

Drivers should contact a Summit GT Racing Series admin if they have questions regarding rules, race procedures, protests, penalties, appeals, attendance, car selection, or general league operations.

The current Summit GT Racing Series admins are:

Drivers are expected to communicate with admins respectfully and professionally. Admins are available to help clarify rules and procedures, but drivers should avoid arguing penalties, incidents, or race decisions in public channels.

Questions, protests, appeals, or sensitive matters should be handled through the proper league communication channel whenever possible.

2.2 Incident Review Team

The Summit GT Racing Series Incident Review Team, also referred to as the IRT, may assist with race control, incident review, protest review, penalty recommendations, appeal review, and general event oversight.

IRT members are expected to review incidents fairly, remain professional, and make decisions based on the rulebook, available evidence, and the overall integrity of the series.

The current Summit GT Racing Series IRT members are:

Drivers may contact an admin or IRT member with questions regarding incidents, protests, penalties, or race control matters. Formal protests and appeals must still be submitted through the proper Summit GT Racing Series process.

IRT members who are directly involved in an incident may be excluded from reviewing that specific incident to help maintain fairness and avoid conflicts of interest.

3.0 Driver Eligibility and Expectations

Drivers must meet all eligibility requirements established by Summit GT Racing Series officials.

Drivers are expected to race with respect, control, awareness, and good judgment at all times. Aggressive racing is allowed, but reckless driving, intentional contact, retaliation, harassment, or repeated poor racecraft will not be tolerated.

Drivers are expected to know the schedule, race format, car selection requirements, event announcements, and any race-specific rules before entering an official session.

Drivers are also expected to be present in the required Discord channels when applicable and to monitor league communications.

3.1 iRating Entry Limit

To maintain a competitive and balanced field, the Summit GT Racing Series will enforce a maximum entry limit of 4000 iRating.

Drivers must have an iRating of 4000 or lower at the time of registration and approval into the series.

Drivers above the 4000 iRating limit are not eligible to compete unless specifically approved by League Administration.

League Administration reserves the right to verify a driver's iRating prior to approving entry into the series.

3.2 Driver Classifications

The Summit GT Racing Series will operate with three driver classifications: AM Division, PRO/AM Division, and PRO Division.

Once a driver is placed into a division and the season begins, that classification will remain in effect for the duration of the season unless modified by League Administration.

3.3 Administrative Review and Reclassification

To preserve competitive balance and the integrity of all divisions, League Administration reserves the right to review a driver's classification at any time during the season.

If a driver is determined to be competing significantly above or below the intended competitive level of their assigned division, League Administration may reclassify that driver between AM, PRO/AM, and PRO during the season.

Administrative reclassifications may be based on, but are not limited to:

• Demonstrated race pace
• Consistent competitive performance
• Championship results
• Significant changes in driver skill level
• Information unavailable during the initial classification process
• Any circumstance deemed necessary to maintain fair competition

All classification decisions made by League Administration are final and are not subject to protest or appeal.

3.4 Administrative Authority

Any driver found to have intentionally provided false or misleading information regarding their iRating may be subject to penalties. Penalties may include, but are not limited to, reclassification, loss of points, suspension, or removal from the series.

League Administration reserves the right to interpret and enforce these regulations in the best interest of fair competition and the long-term health of the Summit GT Racing Series.

3.5 Driver Inactivity Policy

Drivers who are inactive for a period of 30 or more consecutive days will forfeit their spot within the Summit GT Racing Series organization.

Inactivity is defined as having no participation in league events, communications, or league-related activity for the applicable period.

Upon removal, the driver will be:

• Removed from the Summit GT Discord server
• Removed from the iRacing league page
• Removed from the championship standings
• Their assigned car number will be released and made available to any incoming driver

Drivers who are removed due to inactivity and wish to return to the series must reapply through the standard registration process. There is no guarantee that a returning driver will receive their previously held car number, division classification, or standing.

4.0 Car Selection and Season Car Lock

4.1 Approved Car Classes

Season 2 of the Summit GT Racing Series will feature GT3 and LMP2 competition.

GT3 cars are available to approved drivers in the AM, PRO/AM, and PRO divisions.

LMP2 cars are restricted to PRO/AM and PRO drivers only. AM drivers are not permitted to compete in the LMP2 class.

Only cars approved by league officials for the current season may be used. The approved car list may be adjusted during the offseason or before the start of a season.

League Administration reserves the right to review and approve car/class eligibility in order to maintain safety, competitive balance, and the integrity of the series.

4.2 Car Selection

Drivers must select their car prior to the start of the season or prior to their first official race entry if joining after the season begins.

Once a driver has started their first official race of the season, that car becomes their registered car unless an approved in-season car change is completed under Section 4.3.

4.3 Season Car Change Limit

Each driver is permitted one car change per season. Any approved car change must occur within the first six races of the schedule.

Drivers requesting a car change must submit a new car entry form and receive approval or acknowledgement from League Administration before competing in the new car.

Drivers may not change cars without admin acknowledgement. A driver who enters practice, qualifying, or the race in a car other than their registered or approved car will be disqualified from that event.

Car changes will not be permitted after Race 6 of the season. Drivers may change cars during the offseason prior to the start of the next season.

5.0 Season 2 Schedule and Event Format

5.1 Season 2 Schedule

Season 2 will follow the official Summit GT Racing Series schedule published by League Administration.

The final track list, event dates, special event details, and any event-specific procedures will be announced before the season begins and may be updated through official race announcements.

5.2 Standard Event Schedule

Unless otherwise announced, standard Summit GT Racing Series events will follow this schedule:

Standard practice length will be 60 minutes.

Qualifying will be conducted as a 2-lap lone qualifying session unless otherwise stated in the event announcement.

Standard race length will be 60 minutes.

5.3 Special Event Exceptions

Certain events may use extended race lengths, adjusted qualifying procedures, special fuel or tire rules, different caution procedures, or other event-specific settings.

Any special event exceptions will be announced before the event and included in the race announcement.

League officials may announce additional format adjustments before special events.

5.4 Event Announcements

Event announcements may include race-specific information such as:

• Track
• Date
• Session times
• Race length
• Qualifying format
• Setup format
• Fuel setting
• Tire limits
• Fast repair setting
• Caution procedure
• Incident limit
• Special race procedures
• Broadcast information
• Any race-specific rule changes

Drivers are responsible for reviewing event announcements before each race.

6.0 Race Settings and Competition Format

6.1 Setup

Summit GT Racing Series events will use open setups unless otherwise stated in the event announcement.

Drivers are encouraged to practice for upcoming events in order to fine tune their setups, improve consistency, and maximize overall performance.

Drivers are responsible for selecting and managing their own setup. League Administration will not be responsible for setup-related performance issues, handling problems, tire wear, fuel usage, or drivability concerns.

6.2 Fuel

Fuel will be set to 80% unless otherwise stated in the event announcement.

6.3 Fast Repair

Fast repairs will not be available during Season 2 unless otherwise announced by League Administration before a specific event.

Drivers are responsible for managing damage and making safe decisions throughout the race. Because no fast repair is available, damaged cars that cannot maintain safe pace, remain predictable, or continue without creating a hazard must safely move off the racing surface and tow or retire from the event.

League Administration may adjust fast repair settings for special events or future seasons, but any change must be announced before the event.

6.4 Tire Limits

Certain events may limit the number of tire sets available during the race.

If tire limits are being used, the number of available sets will be included in the event announcement. Drivers are responsible for reviewing the event details prior to the race.

Tire limits may vary for standard races, endurance races, or special events.

6.5 Incident Limit

An incident limit may be used for official Summit GT Racing Series events. The specific incident limit will be listed in the race announcement or session settings.

Incident limits may vary depending on the track, race length, expected traffic, and overall event format.

Drivers are expected to maintain control of their car and race within reasonable limits. Reaching the incident cap may result in an in-sim penalty, removal from the race, or further league review if the incidents involve avoidable contact or unsafe driving.

6.6 Stop-and-Hold Penalties

Some events may include a stop-and-hold penalty before a driver reaches the final incident cap.

When used, the stop-and-hold threshold will be listed in the event announcement or session settings. Drivers who reach that threshold will be required to serve the penalty as applied by iRacing.

Failure to properly serve an assigned penalty may result in further race control review.

6.7 Disqualification Due to Incident Cap

Drivers who are disqualified by iRacing due to reaching the incident limit will be scored based on the official race results.

A driver disqualified for incident count may be listed as non-classified or may receive reduced finishing credit depending on the scoring system and league admin review.

Repeated disqualifications or excessive incident totals may result in additional penalties, probation, or review by league officials.

7.0 Points and Championship Format

7.1 Points System

The Summit GT Racing Series will use IMSA-style points unless otherwise announced by league officials.

7.2 Bonus Points

Drivers may earn bonus points as follows:

7.3 Drop Weeks

Each driver will receive two drop weeks during the season.

Drop weeks are intended to allow drivers flexibility for missed events, poor finishes, or unavoidable conflicts.

League officials reserve the right to determine whether penalties, suspensions, disqualifications, or other disciplinary results may be dropped.

7.4 Official Results

Official race results will be based on iRacing results unless adjusted by league officials due to penalties, protests, scoring review, or administrative correction.

Post-race penalties may be applied to the next event or to the final results of the event where the infraction occurred, depending on the circumstances.

8.0 Communications, Broadcast, and Race Procedures

8.1 Voice Chat

All drivers are required to have voice chat enabled during official Summit GT Racing Series sessions so they can hear race control, admin instructions, and any necessary league communication.

Drivers are not required to own or use a microphone. However, all drivers must be able to hear official communication when it is given.

Failure to monitor voice chat may not be accepted as an excuse for missing race control instructions, admin calls, or event-specific direction.

8.2 Discord

Drivers are expected to be present in the Summit GT Discord and monitor league announcements.

Drivers may be required to use Discord for attendance, event information, protest submissions, appeal submissions, interviews, or league updates.

8.3 Attendance

Drivers should use the approved Discord attendance system when required.

Drivers may be asked to mark themselves as:

• Accepted
• Declined
• Tentative

Drivers are expected to update their attendance status as early as possible if they are unable to participate.

Repeated failure to attend after signing up may result in review by league officials.

8.4 Driver Numbers

Driver numbers will be assigned at signup or approved by league officials.

Drivers are expected to use their approved number during official Summit GT Racing Series events unless otherwise approved.

8.5 Broadcast and Interviews

Summit GT Racing Series events may be broadcast by an approved broadcast partner.

Drivers are expected to conduct themselves professionally during broadcasted events.

Top finishing drivers may be asked to participate in post-race interviews. Drivers must be available in the required Discord voice channel to be eligible for interviews.

Generally, the top three eligible finishers may be selected for interviews unless otherwise determined by league officials or the broadcast team.

8.6 Blue Flags and Lapped Traffic

Blue flags are considered advisory unless otherwise enforced by iRacing or race control.

Drivers being shown the blue flag are not required to immediately pull off the racing line or surrender the position. However, lapped traffic is expected to race respectfully, hold a predictable line, and avoid unnecessarily delaying lead-lap cars.

Lead-lap drivers are also expected to show patience when approaching lapped traffic. Divebombs, forced moves, or low-percentage passes around lapped cars may be reviewed if contact or avoidable incidents occur.

Both drivers share responsibility in blue flag situations. Incidents involving lapped traffic may be reviewed closely by league officials.

8.7 Full-Course Cautions

Full-course cautions will be enabled for official Summit GT Racing Series events unless otherwise stated in the event announcement.

Drivers must follow all iRacing caution procedures, pace car instructions, race control directions, and any event-specific caution rules provided before the race.

During full-course cautions, drivers are expected to maintain control, hold proper pacing speed, avoid unnecessary weaving or brake checking, and remain aware of surrounding traffic.

Passing under caution is not permitted unless directed by iRacing, race control, or required for accident avoidance.

Any driver who causes contact, fails to maintain caution pace, jumps the restart, passes improperly, or creates an unsafe situation under caution may be subject to penalty or further review.

8.8 Netcode Incidents

Netcode refers to situations where iRacing registers or predicts contact between cars even when visible contact may appear limited or absent on replay.

League officials may review netcode-related incidents to determine whether the contact was clearly caused by a false prediction or whether the drivers involved were racing in a manner that created an avoidable risk.

If the contact appears to be a true netcode error with no reasonable action available to either driver, a penalty may not be issued.

If the incident appears to result from overly aggressive positioning, lack of racing room, poor connection awareness, or avoidable proximity, league officials may still issue a penalty.

Claiming "netcode" does not automatically remove driver responsibility. Drivers are expected to leave reasonable racing room and understand that connection quality, latency, and iRacing collision prediction can affect close racing.

8.9 Clearing Black Flags

For consistency across all Summit GT Racing Series events, black flags will not be cleared by race admins, officials, or race control during official sessions.

Drivers are responsible for serving any black flag penalties issued by iRacing. This includes penalties for race starts, pit road violations, unsafe pit entry or exit, passing under yellow, course cutting, or any other violation enforced by the sim.

League officials may review black flag situations after the race if needed, but black flags will not be removed during the event.

This rule is intended to ensure that all drivers are treated equally and that race control decisions remain consistent throughout the field.

8.10 Custom Paints, Liveries, Suits, and Helmets

All drivers are responsible for ensuring their custom paints, liveries, decal layers, suits, and helmets comply with iRacing rules, policies, and terms of service.

Drivers should review and follow the official iRacing Custom Paint Policy and iRacing Terms of Use.

Custom paints may not include content that is offensive, obscene, defamatory, threatening, abusive, hateful, racist, pornographic, illegal, harassing, or otherwise inappropriate for league competition or broadcast.

Drivers may not use logos, brands, or intellectual property they do not have permission to use. This includes sponsor logos, company marks, race team branding, parody logos, or designs based on protected intellectual property.

Paint schemes may not display logos or branding that directly compete with iRacing, the vehicle manufacturer, or any restricted category prohibited by iRacing policy.

Any paint already available through the official iRacing paint shop or included on an iRacing stock livery may be used.

Summit GT Racing Series reserves the right to require a driver to change or remove a paint, livery, suit, or helmet if league officials determine it violates iRacing policy, league standards, broadcast expectations, or general professionalism.

The responsibility for using an approved and compliant paint belongs solely to the driver.

8.11 League Banner and Number Plate Requirement

All Summit GT Racing Series drivers are required to display the official league banner and number plate on their car.

The required banner and number plate files can be found in the Series Decals channel within the Summit GT Discord.

This requirement is in place to provide a consistent visual aid for drivers, admins, officials, and broadcast partners when identifying cars on track. Proper placement of league decals also helps improve the overall presentation and professionalism of the series.

Drivers who need assistance applying the league banner or number plate should contact any Summit GT Racing Series admin for help.

Drivers must have the required league banner and number plate applied within two weeks of being accepted into the league.

Failure to comply with this requirement will result in race disqualification until the issue is corrected and the required league banner and number plate are properly applied.

9.0 Protests, Reviews, and Penalty Guidelines

9.1 Protest Procedure

If a driver believes they were directly affected by a rule violation or avoidable incident, the driver may file a protest for league review. A team owner may also file a protest on behalf of their driver.

Only drivers directly involved in the incident, or their team owner, may submit a protest. Drivers not directly involved in the incident should not file protests on behalf of others unless requested by race officials.

Drivers may only protest incidents that directly involve themselves or an immediate teammate. Drivers may not submit protests for incidents that do not involve them or their team, regardless of whether the incident was observed during the race or found during post-race review. This rule is in place to prevent drivers from reviewing the entire race in search of incidents to protest and to keep the protest process focused on situations that directly affect the protesting party.

Protests may be submitted during the event when race control is available, or after the race if the incident was not reviewed live, occurred late in the race, or requires additional replay review.

9.1.1 Post-Race Protests

Post-race protests must be submitted through the approved Summit GT protest process or designated league communication channel.

All protests must be submitted within 24 hours of the conclusion of the race. Protests submitted after the 24-hour window will not be accepted or reviewed, regardless of the nature of the incident.

Drivers are encouraged to provide the following information when submitting a protest:

• Race event and track
• Lap number or approximate time of incident
• Cars involved
• Brief description of the incident
• Replay file, clip, or timestamp if available

A replay file is helpful but may not always be required. League officials may request additional information before making a final decision.

9.1.2 Protest Review

League officials will review submitted protests and determine whether a rules violation occurred.

A single incident may include more than one violation. Penalties may be adjusted based on severity, impact on other drivers, prior history, and whether the action appeared accidental, careless, reckless, or intentional.

Not every racing incident will result in a penalty. Officials may determine that an incident was a racing incident, netcode-related, unavoidable, or not severe enough to warrant further action.

9.2 Protestable Infractions

The following are examples of infractions that may be protested or reviewed by Summit GT officials.

9.2.1 Unsafe Pace, Minimum Speed, or Driving Quality

All drivers are expected to maintain a reasonable pace and demonstrate safe driving standards during official sessions.

Drivers may be penalized for operating at an unsafe speed, driving erratically, failing to maintain predictable control, or continuing to race a damaged car that cannot safely remain at speed.

If a car is too damaged to maintain safe pace, regain position, or continue without creating a hazard, the driver is expected to safely move off the racing surface and tow.

Possible penalties may include a warning, post-race penalty, probation, or removal from the event depending on severity.

9.2.2 Missing the Drivers Meeting

If a drivers meeting is held, all drivers are expected to attend and listen to the full briefing.

Drivers may not continue practicing, ignore instructions, or fail to monitor the briefing. Race-specific procedures announced in the drivers meeting may supersede standard rulebook procedures for that event.

Failure to attend or follow the drivers meeting may result in a warning or penalty.

9.2.3 No-Show or Failure to Withdraw

Drivers who enter an event are expected to attend or properly withdraw if they are unable to race.

Drivers should notify league officials as early as possible if they cannot attend. Repeated no-shows may affect future eligibility, starting priority, or league standing.

A driver who repeatedly signs up and fails to appear may be subject to review by league officials.

9.2.4 Abuse of Track Limits

Drivers are expected to remain within the accepted racing surface and follow iRacing track limits.

Although iRacing may issue its own off-track or slowdown penalties, league officials may also review situations where a driver gains time, gains a position, avoids normal racing conditions, or creates an unfair advantage by leaving the racing surface.

Examples may include repeatedly exceeding track limits, using runoff to carry extra speed, cutting corners, or using non-racing surfaces to complete a pass.

Possible penalties may include a warning, time penalty, points penalty, or additional review for repeated behavior.

9.2.5 Start and Restart Violations

Drivers must follow all start and restart procedures given by iRacing, race control, league admins, and the event briefing.

On all starts and restarts, drivers are required to maintain their assigned pacing line and remain in position until they have crossed the start/finish line. Drivers may not pull out of line, overlap another car, jump the start, or attempt to pass before crossing the start/finish line.

The only exceptions to this rule are:

• Accident avoidance
• A car ahead fails to accelerate
• A car ahead has an obvious issue, spins, checks up, or creates an unsafe condition
• iRacing or race control directs otherwise

Drivers are expected to use good judgment and remain predictable. If a driver leaves their pacing line before the start/finish line, they must only do so to avoid an incident or respond to a clear issue with the car ahead.

Any driver who gains an advantage, causes contact, forces another driver to take evasive action, or creates an unsafe situation during a start or restart may be subject to penalty.

Start and restart violations may result in a warning, End-of-Line penalty, lap hold, points penalty, or further review depending on the severity of the incident.

9.2.6 Black Flag-Related Incidents

Summit GT officials will not clear black flags issued by iRacing during official sessions.

However, if a driver receives a black flag because another driver failed to follow race procedures, created an unsafe situation, or violated league rules, the responsible driver may be subject to protest and review.

The black flag itself will remain the responsibility of the driver who received it, but the conduct that caused or contributed to the situation may still be penalized after review.

9.2.7 Voice or Text Chat Abuse

All voice and text communication must remain respectful and controlled during league events.

Profanity directed at another driver, personal attacks, harassment, threats, abusive language, or excessive arguing may result in a penalty.

Drivers are also expected to keep race communications clear during green-flag racing. Ongoing discussion, complaints, or unrelated conversation should be kept to private channels.

Possible penalties may include a warning, chat restriction, points penalty, probation, suspension, or removal from the league depending on severity.

9.2.8 Social Media and Discord Conduct

Drivers are expected to represent the Summit GT Racing Series in a respectful manner on Discord, iRacing forums, social media, broadcast chats, and other public platforms.

Conduct that damages the league, attacks other members, harasses drivers, creates unnecessary drama, or reflects poorly on the series may be reviewed by league officials.

This includes posts, comments, messages, screenshots, videos, or public accusations related to league events or members.

Possible penalties may include a warning, probation, suspension, or removal from the league depending on severity.

9.2.9 Race-Specific Rules

Some events may include race-specific rules or procedures that are announced before the event or during the drivers meeting.

Race-specific rules may include pit procedures, start procedures, restart rules, tire limits, fuel settings, caution procedures, track limits, or special event instructions.

When race-specific rules are announced, they take priority over the standard rulebook for that event.

Failure to follow race-specific instructions may result in a warning, penalty, or additional review.

9.3 Racecraft Infractions

Racecraft infractions are on-track actions involving racing conduct, car control, avoidable contact, or driver decision-making.

All drivers are expected to race with respect, awareness, and reasonable judgment. Aggressive racing is allowed, but reckless or avoidable contact may be penalized.

9.3.1 Blocking

Drivers may defend their position, but blocking is not permitted.

Blocking includes making more than one defensive move, reacting to the attacking driver's movement, or moving late in response to an attempted pass.

Once an attacking driver has established significant overlap, the defending driver must leave racing room. Significant overlap means the front axle of the overtaking car is alongside the rear axle of the car being overtaken.

Officials may review blocking based on timing, car positioning, overlap, and whether the move created unnecessary risk or contact.

9.3.2 Unsafe Rejoin or Unsafe Track Entry

Drivers must rejoin the racing surface safely after leaving the track, spinning, stopping, or exiting pit road.

A driver who is off-track, stopped, damaged, or facing the wrong direction must wait for a safe opportunity before returning to the racing line.

Unsafe rejoins that cause contact, force other drivers to take evasive action, or create a hazard may result in a penalty.

Drivers approaching an incident are also expected to use caution and avoid making the situation worse.

9.3.3 Failure to Maintain Control

Drivers are expected to maintain reasonable control of their car at all times.

Mistakes can happen, but a driver may be penalized if a loss of control directly and significantly affects another competitor.

Once a driver loses control, spins, or becomes unstable, the driver is expected to hold the brakes and remain as predictable as possible until the car comes to a stop or the situation is under control.

Failing to hold the brakes, rolling back across the racing surface, or creating additional contact after a loss of control may result in a harsher penalty.

Repeated solo spins, repeated avoidable incidents, or repeated loss-of-control situations may result in further review by league officials.

9.3.4 Major Contact

Major contact includes car-to-car contact that causes a driver to lose control, spin, leave the racing surface, suffer significant damage, or lose substantial track position.

This may include contact caused by braking mistakes, accelerating too early, failing to account for closing speed, checking up unpredictably, missing a braking zone, or forcing a move without sufficient racing room.

League officials will review the actions of all involved drivers before assigning responsibility.

Possible penalties may include a warning, time penalty, points penalty, probation, suspension, or removal from the league depending on severity and history.

9.3.5 Late-Race or Race-Finishing Infractions

Incidents that affect the finishing order near the end of a race may be reviewed more closely due to their impact on the final results.

A late-race infraction may include avoidable contact, blocking, unsafe rejoin, retaliation, or any rule violation that directly changes the finishing order in the closing laps.

If a driver gains or preserves a finishing position through a violation, league officials may adjust the finishing result, issue a points penalty, move the driver behind the affected competitor, or apply additional discipline.

The severity of the penalty will depend on the nature of the incident, the impact on the final results, and whether the action appeared accidental, reckless, or intentional.

9.3.6 Weaving / Tire Warming

Drivers who cause contact, force another driver to take evasive action, or create an unsafe situation while weaving may be subject to a warning, penalty, or further review depending on the severity of the incident.

If a driver loses control while weaving and causes an incident involving themselves or another driver, the incident may be reviewed under Rule 9.3.3 -- Failure to Maintain Control.

Drivers must remain aware of surrounding cars and are responsible for maintaining control of their vehicle while weaving. Tire warming does not give a driver permission to make sudden, unpredictable, or excessive movements that create unnecessary risk.

Drivers are permitted to weave during pace laps or caution laps for the purpose of warming tires, provided it is done in a safe and controlled manner.

9.3.7 Cool Down Lap Conduct

Upon taking the checkered flag, drivers are expected to complete the cool down lap in a safe and controlled manner. Drivers who are unable to complete the full cool down lap must pull off the racing surface at the first safe opportunity, at minimum after the first corner, and bring their car to a stop in a safe location off the racing surface.

Drivers must not crash, make avoidable contact, or drive in a reckless manner during the cool down lap. This includes intentional contact, celebrations that endanger other drivers, or any other behavior unbecoming of the series. The cool down lap remains an active on-track session and all drivers remain responsible for their conduct until they have exited the racing surface.

The Summit GT Racing Series is a broadcast-quality production. Reckless or embarrassing behavior during the cool down lap reflects poorly on all participants and the series as a whole. Drivers found to have caused avoidable incidents or behaved inappropriately during the cool down lap may be subject to a warning, points deduction, or further disciplinary action.

9.4 Major Offenses

Major offenses are serious violations that may result in suspension, removal from the event, loss of league eligibility, or removal from the Summit GT Racing Series.

These situations will not be decided lightly and will generally be reviewed after the race by league officials. Accusations of major offenses should only be made when the conduct is severe and supported by clear evidence.

9.4.1 Retaliation

Summit GT Racing Series has zero tolerance for retaliation.

Drivers may not intentionally make contact, wreck another driver, brake-check, block with intent to harm, wait for another car, or otherwise retaliate on track.

Retaliation may result in suspension or removal from the league.

9.4.2 Intentional or Egregious Conduct

Any action determined to be intentional, reckless, malicious, or extremely unsafe may result in major discipline.

This includes intentionally causing contact, deliberately interfering with another driver's race, creating a dangerous situation, or committing an action that league officials determine is damaging to the integrity of the series.

Penalties for intentional or egregious conduct will be determined by league officials based on the severity of the situation.

9.4.3 Multi-Division and Multi-Class Interaction

Drivers are expected to exercise increased awareness, patience, and judgment when racing near drivers from another division or car class. This includes AM, PRO/AM, and PRO division interaction, as well as GT3 and LMP2 class interaction.

The Summit GT Racing Series includes multiple driver divisions and may include multiple car classes on track at the same time. Drivers must understand that pace differences may exist between AM, PRO/AM, and PRO drivers, and that the LMP2 car will have a significant closing-speed advantage over GT3 cars.

LMP2 drivers are responsible for completing overtakes safely. The LMP2 car does not have automatic right-of-way simply because it is faster. LMP2 drivers must be patient, predictable, and must not force low-percentage moves on GT3 traffic, especially in braking zones, corner entry, or sections of the track where the GT3 driver has limited ability to safely adjust their line.

GT3 drivers are expected to hold a predictable racing line when being approached by an LMP2. GT3 drivers are not required to leave the racing surface or give up the normal racing line, but they must not make sudden, reactionary, or defensive moves against faster class traffic when the cars are not directly racing for the same class position.

AM drivers, PRO/AM drivers, and PRO drivers remain responsible for maintaining awareness of surrounding traffic regardless of division classification. Participation in the PRO division or the LMP2 class does not grant automatic right-of-way, and participation in the AM division does not excuse avoidable incidents caused by lack of situational awareness.

Drivers who cause contact, force another driver to take evasive action, or create an unsafe situation while overtaking, defending against, or interacting with a driver from another division or car class may be subject to penalty. Incidents involving LMP2 and GT3 interaction may be reviewed closely due to the closing speeds involved and the potential impact on multiple championship battles.

If a driver is found responsible for an avoidable incident involving another division or class, League Administration may apply additional penalties beyond the standard post-race penalty schedule when the incident significantly affects another driver’s race, class battle, championship position, or the overall safety of the event.

All drivers are expected to race with a heightened level of care when interacting with drivers from another division or car class. Failure to do so may result in post-race time penalties, points deductions, probation, suspension, or other disciplinary action as deemed appropriate by League Administration.

9.4.4 Race Manipulation

Race manipulation is strictly prohibited and is considered one of the most serious violations within the Summit GT Racing Series. The integrity of every race result must be preserved at all times.

Drivers may not deliberately alter their pace, stop on track, slow without cause, or take any other action intended to artificially change the finishing position of themselves or any other driver. Every driver is expected to race at their maximum competitive effort for the full duration of the event.

Examples of race manipulation include, but are not limited to:

• Deliberately slowing or stopping on track to gift a position to another driver
• Reducing pace significantly without a mechanical reason in order to alter championship standings
• Allowing another driver to pass without racing for position when no mechanical issue is present
• Coordinating with another driver or team to predetermine a race outcome or finishing order
• Blocking or impeding another driver in a manner designed to benefit a third driver rather than defend a legitimate position

Race manipulation undermines the integrity of the championship and is an offense against every driver competing honestly in the series.

Any driver found to have manipulated a race result may be subject to disqualification from the event, loss of championship points, suspension, or permanent removal from the Summit GT Racing Series depending on the severity and intent of the violation.

9.5 Driver and Admin Conduct Policy

The Summit GT Racing Series is built on a foundation of respect, sportsmanship, and community. Every driver, admin, and official associated with this series is expected to uphold these values at all times -- on track, in the simulator, in Discord, on broadcast, and in any public setting where this league may be discussed or represented.

This policy applies to all drivers, administrators, officials, and any individual affiliated with or representing the Summit GT Racing Series.

9.5.1 In-Sim Voice Channels

All communication in iRacing voice channels during league events must remain professional and respectful. Drivers are competing in a broadcast-quality environment and must conduct themselves accordingly at all times while a session is active.

The following are strictly prohibited in in-sim voice channels:

• Bullying, harassment, or intimidation of any driver, admin, or official
• Belittling, mocking, or demeaning comments directed at any individual
• Racist, discriminatory, or derogatory language of any kind
• Threatening, abusive, or hostile language toward any person
• Excessive profanity, particularly directed at others

9.5.2 Discord Channels

All Summit GT Discord channels -- including general, race discussion, protest, media, and any other official or unofficial channels within the server -- are subject to this conduct policy. This includes both text and voice channels within the Discord server.

The following are strictly prohibited in all Discord channels:

• Bullying, harassment, or targeted attacks on any member
• Racist, discriminatory, or derogatory language or imagery
• Belittling, mocking, or demeaning comments directed at any driver, admin, or official
• Public arguments, personal disputes, or drama that disrupts the community
• Threats, hostile language, or intimidation of any kind
• Spamming, trolling, or intentionally disruptive behavior

9.5.3 Broadcast and Interview Conduct

The Summit GT Racing Series operates as a broadcast-quality production. Any driver, admin, or official who appears on stream, participates in a pre- or post-race interview, or is otherwise featured on any league broadcast represents the entire organization.

During any broadcast or interview, all individuals are expected to:

• Conduct themselves in a professional and respectful manner
• Avoid any language, gestures, or behavior that would reflect poorly on the series
• Avoid making derogatory, racist, or discriminatory remarks of any kind
• Refrain from publicly attacking, belittling, or calling out other drivers or officials
• Represent the Summit GT Racing Series with pride and sportsmanship

Conduct that embarrasses the series, its members, or its broadcast partners during a live or recorded stream is subject to review and disciplinary action regardless of whether it occurred during or after the race.

9.5.4 External Conduct -- Outside the League Discord

Drivers and admins are ambassadors of the Summit GT Racing Series at all times, including outside of the official league Discord. The way members discuss this league in other Discord servers, on social media, in iRacing forums, on streaming platforms, or in any other public setting reflects directly on the organization.

The following are prohibited when discussing the Summit GT Racing Series in any external setting:

• Publicly disparaging, mocking, or attacking the league, its admins, officials, or fellow drivers
• Sharing private league communications, protest details, penalty decisions, or internal matters in public forums without authorization
• Making false, misleading, or defamatory statements about any member, admin, or official of the series
• Using other platforms to harass, pressure, or retaliate against another member over league-related matters
• Any conduct that could damage the reputation of the Summit GT Racing Series or its members in the broader sim racing community

Members are encouraged to resolve issues through the proper league channels -- protest submissions, direct admin communication, or the official appeal process. Taking disputes public is never the appropriate course of action and will be treated as a conduct violation.

9.5.5 Admin Conduct

Admins and officials of the Summit GT Racing Series are held to the same conduct standards as drivers -- and in many cases, a higher one. Admins represent the league in an official capacity and must lead by example in every setting.

9.5.6 Penalties for Conduct Violations

Conduct violations under Section 9.5 may result in the following penalties depending on severity and frequency:

• Formal warning
• Points deduction
• Muting or restriction from Discord channels
• Probation
• Suspension from one or more events
• Permanent removal from the Summit GT Racing Series

Racist, discriminatory, or threatening behavior is considered a zero-tolerance violation and may result in immediate suspension or permanent removal from the league without prior warning.

10.0 Penalty Review and Fault Determination

10.1 Determining Fault for Incidents

When reviewing an incident, the first step for Summit GT Racing Series officials is to determine whether any driver involved was at fault, and if so, to what degree.

Fault may be assigned to one driver, multiple drivers, or no driver depending on the facts of the incident. Not every contact situation will result in a penalty. Some incidents may be ruled as racing incidents, unavoidable contact, netcode-related contact, or situations where no single driver is primarily responsible.

When two or more cars are involved in an incident, league officials will review the actions of each driver individually. The review may include the buildup to the incident, the moment of contact, the actions taken by each driver, and the result of the contact.

Officials will look for driving that falls outside of fair, reasonable, and acceptable racing standards. This may include excessive aggression, avoidable contact, poor judgment, lack of control, failure to leave racing room, unsafe rejoin, reactionary movement, or any action that contributed to the incident.

Netcode may be considered during review, but it will not automatically excuse driver responsibility. Drivers are expected to understand that close racing in iRacing may be affected by connection quality, latency, and collision prediction. Drivers are expected to leave reasonable room to reduce the chance of netcode contact.

If the review shows that contact was clearly caused by a false or heavily exaggerated netcode event, and no reasonable driver action would have prevented it, the incident may be ruled as a racing incident. However, if a driver placed themselves or another car in an unnecessarily tight or risky position, officials may still assign fault even if netcode contributed to the contact.

When determining fault, officials may consider, but are not limited to, the following:

• Position of each car before, during, and after the incident
• Speed of each car
• Braking point and throttle application
• Steering input or lack of input
• Corner entry angle
• Vehicle trajectory
• Track position
• Racing room given or not given
• Whether overlap was established
• Likelihood of the move being completed safely
• Track layout and available racing surface
• Driver awareness and visibility
• Reaction time
• Level of aggression
• Defensive or offensive driving tactics
• Location of contact on each car
• Location of the incident relative to other traffic
• Whether the incident caused damage, loss of control, loss of position, or race-ending consequences
• Whether the incident created additional risk for other drivers

After reviewing the available evidence, officials may determine each driver's level of responsibility. Penalties, if issued, will be based on the assigned fault, severity of the incident, effect on other drivers, driver history, and whether the action appeared accidental, careless, reckless, or intentional.

Summit GT officials reserve the right to issue no penalty, a warning, time penalty, points penalty, probation, suspension, or removal from the series depending on the circumstances.

11.0 Post-Race Penalty Schedule

11.1 Penalty Philosophy

The Summit GT Racing Series will use a post-race penalty schedule for most reviewed incidents. The intent is to apply penalties to the race in which the violation occurred whenever possible, allowing drivers to move into the next event without routine carryover penalties.

Next-race penalties such as End-of-Line penalties, drive-through penalties, 1-lap holds, or 2-lap holds should not be the standard penalty for normal racing incidents. These penalties are reserved for repeat behavior, major safety concerns, intentional conduct, retaliation, or cases where a post-race time or points penalty is not sufficient.

Once League Administration determines that a driver is primarily at fault, the default penalty will be based on the measurable result of the incident. Officials should use the table below as the standard penalty guide.

11.2 Standard Post-Race Time Penalty Schedule

The following penalties apply when a driver is found primarily at fault for the listed action or result.

11.3 Automatic Penalty Modifiers

The following modifiers will be applied to the default penalty when applicable.

Penalty reductions may not reduce a penalty below a warning. Modifiers may be combined when more than one applies.

11.4 Points Penalties When Time Penalties Are Not Sufficient

Post-race time penalties should be used whenever they reasonably affect the race result. If a time penalty would have no practical effect, League Administration may convert the penalty to a points penalty.

A points penalty may be used when:

• The at-fault driver finished last or did not finish
• The at-fault driver was already disqualified
• The violation involved conduct rather than on-track race result
• The violation occurred after the checkered flag or during the cool down lap
• A time penalty does not fairly account for the damage caused
• The incident affected championship integrity, race manipulation, or repeated behavior

When converting a time penalty to a points penalty, the following schedule should be used:

League Administration may also remove bonus points, adjust finishing position, or remove event points when the violation directly affected the integrity of the result.

11.5 Probation and Suspension Triggers

The following repeat-offense triggers are designed to identify patterns of unsafe or careless driving.

A driver placed on probation may be subject to stronger penalties for additional at-fault incidents during the probation period.

11.6 Next-Race Penalties and Lap Holds

Next-race penalties are not the standard penalty for normal racing incidents. They may only be used when League Administration determines that a post-race time or points penalty is not enough to address the conduct.

Next-race penalties may be used for:

• Repeated avoidable contact
• Repeated unsafe rejoins
• Repeated start or restart violations
• A driver on probation committing another at-fault incident
• Major safety concerns
• Retaliation or intentional conduct
• Failure to follow race control or admin instructions
• Any situation where allowing the driver to start the next race normally would create an unnecessary risk to the field

If a 1-lap hold is issued, the driver may qualify and start from their earned qualifying position unless League Administration specifically states otherwise. At the end of lap 1, the driver must enter pit lane to serve the hold. The driver must stop in the designated hold location and may not receive car service while serving the hold. The driver must remain stopped until the race leader has crossed the start/finish line under green flag conditions once. The driver may then proceed and rejoin the race normally.

If a 2-lap hold is issued, the same procedure applies, except the driver must remain stopped until the race leader has crossed the start/finish line under green flag conditions twice.

Failure to properly serve a lap hold may result in additional points penalties, suspension, or further administrative review.

11.7 Unlisted Situations

No penalty schedule can list every possible situation. If an incident or violation is not specifically listed, League Administration should apply the closest matching rule or penalty from this schedule.

When using the closest matching penalty, officials should document the reason for the decision and apply the rule consistently with similar incidents in future events.

League Administration retains final authority to issue a warning, time penalty, points penalty, disqualification, probation, lap hold, race suspension, or league removal when necessary to protect fair competition and the integrity of the Summit GT Racing Series.

12.0 Appeals

12.1 Appeal Process

If a driver believes they were incorrectly penalized, they may file an appeal for league review.

Appeals may be submitted for both in-race penalties and post-race penalties. The purpose of an appeal is to allow league officials to review additional evidence, clarify the circumstances, and determine whether the original penalty should stand, be reduced, be removed, or be modified.

An appeal should only be submitted when the driver believes there is a legitimate reason the penalty was issued incorrectly. Appeals should not be used simply because a driver disagrees with race control or is unhappy with the outcome.

12.2 In-Race Appeals

If a driver receives an in-race penalty and wishes to appeal, they must notify race control as soon as possible.

Race control may choose to allow the penalty to stand during the race and review it afterward, or may choose to defer enforcement until after the race if the situation requires additional review.

If an in-race penalty is deferred and later upheld after review, league officials may apply the original penalty or issue an adjusted post-race penalty based on the circumstances.

If the appeal is denied and officials determine the appeal was unnecessary, frivolous, or made without reasonable basis, the penalty may be increased.

12.3 Post-Race Appeals

Drivers may appeal a post-race penalty after receiving official notice of the penalty.

Post-race appeals must be submitted through the approved Summit GT appeal process or designated league communication channel within 24 hours of the penalty being issued.

Appeals submitted after the 24-hour window may not be reviewed unless league officials determine there is a valid reason for the late submission.

12.4 Appeal Submission Requirements

Appeals should include as much relevant information as possible, including:

• Race event and track
• Penalty being appealed
• Rule or infraction cited, if provided
• Driver or drivers involved
• Lap number or approximate time of the incident
• Brief explanation of why the penalty should be reviewed
• Replay file, video clip, screenshot, or other supporting evidence if available

A replay file is strongly recommended but may not always be required. League officials may request additional information before making a final decision.

12.5 Appeal Review Timeline

League officials will acknowledge receipt of the appeal when practical.

The goal is to issue an appeal decision within 72 hours of receiving the appeal. Some reviews may take longer if additional evidence, admin discussion, or driver statements are needed.

Once a decision has been made, league officials will notify the driver of the result.

12.6 Appeal Outcomes

After reviewing an appeal, league officials may choose to:

• Uphold the original penalty
• Reduce the penalty
• Remove the penalty
• Modify the penalty
• Increase the penalty if the appeal is found to be unsupported, misleading, or frivolous

Appeal decisions are considered final unless league officials determine that new evidence warrants further review.

12.7 Final Authority

Summit GT Racing Series officials have final authority over all appeal decisions.

Drivers are expected to remain respectful throughout the appeal process. Arguing, personal attacks, public drama, or harassment related to an appeal may result in additional discipline.

13.0 Final Authority and Special Circumstances

Summit GT Racing Series officials reserve the right to modify, clarify, or adjust event rules and procedures when necessary to address special circumstances, technical issues, unforeseen situations, event format changes, or matters affecting competitive fairness.

Race-specific procedures may be issued for individual events and may override portions of the standard rulebook for that event only. Any race-specific rule changes should be communicated to drivers prior to the race whenever possible.

League officials have final authority on race administration, rule interpretation, penalties, appeals, scoring matters, and event procedures.

Decisions made by Summit GT Racing Series officials are final unless officials determine that additional review is necessary due to new evidence, administrative error, or extraordinary circumstances.

14.0 Driver Acknowledgment

By participating in the Summit GT Racing Series, each driver acknowledges that they have read, understand, and agree to follow this rulebook, iRacing rules, event announcements, and any instructions issued by league officials.

Drivers also acknowledge that league officials have the authority to review incidents, issue penalties, update procedures, and make final decisions in the best interest of the series.

Participation in the series confirms acceptance of these rules and expectations.