236 lines
4.7 KiB
Markdown
236 lines
4.7 KiB
Markdown
# GridPilot for Admins
|
||
*Professional tools that eliminate the chaos of running an iRacing league — without changing how your community works.*
|
||
|
||
---
|
||
|
||
## 1. Why Admins Need GridPilot
|
||
|
||
Running a league today means juggling:
|
||
- Discord threads
|
||
- Google Sheets
|
||
- CSVs
|
||
- DMs
|
||
- PDFs
|
||
- manual points
|
||
- manual sign-ups
|
||
- manual session creation
|
||
- messy protest handling
|
||
|
||
Meanwhile, admins just want to:
|
||
- run good races
|
||
- keep drivers happy
|
||
- keep things fair
|
||
- and not drown in repetitive work
|
||
|
||
GridPilot gives admins the structure and tools iRacing never provided.
|
||
|
||
---
|
||
|
||
## 2. League Identity & Presentation
|
||
|
||
Admins get a clean, modern league homepage — instantly.
|
||
|
||
### Includes:
|
||
- league logo + colors
|
||
- season schedule
|
||
- standings (driver + team)
|
||
- team list
|
||
- driver roster
|
||
- results archive
|
||
- links to Discord, YouTube, Twitch
|
||
|
||
### Optional:
|
||
- custom subdomain (e.g. *yourleague.racing*)
|
||
|
||
This makes small leagues feel **professional** without any technical effort.
|
||
|
||
---
|
||
|
||
## 3. Season Management
|
||
|
||
A complete toolkit to organize seasons without spreadsheets.
|
||
|
||
### Admins can:
|
||
- define the league format
|
||
- create calendars (tracks, car classes)
|
||
- configure points systems
|
||
- define drop weeks
|
||
- choose team vs solo format
|
||
- set rules & info pages
|
||
- open/close registration
|
||
- manage rosters
|
||
|
||
Everything stays in one clean UI.
|
||
|
||
---
|
||
|
||
## 4. Driver & Team Sign-ups
|
||
|
||
Forget Discord forms and DMs.
|
||
|
||
### GridPilot handles:
|
||
- driver sign-ups
|
||
- team registrations
|
||
- automatic roster generation
|
||
- driver availability status
|
||
- team composition
|
||
- waitlist management
|
||
|
||
Admins no longer need to chase people for info.
|
||
|
||
---
|
||
|
||
## 5. Automatic Results Import
|
||
|
||
One of the biggest pains in league racing — **gone**.
|
||
|
||
GridPilot automatically imports results from iRacing:
|
||
|
||
### Extracts:
|
||
- finishing positions
|
||
- incident count
|
||
- best laps
|
||
- lap-by-lap data
|
||
- gained/lost positions
|
||
- SoF (if available)
|
||
|
||
### Updates:
|
||
- driver standings
|
||
- team standings
|
||
- season points
|
||
- drop-week applied points
|
||
|
||
Admins don’t upload CSVs or calculate anything manually again.
|
||
|
||
---
|
||
|
||
## 6. Complaints & Penalties
|
||
|
||
A structured workflow to replace protest chaos.
|
||
|
||
### Drivers can submit complaints:
|
||
- select the race
|
||
- select involved drivers
|
||
- add timestamps
|
||
- add explanations
|
||
- optionally add short clips
|
||
|
||
### Admins get:
|
||
- a review dashboard
|
||
- quick decision tools:
|
||
- no action
|
||
- warning
|
||
- time penalty
|
||
- points deduction
|
||
- DQ for the race
|
||
|
||
### GridPilot updates everything automatically:
|
||
- recalculates standings
|
||
- adjusts team points
|
||
- logs penalties visibly
|
||
|
||
Admins stay in full control — GridPilot just removes the manual work.
|
||
|
||
---
|
||
|
||
## 7. Optional: Session Creation QoL
|
||
|
||
Automation is *optional* — but powerful for admins who want it.
|
||
|
||
### One-click creation of:
|
||
- practice sessions
|
||
- race sessions
|
||
- full season batches
|
||
|
||
### Benefits:
|
||
- no repetitive form filling
|
||
- consistent settings
|
||
- saves hours every season
|
||
- always under admin control
|
||
|
||
GridPilot acts as an **assistant**, not a bot.
|
||
Admins keep full responsibility.
|
||
|
||
---
|
||
|
||
## 8. Roster & Driver Management
|
||
|
||
Admins can:
|
||
- view complete roster
|
||
- assign drivers to teams
|
||
- manage substitutes
|
||
- approve/reject sign-ups
|
||
- track attendance
|
||
- see driver stats for performance evaluation
|
||
|
||
Helps maintain a healthy community and balanced competition.
|
||
|
||
---
|
||
|
||
## 9. Transparency & Trust
|
||
|
||
GridPilot creates structure admins normally have to enforce manually:
|
||
|
||
- clear point systems
|
||
- visible penalties
|
||
- visible rules
|
||
- logged decisions
|
||
- consistent standings
|
||
- predictable schedules
|
||
- no lost messages or hidden complaints
|
||
|
||
This removes accusations of favoritism or unfairness.
|
||
|
||
Admins gain **presence**, not stress.
|
||
|
||
---
|
||
|
||
## 10. Zero Technical Overhead
|
||
|
||
No coding.
|
||
No servers.
|
||
No spreadsheets.
|
||
No HTML.
|
||
No spreadsheets.
|
||
No setup.
|
||
|
||
Admins simply:
|
||
1. create a league
|
||
2. configure the season
|
||
3. share the league link
|
||
4. run the races
|
||
5. GridPilot handles the rest
|
||
|
||
---
|
||
|
||
## 11. What GridPilot Is *Not* for Admins
|
||
|
||
- not a replacement for your Discord community
|
||
- not a stewarding system (no live stewarding)
|
||
- not intrusive automation
|
||
- not a tool that changes racing behavior
|
||
- not a way to manipulate results
|
||
|
||
We respect the league → we just make it manageable.
|
||
|
||
---
|
||
|
||
## 12. Summary
|
||
|
||
GridPilot gives admins:
|
||
|
||
- **professional presentation**
|
||
- **zero manual points work**
|
||
- **automatic standings**
|
||
- **clean sign-ups**
|
||
- **structured complaints**
|
||
- **quick penalties**
|
||
- **optional session automation**
|
||
- **roster tools**
|
||
- **driver & team identity**
|
||
- **season organization**
|
||
|
||
It lets admins focus on racing, not paperwork.
|
||
|
||
GridPilot =
|
||
**less chaos, more competition.** |