Writing it into the IEP: a parent and advocate guide to ASL goals, Deaf interpreter access, and accountability language

This page provides general information for educational purposes and is not legal advice; rules and timelines vary by state, and families should verify their state's specific requirements and consult a qualified special education advocate or attorney for guidance on individual situations.

An IEP is a legal document. What it says, and what it doesn't say, determines what a Deaf or hard-of-hearing student will and won't receive. Vague language gives the school flexibility to do less. Specific language creates obligations.

This is not a hypothetical concern. Parents and advocates working in Deaf education encounter the same patterns repeatedly: IEPs that mention "communication access" without naming ASL. Goals that track academic performance without measuring language development. Interpreter accommodations that say "certified interpreter" without specifying qualifications relevant to this particular student's profile. Progress monitoring that looks complete on paper but is collected by staff who cannot assess ASL.

Each of those gaps is a place where a Deaf student's access can quietly shrink, legally, because the IEP didn't prevent it.

This guide walks through the major categories of IEP language that matter for Deaf and hard-of-hearing students. For each one, it explains why the language matters, how to introduce it to an IEP committee, and how to respond when committee members push back. The model language throughout is adapted from established IEP frameworks used by Deaf education specialists and advocates. Every goal must be individualized to the specific student's present levels and needs.

The IEP process is collaborative. The goal here is not to arrive at a meeting with a script to force through, but to show up informed, know what to ask for and why, and be prepared to hold your ground when the school's first answer is no.

Before getting into specific language, it helps to understand what the law already requires, because this provision is the opening argument for most of what follows.

Under the Individuals with Disabilities Education Act, when an IEP is being developed for a child who is Deaf or hard of hearing, the IEP team is specifically required to consider:

• the child's language and communication needs
• opportunities for direct communication with peers and professional personnel in the child's language and communication mode
• the child's academic level and full range of needs
• opportunities for direct instruction in the child's language and communication mode

This requirement is at 34 CFR § 300.324(a)(2)(iv). It applies to every Deaf or hard-of-hearing child regardless of the school's preferred approach or history. It is not optional.

What this means in practice: the IEP team cannot assign a hearing interpreter and call the communication question resolved. They are legally required to consider whether the student has direct communication with peers and adults in their language mode, whether direct instruction is happening in that mode, and whether the student's language development needs are being addressed as distinct from academic performance. Each section of this guide connects back to this requirement.

The Present Levels of Academic Achievement and Functional Performance, or PLAAFP, is the foundation of the IEP. Every goal, service, and accommodation should trace back to something documented there. If a student's ASL proficiency, language history, or communication access needs aren't in the present levels, there's no documented basis for goals or services that address them.

For many Deaf students, the PLAAFP describes them in English-centric terms: "Student receives instruction via a sign language interpreter." "Student communicates adequately with familiar adults." Neither statement says anything about ASL proficiency level, language history, or whether the interpreting in place is actually working. They create the appearance of documentation without the substance.

What the PLAAFP should do instead is name ASL as the student's primary and preferred language, document the current ASL proficiency level based on a qualified assessment, and note where there are gaps between the student's chronological age and current language function. Model language:

"[Student] is a Deaf child whose primary and preferred language is American Sign Language (ASL). [Student]'s current ASL proficiency, as measured by [qualified assessment], is at [level or age-equivalent]. [Student] requires direct, sustained access to a fully accessible language model in ASL across all instructional settings in order to develop age-appropriate language, literacy, and academic skills."

This matters because it builds the documented foundation for everything that follows. A PLAAFP that describes the student's primary language as ASL and notes their proficiency is below age level is the basis for requiring ASL language goals, a qualified interpreter or CDI, and progress monitoring conducted by ASL-fluent staff.

The PLAAFP is also the appropriate place to name language deprivation as a distinct concern. A child who has had limited or inconsistent access to a complete natural language can show developmental gaps that closely resemble cognitive disability. Naming that distinction in the PLAAFP protects the student from misclassification later. Model language:

