GR Aetherwing | Official Handbook
GR AETHERWING // OPS
← Return to Base
DOCUMENT ID: GR-AW-2026-HB

Driver Standards & Team Handbook

The operational guidelines for GR Aetherwing eMotorsports. All contracted drivers—across iRacing and Roblox RoRacing—are expected to adhere to these protocols during the 2026 Season.

01. Organization & Hierarchy

"One Team, One Mission"
1.1 Team Identity

GR Aetherwing eMotorsports is a competitive simulation racing organization. We have transitioned from the "BellSouth" era to the "GR Aetherwing" era, operating as a factory-supported partner of Toyota Gazoo Racing. We compete for Constructor Championships, not just individual wins.

1.2 Chain of Command
  • Team Principal (Wispy): Final authority on roster decisions, strategy, and disputes.
  • Lead Engineers/Designers: Responsible for car setups and official liveries.
  • Drivers: Responsible for execution on track.
1.3 Respect for Leadership

Disputes regarding strategy or setups should be handled in private channels, not public voice chat. Public undermining of team leadership is a conduct violation.

1.4 Recruitment Path

Drivers rarely sign directly to the GR Aetherwing Primary Roster. Talent is scouted and filtered through our Driver Development Program (See Section 8).

1.5 Dispute Resolution

If a driver disagrees with a penalty or team decision, they may file a formal appeal to the Team Principal via DM within 24 hours. Arguing in general chat channels is prohibited.

02. Branding & Livery

"Look Elite, Feel Elite"
2.1 Official Assets

All GR Aetherwing entries must utilize the official 2026 vector assets (TGR Logos, Number Fonts, Sponsors). Unauthorized modification of the "Feather" emblem or sponsor placement is prohibited.

2.2 Third-Party Paint Schemes

Drivers wishing to run a "special event" paint scheme must submit the file to the Design Team for approval 48 hours before the event to ensure sponsor obligations are met.

2.3 Competitor Branding

To protect team partnerships, drivers must not display logos of direct competitors to our current sponsors (e.g., competing retail brands or non-Toyota manufacturers where applicable) on their car or suit during official events.

2.4 Suit & Helmet Standards

Drivers are encouraged to run the official team suit and helmet files to maximize brand visibility during broadcast interviews and victory lane celebrations.

2.5 Screenshot Guidelines

When sharing race results or car photos in public channels, use high-quality screenshots. "Phone photos" of monitors are unprofessional and should not be used for social media promotion.

03. Operations & Availability

"Attendance is Currency"
3.1 Championship Commitment

GR Aetherwing has fully transitioned into operational status. Drivers accepting a seat for a Championship Series are committing to the full schedule. "Cherry-picking" races is not permitted for points-paying entries.

3.2 Absence Protocol

If a driver cannot attend a scheduled league race, they must notify management via the Discord at least 3 hours in advance.

3.3 Communication

All drivers must be in the team Discord voice channel at least 15 minutes prior to qualifying for the pre-race briefing. "Radio silence" during a race is discouraged; communication regarding pit cycles is mandatory.

3.4 Punctuality

The car must be on the grid on time. Missing the grid or starting from pit lane due to poor time management forfeits team points and will be reviewed as a performance infraction.

3.5 Post-Race Debrief

Following the conclusion of a race, drivers are expected to remain in voice chat for a brief "cool down" and debrief to discuss strategy hits and misses, regardless of the race result.

04. On-Track Conduct

"The Duty of Preservation"
4.1 Situational Awareness

Speed is secondary to intelligence. Drivers are required to demonstrate situational awareness. This includes the "Duty to Lift" during wreck avoidance. Telemetry data showing 100% throttle application through an active crash scene is grounds for immediate suspension or contract termination.

4.2 The "Badge" Rule

Your conduct follows you. Whether you are driving the GR Aetherwing #28, a rental seat for another team, or a public lobby truck, you are an ambassador of this brand. Reckless driving in any event is a liability to our sponsors and partners.

4.3 Data Accountability

GR Aetherwing operates on data, not excuses. All incidents involving contact will be reviewed via replay and telemetry. If the data shows negligence (late braking, no lift, unsafe rejoins), the driver will be held accountable regardless of their intent.

4.4 Safe Rejoins

If a driver goes off-track or spins, they must hold their brakes and wait for a clear gap before re-entering the racing surface. An "unsafe rejoin" that collects another car is considered a Major Infraction.

4.5 Blue Flag Courtesy

