Managing rosters when your community plays more than one game
Updated 11 November 2026 · 6 min read · By the Esports Hub team
Short answer
When a community plays more than one game, keep one master list of people, one roster per game, a clear captain for each, and a single announcement channel. Update the lists after every event so cards, brackets and check-in all use the same data.
Once a club fields teams in two or three games, the spreadsheet that worked for one team starts to break: one player appears in two rosters, a substitute is double-booked, and nobody knows which captain to ask. A few simple rules keep it manageable.
Keep one list of people and one list per team
Keep a single master list of everyone in the community: name, contact, and which teams they play for. Then each team has its own roster pointing at that list. A person is entered once, so a change of phone number or a left player is fixed in one place.
- Master list: name, contact, join date, status (active, on break, left).
- Team roster: game, team name, captain, players, substitutes, coach.
- Event entries: which roster entered which event, and when the roster was locked.
Name roles clearly
- Captain: the contact for the team and the event organisers.
- Starter and substitute: who plays by default and who covers.
- Coach or manager: not a player, may not play unless the rules allow it.
- Admin: someone in the community who can change rosters.
Rules for players in more than one team
Decide in advance whether a player may play for two teams in the same game (usually no) and in different games (usually yes). Check each tournament's own rule, since many allow a player on only one team per event. Put your rule in writing so captains do not argue about it.
A weekly routine
- Monday: captains confirm availability for the coming week.
- Midweek: lock rosters for any event that week and send the list to the organiser.
- After each event: record results and attendance.
- Monthly: remove players who left, add new ones, review who is overloaded.
Cards, passes and entry lists
When you enter an event, the organiser usually wants a roster with names and roles, and may issue passes. If you keep your roster clean, you can export it and the organiser can load it straight into an ID card maker. See player ID cards and passes.
Privacy
A community roster holds personal details. Keep it in a place only the admins can open, collect the least you need, and get a guardian's consent for anyone under 18.
A simple roster layout
A spreadsheet is enough for most communities. Keep one sheet for people and one for each team.
| Sheet | Columns |
|---|---|
| People | Name, phone or contact, joined on, status, notes |
| Each team | Player, role (starter, substitute, coach), in-game ID, contact, joined team on |
| Events | Event, date, which team entered, roster locked on, result |
Lock a copy of the roster on the day you enter an event. That copy is what the organiser has, so it is the one to check if a question comes up later.
Handling clashes
- Keep one shared calendar for all teams, not one per game. A clash is easy to see when everything is in one place.
- When two events fall on the same day, decide by a written priority (for example, the event with prize money first) rather than by who shouts loudest.
- Ask players for the days they cannot play at the start of each month.
- If a substitute is needed, have a short list of who can cover which game before the day, not on it.
When people join and leave
- New player: add them to the master list, put them on one team, tell them the rules and who the captain is.
- Moving teams: remove them from the old roster, add them to the new one, and note the date.
- Leaving: mark them as left, remove them from every roster and group chat, and delete personal details you no longer need.
A short group-chat rule helps too: one chat per team for match talk, one announcement chat for the whole community where only admins post.
A worked example: one community, three games
Say a club has 22 people. Eight play Free Fire (a squad of four plus four reserves), five play Valorant, and some of the Free Fire players also play a mobile game with a separate team. The master list has 22 rows. The Free Fire sheet has 8 rows, the Valorant sheet 5, and the third team 4. Nobody is typed in twice, so when a phone number changes it is fixed once.
When a fest announces a Free Fire event, the captain copies the locked Free Fire roster into the organiser's registration form, or sends the captain's link from the registration tool. Because the roster already has names, roles and in-game IDs, the organiser can load the same list into the ID card maker and print one card per person in about an hour.
Checklist before you enter an event
- The captain has confirmed every player can attend on the day.
- The roster has a starter and a substitute for each place, with in-game IDs checked for spelling.
- Anyone under 18 has a guardian's consent recorded.
- A copy of the roster is locked and sent to the organiser, and the date is noted.
- Nobody is on two rosters for the same game or event if the rules forbid it.
- The captain knows the schedule, the rules and who the organiser's contact is.
Common mistakes
- Keeping a separate spreadsheet per game, so one person appears in three places with three phone numbers.
- Letting every player edit the roster. Give edit rights to admins only.
- Not locking a copy on entry day, so a later change cannot be checked against what the organiser received.
- No written rule for a player who wants to play for two teams, which turns into an argument on the day.
- Leaving old players on rosters and group chats after they have left.
- Keeping personal details forever. Delete what you no longer need.
Questions and answers
The things people ask most about this, answered plainly.
How do I keep rosters for several games in one community?
Keep one master list of people (name, contact, join date, status) and one roster per team that points to it, so a person is entered once and can play in more than one game. Add an events sheet that records which roster entered which event and the day it was locked. Fix a phone number or a left player in one place. When an organiser asks for your entry list, export the roster and load it into the ID card maker so cards use the same data.
Can a player be on two teams in the same game?
Usually no, and in different games usually yes, but check each tournament's own rule because many allow one team per player per event. Put your community's rule in writing so captains do not argue about it, and lock a copy of each roster on the day you enter an event so there is one version to check later. The ID card maker prints a card per person and team from the same roster, so each player has one pass per event.
Who should own each roster?
A named captain or admin for each game, with one overall organiser who can see all of them. The captain is the contact for the team and for tournament organisers, and an admin is the only person who changes rosters. Write the roles down: captain, starter, substitute, coach or manager, admin. The registration feature on this site, with a free account, lets captains submit their own team and lets the organiser approve it into the event roster.
What do I do when someone leaves or changes team?
Mark them as left on the master list, remove them from every roster and group chat, and delete personal details you no longer need. If they move teams, remove them from the old roster, add them to the new one and note the date. For any upcoming event, a player who moved needs a new card: a pass signed for the old team or role fails at the gate scanner by design, so reprint it in the ID card maker.
How do I handle schedule clashes between games?
Keep one shared calendar for all teams instead of one per game, so a clash is visible when it is made. When two events fall on the same day decide by a written priority, for example the event with prize money first, not by who shouts loudest. Ask players for the days they cannot play at the start of each month and keep a short list of substitutes for each game. The match schedule maker helps you work out how long a day of matches takes.
Is it safe to store player details in a shared spreadsheet?
Only if access is limited. A community roster holds personal details, so keep it in a place only the admins can open, collect the least you need, get a guardian's consent for anyone under 18, and delete details you no longer need. Do not store government ID numbers in it. The ID card maker on this site works in your browser, so cards can be made from an exported copy without uploading photos or names anywhere.
Try it
Free to use, no account needed.
Keep reading
Spotted a mistake or something out of date? Tell us on the contact page and we will fix it. How we write and update guides: about this site.