"Delayed or inconsistent access to a complete, natural language has [resulted in / has the potential to result in] language deprivation, which is distinct from and should not be conflated with cognitive or intellectual disability."

Before the meeting, request copies of any existing evaluations and look at how the student's language is currently described. If ASL isn't named as a primary language, or if proficiency has never been formally assessed, that's the first gap to address.

Ask whether the evaluation informing the current PLAAFP was conducted by someone with ASL fluency and documented expertise in assessing Deaf children's language development. If not, you have grounds to request that the assessment be supplemented or redone.

At the meeting, frame the PLAAFP revision as a clarification. "I'd like to make sure the present levels accurately reflect [Student]'s language as documented in the evaluation, and I want to add specifics about ASL proficiency and communication access history. Can we look at that section together?" Put proposed edits in writing before the meeting and bring them to share.

"The student communicates well with the adults in the building." Familiar communication in a predictable environment is a different skill than language proficiency. A student can function well within the routines of school while still having significant gaps in ASL vocabulary, grammar, and narrative ability. Language proficiency requires formal assessment, not observation of everyday interaction.

“We don’t have tools to assess ASL.” The Minnesota Commission of the Deaf, DeafBlind and Hard of Hearing has published Language and Communication Focused IEPs for Learners Who Are Deaf or Hard of Hearing: A Discussion Guide, a practical resource designed specifically to help IEP teams address language and communication needs for Deaf and hard-of-hearing students. The Minnesota Language and Communication Checklist is another widely used framework for documenting those needs during IEP planning. Neither is the only option. If the school lacks a qualified evaluator for ASL assessment, that is a staffing gap the district is responsible for addressing. The student’s right to a valid assessment doesn’t disappear because the school hasn’t hired for it.

"We already have a communication section in the IEP." A general note about interpreter services is not the same as a documented ASL proficiency level. Ask where the student's language proficiency is specifically recorded in the current plan. If it isn't there, that gap in the PLAAFP is what needs to be fixed.

ASL language goals are the piece most often missing from Deaf students' IEPs, and their absence is a significant gap. Without them, there is no mechanism to track whether a student is actually developing language, and no trigger for action if they aren't.

Academic goals measure what a student produces: a score, a reading level, a percentage of correct responses. They don't measure the language the student is using to learn, whether that language is developing, or whether gaps in language are what's limiting academic performance.

This is where the language deprivation literature and the Language Skill Hierarchy frameworks developed by Deaf education specialists and SLPs become relevant. Children who have had limited early access to a complete natural language develop along a trajectory that can diverge significantly from what grades would suggest. A student can pass grade-level tests, behave well in class, and get along with teachers while their ASL development is years behind age-appropriate norms. Those gaps accumulate. Without language goals in the IEP, neither the school nor the family has a reliable way to see that happening until the student reaches a point where the gap can't be ignored.

ASL language goals should measure real language function: receptive and expressive ASL proficiency, grammar and syntax (classifiers, role shift, non-manual markers, spatial referencing, verb agreement), vocabulary in academic and social registers, and for students with a language deprivation history, foundational measures like mean length of utterance. An example goal for expressive ASL grammar:

"By [date], [Student] will produce ASL utterances that demonstrate use of [specific ASL grammatical features] in [4] out of [5] observed structured language samples, as measured by video-recorded language samples analyzed by a qualified ASL-fluent evaluator or Deaf language specialist."

Note on who collects this data: interpreters and CDIs are trained to interpret, not to conduct language assessments. Progress data on ASL language goals should be collected and analyzed by an evaluator with specific training in Deaf children's language development, such as a Teacher of the Deaf with ASL competency or a Deaf language specialist. See Section 4 for more on qualified evaluator language.

