Describe your school, enrollment process, and district wording. Makeform turns the brief into a family-friendly home language survey covering languages a student first learned, uses, understands, and hears at home, plus the family's communication preference. Registrars get structured answers to route for staff review.
Route enrollment responses to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt that matches your enrollment workflow, adapt the wording, or send it to the Makeform builder. The field structure is an example for staff review, not an eligibility or placement decision.
Audience
Parents and guardians enrolling a new K–12 student
Format
Short required survey with conditional language details
Prompt size
704 chars
Example survey structure
Short required survey with conditional language details
Student, school, grade, and family contact
What language did the student first learn?
What language does the student use most often?
What languages do adults use with the student?
Language details and interpreter request
Suggested routing tags
English only reported
Language review needed
Interpreter requested
Ask separately about the language first learned, the language the student uses most, and languages used by adults at home. One broad question can hide a multilingual student's actual language experience.
Step 1
Enroll
family completes the survey with registration
Step 2
Identify
separate questions reveal the student's language context
Step 3
Route
responses needing attention reach the right staff queue
Step 4
Follow up
staff handle screening, records, and family contact
Why the questions matter
A useful home language survey separates what the student first learned, what the student uses, and what family members use at home. Those distinctions give trained staff a clearer starting point for the district's review process.
First-learned language, student-use language, and adult-to-student language each get their own required question. A family can report multiple languages without forcing a single 'primary' label that loses context.
Conditional logic can reveal language names, use patterns, prior services, and interpreter needs after a qualifying response, while families reporting only English move through a shorter path.
Tags and notifications can flag a submission for designated staff. The survey gathers enrollment information; your school keeps screening, program decisions, and family communication in the hands of its established team.
Built around enrollment
Keep the district's approved questions consistent, then tailor the surrounding identity, prior-school, and communication fields to the moment when each family enters.
Place the survey immediately after student and guardian details, carry over the student ID, and avoid asking families to type the same enrollment information twice.
Use age-appropriate prompts about languages heard from birth, current communication, and who speaks each language with the child rather than asking families to rate proficiency.
Add former schools, countries and dates of attendance, and any prior screening or services the family knows about so staff know which records to request.
Record preferred spoken and written languages, interpreter requests, and the best contact channel separately from the student's language responses.
Enrollment workflow
Start with the exact questions your school uses, make multilingual answers easy to report, and define what staff should see after a family submits.
Tell Makeform the grade range, campuses, who completes the survey, when it appears in registration, and the exact language questions or district text you need preserved.
Add the languages common in your community, keep an 'another language' write-in, allow multiple selections, and check that a non-English response opens the intended details.
Ask preferred spoken and written language, interpreter need, and contact method as separate questions. A student's home language does not necessarily equal a caregiver's communication preference.
Submit English-only, multilingual, write-in, and interpreter-request test cases. Confirm each reaches the intended registrar or language-services workflow with enough context for follow-up.
Question design
The survey should collect observable language history and use. Screening results and program decisions belong in the later workflow your school has established.
Field guide
Use these six sections as a drafting checklist, then align labels, notices, and routing with your school's approved enrollment process. The goal is a complete, understandable family response that staff can act on.
Student match
Start with the identifiers staff need to match the survey to registration. Consistently formatted fields reduce duplicate records when siblings enroll together or a student uses a preferred name.
Core questions
Ask each core question on its own screen or line. Do not collapse first language, current student use, and household use into one field. Let families choose multiple languages and write in a language, dialect, or sign language that is not listed.
Language detail
When a response calls for more context, carry the selected language into a short conditional section. Ask about people, settings, and frequency rather than making caregivers assign a technical proficiency level they may not know how to judge.
Prior experience
Transfer families may remember language instruction or screening but not the program name. Use optional prompts and preserve uncertainty instead of requiring a guess.
Family access
Communication preference is a separate operational need. Ask the caregiver directly which language works best for speaking and writing, whether an interpreter is wanted, and which channel is easiest. Do not infer these choices from the student's answers.
Staff handoff
A completed survey is useful only when it arrives with a clear owner. Design tags and notifications around the actual enrollment workflow, such as registrar completeness review, language-services follow-up, interpreter coordination, or records requests.
Related tools
Pair the language questions with registration, family contact, feedback, and translation-request forms while keeping each step focused on one job.
Collect the broader student, guardian, grade, campus, and registration details around the language survey.
Open toolStart from a historical enrollment tool for a general student registration workflow.
Open toolGather program-specific student and family details after the school-day enrollment is complete.
Open toolAsk participants which language they prefer for communication in a focused standalone form.
Open toolRoute requests to translate family notices, enrollment materials, or other school content.
Open toolInvite families to share how enrollment, communication, and school services worked for them.
Open toolFAQ
Practical answers for registrars, enrollment teams, and school staff building a clearer family intake flow.
A home language survey is an enrollment questionnaire describing the student's language background. It asks which language the student first learned, uses most often, and hears from parents, guardians, or other adults. Schools can use responses as a signal for trained staff to review under their established process. The survey should not label proficiency or make a placement decision.
Begin with the student's identifying enrollment details, then ask the core language questions separately: first-learned language, language or languages the student uses most often, and languages adults use with the student at home. Allow multiple selections and a write-in response. Useful follow-ups can cover who uses each language, how frequently, prior schools or language services if known, and the family's preferred spoken and written communication language. Keep interpreter requests separate so they are easy to route.
No. A reported language other than English gives school staff information to review; it is not by itself a language-proficiency result or placement decision. The next steps depend on the school's established procedures and may include checking records, speaking with the family, and conducting an appropriate screening through trained staff. In the form, use neutral routing such as 'language review needed' instead of automatically assigning an ELL or multilingual learner status.
Yes. The form should support multiple languages because a student may hear one language from a grandparent, use another with siblings, and use English at school. Use checkboxes or a repeatable language section, always include an 'another language' write-in, and consider optional fields for dialect or sign language. Asking who uses each language and in what setting gives staff more useful context than forcing the family to choose one primary language.
Ask it directly and separately from the student's language background. A caregiver's preferred language may differ from the language a student uses most often. Include one question for spoken conversations or meetings, another for written notices, and a clear interpreter-request option. You can also ask for the best contact channel and scheduling notes. Route interpreter requests to the staff member who coordinates family communication rather than leaving them buried in the general submission.
Yes. Conditional logic can show relevant questions when a family reports another language, previous language support, or an interpreter need. Selecting two languages can open a repeatable section asking who uses each and how often. Test multiple selections and write-in answers so responses reach staff review and every required field fits.
Use short sentences, one concept per question, familiar family language, and examples only where they clarify the task. Avoid asking caregivers to rate technical proficiency or interpret school acronyms. Offer translated versions or language support according to your school's process, keep the visual order consistent across versions, and test the survey on a phone. Add a contact for questions and make clear that families may list every language relevant to the student.
Yes. Makeform is unlimited free for creating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge. Before using a generated survey, match your school's approved wording, test conditional paths, confirm notifications, and have the responsible team review how submissions enter its screening and communication workflow.
Make language context part of a welcoming enrollment.
