Tournament registration form: what to ask, what to leave out and how to approve teams
Updated 11 November 2026 · 7 min read · By the Esports Hub team
Short answer
A tournament registration form should ask for the team name, the college or club, a captain's contact, each player's name and in-game ID, and whether anyone is under 18. Set a closing date and a team limit, confirm each team in writing, and leave out anything you will not use.
A registration form decides how much chasing you do later. Too few fields and you spend the week messaging captains. Too many and people give up or give you wrong data. This guide lists what to ask for each kind of event, what to leave out, and how to go from a submitted form to an approved roster.
The fields every form needs
| Field | Why you need it |
|---|---|
| Team name | How the team appears in brackets and tables |
| College, club or city | Eligibility and a tie-break for disputes about who a team is |
| Captain's name and phone or email | The one contact for all messages |
| Each player's name | Roster, ID cards and certificates |
| In-game name and ID for each player | How opponents and referees find them in a lobby |
| Substitutes | So a missing player does not cost the team the match |
| Under-18 flag | Triggers a guardian's consent |
| Agreement to the rules | A tick box that links to the rules page |
Fields to add by game and event
- Squad games (such as Free Fire or BGMI): four players and one substitute per squad. See the Free Fire and BGMI guides.
- 5 v 5 games (such as Valorant): five players, one or two substitutes. See the Valorant guide.
- Solo events: one player, no captain.
- Offline events: a photo for each player, if you will print cards.
- Entry fee events: how and when it is paid. Check the rules and law before you take money.
What to leave out
- Government ID numbers, including Aadhaar numbers: you rarely need them, and holding them is a risk.
- Home addresses.
- Anything you cannot say what you will use it for.
- Long free-text questions. A long form lowers completion.
Tell people on the form what you will do with their details and how long you will keep them. Delete them when the event is over. Our privacy policy explains how this site handles data entered in the registration feature.
Free Fire and BGMI tournament registration form
A squad game needs four players and one substitute for each team, so the form needs a line for each of them with a name and an in-game name or ID. The free tournament registration form has a squad preset for this: pick it, type your event name and copy the questions into Google Forms or WhatsApp. For the rest of the event, see the Free Fire and BGMI guides.
Open, close and approve
- Publish the rules with the form, so a tick on the form means something.
- Set a team limit and a closing date. Close a day before the event so you can check the list.
- Check each registration: spellings, duplicate players, eligibility.
- Approve or reject each team and tell the captain in writing, with the schedule and the rules attached.
- Keep a waiting list. Teams drop out.
Use a ready form
The free registration form lets you copy a ready form for squad, 5 v 5, duo or solo events, with no account. With a free account you get a registration link: captains fill in the form on their phone, you set a team limit and a closing time, and an approved team and its players go straight into your roster, ready for ID cards and gate check-in.
For the whole event around the form, see how to run a college tournament.
A sample squad form
For a four-player squad game, a good form has about 25 fields: the squad name, college or city, the captain's name and phone or email, four players (name and in-game name and ID each), one substitute, an under-18 box for each player, and one tick box for the rules. Nothing else. Asking players for a photo is useful only for offline events where you will print cards, and the ID card maker can collect those with an invite link.
| Section | Fields |
|---|---|
| Team | Squad name, college, club or city |
| Contact | Captain's name, phone or email |
| Players | Name, in-game name and ID, under 18 (yes or no), for each of four players |
| Substitute | Name, in-game name and ID |
| Agreement | Tick box that links to the rules |
Checklist and common mistakes
- Rules published with the form.
- Team limit and closing time set.
- Each registration checked for duplicate players and spelling.
- Every captain told in writing whether they are approved, with the schedule attached.
- A waiting list kept.
- Asking for Aadhaar numbers, addresses or anything you will not use.
- A long free-text form that people abandon.
- Not saying what you will do with the details.
- Closing registration on the morning of the event.
- Approving teams by chat message instead of in one list.
Questions and answers
The things people ask most about this, answered plainly.
What should a tournament registration form ask?
Team name, college, club or city, the captain's name and phone or email, each player's name and in-game name or ID, substitutes, whether anyone is under 18, and a tick box agreeing to the rules. Add fields by game: four players and a substitute for a squad game, five players for 5 v 5, one player for a solo event. The registration tool on this site gives you a copyable form for squad, 5 v 5, duo or solo events with no account.
Should I collect Aadhaar or other ID numbers on a registration form?
Not unless you truly need them. They are sensitive, a registration rarely needs them and holding them is a risk. Collect only what you will use, say how long you will keep it and delete it when the event is over. If you must verify an ID at a gate, check it by eye and do not copy the number. The ID card maker keeps only the last four digits when it reads an Aadhaar card.
How do I handle players under 18 in registration?
Ask on the form whether any player is under 18, and get a parent or guardian's consent before the event and before printing their card. Record that consent against the player in your roster. In the registration tool captains mark players who are under 18, so you can see at the approval step who still needs consent. Keep the consent as a simple record next to the roster, and do not collect more details about a minor than you would for an adult, because the form only needs what the event itself needs.
Is there a free registration form for esports teams?
Yes. The registration tool on this site gives you a copyable form with no account. With a free account you also get a registration link: captains fill in the form on their phone, you set a team limit and a closing time, and approve or reject each team. An approved team and its players and substitutes go straight into your roster, ready for ID cards and gate check-in.
How do I approve teams and handle a waiting list?
Publish the rules with the form so a tick means something, set a team limit and a closing date, and close a day before the event so you can check the list. Check spellings, duplicate players and eligibility, approve or reject each team and tell the captain in writing with the schedule and rules attached. Keep a waiting list, because teams drop out.
Who can see the contact details people enter?
In the registration feature, contact details are shown only to the organiser of the event and are deleted with the event or your account. They are never shown publicly. The privacy policy explains how this site handles data entered in the registration feature. Tell captains on the form what you will do with their details and how long you will keep them.
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.