Loading...
education

Homeless Student (McKinney-Vento) Eligibility and Services Form

This Homeless Student (McKinney-Vento) Eligibility and Services Form records eligibility, enrollment needs, transportation, and support services so a student can stay in school without delay.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: K 12 Education · Public School Districts · Charter Schools

Overview

This Homeless Student (McKinney-Vento) Eligibility and Services Form is built to document whether a student qualifies for McKinney-Vento protections and what supports are needed to keep school access stable. It combines the eligibility review, enrollment needs, transportation planning, and sign-off into one structured record so staff do not have to reconstruct the case from scattered notes.

Use this template when a student may be living in a shelter, motel, doubled-up arrangement, temporary housing, or another situation that affects school continuity. It is also appropriate for unaccompanied youth cases where the school needs to confirm eligibility and coordinate immediate enrollment, records transfer, school of origin placement, and transportation. The form is especially useful when multiple staff members need a shared case record with a clear review date and decision summary.

Do not use this template as a general student intake form or for routine enrollment that does not involve housing instability. It should also not collect extra personal data that is not needed to determine eligibility or arrange services. If your workflow does not require transportation planning, service coordination, or a documented determination, a simpler referral or support request form may be a better fit. The value of this template is that it keeps the case focused on the fields that matter for access, stability, and follow-through.

Standards & compliance context

  • Collect only the PII needed to determine McKinney-Vento eligibility and arrange services, consistent with the minimum-necessary principle.
  • If the form is public-facing or self-service, the layout and controls should support WCAG 2.1 AA accessibility, including clear labels and keyboard-friendly inputs.
  • When collecting student or family information, include a consent or disclosure statement that explains how the data will be used and shared within the school process.
  • Maintain an audit trail with review dates, decision summaries, and staff sign-off so eligibility and service decisions are traceable.
  • If the student is unaccompanied or requests support without a parent or guardian present, the workflow should still allow enrollment and service coordination without unnecessary delay.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice and Privacy Disclosure

This section tells the submitter why the form exists, what information will be collected, and how PII will be used before any case details are entered.

  • I understand this form is used to review McKinney-Vento eligibility and document school supports. (required)
  • Consent to collect and use the information provided for eligibility review and service coordination (required)

    By submitting, you consent to the collection and use of the minimum necessary PII for school enrollment, transportation, and support coordination.

  • Request anonymous submission for initial concern reporting

    Select only if you want to submit a concern without identifying the student initially. A follow-up may be needed to complete eligibility review.

  • Submitter role (required)

Student and Case Identification

This section ties the eligibility review to the correct student and case record so services and follow-up are not misassigned.

  • Student full name (required)
  • Student date of birth

    Provide only if needed to match the student record.

  • Student ID

    Optional if the student already has a district ID.

  • Current or requested school (required)
  • Grade level (required)
  • Case open date (required)

McKinney-Vento Eligibility Review

This section captures the housing situation and eligibility basis needed to determine whether McKinney-Vento protections apply.

  • Current housing situation (required)
  • Is the student an unaccompanied youth? (required)
  • Eligibility basis (required)
  • Eligibility determination (required)
  • Determination notes

    Record only objective facts needed for the audit trail and case review. Avoid unnecessary personal details.

Enrollment and School Stability Supports

This section documents the immediate enrollment and school continuity actions needed to keep the student in class without avoidable delay.

  • Immediate enrollment support needed (required)
  • Records or documents needed for enrollment
  • School of origin requested (required)
  • School stability supports needed

Transportation and Service Plan

This section records how the student will get to school and what additional supports are needed to make the plan workable.

  • Transportation to school of origin needed (required)
  • Transportation mode
  • Transportation start date
  • Additional services requested

Review, Sign-Off, and Audit Trail

This section creates the decision record, confirms review, and preserves accountability for later follow-up or audit.

  • McKinney-Vento liaison name (required)
  • Review date (required)
  • Decision summary (required)

    Summarize the eligibility decision and the supports approved.

  • Parent/guardian or youth signature

    Use when signature is available and appropriate.

  • Staff signature (required)

How to use this template

  1. 1. Add the form to your district workflow with required fields limited to the information needed for eligibility, enrollment, and service coordination.
  2. 2. Assign the case to the homeless liaison or designated staff member who will review the housing situation and complete the eligibility determination.
  3. 3. Capture the student’s identification details, then use conditional logic to show only the eligibility and support fields that apply to the case.
  4. 4. Record the enrollment and transportation plan, including school of origin, records needed, service start date, and any additional supports.
  5. 5. Review the completed form, obtain the necessary staff and parent or guardian sign-off when applicable, and save the decision summary in the audit trail.

