Event Teams
How event teams work, including roster change requests.
An event team is the tournament-specific copy that Strave creates when a team registers. The copy protects the integrity of the event, and the original team can keep working normally.
Source team and event team
The team that registers is the source team. The copy that the event uses is the event team. This table shows how they differ:
| Source team | Event team |
|---|---|
| Its members own it. | The event and its organisers govern it. |
| You use it across Strave. | You use it only inside one event. |
| Its roster and profile can keep changing. | Its name, logo, and lineup follow the event policies. |
| It provides the initial registration data. | It holds signup answers, groups, check-ins, and competition status. |
When the source team changes its profile or lineup, Strave updates the event team according to the organiser's change policy:
- Open: Strave applies the change automatically.
- Requires Approval: Strave creates a review request for the organiser.
- Locked: Strave doesn't change the event team.

Registration statuses
Each event team has one of these statuses:
| Status | Meaning |
|---|---|
| Registered | Strave received the signup. It waits for any required review. |
| Approved | The organiser accepted the team. |
| Checked In | The team is ready for its first-stage group. |
| Eliminated | The team finished competing through normal progression. |
| Disqualified | An organiser removed the team from the competition. |
Strave can also record check-in for each group. This matters when the first stage has more than one qualifier.
Manage signups as an organiser
The Signups page in the event workspace is where you manage registered teams. On this page, you can:
- Search by team name or tag.
- Switch between table and card views.
- Filter by status.
- Invite a team directly.
- Approve, check in, disqualify, or remove a team.
- Review signup answers and the registered lineup.
- Edit the event-team profile, or sync it from the source team.
When you select a team, its detail view opens. The view has separate sections for details, players, answers, and change requests.
Change policies
In Configuration → Team Changes, you set a separate policy for the team name, the logo, and the lineup:
| Policy | Result |
|---|---|
| Open | Eligible team managers can apply the change directly. |
| Requires Approval | Strave holds the change until an organiser approves it. |
| Locked | Strave blocks the change. |
Optional change windows limit when a policy applies. Outside all matching windows, Strave blocks the change, even when the policy would allow it.
Review a change request
A change request can cover a name or logo update, adding or removing a member, replacing a player, or changing a lineup role. To review a request, follow these steps:
- Open Signups and select the event team.
- Open Changes.
- Review the requested value, the affected member, the requester, and the time of the request.
- Select Approve or Decline.
Resolved requests stay visible as an audit trail.
Responsibilities of team managers
If you manage a team in an event, you must:
- Check the event team after registration.
- Respond before change windows close.
- Check in to every required group.
Changes under an Open policy appear in the event team automatically. Changes under a Requires Approval policy stay pending until an organiser accepts them.
Next steps
- For the participant flow, see Sign up for an event.
- For what happens after seeding, see How matches work.