Describe your dance rules. Makeform creates a homecoming guest form linking each outside guest to a student sponsor, school details, acknowledgments, and administrator review fields.
Send guest requests to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it to your policies, or send it to the Makeform builder.
Audience
Students inviting a guest from another high school
Format
Guest request with student sponsor and school verification
Prompt size
243 chars
Example form structure
Guest request with student sponsor and school verification
Host student name, grade, and school ID
Outside guest name, age, grade, and school
Guest school administrator contact
Emergency contact name and phone
Dance rules acknowledgment
Suggested routing tags
Pending review
More information needed
Decision recorded
Ask for the student sponsor's school ID and the guest's school contact separately; that gives reviewers two clear reference points.
Step 1
Sponsor
student identifies the outside guest
Step 2
Verify
school and guardian details are checked
Step 3
Review
administrator records a decision
Step 4
Check in
approved guest details support event entry
A clearer guest process
Replace paper slips with one structured request staff can review before the dance.
Capture the enrolled student's name, grade, ID, and contact beside the outside guest's identity and school information.
Required school, emergency-contact, and acknowledgment fields reduce the back-and-forth caused by incomplete paper requests.
Use status, reviewer, decision date, and notes fields so staff can distinguish pending requests from completed decisions.
Adapt it to your dance
Start with the rules your school already uses, then show only the questions relevant to each guest type.
Request the guest's campus, grade, administrator contact, and any verification details your school chooses to review.
Branch to graduation year, former school, and age details when the guest is a recent graduate rather than a current student.
Show guardian contact and acknowledgment questions when age or school policy makes that information relevant.
Keep staff notes and missing-information messages connected to the original student-and-guest submission.
Form setup
Turn event rules and review responsibilities into a clear submission path.
Give the builder your dance date, submission deadline, eligible guest ages or grades, and the information reviewers need.
Add your campus list and policy text, then branch guardian or former-school questions according to the guest's situation.
Send students the public form link and direct new responses to the staff inbox or connected worksheet used for review.
Check the submitted details, request missing information when needed, and record the reviewer, decision, and date on the response.
Online form vs paper slip
The form should support a decision, not merely collect a guest's name. Structured fields make incomplete requests and review status easier to spot.
Field guide
Use these six sections as a practical checklist, then adjust the questions and wording to match your school's event process.
Student sponsor
Start with the student submitting the request. A school ID helps staff match the response to the correct student.
Outside guest
Ask for current identity and contact information. Limit sensitive fields to what your process requires.
School reference
Collect the other school's campus details and staff contact in separate fields so reviewers can find them quickly.
Safety contacts
Make emergency contacts easy for event staff to find. Show guardian questions conditionally when required.
Rules
Present arrival, identification, conduct, and dismissal rules before asking the student and guest to acknowledge them.
Administrative review
Reserve review fields for staff. A status and dated note show what needs attention without changing submitted answers.
Related tools
Create registration, consent, attendance, and feedback forms that complement your outside-guest process.
Collect structured guest details for events that do not need the full school-specific workflow.
Open toolBuild the main attendee registration process for a dance, banquet, or school celebration.
Open toolCreate a separate parent or guardian acknowledgment process when your event plan needs one.
Open toolOrganize student, guardian, emergency-contact, and activity details for off-campus events.
Open toolRecord student attendance in a structured list for school programs and events.
Open toolAsk students and staff what worked after the dance and what should change next year.
Open toolFAQ
Practical answers for school administrators organizing outside-guest requests.
It links an enrolled student to an outside guest, collects contact and school details, presents dance rules, and gives staff fields for recording their review.
Include student sponsor, guest, school, emergency-contact, and acknowledgment fields. Add staff-only status, reviewer, decision date, and notes fields.
Use conditional logic. Current students provide campus contacts; recent graduates provide graduation year and former school. Ask only for details your process requires.
Yes. Show guardian name, relationship, phone, email, and acknowledgment fields only when the guest's answers and your policy require them.
Use separate staff fields for status, reviewer, decision, review date, missing information, and notes. A connected worksheet can provide a shared queue.
Only if it is part of your established process. If staff merely inspect identification at check-in, present that instruction without collecting a copy.
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and collect requests without a form or response cap; the paid tier removes the Makeform badge.
No. Submission starts the school's review. Explain how decisions are communicated and keep a separate staff decision field so submission is not mistaken for approval.
Replace the stack of guest slips.