While we race to the end, lapped cars must respect leaders. Do not fight the leaders excessively if you are multiple laps down. Facilitate a clean pass to protect the team's reputation.

05. Media & OpSec

"Protect the House"
5.1 Social Conduct

Arguments with other teams or drivers on public platforms (Twitter/X, Reddit, League Discords) are prohibited. "If you type it, you own it." Brand damage via social media is a punishable offense.

5.2 Operational Security (OpSec)

Leaking internal team strategies, setup files, telemetry data, or private Discord screenshots is a breach of contract and results in an immediate ban and blacklist.

5.3 Sponsor Protection

Drivers shall not make disparaging remarks about team partners (e.g., Kmart, PetSmart, Toyota) or use competing branding that conflicts with team exclusivity agreements during official events.

5.4 Broadcast Interviews

If interviewed by a league broadcaster, mention the team name ("GR Aetherwing") and key partners. Avoid blaming other drivers on-air; save the frustration for the internal debrief.

5.5 Crisis Management

In the event of a major controversy, do not post statements without consulting Team Management. Silence is often better than an emotional reaction.

06. Disciplinary Process

"Fair but Firm"
6.1 The Strike System
Standard infractions follow a three-step process:
  • Strike 1: Verbal Warning & Coaching.
  • Strike 2: Race Suspension (Parked for 1 event).
  • Strike 3: Termination of Contract.
6.2 Major Infractions (Zero Tolerance)

Specific actions bypass the strike system and result in immediate termination. These include: Intentional Wrecking, Hate Speech/Slurs, Cheating/Hacking, or "Rage Quitting" an official event.

6.3 Probationary Period

New drivers, or drivers returning from a suspension, are placed on a 3-race Probationary Period. Any infraction during this time results in immediate termination.

6.4 Strike Reset

Minor strikes (Strike 1) expire after 90 days of clean driving. Major infractions remain on the driver's internal record permanently.

6.5 Voluntary Withdrawal

If a driver feels they cannot compete safely (anger, fatigue, equipment failure), they may voluntarily park their car. This mature decision will not result in disciplinary action.

07. Technical Standards

"Equipment Check"
7.1 Network Stability

Drivers are responsible for maintaining a stable internet connection. Consistently high ping or "netcode" issues that endanger other cars are grounds for being parked until the issue is resolved.

7.2 Hardware Requirements

While a Force Feedback (FFB) wheel is highly recommended for precision, it is not mandatory. Drivers using a controller/gamepad are permitted provided they can demonstrate smooth inputs and lane stability consistent with team standards.

7.3 Audio

A functioning microphone with "Push-to-Talk" enabled is required for all official sessions to ensure clear communication during races.

7.4 Software Updates

Drivers are expected to update their simulator (iRacing/Roblox), Windows, and GPU drivers before race night. Missing a race start due to an "unexpected update" is considered an unexcused absence.

7.5 Field of View (FOV)

Drivers are encouraged to calibrate their FOV correctly. Running a distorted "fish-eye" view creates blind spots and misjudged distances, contributing to avoidable contact.

7.6 Setup Transparency

GR Aetherwing operates an "Open Garage" policy. If you develop a fast setup or find speed, you are expected to share it with your teammates. "Gatekeeping" setups to beat your own teammates is prohibited.

08. Driver Development

"The Path Forward"
8.1 The Partnership

The Driver Development Program (DDP) is operated in strategic partnership with Nico Goated Motorsports. This program serves as the entry point for all new talent looking to join the GR Aetherwing Primary Roster.

8.2 What We Look For

Promotion to the main team is not awarded based on lap times alone. We evaluate:

  • Consistency: Finishing races is more valuable than one fast qualifying lap.
  • Availability: Showing up to scheduled practices and events without being chased.
  • Attitude: How you handle a loss or a wreck says more about you than how you handle a win.
8.3 Promotion Path

Drivers in the DDP who demonstrate these qualities over a full season may be offered a Reserve or Primary Seat contract with GR Aetherwing eMotorsports for the following season.

8.4 Performance Reassignment

Aetherwing maintains a "performance-based" roster. Primary drivers who consistently miss events or violate conduct policies may be reassigned to the DDP to rebuild their consistency before returning to the main team.

8.5 Mentorship Access

Drivers in the DDP receive full access to team setups and telemetry. We expect you to utilize these resources and actively seek advice from Primary Roster drivers to improve your pace.

8.6 Code of Conduct

