Describe your school's housing or disability accommodation process. Makeform turns it into an intake form with request categories, uploads, consent choices, and office routing.
Route requests to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it to your school, or send it to the builder.
Audience
Students requesting a housing adjustment
Format
Conditional housing request with ranked preferences
Prompt size
273 chars
Example form structure
Conditional housing request with ranked preferences
Student identity and school contact
Current housing assignment
Requested housing features
Preferred effective date
Supporting information
Suggested routing tags
Housing review
Accessibility review
More information needed
Ask about the barrier and requested adjustment; avoid forcing a diagnosis into a general text box.
Step 1
Request
student explains the barrier and preferred adjustment
Step 2
Route
housing or accessibility staff receive the right path
Step 3
Review
staff request clarification and assess available options
Step 4
Follow up
student receives next steps through the chosen channel
Why structured intake matters
Scattered emails cause repeated details and incomplete requests. A structured form gathers what staff need to route and begin review without promising an outcome.
Conditional logic shows housing, classroom, or temporary-support questions only when relevant.
Ask about the barrier, adjustment, timing, and setting. Keep uploads optional unless required by your process.
Route submissions to the responsible office and explain next steps, contacts, and updates.
Built around school workflows
Choose a workflow, then replace its choices and contacts with your school's process.
Room features, location considerations, current assignment, effective date, and acceptable alternatives for housing review.
Classroom, testing, communication, and technology requests tied to relevant courses or activities.
Short-term barriers, urgent dates, interim adjustments, and a planned review point in one time-bound request.
Household details, unit features, move-in windows, and ranked alternatives without implying guaranteed placement.
Form-building workflow
Build around what staff need for triage, then test every branch before sharing it.
Name request categories, responsible offices, essential questions, timing, and an alternative way to request help.
Use campus terms, explain why information is requested, and remove unnecessary fields.
Route housing and academic access needs separately while hiding unrelated questions.
Test every branch, keyboard and mobile use, confirmation, notifications, and staff handoff.
Form vs email vs generic document
A form does not decide availability. It creates a consistent starting record for the student and reviewing office.
Field guide
Adapt these six sections to your school's process and have the responsible office review them.
Student and enrollment
Gather only the identifiers staff use to find the student's record and make contact.
Request category
A first question can distinguish housing, academic, technology, transportation, or temporary needs and open the right branch.
Barrier and adjustment
Ask what creates a barrier, what change is requested, and what would improve access.
Supporting information
Explain which files are useful, whether they are optional, and how students can provide them another way.
Timing and priority
Start dates, move windows, tests, and upcoming activities help staff triage without implying approval.
Consent and follow-up
Use specific consent choices, limit notifications, and explain the next step in the confirmation.
Related tools
Build adjacent forms for enrollment, student concerns, technology needs, and accessibility requests using real Makeform tools.
Create a broader accessibility request path for organizations and service teams.
Open toolCollect accommodation registration details for programs, stays, or coordinated services.
Open toolGive students a separate channel for concerns that are not accommodation requests.
Open toolCollect core registration details before routing students to specialized services.
Open toolIdentify device, connectivity, and assistive technology needs across a student group.
Open toolCollect student insurance information in a distinct workflow when the school requires it.
Open toolFAQ
Practical answers for school offices designing a clear intake and routing process.
It lets students describe a barrier, request a housing or disability-related adjustment, share timing, and choose how the school may follow up. It starts review; it does not approve an accommodation.
Include student details, request type, barrier, requested adjustment, affected setting, effective date, alternatives, optional uploads, contact preference, and coordination consent. Remove fields the office does not need.
Yes. Use a request-category question and conditional branches. Show assignment and room questions for housing, or course and adjustment questions for academic requests, then route each submission appropriately.
That depends on school policy. Explain what is relevant, whether upload is optional at intake, and how students can provide information another way. Require a file only when the responsible office chooses to.
Ask only what begins review, explain why, and notify the smallest appropriate staff group. Keep diagnosis details out of broad alerts, offer a safer contact channel, and review access and retention settings.
Yes. Add the barrier start, affected activities, interim adjustments, deadlines, expected duration, and review date. Conditional logic can separate these questions from ongoing requests.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier only removes the Makeform badge.
Show a request reference, receiving office, next step, contact, and correction or withdrawal instructions. Do not promise approval or timing unless the school has a documented commitment.
Turn a complex request into a clear first step.