The specificity matters. "Will improve ASL skills" is not a measurable goal. "Will demonstrate use of classifiers, role shift, and non-manual markers in 4 of 5 structured language samples, analyzed by a qualified ASL-fluent evaluator" is.

For vocabulary development, a measurable goal might read:

"By [date], [Student] will acquire and correctly use [X] new grade-level academic ASL vocabulary terms per [quarter], demonstrated through expressive use in academic and social contexts across [2] settings, as measured by vocabulary probes and a Teacher of the Deaf data log."

Frame these goals as foundational supports, not new demands. "I'd like to add language development goals that will help us track whether [Student] is developing ASL at an appropriate rate. These goals won't replace academic goals. They'll help us see whether [Student] has the language foundation the academic goals depend on."

If the team doesn't have a Teacher of the Deaf or ASL-fluent staff member who can write these goals, name that explicitly: "I understand the team may need to bring in someone with ASL expertise to write these properly. I'd like that to happen before we finalize the IEP." A staffing gap does not remove the student's right to appropriate language goals. The district is responsible for finding the expertise.

Bring sample goal language to the meeting. You don't need the committee to adopt it word for word. You need them to understand what you're asking for and why it's grounded in the student's documented present levels.

"Their grades are fine." Grades measure academic outputs, not language development. A student can pass standardized tests while ASL proficiency is significantly behind their chronological age. These are separate measures. The relevant question is not whether the student is passing but whether their language is developing at an appropriate rate.

"We have an interpreter. Isn't that enough?" Interpretation requires language to receive. If a student's ASL proficiency is below the level of the interpreted content, interpretation doesn't deliver full access. It delivers something the student can partially process. Language goals address the student's capacity to benefit from interpreted instruction, not just whether instruction is being interpreted.

"We don't have anyone qualified to write ASL goals." The student has a right to goals that address their language development needs. The district is responsible for providing or contracting the expertise to write and monitor those goals. If the district genuinely cannot write appropriate ASL goals, that acknowledgment itself says something important about the adequacy of current services.

"This isn't how we write IEPs in our district." ASL language goals directly serve the IDEA requirement at 34 CFR § 300.324(a)(2)(iv) to consider language and communication needs and provide opportunities for direct instruction in the student's language mode. These goals aren't outside standard IEP practice. They are the law applied to this student.

When most people think about communication access for a Deaf student, they picture a sign language interpreter. That's a reasonable starting point, but it isn't always sufficient. For students with specific language profiles, a hearing interpreter alone may provide very little real access at all.

Hearing interpreters, even highly qualified ones, work by translating between two languages: spoken English and ASL. What a hearing interpreter produces is their own ASL, shaped by their training, their fluency level, and their language background. It is not necessarily the same as the student's language.

A student with a history of language deprivation, non-standard or idiosyncratic signing, limited exposure to conventional ASL before school age, or significant language development gaps may not be able to access what even a qualified hearing interpreter is producing. The interpreter is doing their job correctly; the bridge between the interpreter's language and the student's language simply doesn't exist yet.

This is where a Deaf Interpreter (DI) or Certified Deaf Interpreter (CDI) fills a role a hearing interpreter cannot. A CDI is a Deaf professional who holds certification through RID/CASLI in the specific work of interpreting for Deaf individuals whose language access differs from conventional ASL. CDIs bring lived experience with Deafness, a broader range of visual communication strategies, and the ability to work from within the student's existing language toward the standard ASL the student is developing.

The National Deaf Center on Postsecondary Outcomes has documented the specific ways CDIs provide access that hearing interpreters alone cannot, particularly for students with complex communication profiles. The standard configuration is a CDI working in team with a hearing interpreter: not replacing the hearing interpreter, but bridging the gap between the hearing interpreter's output and the student's reception.

This matters especially for high-stakes situations. A student who doesn't fully receive interpreted directions during a standardized assessment isn't demonstrating their content knowledge. They're demonstrating the limits of the interpreting access they had. CDI access for assessment doesn't change what is being measured. It produces a condition where the test can actually measure the student's knowledge rather than their ability to process a hearing interpreter's ASL production.