To maintain your spot in the DDP, you must adhere to the following standards:

  • Reputation Management: We have a zero-tolerance policy for intentional wrecking, chat toxicity, or "rage quitting" in any public or league session. If you are associated with Aetherwing, you must act like a professional.
  • Proactive Communication: It is the driver's responsibility to mark their availability for events. Silence is interpreted as inactivity; drivers who fail to communicate their status for consecutive weeks may be removed.
  • Data Contribution: Mentorship is a two-way street. Drivers are expected to upload their telemetry logs after designated events to support the team’s data analysis.

09. General iRacing

"The Simulation"
9.1 Oval & Stock Car

Bump Drafting: Permitted on straightaways. Bump drafting in corners is prohibited unless the specific league rules explicitly permit it. If the league allows it, the trailing car assumes 100% fault for any resulting incident.
Apron Usage: Do not use the apron to advance position in corners unless league rules explicitly permit it (e.g., Roval layouts).

9.2 Formula & Open Wheel

Netcode Safety: Open-wheel cars are fragile. Drivers must leave slightly more margin (the "Netcode Gap") when side-by-side to prevent wheel entanglement.
Defensive Moves: STRICT adherence to the "One Move" rule. No moving under braking.

9.3 Sports Car (Road)

Multi-Class Traffic: In multi-class events (IMSA/WEC), the faster class has the responsibility to pass safely, but the slower class must be predictable. Stick to the racing line.
Track Limits: GR Aetherwing drivers respect the white line. Consistently abusing track limits looks unprofessional on broadcast.

9.4 Dirt (Oval & Road)

Slide Jobs: Must be executed cleanly. If you slide up in front of a driver, you must clear their nose. "Using up" a competitor by sliding into their door is considered a collision fault.

10. iRacing Endurance

"To Finish First, First You Must Finish"
10.1 Fair Share & Drive Time

Drivers must strictly adhere to the league's "Fair Share" rules. Failure to meet minimum drive time results in disqualification for the entire team. It is the driver's responsibility to monitor their own stint timer, not just the spotter's.

10.2 Handoff Procedures

We don't need strict radio protocol, we just need to avoid stupid mistakes.

  • Heads Up: Just let the next driver know you're pitting a lap before you come in.
  • The Swap: When you stop, hop out. The next driver needs to say "I'm in" or "Go" so we know the car is active.
  • Don't Ghost: Make sure the swap actually worked before you mute your mic and walk away.
10.3 Stint Logic

Double-stinting tires is encouraged when pace permits to save pit time. Triple-stinting is generally prohibited unless approved by the Crew Chief due to the high risk of fatigue-related errors.

10.4 Disconnect Protocol

If the active driver disconnects (hardware/internet failure), the "Reserve" or next available driver must immediately hop in the car to minimize lap loss. Do not wait for the original driver to reboot.

10.5 Sleep & Availability

For 24-hour events, drivers must be awake and in Discord voice chat 30 minutes prior to their scheduled stint. Oversleeping your shift is considered a Major Infraction (See Section 6.2).

11. Roblox RoRacing

"Roblox Operations"
11.1 Platform Integrity

Drivers must adhere to strict anti-exploit rules. Glitching through meshes or intentional lag-switching results in immediate contract termination.

11.2 Wall-Riding Protocol

General Rule: Wall-riding is prohibited by default. It may only be used for recovery (catching the pack) if the specific league rules explicitly permit it.

Zero Tolerance on Overtakes: Wall-riding to advance your position (pass a car) or defend a position is prohibited under all circumstances. Even if a league allows wall-riding, GR Aetherwing drivers shall not use the wall to pass.

11.3 Pit Stop Protocol

Drivers must adhere to all league-specific pit mandates. "Short-pitting" to exploit timing glitches or utilizing multiple pit stalls to service a single vehicle is prohibited. Drivers must service their vehicle in their assigned stall only.

11.4 Spawn Safety

Drivers must ensure the track is clear before spawning their vehicle. "Spawning in" directly in front of approaching traffic or dropping a car onto the racing line during a live session is considered a Major Safety Infraction.

11.5 Account Security

Drivers must use their primary, verified Roblox accounts for league races. Use of "alt" accounts to evade penalties or hide identity is a major infraction.

11.6 Conduct & Maturity

RoRacing environments often have younger administration. GR Aetherwing drivers will treat all admins with professional courtesy, regardless of age or perceived error. We do not participate in "server raids" or chat spamming.