Understanding IDEA Evaluation, Eligibility & Reevaluation
Special education evaluation is a decision-making process, not simply a testing event. This reference follows the path from initial concern through intervention, evaluation, eligibility, and reevaluation, with emphasis on the data teams need, the decisions IDEA actually requires, and the procedures that keep those decisions defensible.
From concern to evaluation
The process of identifying a student who may need special education is a continuum rather than a binary “refer / don't refer” decision. Child Find requires the identification, location, and evaluation of all students who are suspected of having a disability and needing special education.
The conceptual trigger is suspected disability plus a possible need for special education. Concern can arise from patterns involving academic performance, classroom functioning, teacher observations, intervention response, CBM or progress-monitoring data, behavior, attendance, work completion, parent information, prior evaluations, screening data, or educationally relevant medical and developmental history.
Grades are useful data—but they are not the decision
Grades can provide meaningful qualitative and educational information, especially when patterns are examined across teachers, courses, semesters, supports, attendance, work completion, and other measures. However, advancing from grade to grade does not categorically remove a student from Child Find when a disability and need for special education are suspected.
The standard rejects both extremes: “passing means there is no possible disability” and “grades are meaningless.” Grades are a valuable piece of the overall profile, not the final determinant of eligibility or the need for evaluation.
MTSS, intervention, and progress monitoring
MTSS and intervention data help teams answer critical questions: What skill or behavior is actually weak? What has been tried? Was the intervention delivered with reasonable fidelity? Did performance improve, and how rapidly? Does the difficulty persist despite appropriate instruction and support?
Repeated measures, such as Curriculum-Based Measurement (CBM), can provide a trajectory that grades or one-time testing cannot. Establishing a baseline, collecting repeated comparable measures, setting an aimline or trendline, and measuring instructional response against intervention fidelity are powerful ways to understand a student's educational needs.
MTSS data may inform an evaluation, but MTSS cannot become a mandatory waiting period when a disability is already suspected. At the same time, simply receiving intervention does not automatically mean a student needs an IDEA evaluation. OSEP Memorandum 11-07 clarifies that while RTI cannot delay or deny an evaluation, the obligation to evaluate is triggered by the suspicion of a disability.
Parent and school evaluation requests
Either a parent or the public agency may initiate a request for an initial evaluation. Teams should respond to the substance of the request and the existing data, regardless of whether a parent's request is forceful, lengthy, attorney-written, advocate-written, AI-assisted, or informal.
A highly persuasive email does not change the IDEA standard, nor does a weakly worded expression of concern eliminate the district's Child Find obligation. The team should systematically ask: What concerns are being alleged? What existing data support or contradict those concerns? Is a disability reasonably suspected? Is there reason to suspect a need for special education? What additional information, if any, is needed?
If the agency suspects a disability and a need for special education, it must move forward with seeking consent for evaluation. If the agency does not suspect a disability and refuses the request, that refusal must be documented through Prior Written Notice (PWN), detailing the reasons and the data supporting the decision.
A school receives a highly assertive evaluation request demanding an immediate battery of cognitive and achievement tests. Rather than acting defensively, the team objectively reviews the student's current functioning. They examine recent CBM data showing strong response to intervention, passing grades, and teacher observations noting age-appropriate engagement. The team determines they do not suspect a disability, refuses the evaluation request, and provides a PWN that clearly points to the objective data supporting their decision.
Let the information drive the decision
IDEA requires teams to draw from a variety of sources and carefully consider the information obtained. No single data point should become the decision merely because it is convenient.
Teams should synthesize data from across the student's profile: grades and course patterns, attendance, state and local assessments, CBM and progress monitoring, intervention data and fidelity, teacher and parent input, student input when appropriate, records and history, standardized testing, rating scales, observations, language acquisition history, adaptive or functional information, and prior evaluations.
For example, grades are valuable but not dispositive. Standardized test scores are similarly valuable but not dispositive. The total pattern of functioning drives the decision.
Evaluation is broader than testing
Evaluation is the process of answering IDEA's educational questions. Testing is one possible source of data within that process.
IDEA requires multiple tools and strategies, prohibits the use of a single measure as the sole criterion, requires assessment of all relevant suspected areas, and demands sufficient comprehensiveness to identify all of the student's special education and related service needs. The operational question for the team should naturally be: What data do we already have, and what additional data—if any—do we actually need?
SLD, intervention data, and CBM
Specific Learning Disability (SLD) is the area where instructional response and progress-monitoring data become particularly important in IDEA. State criteria must permit a process based on the student's response to scientific, research-based intervention and may permit alternative research-based procedures. When determining SLD eligibility, teams must consider whether the student received appropriate instruction and examine data-based documentation of repeated assessments of achievement at reasonable intervals.
When an evaluation is prompted by a lack of adequate progress after an appropriate period of instruction, or whenever a referral occurs, the agency must promptly seek consent and proceed with the evaluation. OSEP guidance confirms that RTI cannot delay the evaluation.
Curriculum-Based Measurement (CBM) can be a strong method for producing this repeated achievement and progress data because it can show level, trend, instructional response, and intervention-phase changes. However, IDEA does not mandate a specific CBM product. Locally generated CBM does not automatically carry national norms or standardized benchmarks. It is one data source, not an eligibility formula. Crucially, intervention fidelity affects interpretation: poor response under a poorly implemented intervention provides weak evidence about the student's actual responsiveness.
From evaluation to eligibility
Eligibility under IDEA is not determined by a low score, a clinical diagnosis, a parent's request, a failing grade, or the fact that a student did not respond to Tier 2 interventions. IDEA eligibility requires meeting the applicable disability criteria and demonstrating an educational need for special education.
Teams must carefully consider exclusionary factors. A student cannot be found eligible if the determinant factor is a lack of appropriate reading or math instruction, or limited English proficiency.
Limited English proficiency cannot be the determinant factor for IDEA eligibility. Teams therefore need enough data to distinguish disability-related difficulty from language acquisition and instructional opportunity. Intervention data may be useful evidence in making that distinction, but intervention cannot be turned into an automatic prerequisite when a disability is suspected.
Eligibility conversations go better when everyone at the table can see what a score means. Make Scores Make Sense plots cognitive, achievement, adaptive, and rating-scale scores on one normal curve with the publisher's confidence intervals, explains each score in plain language, and keeps the score conversion reference and CHC ability definitions on the same page. It also looks up the 2016 New Mexico SLD regression table exactly as published and can shade that discrepancy range on the curve, labeled as one documented reference and not as a state or district eligibility rule. Use it to explain, not to decide.
Reevaluation and the RED
Reevaluation is a review of data first, and a testing event second—if additional data are needed. During a Review of Existing Data (RED), the team examines existing evaluation data, parent information, classroom, local, and state assessments, observations, and teacher or provider information.
The team uses this review to determine what additional data, if any, are needed to answer key questions: Does the student continue to have a disability? What are the student's current educational needs? What are the current achievement and developmental levels? Does the student continue to need special education and related services? Are additions or modifications to services needed?
The RED is the decision process that determines whether more data are necessary; it is not merely paperwork preceding automatic testing. IDEA requires reevaluations at least once every three years (unless the parent and agency agree it is unnecessary) and ordinarily not more than once annually, while adhering to the no-additional-data rule and the parent's right to request assessment.
When additional testing is—and is not—needed
IDEA does not require repeating the same cognitive or achievement battery every three years. The need for additional testing depends on the sufficiency of the existing data.
Additional assessment is more defensible when:
- Existing data no longer adequately answer questions about continued eligibility or current educational needs;
- The student's profile or functioning has materially changed;
- Important suspected areas were never adequately assessed;
- Prior data are very old, and there is insufficient current converging evidence;
- Current performance conflicts substantially with the old evaluation;
- A new suspected disability or area of need has emerged;
- The team needs specific data to determine services or programming;
- Existing data are internally inconsistent or too limited to support a defensible decision.
Additional standardized testing may not be necessary when:
- Current data adequately answer all reevaluation questions;
- Eligibility and need remain well supported by multiple current sources;
- The student's present needs are clearly described;
- Progress and service data are current and sufficient;
- There is no meaningful unresolved suspected area requiring additional assessment.
Old data require stronger scrutiny. IDEA does not establish an expiration date for a cognitive or academic score. However, as the time since direct assessment increases, the team should ask whether the existing record still adequately describes the student's current functioning and answers the required reevaluation questions. A first-grade evaluation being relied upon for a high school sophomore should prompt a serious review of whether current data are truly sufficient.
Example A — Testing warranted: A student was last comprehensively assessed in early elementary school, is now in high school, current academic and functional profile has changed, and existing data do not adequately explain current needs.
Example B — Testing not warranted: A student has recent evaluation data plus current CBM, grades, observations, service and progress data, teacher and parent input, and no new suspected areas. The RED answers all required questions without another full standardized battery.
Refusing or proposing evaluation: Prior Written Notice
Prior Written Notice (PWN) is required when a public agency proposes or refuses to initiate or change the identification, evaluation, educational placement, or provision of FAPE. A defensible PWN must clearly communicate what the agency proposes or refuses, why, what evaluations, assessments, records, or reports were used, alternatives considered and why they were rejected, other relevant factors, and procedural safeguards information.
Evaluation requests:
- Possible refusal: Parent demands a specific test battery, but the team determines the requested testing is not necessary because existing data adequately answer the relevant evaluation questions.
- Possible refusal: Parent requests initial evaluation, but after reviewing the concern and current data the agency does not suspect disability/need for special education. The agency documents the refusal and supporting data in PWN.
General education supports / intervention data: General education intervention may be appropriate when the current data do not support suspicion of disability and the problem is better addressed through general education. However, do not present “try general education first” as a mandatory IDEA prerequisite.
English learners / exclusionary factors: Limited English proficiency cannot be the determinant factor for IDEA eligibility. Teams may need additional language, instructional, intervention, and educational history data to distinguish language acquisition from disability. If a disability is suspected, language status cannot be used as a reason to simply postpone evaluation.
Who writes the PWN?
Federal IDEA places the notice obligation on the public agency. It does not assign PWN authorship to a particular staff title.
Who drafts the PWN is a local decision. Check your district's procedures for who writes notices tied to evaluation decisions and who writes notices tied to IEP services and placement.
Keeping it practical
Good evaluation practice is not “test everyone” and it is not “avoid testing.” It is collecting the smallest set of sufficiently current, relevant data needed to answer IDEA's questions accurately and document the team's reasoning.
- Define the concern. What exactly are we trying to explain?
- Review what is already known. Current performance, history, interventions, progress, observations, parent/teacher information, prior evaluations.
- Decide whether disability is suspected.
- Identify the unanswered questions.
- Gather only the additional data needed to answer them.
- Determine eligibility from the full pattern—not one score.
- Document the decision and reasoning.
Enough data to make the right decision. No testing merely because a calendar says three years. No refusal merely because testing would create work.
References
Federal Regulation
- 34 C.F.R. §300.8 — Child with a disability
- 34 C.F.R. §300.111 — Child Find
- 34 C.F.R. §300.300 — Parental consent
- 34 C.F.R. §300.301 — Initial evaluations
- 34 C.F.R. §300.303 — Reevaluations
- 34 C.F.R. §300.304 — Evaluation procedures
- 34 C.F.R. §300.305 — Additional requirements for evaluations and reevaluations
- 34 C.F.R. §300.306 — Eligibility
- 34 C.F.R. §§300.307–300.311 — SLD
- 34 C.F.R. §300.503 — Prior Written Notice
Federal Guidance
- OSEP Memo 11-07 — RTI cannot delay/deny evaluation
Professional Standards
- NASP 2020 Practice Model, especially Domain 1: Data-Based Decision Making
Related FarPoint Resources
- Understanding CBM
- CBM Tracker / tools where appropriate
- Make Scores Make Sense: Assessment Score Explorer