Describe your guild. Makeform creates an editable guild application form for experience, availability, goals, roles, references, and conduct expectations.
Route new applications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adjust it, or send it to the Makeform builder.
Audience
Players applying for a progression roster
Format
Role-based application with availability and logs
Prompt size
411 chars
Example form structure
Role-based application with availability and logs
Character, server, class, and specialization
Profile and combat-log links
Which raid nights can you attend?
Describe your recent progression experience
I have read the attendance and conduct rules
Suggested review tags
Ready to interview
Needs follow-up
Not a fit
Ask for specific availability and time zone so answers align with raid, event, or workshop schedules.
Step 1
Apply
identity, experience, goals, and availability
Step 2
Screen
officers compare required answers consistently
Step 3
Meet
shortlisted applicants move to chat or tryout
Step 4
Decide
accept, waitlist, or close the application
Better member screening
Gather the same evidence from every prospect so officers can review fit without reconstructing chat conversations.
Require profiles or portfolios, time zone, availability, and goals before review.
Show specialist questions only for the selected role, team, or craft interest.
Keep complete submissions together with consistent review tags.
Guild-ready starting points
Keep a screening core, then add evidence that matches your roster or workshop.
Collect character data, performance links, progression, attendance, and role flexibility.
Focus on interests, time zone, communication, referrals, and conduct.
Compare rank, team history, practice schedule, clips, and preferred role.
Review discipline, portfolios, teaching interests, availability, and studio expectations.
Application workflow
Publish one application link based on your acceptance criteria and review path.
Name the game or craft, needed roles, experience, schedule, and community values.
Use your terminology, add role follow-ups, and require essential evidence.
Notify recruiters and store structured answers in a shared review sheet.
Tag follow-up, tryout, waitlist, acceptance, or decline consistently.
Application form vs chat intake
Structured intake helps several officers compare applicants and follow up consistently.
Field guide
Learn who is applying, what they do, when they participate, and whether expectations align.
Identity and contact
Collect the player handle or maker name reviewers use, plus a reliable contact route.
Experience and evidence
Request profiles, logs, clips, portfolios, or work samples only when reviewers use them.
Availability and commitment
Use checkboxes for event nights and collect time zone. Separate required attendance from optional activities.
Motivation and collaboration
Ask why they chose the guild, what they contribute, and for a brief collaboration example.
Roles and conditional paths
Branch from role, game, team, or craft discipline to keep questions relevant.
Expectations and next steps
Summarize conduct, attendance, safety, and trial expectations, then explain the next step.
Related tools
Connect applications with member interest, registration, and departure forms.
Build broader member intake with eligibility and preference fields.
Open toolLearn which events, games, workshops, or roles members want.
Open toolRegister members for meetups, tournaments, and guild events.
Open toolCapture departure reasons and close memberships cleanly.
Open toolFAQ
Practical answers for gaming officers, community moderators, and craft guild coordinators.
A guild application form screens prospective members through consistent questions about identity, experience, roles, availability, goals, evidence, referrals, and guild expectations.
Ask for player handle, game ID, region, time zone, role, experience, profile or gameplay links, availability, goals, referral, and motivation. Request rank, logs, equipment, or voice chat only when reviewers use them.
Use craft discipline, experience, maker biography, portfolio samples, techniques, teaching interests, equipment access, availability, and studio expectations. Show conditional questions to applicants who want to teach or sell at events.
Yes. Branch after a game, role, team, membership type, or craft discipline is selected. Healers can receive role questions, officer candidates leadership prompts, and prospective teachers workshop questions.
Send submissions to a shared inbox or sheet and notify recruiters through Slack or Zapier. Use consistent tags for follow-up, tryout, waitlist, accept, and decline, while keeping internal notes separate.
Yes. Makeform offers unlimited free forms and responses for generating, editing, publishing, and collecting guild applications. The paid tier removes the Makeform badge.
Yes. Summarize attendance, conduct, communication, safety, or trial expectations and add an acknowledgment checkbox. Link to longer current rules and explain how updates are handled.
Show the review path and contact channel. Check required answers, request missing context, and invite shortlisted applicants to a conversation, tryout, event, or workshop. Use consistent decision labels.
Turn interest into a review-ready application.
