211 lines
4.6 KiB
Markdown
211 lines
4.6 KiB
Markdown
# GridPilot for Teams
|
||
*Teams are the backbone of real motorsport. GridPilot finally gives them the tools they’ve always needed in iRacing league racing.*
|
||
|
||
---
|
||
|
||
## 1. Why Teams Matter
|
||
|
||
Teams add:
|
||
- identity
|
||
- rivalry
|
||
- long-term story
|
||
- shared goals
|
||
- consistency
|
||
- progression
|
||
- fun beyond solo racing
|
||
|
||
But in iRacing leagues today, teams are treated as:
|
||
- “a tag on a spreadsheet”
|
||
- “a logo in a Discord channel”
|
||
|
||
GridPilot fixes that by making teams **first-class citizens** of the platform.
|
||
|
||
---
|
||
|
||
## 2. Team Profiles
|
||
|
||
Every team gets its own home on GridPilot:
|
||
|
||
### **Team Profile Includes**
|
||
- team name
|
||
- logo & colors
|
||
- description/bio
|
||
- captain / co-captains
|
||
- full roster
|
||
- active seasons
|
||
- past seasons
|
||
- team standings
|
||
- points history
|
||
- achievements
|
||
|
||
### Why it matters
|
||
Drivers finally have somewhere to “belong,”
|
||
and teams become part of the league’s story — not a footnote.
|
||
|
||
---
|
||
|
||
## 3. Team Creation & Management
|
||
|
||
Teams can be created by any user:
|
||
|
||
### Team captains can:
|
||
- invite drivers
|
||
- approve join requests
|
||
- remove drivers
|
||
- assign roles (captain, strategist, reserve driver)
|
||
- manage the team profile
|
||
- mark the team as “recruiting”
|
||
|
||
### Drivers can:
|
||
- request to join
|
||
- switch teams between seasons
|
||
- follow recruiting teams
|
||
- represent their team in multiple leagues
|
||
|
||
Everything is clean, modern, and transparent.
|
||
|
||
---
|
||
|
||
## 4. Team Registration for Seasons
|
||
|
||
When a league supports team racing, teams can register directly:
|
||
|
||
### Team season registration:
|
||
1. captain chooses league
|
||
2. reviews schedule & format
|
||
3. submits team
|
||
4. roster automatically populated
|
||
5. drivers assigned to specific car slots if needed
|
||
6. team appears in league standings
|
||
|
||
No forms.
|
||
No DMs.
|
||
No spreadsheets.
|
||
|
||
---
|
||
|
||
## 5. Constructors-Style Team Competition
|
||
|
||
This is where GridPilot goes beyond what any league tool offers.
|
||
|
||
### **How it works**
|
||
- multiple drivers from a team race in parallel
|
||
- each race week can have different participating drivers
|
||
- **all scored points contribute to the team championship**
|
||
- standings update automatically from iRacing results
|
||
|
||
### **Why it’s superior**
|
||
- teams aren’t just “one driver per car slot”
|
||
- stronger teams can field more competitive drivers
|
||
- every driver matters
|
||
- team strategy becomes part of the championship
|
||
- it feels like real motorsport (F1: Constructors, WEC, GT teams)
|
||
|
||
This is a massive upgrade over the usual “driver only” league structure.
|
||
|
||
---
|
||
|
||
## 6. Team Standings & History
|
||
|
||
Each team gets:
|
||
- season standings
|
||
- total points
|
||
- podiums
|
||
- wins
|
||
- member contributions
|
||
- historical performance graphs
|
||
- list of every season ever raced
|
||
|
||
Over time, this becomes:
|
||
- reputation
|
||
- prestige
|
||
- an asset teams are proud of
|
||
|
||
Teams become part of the GridPilot universe, not just this week’s race.
|
||
|
||
---
|
||
|
||
## 7. Driver Contribution Breakdown
|
||
|
||
Teams can see:
|
||
- which driver scored points
|
||
- how many
|
||
- consistency over time
|
||
- incidents
|
||
- average finishing position
|
||
- contribution %, similar to "driver share"
|
||
|
||
This builds:
|
||
- internal competition
|
||
- motivation
|
||
- clarity
|
||
- lineup optimization
|
||
|
||
It also helps captains choose who drives what event.
|
||
|
||
---
|
||
|
||
## 8. Discoverability: Find & Recruit Drivers
|
||
|
||
Teams can mark themselves as:
|
||
- **Actively Recruiting**
|
||
- **Closed**
|
||
- **Looking for reserve drivers**
|
||
|
||
Drivers can:
|
||
- browse teams
|
||
- search by region / league / car class
|
||
- request to join
|
||
- follow teams they like
|
||
|
||
This solves the huge problem of:
|
||
> “Where do we find new drivers for our team?”
|
||
|
||
---
|
||
|
||
## 9. Communication Tools (Lightweight)
|
||
|
||
Teams get:
|
||
- team announcements
|
||
- team chat
|
||
- direct messages
|
||
- lineup discussions
|
||
- strategy notes
|
||
|
||
Not a full Discord replacement —
|
||
but enough to organize race days without noise.
|
||
|
||
---
|
||
|
||
## 10. Why Teams Should Use GridPilot
|
||
|
||
Teams get what iRacing never gave them:
|
||
|
||
### ✔ Real constructors-style competition
|
||
### ✔ A permanent home
|
||
### ✔ A public identity
|
||
### ✔ A place to recruit
|
||
### ✔ A performance history
|
||
### ✔ a reason to stay long-term
|
||
### ✔ pride and prestige
|
||
### ✔ fewer spreadsheets
|
||
### ✔ clearer communication
|
||
|
||
Teams turn league racing into something that **feels like real motorsport**.
|
||
|
||
---
|
||
|
||
# Summary
|
||
|
||
GridPilot for Teams delivers:
|
||
- professional team identity
|
||
- constructors-style points
|
||
- automatic team standings
|
||
- clear contributor stats
|
||
- season + all-time history
|
||
- recruitment tools
|
||
- team chats & coordination
|
||
- smooth season registration
|
||
|
||
Teams finally become **true participants** in iRacing league racing —
|
||
not just a tag next to a driver name. |