A note on the CDI's role: CDIs are trained interpreters. Interpreting and language assessment are distinct professional functions, and a CDI should not be placed in the position of evaluating a student's ASL proficiency or serving as the qualified data collector for ASL language goals. When the IEP includes ASL language goals, the evaluator responsible for progress data must have specific training in Deaf children's language development, not just interpreting credentials. See Section 4 for qualified evaluator language.

IEP language for standing CDI access:

"A Deaf Interpreter (DI) or Certified Deaf Interpreter (CDI), working in a team with a hearing, certified educational interpreter, will be provided for [all core academic instruction / specific settings: high-stakes testing, IEP meetings, novel or complex content introduction, counseling services, disciplinary meetings]."

For assessment specifically:

"For all district and state assessments requiring interpretation, a DI/CDI team will be used to interpret directions and content in order to allow the assessment to measure [Student]'s content knowledge rather than their receptive skill with a hearing interpreter's ASL production. This accommodation does not alter the construct being measured."

Interpreter-mediated access and direct ASL access are not the same thing, and the IEP should address both separately.

The IDEA's special factors requirement at 34 CFR § 300.324(a)(2)(iv) specifically mentions "opportunities for direct communication with peers and professional personnel in the child's language and communication mode." The word direct matters. A hearing interpreter in the room provides mediated access: the student receives ASL from the interpreter, not from the teacher or peers. For many students, that is adequate. For others, particularly those working on language development or building Deaf identity, direct access to ASL-fluent adults and peers is a distinct need.

Direct access means access to Deaf educators, Teachers of the Deaf who communicate in ASL, Deaf paraprofessionals, or instructional settings where ASL is the primary language rather than an interpreted medium. It also includes access to Deaf peers in the educational environment.

When a student needs direct ASL access, the IEP should name it explicitly, in terms of both quality and quantity. Vague language like "student will have access to Deaf role models" means little in practice. Specific language is:

"[Student] will receive a minimum of [X hours per week] of direct instruction from an ASL-fluent educator (Teacher of the Deaf, Deaf education specialist, or other qualified Deaf or hearing ASL-fluent professional) as a separate service from interpreter-mediated instruction."

"[Student] will have documented opportunities for direct interaction with Deaf adult professionals and/or Deaf peers [frequency] per [week/month], consistent with the IDEA requirement at 34 CFR § 300.324(a)(2)(iv) to provide opportunities for direct communication with professional personnel and peers in the student's language mode."

If the school proposes that an interpreter in the classroom satisfies the direct access requirement, ask the team to explain how interpreter-mediated communication with hearing adults constitutes direct communication in the student's language mode. That is a meaningful distinction, and the answer will tell you a lot about how the school understands the law.

Start with the PLAAFP. CDI access and direct access both flow from a documented need, and that documentation belongs in the present levels. Once the student's language profile is described accurately, the case for these supports follows directly.

At the meeting, ask directly: "Given [Student]'s language profile as described in the present levels, does the team believe a hearing interpreter alone provides equivalent access? What evidence are we using to make that determination?" If the answer is "we've always done it this way" or "the student seems to understand," that's not a language-access analysis. It's an assumption.

Ask about the current interpreter's qualifications: their RID certification level, their EIPA score if applicable, and their experience with students whose language profile matches this student's. This is relevant information for whether the student is actually receiving appropriate access.

If the committee is open to a CDI but needs time to look into it, put the request in writing after the meeting. Document the date, what was discussed, and ask for a written timeline. An undocumented request is easy to lose.

"We already have a certified interpreter." Certification documents that the interpreter met a standard for the profession. It does not certify that this interpreter's ASL production is at a level this particular student can receive. The question isn't whether the interpreter is certified. The question is whether this student's access is equivalent to what a hearing student receives.

