Free Fire tournament registration form template
Updated 16 November 2026 · 5 min read · By the Esports Hub team
Short answer
A Free Fire tournament registration form needs the team name, captain contact, each player's in-game name and UID, the roster and substitute, and a rules agreement. Collect only what you need, and confirm each slot by message so teams know they are in.
A good registration form saves the whole event, and a bad one ends in 60 messages asking whether a team is in. Below is the field list, the privacy limits, a slot confirmation flow and the message to send, ready to copy into your own form or into the registration tool.
The fields to collect
Start with the minimum. Every extra field costs you completion and creates data you must protect.
| Field | Why you need it |
|---|---|
| Team name | Shown on the table and poster |
| Captain name and phone or WhatsApp | The one contact for room details |
| Four player names and in-game UIDs | To check the right players are in the room |
| In-game names | So referees can match the lobby |
| Substitute (optional) | Roster rules, if you allow one |
| City or college | For eligibility or local events |
| Rules agreement | A tick box that the team has read the rules |
The FFWS MEA 2025 rulebook sets a roster of 5 players for a 4-player team, a minimum of 3 rostered players for non-invited teams, at most 2 import players, and says the roster must be final before a published deadline. Use the same structure as a default: four starters and one substitute, with the deadline clear.
What to leave out
Collect nothing you do not use. Skip these unless the event truly needs them:
- Government ID numbers.
- Home addresses of players.
- Payment card details. Use a separate payment provider for fees, and never ask for card or UPI PIN details in a form.
- Photos of players, unless you make ID cards. For that, the player ID cards guide shows a safer approach.
For players under 18, ask for a parent or guardian contact and say how you will use it. Tell teams what you collect, who sees it, and when you will delete it after the event. Put those three lines at the top of the form.
A step-by-step setup
- Write the rules page first and link it from the form. The Free Fire tournament rules guide is a good start.
- Set a registration deadline and a maximum number of teams.
- Build the form with the fields above, with the captain contact as a required field.
- Make the UID field a short text field, and say where to find the UID in the game.
- Test the form on a phone, because players will use one.
- Share the link on your poster and group chats. The poster maker can make a post with the link and the date.
The registration form tool gives you a ready-to-copy form, or a link that collects teams and adds approved ones to your roster.
Slot confirmation
A registration is not a slot until you confirm it. Use three states and tell teams which one they are in:
- Received: the form is in, nothing guaranteed.
- Confirmed: a slot is held. The team gets room timing and rules.
- Waitlisted: a place if another team drops.
Send the confirmation within a day of the form, so teams do not register twice. Here is a message to adapt:
Hi [Captain], your team [Team name] is confirmed for [Event name] on [date]. Check-in opens at [time]. The room ID and password will be sent here [15] minutes before the first match. Rules: [link]. Reply with YES to keep your slot by [deadline].
Teams that do not reply by the deadline lose the slot, and the waitlist moves up.
After the form closes
Export the list and check it before the event.
- Remove duplicates, such as one captain registering twice.
- Check that the number of confirmed teams fits your lobbies. The battle royale format guide shows how to count.
- Print a check-in list. For larger events, the gate check-in scanner works with QR passes.
- Delete personal data you no longer need after the event, as you promised on the form.
Common mistakes
- Asking for too much, so teams give up halfway through the form.
- No deadline, so registrations trickle in during the event.
- Forgetting the captain's phone number.
- Not saying where to find the UID.
- Sending the room ID and password with the confirmation, days early. Send it just before the match.
- Leaving the form open after your slots are full without saying so.
Questions and answers
The things people ask most about this, answered plainly.
What should a Free Fire registration form ask for?
At least the team name, the captain's name and contact, each player's name and in-game UID, the substitute if you allow one, and a tick box for the rules. Add city or college only if your event needs it. Keep it short, because every extra field makes teams less likely to finish the form.
How do I confirm a team's slot in a Free Fire tournament?
Send a message to the captain within a day of the form saying the slot is confirmed, with the date, check-in time and rules link, and ask for a reply by a deadline. If the team does not reply, give the slot to the next team on the waitlist. Keep a simple list with three states: received, confirmed and waitlisted.
Is it safe to collect players' details for a gaming event?
It is safe if you collect only what you need, explain how you will use it, store the sheet with access limited to organisers, and delete it after the event. Do not ask for government ID numbers or payment card details in a form. For players under 18, ask for a guardian's contact and say why.
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.