School District Language Access: What the Law Still Requires for IEPs and Family Engagement

A parent arrives for an IEP meeting she has waited five weeks to attend. Six district staff are already seated. The documents in front of her are in English. Someone asks whether her eleven-year-old son — the student the meeting is about — would mind translating for her.

Every person in that room means well. The special education coordinator is short-staffed. The case manager sent the notice on time. Nobody set out to exclude anyone. And yet the meeting that just happened will not hold up, because a parent who cannot follow the proceedings has not participated in them, and a district that leans on a child to bridge that gap has put the child in a position no federal regulation contemplates.

If you run English learner programs, special education, or family engagement for a district, you already know this scene. What changed recently is not the obligation. What changed is that the document most districts used to explain the obligation to their own boards and principals is gone — and a lot of people have quietly concluded that the rule went with it.

It did not.

Did the rules change when the federal guidance disappeared?

In August 2025, the U.S. Department of Education rescinded the January 7, 2015 joint Dear Colleague Letter from ED’s Office for Civil Rights and the Department of Justice — the one that spelled out, in plain language, what districts owed English learner students and limited English proficient parents. The letter remains posted for historical reference only.

Here is the part that matters for your planning: a Dear Colleague Letter is guidance. It explains existing law; it does not create it. Rescinding it removed the explanation, not the statute. Every legal source the letter rested on is still in force:

• Title VI of the Civil Rights Act of 1964 (42 U.S.C. § 2000d), which bars national origin discrimination by recipients of federal funds — which is nearly every public district in the country.
• Lau v. Nichols, 414 U.S. 563 (1974), in which the Supreme Court held that identical instruction in a language students cannot understand is not equal treatment.
• The Equal Educational Opportunities Act of 1974 (20 U.S.C. § 1703(f)), which requires districts to take “appropriate action to overcome language barriers.”
• Castañeda v. Pickard (5th Cir. 1981), which supplies the three-part test courts still apply to EL programs.
• The Every Student Succeeds Act, including 20 U.S.C. § 6318(f), which requires districts to provide information and school reports “in a format and, to the extent practicable, in a language such parents understand.”

The Department’s own civil rights pages continue to state the requirement directly: Title VI requires schools to communicate with LEP parents about important school-related information in languages they can understand.

This is the same pattern public agencies met when Executive Order 13166 was revoked in March 2025. The executive order was an implementation instruction layered on top of Title VI. Title VI itself was never touched, and agencies that treated the revocation as a repeal of their obligations were reading the wrong document. We wrote that up in detail in our post on what language access requires of public agencies now — the analysis transfers almost line for line to K-12.

What does IDEA require for IEPs specifically?

Special education is where the requirement stops being general and becomes explicit, and it is where districts are most exposed — because IDEA gives parents due process rights, and a parent who did not understand the proceeding has a concrete procedural claim.

Three regulations do most of the work:

34 CFR § 300.322(e) — parent participation. The public agency “must take whatever action is necessary to ensure that the parent understands the proceedings of the IEP Team meeting, including arranging for an interpreter for parents with deafness or whose native language is other than English.” Note the standard: not “offer an interpreter if requested,” but ensure the parent understands.

34 CFR § 300.503(c) — prior written notice. The notice must be written in language understandable to the general public and provided in the native language of the parent, unless it is clearly not feasible to do so. If the parent’s native language is not a written language, the district must translate the notice orally or by other means, ensure the parent understands its content, and keep written documentation that it did both.

34 CFR § 300.9 — consent. Consent counts as consent only if the parent has been fully informed of all relevant information in their native language or other mode of communication.

Read together, these create a documentation duty, not just a service duty. The district that provides a good interpreter but records nothing is in a weaker position two years later than the district that logged the language, the interpreter, and the mode of delivery at the time.

Why not use bilingual staff, or the student?

Because competence in a language is not competence in interpreting — and because federal guidance has consistently warned districts against relying on students, siblings, friends, or untrained staff for translation and interpretation.

The practical reasons hold up without any legal citation at all:

• A bilingual paraprofessional may speak fluent Spanish and still have no working vocabulary for least restrictive environment, present levels of academic achievement, or extended school year services. IEP language is technical in English, and it is technical in every other language too.
• Staff pulled in to interpret are also participants. Someone who is simultaneously a team member cannot neutrally render what the team says about a student they teach.
• Asking a child to interpret places the student inside a conversation about their own disability and hands them the job of telling their parent what the adults decided.
• A district that uses ad hoc interpreters has no record of qualifications when a complaint arrives.

The fix is not to forbid bilingual staff from ever speaking their language with families. It is to separate helping a family feel welcome from rendering a legally consequential proceeding, and to staff the second one properly.

What does a working district language access plan look like?

The districts that handle this well are not the ones with the biggest budgets. They are the ones that made four decisions in advance instead of improvising at each meeting.

1. Know your languages by count, not by impression. Pull your home language survey data and rank it. Most districts find that four or five languages cover the large majority of LEP families, with a long tail covering the rest. Those two groups need different solutions — pre-translated materials for the first, on-demand capacity for the second.

2. Decide what gets translated in writing versus interpreted live. Standing documents with a long shelf life — enrollment packets, handbooks, discipline procedures, procedural safeguards notices, registration forms — are worth translating once and reusing for years. Individualized, time-sensitive content — an IEP meeting, a discipline conference, a parent-teacher conference — needs live interpretation, because it does not exist until it happens.

3. Build a real escalation path for the long tail. On-demand phone interpretation covers the language that shows up once a year at 3 p.m. on a Thursday. Scheduled onsite or video remote interpreting covers the IEP meeting you booked three weeks out. A district that has both stops having to choose between delaying a meeting and running it without access.

4. Write down what you did. Language of record, interpreter used, mode of delivery, and — for prior written notice delivered orally — the documentation that § 300.503(c) actually requires. It costs nothing at the moment of service and it is the entire case later.

How do you get started without boiling the ocean?

Districts stall on this because they picture translating everything at once. You do not have to. The sequence that works is narrow and repeatable:

1. Rank your languages from the home language survey.
2. List the ten documents families most often ask about, misunderstand, or return incomplete.
3. Translate those ten into your top languages first, and set a review cycle so they stay current.
4. Put a live interpretation channel behind every meeting type where a decision gets made.
5. Add a language field to your meeting records so the documentation happens automatically.

That is a term’s worth of work, not a multi-year program, and it moves you from improvising to having a plan you can hand to a principal.

Where does Taika fit?

Our education language access practice supports districts and charter networks across the span of this problem: translated enrollment and procedural safeguards documents, IEP and 504 meeting interpretation, on-demand phone interpretation for unpredictable languages, ASL and CART for deaf and hard-of-hearing parents, and accessible-format conversion for families who need it. We work in the languages your home language survey actually shows, not a standard menu.

We are a guide here, not your compliance officer. You know your families and your calendar. What we bring is the linguist bench, the scheduling capacity, and a quality process that turns “we should really get that translated” into a document your board can adopt and a meeting your parent can follow — with translation quality we stand behind.

Start with the smallest useful step. Send us your home language survey breakdown and the three documents your families most often misunderstand, and we will scope what it takes to get them right.

Request a quote or read more about how we support districts on our education language access page. If interpretation is the immediate pressure point, our interpretation services page walks through onsite, video remote, and on-demand phone options and when each one is the right call.