"We don't have access to a CDI." Geographic unavailability is the district's problem to solve, not a legal exemption from providing appropriate access. Districts can contract with remote CDI services, bring in CDIs for high-stakes periods, or work with state education agency resources. "We can't find one" is not a complete answer. The follow-up question is: "What steps have you taken, and when can I expect a written response?"

"The interpreter and student have worked together for years and communicate fine." Familiarity can mask access gaps. A student who has adapted to limited access, by guessing from context, watching peers, or limiting themselves to familiar patterns, may appear to follow instruction while missing significant content. The length of a working relationship doesn't answer the question of whether the student is receiving full, equivalent access.

"It's too expensive." Cost cannot override FAPE under IDEA. If CDI services weren't budgeted, that is a planning issue for the district. Acknowledging the cost while being clear that it is not a legally valid reason to deny an appropriate accommodation is an appropriate response: "I understand this is an additional cost. I also know that IDEA doesn't allow cost to be used as a reason to deny appropriate communication access."

The IEP should also include scheduling and backup language to prevent access gaps from being quietly absorbed without notice:

"DI/CDI services will be scheduled and confirmed a minimum of [X] days in advance of any known need (assemblies, field trips, testing windows) by [designated staff role], with a documented backup plan if a DI/CDI is unavailable."

IEPs can look complete and fail in practice. Progress monitoring entries that read "goal partially met" without specifying what was measured, by whom, and how are not actually monitoring progress. They are filling a compliance checkbox.

For Deaf students with ASL language goals, this problem is compounded by who is available to collect the data. Progress data collected by a hearing teacher who doesn't know ASL, or a speech-language pathologist without DHH-specific training, is not a valid measure of ASL proficiency. Including it in progress reports creates the appearance of accountability without the substance.

The same limitation applies to interpreters and CDIs. Their professional training is in facilitating communication, not in evaluating language development. An interpreter, however skilled, should not be the person assessing whether a student's ASL proficiency is progressing toward IEP goals. Those two roles require different expertise, and conflating them produces unreliable data.

The IEP can prevent this. Qualified evaluator language names who is responsible for data collection and what qualifications they must have. Trigger and threshold clauses tie consequences to data rather than leaving review discretionary. Together, they close the gap between what the IEP says and what actually happens.

Qualified evaluator language:

"Progress toward ASL language goals will be measured a minimum of [monthly/quarterly] and will be collected by a qualified ASL-fluent evaluator, Deaf language specialist, or Teacher of the Deaf with documented competency in Deaf children's language development, not solely by a hearing or non-fluent staff member. Interpreters and CDIs will not serve as the evaluators of record for ASL language goals."

"Any assessment of [Student]'s ASL proficiency will be conducted or reviewed by an individual who is fluent in ASL and has documented competency in evaluating Deaf children's language development. Assessments administered solely through spoken English or by evaluators without ASL fluency will not be considered valid measures of [Student]'s language progress."

Trigger/threshold clauses:

"If progress monitoring data indicates [Student] is not making expected progress toward IEP goals for two consecutive progress-reporting periods, the IEP team will reconvene within [10] school days to review whether current interpreting and communication supports are providing equitable access, and will document that review in the IEP."

"If a qualified interpreter or DI/CDI is unavailable on a given day, the school will notify the parent/guardian within 24 hours and document the gap in service. Repeated gaps of [3 or more per grading period] will trigger an IEP team review."

The trigger language matters because it removes discretion from the decision about when to act. Without it, two consecutive quarters of missed goals might result in a note at the annual review. With it, the IEP itself requires a response.

Frame accountability language as something that benefits everyone. "If we put specific language around who collects the data and what happens if goals aren't being met, everyone knows what we're tracking and who's responsible. That makes it easier to tell whether things are working."

