Field Notes · 7 min read
The terminology matters. A bilingual reviewer for a Mandarin IEP isn't bilingual English-Spanish, and IDEA doesn't ask for one anyway. Here's what the regulation actually says.
The framing problem
The phrase “we should have someone bilingual look at this” comes up in a lot of IEP meetings. Usually it’s well-intended — a case manager looking at a translated evaluation, wanting to make sure the translation is right. The problem is that the phrase smuggles in two assumptions about translation review that don’t hold up under IDEA.
In most NJ districts, “bilingual” defaults to English and Spanish. Spanish is the largest non-English language by a wide margin — about 65% of the state’s English Learner population — and most districts have at least one staff member comfortable in both languages. So when a translated IEP comes back from a vendor, the reviewer who gets handed the file is usually someone bilingual in English and Spanish.
This is reasonable when the translation is also English to Spanish. It is not reasonable in any other case. A bilingual English-Spanish reviewer cannot review a Mandarin IEP. They cannot review a Haitian Creole IEP, or a Gujarati IEP, or an Arabic IEP. The “bilingual” frame quietly assumes the language pair is the one the reviewer happens to know. It works fine for the most common case and provides no coverage for everyone else.
About 25 NJ districts now have a meaningful population (≥5%) of speakers of a language other than Spanish: Brazilian Portuguese in Newark and Elizabeth, Gujarati in Edison, Haitian Creole in Plainfield and Irvington, Mandarin in West Windsor-Plainsboro, Arabic in Paterson. These families don’t show up in the bilingual reviewer’s queue because the bilingual reviewer can’t review them.
What the regulation actually says
The relevant text is short. 34 CFR 300.503(c) governs prior written notice — the document a district sends parents whenever it proposes or refuses to initiate or change identification, evaluation, placement, or FAPE provisions. The regulation requires the notice to be:
“Provided in the native language of the parent or other mode of communication used by the parent, unless it is clearly not feasible to do so.”
That’s it. There is no list of credentialed reviewers. There is no specified test. The standard is functional: the notice has to actually communicate, in the language the parent reads, what the district is proposing.
34 CFR 300.9 carries the same standard for parental consent — consent has to be informed, which means the parent has to understand what they’re consenting to. 34 CFR 300.322(e) requires the district to take whatever action is necessary to ensure the parent understands the proceedings of an IEP meeting, including arranging an interpreter.
The thing IDEA does not say, anywhere, is “have a bilingual staff member spot-check the translation.” It says the document must be in the parent’s native language. The accountability is for the result, not the process.
The actual bar
The regulations don’t credential anyone, so the bar is set by what a court or OCR investigator would consider defensible if a parent later said they didn’t understand. From twenty years of doing this work, the elements that matter:
ATA certification for the source-target pair where ATA tests it. RID, EIPA, or NJ state interpreter certification for ASL. CCHI for medical-adjacent content. For language pairs that don’t have a national credential — and there are many — university-level translation training plus demonstrable subject-matter experience.
IEP language is dense. PWN, FAPE, LRE, FBA, BIP, ESY, IFSP, related services, accommodations versus modifications, present levels of performance, measurable annual goals. A translator without special-ed background can produce text that is grammatically Spanish but conceptually wrong. The first time a translator writes “el plan 504” as “el plan quinientos cuatro” — five hundred four — you’ve sent a parent a document they cannot reference.
A second qualified translator reads the rendered text against the source. This is standard practice in legal and medical translation; it’s still the exception in school documents, and it shouldn’t be. An IEP is a legal document. Treat it like one.
Acronyms preserved verbatim — IEP, FERPA, IDEA, OCR, Section 504. Citations preserved verbatim — 34 CFR 300.503, NJSA 18A:46. Names not translated — Lau v. Nichols. The reviewer needs to know that “case manager” stays “case manager” in NJ Spanish-language practice because that’s how districts communicate with parents who already know the term.
These are not exotic requirements. They are the difference between a translation that holds up under OCR review and one that doesn’t.
The questions to ask
The framing that works, in our experience, is to stop using “bilingual reviewer” as the unit of trust and start using “qualified translator” — singular or plural, depending on what the document calls for. The questions to ask a vendor:
These questions cost nothing to ask and they sharpen what comes back. If a vendor cannot answer them on a Mandarin IEP, the right move is not to bring in a bilingual English-Spanish reviewer to spot-check; the right move is to find a vendor who can answer them.
A note on terminology
Earlier versions of our own materials used “bilingual reviewer” because it’s the term districts use, and we wanted to meet people where they are. We stopped because the term was actively misleading on every language pair other than the one most reviewers happened to speak.
The substitution we settled on — qualified translator— describes the credential rather than the staffing arrangement. It travels across language pairs without quietly excluding the families whose language doesn’t happen to be the staffer’s second one.
The change isn’t pedantic. It’s the difference between an accommodation that works for 65% of NJ EL families and one that works for all of them.
Working a translation problem?
Document type, language pair, deadline. We'll tell you what the right qualified translator looks like for it — and whether we're a fit.