Describe your game and bracket format. Makeform creates a gaming tournament registration form for player contacts, gamertags, rosters, platform IDs, divisions, and availability.
Route tournament entries to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a tournament brief, tailor it, or send it to the editable Makeform builder.
Audience
Individual players entering an online one-versus-one event
Format
Player entry with platform and availability fields
Prompt size
264 chars
Example form structure
Player entry with platform and availability fields
Player name, gamertag, and contact
Platform and exact in-game ID
Which skill division fits you?
Which round times can you attend?
I have read the event code of conduct
Suggested routing tags
Solo entrants
Team rosters
Needs follow-up
Ask for the exact in-game ID used for invitations, not only a display name that may be shared by several players.
Step 1
Enter
player or captain chooses the right path
Step 2
Identify
gamertags, contacts, platform IDs, and region
Step 3
Roster
starters, substitutes, roles, and availability
Step 4
Organize
entries arrive ready for seeding and follow-up
Cleaner tournament intake
A structured form prevents scattered nicknames, contacts, and roster details from slowing bracket preparation.
Show an individual profile or captain-led roster based on entry type.
Collect gamertag, exact in-game ID, platform, region, and Discord username in labeled fields so organizers know both who to invite and how to reach them.
Required contacts and organizer notifications make missing details visible early.
Flexible event formats
Choose a setup, then edit the game, roster size, divisions, and schedule.
Gamertag, player ID, platform, region, skill division, and round availability for individual entrants.
Captain contact, team identity, starters, substitutes, player roles, and roster confirmation in a single entry.
Time zones, recurring match windows, server region, and communication handles for distributed competitors.
Arrival plans, equipment lists, venue needs, and accessibility requests alongside the competitive roster.
Registration workflow
Describe the tournament, refine the questions, and share the registration link.
Name the game, platform, roster size, region, divisions, schedule, and entry method.
Add real divisions and match windows. Require captain contact, gamertag, ID, and roster slots.
Show roster fields to captains and matching questions to players seeking teammates.
Share the link and send entries to an inbox or roster sheet.
Form vs chat vs spreadsheet
A useful intake gives every entrant the same identity, roster, platform, and availability questions.
Field guide
The best field list follows the organizer's work after submission: identify the entrant, build the roster, place the team correctly, schedule matches, and handle practical requests.
Entry identity
Separate individual and team entries. Collect a reliable contact plus the public identity used in competition.
Roster
Give every roster position the same questions so starters, substitutes, and captains are immediately clear.
Game setup
Ask for the platform and account identifier used for invitations, plus only the regions and modes offered.
Placement
Offer real event divisions and request concise experience details only when they help seeding.
Schedule
Show dates and time zones beside availability choices. Ask for recurring windows or known conflicts as appropriate.
Event operations
Keep practical requests and code-of-conduct acknowledgment in separate fields so organizers can act on them.
Related tools
Continue with player, tryout, contest, or sponsorship intake.
Create a general player profile and contact intake for leagues, clubs, or competitive events.
Open toolStart with broad tournament entry fields and tailor them to your game and bracket format.
Open toolCollect player roles, availability, and experience before team selection or a qualifier.
Open toolAdapt a tournament intake built around a recognizable esports competition use case.
Open toolRegister entrants for a broader contest when brackets and team rosters are not required.
Open toolGather audience, campaign, and partnership details from teams or gaming creators seeking sponsorship.
Open toolFAQ
Practical answers for esports organizers collecting solo and team entries online.
Collect name and contact, gamertag, in-game ID, platform, region, division, and availability. Team events also need a captain contact, starters, substitutes, and roles. Add setup requests and conduct acknowledgment where relevant.
Yes. An entry-type choice can show one player profile for individuals or captain, team, starter, and substitute fields for teams. One link then serves both paths.
Separate the public gamertag from the account ID used for invitations. Ask for platform, explain the expected ID format, and collect email or a community handle for follow-up.
Give each starter a consistent slot for gamertag, ID, platform, and role. Keep substitutes optional and add roster confirmation. State roster size and replacement deadlines in the event details.
Yes. Add an upload for a team logo or relevant supporting item. Explain what is accepted, but keep identity details in normal fields so staff can build the roster without opening files.
Use dropdowns for offered regions and divisions, then checkboxes for match windows labeled with the time zone. Conditional logic can reveal division or LAN fields when relevant.
Yes. Makeform offers unlimited free forms and unlimited free responses, so you can generate, edit, publish, and collect tournament registrations without a response cap. The paid tier only removes the Makeform badge.
Responses arrive in the Makeform inbox and can route to Google Sheets, Slack, or Zapier. A roster sheet helps organizers check team size, group divisions, and resolve missing IDs.
Turn interest into complete entries.
