Team
Handbook
Standards. Operations. Identity.
The internal standard for how Aetherwing eMotorsports operates across race weeks, team communication, visual branding, driver expectations, and league-specific programs.
Read First
This page keeps the team aligned. It is not meant to overcomplicate things — it is here so everyone knows the standard.
Represent the team like the car has your name on it.
Aetherwing eMotorsports is built around competition, branding, and team presence. Drivers are expected to race with awareness, communicate clearly, respect the series they are in, and help keep the team’s public identity sharp.
Core Standards
These standards apply everywhere: NR2003, Roblox RoRacing, iRacing, graphics, public posts, and team communication.
Communicate Early
Availability, paint needs, roster issues, league changes, and conflicts should be brought up before race day whenever possible.
Race With Respect
Hard racing is expected. Careless driving, repeated avoidable incidents, and unnecessary drama are not.
Protect the Brand
Aetherwing should look organized. Graphics, cars, posts, and public wording should feel intentional and consistent.
Own Your Results
Good race or bad race, handle it cleanly. Learn from mistakes, review what happened, and move forward without dragging the team into chaos.
Keep Assets Clean
Numbers, sponsors, logos, screenshots, and liveries should be readable, properly placed, and not rushed into looking unfinished.
Team First
Drivers, designers, coordinators, and leadership should pull in the same direction. The team looks best when everyone is aligned.
Driver Rules
Drivers are the public face of the team during race nights. These rules are meant to keep that face professional and easy to manage.
Race hard, not reckless.
Aggressive racing is fine when it is controlled. Repeated careless moves, avoidable wrecks, and retaliation hurt the whole team.
Say something before it becomes a problem.
Missed races, late arrivals, paint issues, disputes, and uncertainty should be communicated early.
Confirm your race status.
Drivers should make it clear whether they are racing, part-time, unavailable, or waiting on confirmation.
Do not start sponsor-looking drama.
Keep public arguments, league conflict, and unnecessary shots away from team-branded spaces whenever possible.
Use the correct car, number, and sponsor set.
Race entries should match the assigned number, program, and sponsor direction unless leadership approves a change.
Send results when needed.
Screenshots, finishing positions, points updates, and race notes help keep the website and graphics accurate.
Race Week Protocol
Race weeks should feel planned, not improvised. This flow keeps the team from scrambling at the last second.
Confirm lineup and availability.
Drivers should confirm whether they are racing. Leadership should know who is full-time, part-time, unavailable, or waiting on approval.
Lock the scheme direction early.
Sponsor, number, base design, and special-event ideas should be handled before race night so there is time to clean things up.
Show up ready.
Have the correct car, correct number, correct sponsor look, and any required league information ready before the event starts.
Race smart and keep comms useful.
Keep communication focused on useful information. Avoid turning the race channel into a frustration dump.
Send results and notes.
Share finishing position, points, screenshots, incidents worth reviewing, and anything needed for stats or website updates.
Fix the process, then move on.
Review mistakes without dragging them forever. The goal is better execution next race, not endless blame.
League Standards
Each program has its own car base, rhythm, and expectations. Keep wording clear and do not mix up car templates.
Kmart Cup
Runs on NR2003 using the 2008 NASCAR Car of Tomorrow template. Kmart team economy applies only here.
NRRS
Uses the NASCAR Cup Gen 7 template by BBR. Keep standings, averages, and cutline data current.
UARL D1
Uses the NASCAR Cup Gen 7 template by BBR. Keep driver numbers and entry status updated.
GRA D2
Uses the NASCAR O’Reilly Auto Parts Series template by BBR. Track part-time entries clearly.
GamerSupps
Uses the NASCAR Cup Gen 6 MENCS19 template. Race day is Wednesday for current schedule wording.
Brand Rules
The team should feel consistent whether it appears on the website, a car, a race graphic, or a sponsor announcement.
Website Style
The site uses a sharp editorial system: black/dark gray backgrounds, red and gold accents, heavy typography, and no glassmorphism.
- No rounded cards.
- No frosted glass panels.
- Use sharp, edge-to-edge blocks.
Team Graphics
Future team graphics should use a paper-rip or similar background gimmick, but not reveal-style gimmicks.
- Keep the team colors consistent.
- Use strong contrast.
- Do not bury important text.
Sponsor Use
Partner logos should be readable and treated like real sponsor assets, especially on primary paint schemes and announcements.
- Do not stretch logos awkwardly.
- Keep clear spacing around marks.
- Use sponsor colors with purpose.
Numbers
Car numbers should be readable, aligned, and consistent with the series style or team direction.
- Use clean outlines.
- Avoid clutter behind numbers.
- Make sure roof and door numbers match.
Public Copy
Public wording should feel official without sounding fake. Keep team updates clean, direct, and easy to understand.
- No messy sponsor wording.
- No over-explaining on graphics.
- Use the website as the clean reference point.
Records
Only confirmed stats, wins, and history should be shown publicly. Unconfirmed early-era results stay off public pages until verified.
- Confirmed wins go on Wins & History.
- Current stats go on Drivers.
- Vague history stays private until cleaned up.
Contact Chain
Use the right person for the right issue so problems do not bounce around aimlessly.
WispySkies02
Use for major team direction, website content, sponsor presentation, identity decisions, and high-level roster questions.
TrentPlayz
Use for team operations, competitive structure, roster coordination, and general logistics.
Will
Use for liveries, design assets, creative direction, and team graphics when needed.
TrentPlayz & Callornot
Use for iRacing coordination, driver rotation, official session planning, and sim-racing race operations.
Flamingo
Use for Roblox race operations, league coordination, driver entries, and race-night organization.
Nico
Use for race photography, graphic production, media support, and visual storytelling.
Keep the Standard Sharp
The handbook is the working rulebook for how Aetherwing should operate, communicate, race, and present itself. When in doubt, keep it clean, clear, and team-first.