How Matches Work
Match flow from check-in to reported results.
The match room is the shared workspace for both teams and the event staff. It holds the official competitive record. Spectators see a separate public match page.

Match lifecycle
Every match goes through the same stages, from team assignment to the final result:
- The bracket or schedule assigns both teams.
- Both teams check their lineups and wait until the match is ready.
- The map veto starts. The teams complete each ban, pick, decider, and side choice.
- When the event requires the Strave anti-cheat, every required player readies up after the veto. The match starts when all players are ready.
- The teams play the selected maps.
- A team submits each map result, optionally with a score screenshot.
- The opponent confirms or disputes the result.
- The required players upload MOSS evidence when the event uses MOSS.
- Strave finalises the result and advances the bracket.
The match room navigation follows the same order: Lineups, Map veto, Anti-cheat (only when required), Maps & scores, MOSS, and Match record.
Before the match
Open the match from your team workspace and confirm:
- The scheduled time and the best-of format.
- The lineups of both teams.
- The rulebook and the anti-cheat requirements.
- Who on your team makes veto decisions and submits results.
Use match chat for coordination that belongs to the match. Event staff can see the same conversation.
Map veto
The event's match format defines the veto sequence. When it's your team's turn, the room shows Your turn, the required action, and the available maps. If the step has a time limit, the room also shows a countdown. When it isn't your turn, the room shows Waiting for opponent.
Pick and decider steps can include side choices for regulation and overtime. The team that picks a map isn't always the team that chooses the side, so follow the prompt in the room.
Submit scores
You submit a result for each map that you play. To submit a map result, follow these steps:
- Open Maps & scores.
- Select the map and enter the score of both teams.
- Attach a screenshot if the event requires one or if it helps confirm the result.
- Submit the result.
Scores can't be tied. Standard competitive matches also require a minimum winning score. The opponent can approve the result or dispute it for staff review.
Strave anti-cheat
An event can require the Strave anti-cheat in addition to MOSS or instead of it. For a required match, confirm and lock the active lineups. The anti-cheat never holds the map veto, so teams can do the veto early. After the veto, accept the current collection notice and start the anti-cheat agent from the Strave desktop client. The match room shows a ready-up step after the veto.
With hard start enforcement, the match stays in the veto phase with the veto complete until all players are ready. It then starts automatically. An organiser can release the hold with a reason. With soft enforcement, the match starts right after the veto, and organisers see who was not ready. A report uploads only when an organiser requests it. The desktop client then sends that session's encrypted report without a file picker.
MOSS uploads
When MOSS is on, the room shows who must upload, how many files are expected,
and the upload deadline. Upload the original .zip file. Each file can be up
to 500 MB, and each player can upload up to 10 files per match.
Depending on the organiser's policy, missing evidence can:
- Keep the match waiting for completion.
- Prevent a team from starting its next match.
- Cause a disqualification after the upload window closes.
Delete a submitted file only if it's wrong and the window still allows a replacement.
Admin calls and protests
The Get help menu in the match room has two options:
- Select Call an admin for a live problem, such as a technical issue, a connection problem, a rule question, or player conduct.
- Select File a protest for a formal challenge, such as cheating, a rule violation, unfair play, or an incorrect score. This option appears only when the event allows protests.
Describe the specific incident and include the relevant round or map. Staff can resolve a dispute, override a score, record a forfeit, or cancel a match. The match record keeps all of these actions.
Public result and progression
When the result is final, Strave updates the public match page, the standings, and the next bracket slots. A match can stay incomplete even after the server result is known. For example, it can wait for the opponent's confirmation, an organiser's decision, or MOSS uploads.