Suspending a player for a policy violation
Bar a player from a range of rounds in a season, record why, and lift the sanction on appeal.
Overview
When a player breaches your league's policies, you can suspend them from a range of rounds in a season. The suspension is a record, not just a flag: it captures the violation, your written reason, who issued it, and which rounds the player is barred from — so the decision holds up when a team appeals it.
Suspensions are always scoped to one season. Suspending a player in the spring season does not carry into the autumn season, and a player suspended in one league is unaffected in another.
Issuing a suspension
- Make sure the season you want to sanction the player in is the active season in your workspace switcher — suspensions are recorded against that season.
- Go to Teams, then open the team the player is rostered with.
- Find the player in the Players table and click Suspend.
- Choose the Violation, write the Reason, and set the round range.
- Click Suspend player.
The player now shows a red suspension badge on the roster naming the rounds they're barred from, and the sanction appears on the season's Discipline page.
Choosing the round range
The range is inclusive: a suspension from round 4 to round 6 bars the player from rounds 4, 5 and 6, and they are eligible again in round 7. For a single-round sanction, set both the first and last round to the same number.
Rounds are used rather than dates deliberately — if a game is postponed, a round-based suspension still costs the player the same number of matches, whereas a date range would quietly let them off.
| You want to… | Set first round | Set last round |
|---|---|---|
| Bar them from the next round only | the next round number | the same number |
| Bar them for three rounds from round 4 | 4 |
6 |
| Bar them for the rest of a 10-round season, from round 7 | 7 |
10 |
Reviewing sanctions
The season's Discipline page lists every suspension on file — active and lifted — with the player, team, rounds, violation and who issued it. Reach it from the season sub-nav, alongside Schedule and Participation.
On the Participation by round page, any round a player was suspended for is marked SUSP in their row, so a gap in someone's participation is explained rather than mysterious.
Lifting a suspension
If an appeal succeeds, or the sanction is reduced:
- Go to the season's Discipline page.
- Type the reason in the Reason box on the player's row — for example Appeal upheld.
- Click Lift and confirm.
The player is eligible again immediately. The original sanction is never deleted: it stays on the Discipline page marked as lifted, together with who lifted it and why, so the full history remains available.
Suspended players who were fielded anyway
Game rosters are recorded by the scoring app, which cannot yet stop a team from fielding a suspended player. StatsCentral therefore checks after the fact.
If a suspended player appears in a game whose round falls inside their suspension, an amber warning appears in two places:
- On that game's detail page, naming the player and the sanction they breached.
- At the top of the season's Discipline page, listing every such appearance in the season.
Treat these as prompts to act under your own competition rules — for example awarding a forfeit or extending the sanction. StatsCentral flags the breach; it does not decide the penalty.
Edge cases
- No Suspend button on the roster — no season is active in your workspace switcher, or you are not a league admin. Team managers can see that their player is suspended but cannot issue or lift a sanction.
- "This player already has an active suspension" — round ranges for one player in one season cannot overlap. Lift the existing sanction first, or pick rounds outside it.
- The player moved teams mid-season — the suspension follows the player, not the team. The team they were rostered with when the sanction was issued is kept on the record.
- You picked the wrong rounds — lift the sanction with a reason explaining the correction, then issue a fresh one with the right range. This keeps the audit trail intact rather than rewriting history.
Was this helpful?
Thanks for the feedback!