Learn Racey through one race operations workflow
Pick the role that matches what you do on race day, follow a focused guide, and build confidence in the league workspace one workflow at a time. When you need deeper detail, the reference docs are one click away.
Each role guide gives drivers, admins, stewards, and race directors a clear first path.
View 4 optionsUse these paths when the user already knows the task they need to complete.
View 3 optionsFocused guides for the operational tools people reach for after the basic workflow is clear.
View 6 optionsQuick reference, glossary, and program details for people who need a precise answer fast.
View 3 optionsStart with the job someone has on race day
Each role guide gives drivers, admins, stewards, and race directors a clear first path.
Owners, commissioners, and operators
Create the league, shape the season, manage staff, and run the operating workspace for race night.
Drivers, team members, and new joiners
Find leagues, register for seasons, track performance, and handle protests without getting lost in admin tooling.
Stewards, appeals reviewers, and rules officials
Review incidents consistently, understand blind review, and move cases from submission to ruling.
Race directors and operational staff
Own the schedule, results operations, and handoff between league setup and race execution.
Follow the work from setup to live operations
Use these paths when the user already knows the task they need to complete.
Owners, commissioners, and operators
Create the league, set up the first season, invite staff, and verify the race-night operating loop.
Race directors and operational staff
Move from schedule and roster prep into results review, publication, and standings checks.
Stewards, appeals reviewers, and rules officials
Use protest intake, evidence review, voting, rulings, and appeals as one consistent workflow.
Go deeper on imports, AI, and planning tools
Focused guides for the operational tools people reach for after the basic workflow is clear.
Pro-tier league admins and stewards
When to use Racey's three AI features (Protest Summary, Race Report, Scoring Recommendation), what each one does, and where they fall short.
League admins and race directors
Column reference, validation rules, and troubleshooting for the Results import wizard. Templates included.
League admins running closed or invite-only seasons
A planning worksheet for season rosters, the real workflows it feeds (driver self-registration and bulk-invite-by-email), and how it differs from the two-column roster CSV importer.
Race directors and admins doing one-off entries
Long-form reference for hand-entered or JSON-driven result imports — field reference, multiclass, heat + feature, validation rules, and common errors.
League organisers and drivers
How league chat, the organisers thread and team chats work: who can read and post, announcements, moderation, reporting and alert settings.
Drivers and league organisers
How direct messages work: who you can message, message requests, alerts, blocking, reporting, limits and the privacy setting that turns DMs off.
Keep fast lookups and definitions close
Quick reference, glossary, and program details for people who need a precise answer fast.
League staff and returning users
One page for permissions, pricing limits, workflows, and the troubleshooting details teams need mid-session.
Anyone new to league management or sim racing terminology
Plain-language definitions for the terms used across Racey — roles, protests, seasons, multiclass, entry fees, and scoring.
Founding members, league admins, and curious users
What the Founding Partner program is, who qualifies, what it grants, and where the badges show up in the product.
Use School for:
Role onboarding, workflow paths, tool guides, and fast reference lookups.
Use Docs for:
Operational checks, integrations, API details, and deeper product reference.