Describe your competition and entry rules. Makeform builds an application that captures the roster, eligibility, preferences, and one consistent team record.
Route applications to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor the rules, or send it to the builder. Every example is editable.
Audience
Student teams from one university
Format
Team application with eligibility checks
Prompt size
301 chars
Example form structure
Team application with eligibility checks
Team name and captain contact
List every team member
Degree program and graduation year
Preferred case track
Confirm enrollment and schedule
Suggested routing tags
Eligibility review
Complete roster
Waitlist
Designate one captain and collect every member's university email to keep ownership and roster details clear.
Step 1
Apply
captain submits one complete team record
Step 2
Check
organizers review roster and eligibility
Step 3
Place
team receives a track or waitlist status
Step 4
Confirm
captain acknowledges dates and next steps
Why one team application
A purpose-built application keeps the captain, members, eligibility evidence, preferences, and confirmations together from the first submission.
Collect the captain and complete roster in one entry, so organizers do not have to match four separate signups by team name.
Required confirmations for enrollment, team size, dates, and conduct surface incomplete or ineligible entries before scheduling begins.
Send consistent responses to a sheet or organizer inbox, then filter by division, track preference, institution, or review status.
Adapt the entry path
Start with the closest format and replace the sample rules, dates, divisions, and case tracks with your own.
One captain enters the team name, member roster, academic details, preferences, and confirmations.
Conditional questions separate ready-made teams from students who need matching support.
Add motivation, experience, and case-interest questions when organizers must choose among applicants.
Capture the captain's reliable email and a backup contact for status messages and deadlines.
Build the application
Give the builder your entry rules and review needs, then refine the generated questions before sharing the application link.
Include team size, eligible institutions or programs, divisions, important dates, required documents, and whether individuals may apply.
Make captain contact and roster fields required. Show team-matching questions only to individual applicants and adviser fields only when needed.
Share the form on club and campus channels with the deadline and instructions for captains.
Review submissions by track, division, institution, or status and follow up with the captain when a roster or document is missing.
Application vs email vs basic signup
Connect every member to one captain, eligibility review, and preference set.
Field guide
Build each application around the decisions organizers must make: who is entering, whether the roster qualifies, where the team fits, and how to contact them.
Team identity
Start with a team name and captain. Keep a second contact so deadline messages do not depend on one inbox.
Member roster
Use the same fields for every member. A structured roster supports duplicate checks, badges, room assignments, and organizer lists.
Eligibility
Turn team-size, enrollment, program, and participation rules into direct questions. Keep an organizer review step for evidence.
Fit and preferences
Let teams rank cases or divisions. Keep motivation and experience questions short and tied to selection criteria.
Schedule and access
List every required date. Use separate optional fields for accessibility and dietary requests so organizers can plan support.
Expectations
Place your conduct, originality, confidentiality, and withdrawal expectations beside the confirmation fields.
Related tools
Connect applications with registration, pitch collection, judging, feedback, and outreach.
Collect attendance details after teams are selected or open supporting sessions to guests.
Open toolGather structured pitch details, links, and summaries for entrepreneurial competition entries.
Open toolCreate a scoring form for judges evaluating submissions against shared criteria.
Open toolAsk participants about the case, schedule, mentoring, judging, and overall experience.
Open toolRecruit members and volunteers before opening your club's competition applications.
Open toolCollect structured student feedback for a post-competition review and next-year planning.
Open toolFAQ
Practical answers for university clubs, faculty organizers, and competition teams.
It is the team entry record for a case competition. It connects the captain, roster, academic details, eligibility, preferences, motivation, and availability for organizer review.
Include team, institution, captain, roster, academic details, eligibility, case preference, date availability, and acknowledgments. Request uploads only when organizers will review them.
Usually one captain submits the full team. If individuals can request matching, branch them to skills, interests, and availability questions instead.
Yes. Explain what is requested and collect only what review requires. Treat uploads as review material, not automatic proof of eligibility.
Use ranked preferences and request a second choice when capacity is limited. Add a short description so every team chooses with the same information.
Yes. Branch complete teams to roster fields and individuals to skills, preferred role, case interests, and matching availability.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect applications without a response cap. The paid tier removes the Makeform badge.
Organizers review the record or route it to connected tools. Use statuses such as incomplete, eligibility review, selected, and waitlisted, then contact the captain. The form does not select teams.
Open applications with one clear team record.
