One of the most important things I do as an advocate during evaluation meetings is slow the conversation down when a team starts jumping to conclusions.
A few months ago, I attended a meeting involving a student who had already received a medical diagnosis of autism. The parent wasn't asking the district to diagnose autism. The diagnosis already existed. The parent was asking the district to evaluate the student's educational needs and consider an ADOS as part of that process.
The district declined in a Prior Written Notice.
Their reasoning was straightforward:
"We don't see autism at school."
At first glance, that response sounds reasonable. The student earned good grades, communicated well and wasn't getting into trouble.
The student appeared to be functioning successfully throughout the school day. The problem was that none of those things answered the question the team was supposed to be asking. The purpose of an evaluation meeting is not to determine whether a child "looks autistic enough."
The purpose is to determine whether the student has needs that require special education supports and services.
Those are two very different conversations.
As the meeting continued, I kept hearing the team return to what they weren't seeing. They weren't seeing meltdowns, major behavior concerns, significant academic struggles.
Meanwhile, the parent was describing a completely different experience in their parent input statement and verbally during the meeting.
They described sensory overload, anxiety, difficulties with transitions and changes in routine and a child who spent so much energy holding it together throughout the school day that there was very little left by the time they got home.
What struck me was that the team and the parent were not necessarily disagreeing about the child. They were looking at different pieces of the same puzzle. The district was focused on performance and the parent was focused on experience.
My role as an advocate wasn't to accept the district's opinion simply because it came from a school team. My responsibility was to examine the data, compare it to the concerns being raised, and hold the district accountable for conducting a comprehensive evaluation in all areas of suspected disability.
Schools have a responsibility to evaluate in all areas of suspected disability.
Not just the areas that are easy to observe.
Not just the areas that show up in grades.
Not just the areas that create discipline concerns.
All areas of suspected disability.
That includes looking deeper when a parent presents concerns that aren't being explained by the information already on the table.
Eventually, the conversation shifted. The discussion stopped being about whether the student appeared autistic at school and started focusing on what information was still missing. That is where evaluation meetings become productive.
Not when adults argue about labels.
Not when teams try to prove or disprove a diagnosis.
When everyone agrees to gather the information necessary to understand the whole child.
One of the biggest mistakes I see in special education is assuming that a student's strengths eliminate the possibility of support needs.
Strong grades do not erase sensory challenges, strong communication skills do not eliminate executive functioning difficulties and a student who appears successful on the surface may still be working harder than anyone realizes.
That is exactly why comprehensive evaluations matter because our job is not to determine whether a child fits neatly into a category.