Ask directly who will be collecting progress data on ASL goals and what their ASL qualifications are. If the answer is a general education teacher, a speech therapist without DHH experience, or "whoever has the student," name the problem: "I'm concerned that if data is collected by someone without ASL fluency, we won't have reliable information. Can we add language specifying who is responsible for this?"

"All our staff are qualified." For general academic goals, they may well be. For ASL language goals specifically, the relevant question is whether the person collecting data can reliably assess ASL proficiency. That is a specific competency, not a general teaching qualification.

"We already monitor all goals." The question is whether the monitoring is valid for this student's language goals. Progress data from someone who doesn't know ASL cannot reliably measure an ASL goal. Ask who collected the data and how.

"Trigger language isn't standard in our IEPs." IDEA requires the IEP to specify how progress will be measured and reported. Trigger clauses make that requirement concrete. They don't add new legal obligations; they make existing obligations enforceable.

The "least dangerous assumption" is a principle that has been cited widely in special education and AAC advocacy. When evidence is ambiguous, it says, professionals should make the assumption that, if wrong, causes the least harm.

In the context of Deaf education, this principle carries specific weight. Language deprivation, the result of prolonged inadequate access to a complete natural language, can produce developmental patterns that closely resemble cognitive or intellectual disability. Memory difficulties, attention difficulties, limited ability to organize and sequence information, gaps in general world knowledge: all of these can result from language deprivation. They can also result from cognitive disability. Without a proper evaluation conducted in the student's actual language, by an evaluator fluent in that language, you often cannot reliably tell which is which.

The harm from getting it wrong is not symmetric. If a child has a cognitive disability and the team assumes the problem is language access, the intervention is better language access. That doesn't hurt the child, and it may help. If a child has a language access problem and the team assumes cognitive disability, the intervention may be lowered expectations, reduced academic demands, and a placement track that limits the child's future. That outcome is very difficult to reverse.

This is why naming the least dangerous assumption in the IEP is a protective step, especially for students with a history of inadequate language access. Model language from established Deaf education frameworks:

"Consistent with the IDEA Special Factors provision (34 CFR § 300.324(a)(2)(iv)) and the principle of the 'least dangerous assumption,' the IEP team presumes that any gaps in [Student]'s academic performance reflect insufficient language access rather than diminished cognitive capacity, absent evidence to the contrary from an evaluator fluent in ASL."

This language doesn't prevent a cognitive evaluation if there's genuine, independent reason to conduct one. What it does is establish the default assumption in the absence of a valid, ASL-grounded evaluation. It also puts on record that the team has considered this distinction, which matters if questions about cognitive ability come up later.

If a committee member suggests a student's difficulties might be cognitive rather than language-based, ask: "Was the evaluation that supports that conclusion conducted by someone fluent in ASL, with specific training in assessing Deaf children? If the evaluation was done in spoken English or by someone without ASL fluency, it can't reliably separate language deprivation effects from cognitive disability."

That is not a hostile question. It is a valid one. The answer tells you whether the concern is grounded in appropriate data.

If a cognitive evaluation is being proposed, the appropriate request is that it be conducted by an evaluator with documented ASL fluency and DHH-specific training, and that the evaluation explicitly address the distinction between language deprivation and cognitive disability.

"Our psychologist has evaluated many students." General evaluation experience is not the issue. The specific question is whether this evaluator has the competency to distinguish language deprivation from cognitive disability in a Deaf child. An evaluation conducted through a hearing interpreter, or by an evaluator without DHH background, cannot reliably make that distinction.

"We've observed patterns that suggest more than a language issue." That observation may deserve follow-up, but the appropriate response is to find an evaluator who can conduct a valid assessment in ASL, not to proceed on the basis of observations gathered through limited-access interaction. The student's documented history of language access, in the PLAAFP, is necessary context for interpreting any behavioral observations.

This piece is frequently overlooked. Parents need communication access at the meeting where decisions are being made, not only in the classroom.