Best practices

  • Use progressive disclosure so unaccompanied youth, transportation, and additional services only appear when they are relevant.
  • Mark required and optional fields clearly, and keep the required set as small as possible to support data minimization.
  • Use a date picker for dates, dropdowns or radio buttons for eligibility and transportation choices, and multi-select fields for service needs.
  • Include a plain-language disclosure that explains what the information will be used for and who can access it.
  • Offer an anonymous submission path only if your district accepts initial concerns that way, and explain how follow-up will work.
  • Record the school of origin request and transportation start date in the same case so service delays are easy to spot.
  • Write determination notes in plain language so another staff member can understand the basis for the decision without re-interviewing the family.

What this template typically catches

Issues teams running this template most often surface in practice:

Housing situation is described too vaguely to support an eligibility decision.
The form asks for unnecessary PII instead of only the fields needed for the case.
Eligibility basis and determination notes are left blank, making the decision hard to review later.
Transportation is requested but the mode and start date are not captured, delaying service setup.
School of origin is not recorded even when the student needs stability across school changes.
Staff forget to document whether records are needed for immediate enrollment.
Sign-off fields are missing, so the case has no clear audit trail.

Common use cases

District Homeless Liaison Intake
A district liaison opens a new McKinney-Vento case after a family reports temporary housing. The form captures eligibility, school stability needs, and the service plan in one place so the liaison can act quickly.
Unaccompanied Youth Enrollment Support
A high school counselor uses the template when a student is living without a parent or guardian and needs immediate enrollment. Conditional fields help the counselor document the basis for eligibility and the supports needed to keep the student attending.
School of Origin Transportation Plan
Transportation staff and the liaison use the form to record the requested mode, start date, and any additional service needs. This keeps the transportation request tied to the eligibility record instead of living in a separate email thread.
Case Review and Renewal
At a later review, staff reopen the form to confirm whether the student’s housing situation or support needs have changed. The review date, decision summary, and signatures create a clear history for the case file.

Frequently asked questions

Who should use this McKinney-Vento eligibility form?

School district homeless liaisons, enrollment staff, counselors, and case managers use this form to document eligibility and coordinate services. It is also useful when a student is unaccompanied or needs immediate enrollment support. The form is designed to create a clear record for school access decisions and follow-up actions.

What situations does this template cover?

This template covers housing instability, unaccompanied youth, school of origin requests, transportation needs, and related support services. It is meant for students whose living situation may affect enrollment, attendance, or continuity of education. If the student does not have a homelessness-related school access issue, a different intake form is usually a better fit.

How often should this form be completed or updated?

Complete it when a case is opened, when eligibility is reviewed, and whenever the student’s housing, enrollment, or transportation needs change. Many districts also update it during periodic case reviews or at the start of a new school year if the student remains eligible. Keep the review date and decision summary current so the record reflects the latest status.

What information should be collected, and what should be avoided?

Collect only the fields needed to determine eligibility and arrange services, such as housing situation, school of origin request, and transportation mode. Use the minimum-necessary principle and avoid collecting extra PII that does not affect the decision. If you need a consent or disclosure step, make it clear what information will be used and who will see it.

How does this template support accessibility and privacy requirements?

The form should use clear labels, required-versus-optional markers, and field types that match the data being entered. For public-facing or self-service versions, WCAG 2.1 AA accessibility matters, and any PII collection should include a plain-language privacy disclosure. If anonymous submission is allowed for an initial concern report, the form should still explain what happens after submission.

What are common mistakes when using this form?

Common mistakes include making every field required, asking for unnecessary identifiers, and using free-text fields where a date picker or dropdown would be more accurate. Another issue is skipping the determination notes, which makes later review harder. Teams also sometimes forget to record transportation start dates or the staff sign-off needed for an audit trail.

Can this template be customized for district workflows or integrations?

Yes. You can add conditional logic for unaccompanied youth, branch transportation questions by mode, and tailor the service list to local supports. Many districts connect the form to student information systems, case management tools, or ticketing workflows so enrollment, transportation, and follow-up tasks are assigned automatically.

How does this compare with handling McKinney-Vento cases by email or paper notes?

Email threads and paper notes make it harder to track eligibility decisions, service requests, and review history in one place. This template creates a structured record with consistent fields, which reduces missed steps and supports an audit trail. It also helps different staff members work from the same case information without duplicating questions.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Homeless Student (McKinney-Vento) Eligibility and Services Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?