Team requests
Let riders start their own teams, and review the requests when they come in.
Riders can ask to create their own teams. It's off by default, so no club gets this by surprise.
Turning it on
Settings → Recruitment → "Allow riders to create teams"

Beside it, "Who can ask":
| Option | Who it covers |
|---|---|
| Riders on a team (default) | Anyone already rostered somewhere in your club |
| Everyone, including prospects | Also riders who've joined but aren't on a team yet |
A prospect who isn't allowed to ask is told what would unblock them — being placed on a roster — rather than simply being refused. That's worth knowing, because it turns a dead end into a prompt for them to come and talk to you.
Switching it off again is safe
Requests already in the queue stay actionable. You won't strand anyone mid-request by turning the feature off.
Reviewing a request
Requests arrive in your notification bell, alongside loan requests and verifications. Each one shows:
- The team's proposed details
- The rider's category and FTP
- The teams they're already on
- Whatever they wrote in their note
Only commissioners and admins can review these. Captains can't, even for their own race type.

| Action | What happens |
|---|---|
| Approve | The rider becomes captain of the new team, the team gets its own page, and they're placed on its roster |
| Reject | You must give a reason. It's emailed to the rider, and the team name is freed up for someone else |
Rejecting well matters more than approving well
The reason you type is the entire message that rider receives. "Not right now — come back after the season starts and we'll look again" costs you ten seconds and keeps a willing volunteer. A blank-feeling rejection tends to lose one.
Rate limits
A rider can have one open request per club and make three a day. You won't get flooded by one enthusiastic person.
Before you switch it on
Rider-created teams are a good way to grow without every team passing across your desk — but each approved team starts with exactly one rider on it, and somebody has to fill it.
Two things worth deciding in advance, so you're not making the call for the first time with a request already in front of you:
- What you'll say yes to. A development squad, a second team for an oversubscribed slot, a group who all race the same time — these are usually easy. A team that duplicates one you already have usually isn't.
- Who's watching Team Health. A new team that doesn't fill will show as short in the weeks after you approve it. That's useful information, but only if someone's looking.