IDEA's meaningful parent participation requirements mean families must be able to understand and fully contribute to the IEP process. A Deaf parent, a Deaf student attending their own IEP meeting, or a hearing parent working through an interpreter whose ASL production doesn't fully match their communication needs may be nominally present at a meeting while being unable to participate in it. That is not meaningful participation.

One common but serious problem: using the student's classroom interpreter to interpret the IEP meeting.

The student's classroom interpreter works within the daily educational relationship. They have direct knowledge of and a stake in how services are described, how the student is performing, and what the team decides. They are not a neutral communication facilitator for a meeting that evaluates those same services and determines the student's program. Asking that interpreter to interpret the IEP meeting puts them in a conflict of interest and deprives the student and family of independent communication access.

An outside, independent, qualified interpreter should be arranged for IEP meetings. That interpreter has no prior relationship with the team, no stake in the outcome, and no role in the services being discussed. If CDI services are appropriate for this student (see Section 3), those too should come from an outside source, not from the interpreter already assigned to the classroom.

This is not about doubting the classroom interpreter's integrity. It is about structural independence. The same concern applies in other professional contexts: a doctor who is treating a patient should not interpret in a dispute about that patient's care. The roles are incompatible.

The IEP can specify this directly:

"All IEP meetings concerning [Student] will be conducted with a qualified ASL interpreter who is independent of the student's current educational placement, and, if requested by the parent/guardian or IEP team, a CDI who is also independent of the placement. The student's assigned classroom interpreter will not serve as the communication facilitator for IEP meetings."

For Deaf parents or Deaf students attending their own meetings, the same logic applies. The interpreter provided for the meeting should be arranged specifically for that purpose, separate from any interpreter assigned to the child's classroom.

Model language for the general meeting access provision:

"All IEP meetings concerning [Student] will be conducted with a qualified, independent ASL interpreter and, if requested by the parent/guardian or IEP team, an independent CDI, to allow the family and/or student to fully and directly participate in decision-making, consistent with IDEA's meaningful parent participation requirements. The interpreter provided for IEP meetings will not be the student's assigned classroom interpreter."

The goal of the IEP meeting is not to win an argument. It is to get language into the legal document that will govern your child's education. That means being collaborative in process while being specific in substance.

Before the meeting, review the current IEP and identify the specific gaps: missing proficiency documentation in the PLAAFP, absent language goals, vague interpreter language, no qualified evaluator specification. Write your concerns down and send them to the special education director or coordinator before the meeting. The IEP team is required to consider written parent concerns, and having your concerns documented creates a record that protects you if the school later claims an issue was never raised.

Bring proposed language. Not as a demand, but as a starting point. "I've put together some language I'd like the team to consider. I'm happy to discuss the wording." Specific text makes the conversation concrete. A vague request for "better language support" is easier to sidestep than a specific sentence about who must collect progress data and what qualifications they need.

Track everything. Note the date and content of each conversation. Follow up verbal discussions in writing: "Following our meeting on [date], I'm writing to confirm that the team agreed to review the interpreter qualification language before the next IEP meeting." Written confirmation of verbal agreements matters when there's a dispute later.

If the team refuses specific language, ask for the refusal in writing. You have the right to know why proposed language was excluded. If the school declines to include language you believe is required by IDEA, that refusal may be grounds for a formal complaint, a request for an Independent Educational Evaluation, mediation, or due process. Your state's Parent Training and Information Center can help you understand which option fits your situation and what timelines apply.

• Language and Communication Focused IEPs for Learners Who Are Deaf or Hard of Hearing: A Discussion Guide (Minnesota Commission of the Deaf, DeafBlind and Hard of Hearing) — a practical guide for IEP teams on building language and communication-focused plans for Deaf and hard-of-hearing students.

This page provides general information for educational purposes and is not legal advice; rules and timelines vary by state, and families should verify their state's specific requirements and consult a qualified special education advocate or attorney for guidance on individual situations.