One clear starting point for your beta users
This is the beginner path. Pick a role, run one real workflow, and get people to their first win fast. When they need deeper product detail, move them to the reference docs instead of making them relearn the same page twice.
Start with the job they actually have
Each guide is scoped to a real beta persona, with specific tasks to verify in the product.
Owners, commissioners, and operators
Create the league, shape the season, manage staff, and run the operational side of 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.
Broadcasters, commentators, and production staff
Stand up overlays quickly, understand tokenized URLs, and verify what your stream team actually needs on race day.
Race directors and operational staff
Own the schedule, results operations, and handoff between league setup and race execution.
6 min skim
One page for permissions, pricing limits, workflows, and the troubleshooting details teams need mid-session.
Three practical ways to rehearse before opening beta
These are deliberately task-based so the docs stay tied to live product behavior.
Use this when you need a fast beta dry run from empty account to visible season.
Follow this to verify the surfaces people will touch under time pressure.
Best for checking the product during actual session traffic and coordination.
How Racey is organized
Beta testers churn when the platform vocabulary is unclear. Keep these concepts visible and consistent across product and docs.
The home for your community, staff, seasons, settings, and public identity.
A championship container with its own schedule, roster, scoring, and standings.
One race event inside a season, tied to a track, date, and results package.
Approved driver registrations, numbers, classes, and team assignments for a season.
A structured incident report with evidence, respondents, and a steward workflow.
A broadcast graphic page that updates in real time and can be dropped into OBS.
Use School for:
First-session onboarding, role-based walkthroughs, and beta rehearsals where people need the next action fast.
Use Docs for:
Reference material, integrations, operational checks, and deeper product detail once the basics already make sense.