English Learner Identification and Service Plan Documentation
Use this English Learner Identification and Service Plan Documentation template to record the home-language survey, EL screening, placement decision, and annual service plan in one place. It helps schools document eligibility, services, and sign-off with clear privacy language and an audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: K 12 Public Schools · Charter Schools · Private Schools · District Student Services
Overview
This template documents the full EL intake path in one form: submission notice, privacy disclosure, home-language survey, screening results, placement decision, annual service plan, and team sign-off. It is built for school staff who need a consistent record of how a student was identified, what language background information was collected, and what supports were assigned.
Use it when a student may qualify for English learner services, when a family reports a change in language background, or when you need to update the annual service plan for an already-identified student. The structure helps you keep required fields focused on the decision-making process, while optional or conditional fields can capture details only when they apply. That makes it easier to follow data minimization and avoid collecting unnecessary PII.
Do not use this template as a general admissions form or a broad student profile. It is not meant for unrelated health, discipline, or academic records. It also should not be used to collect more language history than your process needs, or to replace a separate consent workflow if your district requires one for service delivery. The goal is a clean audit trail that shows what was asked, what was reviewed, what decision was made, and what plan will be followed next.
Standards & compliance context
- The submission notice and privacy disclosure support data minimization by collecting only the language information needed for EL identification and service planning.
- Clear field labels, required indicators, and structured inputs help align the form with WCAG 2.1 AA accessibility expectations for public-facing school forms.
- If guardian acknowledgement is used, separate acknowledgement of receipt from consent to services so the record is not ambiguous.
- The annual service plan and team sign-off create an audit trail that supports consistent documentation of placement and review decisions.
- Conditional logic helps prevent over-collection of PII by showing follow-up fields only when they are relevant.
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 explains why language information is being collected, who it is for, and what will happen after submission.
- I understand this form is used to document EL identification and service planning.
- I acknowledge that student information will be used only for educational placement, service planning, and compliance purposes.
- Consent to collect and use language background information for educational placement
- Who is completing this form?
Student and Case Identification
This section ties the record to the correct student and school so the screening and service plan can be tracked without ambiguity.
- Student ID
- Student Name
-
Date of Birth
Collect only if needed to match the student record.
- School Name
- Grade Level
Home-Language Survey
This section captures the minimum language background needed to decide whether screening or follow-up is required.
- What language is most often spoken at home?
- What was the first language the student learned?
- Other languages used by the student or family
- Has the language used at home changed since the last school year?
-
Describe the change in language background
Briefly describe the change and when it occurred.
EL Identification and Placement
This section records the screening outcome and the placement decision that determines whether the student receives EL services.
- Was a language screening completed?
- Screening Date
- Screening Result
- English Learner Identification Status
- Placement Decision
-
Placement Notes
Include only placement details needed for service delivery.
Annual EL Service Plan
This section defines the student’s service model, frequency, minutes, goals, and review date for the current year.
- Service Year
- Service Model
- Service Frequency
- Minutes of EL Support per Week
-
Language Support Goals
Summarize the annual language development goals and supports.
- Review Date
Team Members and Sign-Off
This section documents who reviewed the plan, who acknowledged it, and any final notes needed for the audit trail.
- Case Manager Name
- Guardian acknowledgement received
- Team Members
- Final Comments
How to use this template
- 1. Configure the submission notice, privacy disclosure, and consent language so staff and guardians understand why language information is collected and what happens after submission.
- 2. Map the student identification fields to your roster or SIS so staff can enter the student record once and avoid duplicate data entry.
- 3. Set conditional logic for the home-language survey so follow-up fields only appear when a language background change or additional language use is reported.
- 4. Define the EL screening and placement options to match your district process, including who completes the screening, how the result is recorded, and who approves placement.
- 5. Add the annual service plan details, then assign the case manager to review service minutes, goals, and the next review date before the form is finalized.
- 6. Collect guardian acknowledgement and team sign-off, then store the submission in your audit trail and use the final comments field for any exceptions or handoff notes.
Best practices
- Mark required fields only where the information is necessary for identification, placement, or annual review.
- Use a date picker for dates, numeric input for service minutes, and multi-select for languages used so the data is clean and searchable.
- Trigger conditional logic for language-background change details only when the student’s situation has changed.
- Keep the privacy disclosure plain and specific about who can view the record, why it is collected, and how long it will be retained.
- Record the screening date, result, and placement decision in separate fields so the audit trail is easy to follow.
- Use the review date to drive reminders for annual service plan updates instead of relying on memory.
- Limit final comments to exceptions, clarifications, or handoff notes so the form stays usable and focused.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this template?
Use it for students who may qualify for English learner services and need a documented path from home-language survey to placement and annual review. It is typically completed by an enrollment specialist, EL coordinator, case manager, or designated school staff member. The template also supports guardian acknowledgement and team sign-off when your process requires it.
When should this form be completed?
Complete the home-language survey at enrollment or when a student’s language background changes, then use the same record to capture screening and placement decisions. The annual service plan section should be updated on your school year cadence or whenever the student’s EL supports are formally reviewed. If a student exits services or changes schools, keep the record current so the next team can see the full history.
What is the difference between identification and the annual service plan?
Identification documents whether the student meets your EL criteria after screening and review. The annual service plan documents what supports the student will receive, how often, and who is responsible for the plan. Keeping those sections separate helps prevent confusion between eligibility decisions and service delivery.
What fields are most important to customize?
Most schools customize the screening result options, placement decision language, service model choices, and the review cadence to match local procedures. You may also want to adjust the team member list, guardian acknowledgement wording, and final comments field to fit your workflow. Keep required vs optional fields clear so staff only collect what they need.
Does this template support privacy and consent language?
Yes. The submission notice and privacy disclosure section is designed to explain why language information is collected, who will use it, and what happens after submission. That helps you follow data minimization principles by collecting only the PII needed for identification and service planning. If your district allows anonymous questions elsewhere, keep this form identified because it is tied to a student record.
What are common mistakes when using this form?
A common mistake is asking for too much language history in free-text fields instead of using structured fields and conditional logic. Another is leaving the placement decision or review date blank, which breaks the audit trail. Schools also sometimes forget to distinguish guardian acknowledgement from consent to provide services, which can create confusion in the record.
How does this compare with ad-hoc spreadsheets or email threads?
A structured form keeps the same fields in the same order every time, which makes screening, placement, and annual review easier to track. It also reduces missed steps because the submission notice, decision fields, and sign-off are all in one workflow. Compared with email, it is easier to search, review, and hand off between staff members.
Can this template connect to other systems?
Yes, it can be paired with student information systems, case management tools, or document storage through integrations or exports. The most useful connections are to roster systems for student identity, notification workflows for guardians, and reporting tools for EL caseload tracking. Keep the integration scope limited to what you actually use so you do not duplicate data entry.
Related templates
Go deeper on the topic
-
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 —...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
MangoApps is named a Leader in the IDC MarketScape for Content Management in Authenticated Digital Workspaces. See what sets our intranet platform apart.
-
Spring '26 brings AI Course Creation, Power BI-connected AI Agents, and smarter content governance to MangoApps. See what's new across the platform.
Ready to use this template?
Get started with MangoApps and use English Learner Identification and Service Plan Documentation with your team — pricing built for small business.
