When 50 seniors are playing, you can track everything in your head. At 300 players, you cannot. Most large-school seasons collapse because organisers try to run small-game rules at big-game scale. The winning move is not stricter rules, but smarter structure. Here's what actually works when your entire grade is playing.

Why large schools need different structure

The jump from a handful of players to hundreds of players is not just a quantity problem. It changes every part of how you run the game. With 50 players, you can text people individually when someone gets eliminated and verify kills by word of mouth. With 300, you have 60 simultaneous text chains, verification falls apart, and targets get assigned to players who already dropped out of the game.

The core mechanic stays: when you eliminate your target, you inherit their target. But everything around that mechanic has to become systematic. Targets cannot be assigned by hand. Eliminations cannot be verified by trust. Communication cannot happen in a group chat. At large schools, your job is not to play the game, but to build the frame that lets everyone else play.

Parallel tracks instead of one big game

The single most important decision you can make is to stop running one game of 300 and start running five games of 60. This is not the same as restarting the game. All five tracks run simultaneously during the same window, using the same rules, with the same elimination window and the same endgame. The split happens only in target assignment and verification.

Each track is independent. Players in Track A cannot eliminate players in Track B. When you finish a track, the winners merge into a playoff bracket with the other track winners. This structure keeps verification manageable, keeps the game board readable, and prevents a single mistake from collapsing the entire season.

You might split by lunch period, by dorm, by grade-year cohort, or by random assignment. The split method does not matter as much as the fact that you split. Smaller games are faster, easier to verify, easier to communicate about, and easier to fix if something goes wrong.

• Assign players to tracks at the start, not mid-season
• Keep all tracks running on the same schedule
• Merge winners into a single finals bracket
• Verify kills and assign targets within each track separately

Automate the one-way chain with a digital board

In a small game, you can assign targets by hand: you are out, and your target now belongs to whoever eliminated you. At 300 players, you need a system that does this instantly, correctly, and automatically. This is not complicated. It is only necessary.

The target chain generator builds a one-way chain where each player points to their target, and when a player is eliminated, their target reassigns to the player who killed them. A digital board keeps track of who is out, who their target was, and who just inherited that target. No spreadsheet. No manual updates. No confusion.

The moment you move to digital, everything else becomes possible. You can verify eliminations in seconds instead of arguing about them. You can see the entire bracket state at once. You can spot problems before they spiral. A large school without a digital board is trying to play chess with index cards.

Verification: how to confirm kills at scale

With 50 players, an elimination is verified when the target confirms it. With 300, half your eliminations are contested. Someone claims they got you. You did not see it. You think they missed. One week later, you still do not know who is actually out.

Write explicit rules about what counts as an elimination. Water gun? You need it to make contact. Fingers? Does it have to be a certain gesture? In public? On school grounds? In their home? The more specific, the fewer arguments. Then pick one person to verify each track, or require photo and video evidence for contested kills, or let the target confirm by responding to a text within an hour.

The rule you pick matters less than having a rule that is fast and that does not require five text exchanges. At large schools, slow verification eats time you do not have.

Communication: one channel, one source of truth

In a big game, you cannot have fifty group chats. You need one space where the entire school can see the rules, the current bracket, who is still in, and how to report an elimination. Some schools use Discord. Some use Instagram. Some use a shared document. What matters is that every player knows where to look, and every player sees the same information.

Your senior assassin rules template lives in that one place. The current bracket lives there. How to report a kill lives there. The reason you were eliminated lives there. If a player has to search three different places to find the answer to a question, your season is disorganised. With hundreds of seniors asking questions simultaneously, one clear channel is not luxury. It is the only way to keep your own head above water.

Endgame: when the field narrows

By the time you reach finals, everyone is paying attention. This is when the game actually starts for most players. By this point you have probably run four or five tracks in parallel, merged the winners, and now have 30 or 40 players in a single bracket. All the structure you built for the big game still applies, just on a smaller stage.

If your tracks merged unevenly, you might have a playoff bracket to reseed the players. If they merged evenly, you might seed them by how fast they won their track. The exact mechanic depends on how you want to reward speed versus consistency. What stays the same: the one-way chain keeps the endgame moving, and eliminations still get verified before targets reassign.

Rules that actually scale

Most schools lose control of a large season because their rules either do not address what happens at scale, or they try to address it with restrictions that make the game unplayable. A rule like no eliminations during school hours works when people know each other. With 300 players, half of them will not know the rule exists, and the other half will interpret it differently.

Scalable rules are not longer rules. They are rules that prevent the specific chaos that breaks large games. That means rules about target swaps. Rules about what happens if someone's target already got eliminated before they knew it. Rules about how long someone has to act on their new target after an elimination. Rules about whether you can return to a location where you were just eliminated.

The how to play senior assassin guide walks through the actual sequence of events in a game, which is where most of your edge cases will come from. A well-written rules document is built for exactly this: decisions your school actually has to make, not generic restrictions copied from somewhere else.

The mistake that kills large seasons

The most common failure is this: the organisers write good rules, publish the bracket, and then stop communicating. A week in, no one knows what the current state of the game is. Eliminations pile up in a backlog. People do not know if they are still in or out. Half the bracket gives up because it feels frozen.

With 300 players, you have to update the board daily, verify eliminations within hours, and announce results in real time. If you cannot commit to that rhythm, run a smaller game or recruit another organiser to share the load. A large game run once a week is not a game. It is a waiting list. The players who show up on day one and do not see an update until day seven will disappear by day eight.