Player identity
Connect the person to the account.
Collect chosen name, gamertag, contact, region, and time zone. Avoid unrelated identity details.
- Gamertag and account identifier.
- Reliable email or Discord contact.
- Region, time zone, and platform.
Describe your game, roster needs, and schedule. Makeform creates an e sport team application form for gamertags, ranks, roles, availability, and gameplay links.
Route player applications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, and send it to the builder. Each structure is an editable example.
Audience
Ranked players applying for an open starting position
Format
Role-based application with profile and clip links
Prompt size
308 chars
Example form structure
Role-based application with profile and clip links
Gamertag, platform, region, and time zone
Current rank, peak rank, and profile link
Primary and secondary roles
Practice and tryout availability
Gameplay or VOD links
Suggested routing tags
Needs review
Tryout invite
Not this split
Ask for both the player's displayed rank and a profile or tracker link so reviewers can interpret self-reported competitive experience consistently.
Step 1
Apply
player identity, gamertag, rank, and role
Step 2
Screen
profile, experience, region, and schedule checked
Step 3
Try out
shortlisted players receive a session slot
Step 4
Select
decisions and roster status stay organized
A better first screen
A structured application makes rank, role fit, region, and schedule visible before tryout slots are assigned.
Rank, profile, role, and team-history fields give reviewers the same screening view.
Separate primary and backup roles so coaches can focus on open roster slots.
Collect time zones and time windows before assigning practices or matches.
Fits your competition format
Adapt ranks, roles, and screening depth to your recruitment program.
Rank history, results, VODs, roles, and fixed practice availability.
Player goals, skill tier, schedule, and conditional guardian contact.
Gamertags, preferred modes, play times, expectations, and conduct acknowledgment.
Division, region, roles, and availability for captain review.
Application workflow
Describe the players you need, adjust the questions, publish, and route submissions for review.
Name the game, level, open positions, regions, practice windows, and experience.
Use the game's ranks and roles, request profile links, and remove irrelevant details.
Publish the link and send applicants a clear submission receipt.
Label responses by role and region, then contact shortlisted players with tryout sessions.
Form vs chat recruitment
A consistent form reduces repeated questions and makes roster constraints visible.
Field guide
Use six focused sections to collect useful first-review evidence.
Player identity
Collect chosen name, gamertag, contact, region, and time zone. Avoid unrelated identity details.
Rank and account
Ask for current and peak rank, season, and a profile or tracker URL.
Roles and pool
Use fixed options for primary role, backup role, and character pool.
Competitive evidence
Team history, tournament experience, and selected VODs give coaches screening material.
Schedule and setup
Collect recurring availability, conflicts, and only the setup details needed for competition.
Fit and expectations
Ask about motivation and show conduct, attendance, and communication expectations.
Related tools
Pair the team application with live tryout registration, general player intake, tournament signup, sponsorship, and event registration tools.
Collect session choices and the details needed to place shortlisted players into live tryouts.
Open toolCreate a broader player intake for leagues, clubs, camps, or recurring competition programs.
Open toolRegister squads for a game-specific tournament with participant and event information.
Open toolCollect team or individual entries for brackets, match scheduling, and organizer follow-up.
Open toolGather sponsorship requests and creator or team details in a separate review process.
Open toolBuild registration for showcases, viewing events, LAN sessions, or community meetups.
Open toolFAQ
Practical answers for coaches, managers, and league organizers planning player intake and tryouts.
It is a structured intake for prospective esports players. It gathers gamertag, rank, role, experience, region, time zone, availability, and gameplay links before tryouts, giving organizers consistent responses to compare.
Collect gamertag, platform, region, time zone, current and peak rank, profile link, roles, team experience, and practice and match availability. Add VOD links only when reviewers will use them.
Use separate fields for current rank, peak rank, and season. Include a public profile or tracker URL when available. Structured fields make filtering easier than one long answer.
Yes. List practice and match windows as checkboxes, require a time zone, and provide a field for recurring conflicts. Name the organizer time zone beside every scheduled time.
Yes. Add URL fields for profiles, tracker pages, VODs, replays, or highlights. State how many links reviewers want and whether they prefer full matches or short clips.
Set program rules, collect only needed details, and conditionally show a guardian contact when your process requires it. Explain who receives the application and review safeguarding needs for your region.
Yes. Makeform offers unlimited free forms and responses for generating, editing, publishing, and receiving applications. The paid tier removes the Makeform badge.
Send a receipt, route responses to the correct reviewer, and label them by role, region, and availability. Contact shortlisted players with tryout options and update applicants when decisions are complete.
Turn roster interest into complete applications.