By Dr. Sandy Chafouleas, co-developer of the ESSY Whole Child Screener and Board of Trustees and a Distinguished Professor at the University of Connecticut.‍

‍

Picture a student who acts out every morning. Most of us have known that student. And in most schools, we know the drill: document the behavior, put a plan in place, track the incidents. Sometimes that is exactly what's needed, but what if it’s not?

‍
I've spent a lot of my career thinking about the space between what we notice in a student and what we actually understand about them. After years of working alongside school teams, I’ve seen that the gap isn’t because educators don’t care or aren’t paying attention. Educators notice a lot. The problem is that our systems are often set up to capture only part of what they notice.
‍

A few questions worth asking

‍

Most districts I work with have put real effort into their multi-tiered systems of support, including screening. But it's worth stepping back to ask what our screening is actually designed to see. Here are three questions to bring to your next leadership team meeting:

‍
• Are we looking at the whole child, or one piece at a time? When academics, behavior, and
mental health are screened separately, teams tend to plan separately too.
• Are we capturing strengths? If a screener only asks what's going wrong, that's what the conversation will be about. Yet strengths are often where the best supports start.
• Are we seeing context? When every concern is framed as something within the child, our
responses follow suit, even when the real issue is stress at home, a missing connection with a caring adult, or an empty stomach.

‍
We know these needs are connected. Students bring all of it through the door together. Our data should help us see it that way.

‍
What we learned from building the ESSY Whole Child Screener

‍
Those questions are what led our interdisciplinary team to develop the ESSY Whole Child Screener. Teachers rate students across six areas: academics, social and emotional well-being, behavior, physical health, attendance, and supports outside of school, each from substantial strength to substantial concern. A quick first round takes about three minutes per student, and teachers answer more questions only where there's a concern. The report doesn't use scores. Instead, it organizes what teachers know into strengths to maintain, areas to monitor, and concerns to follow up on.

‍
What has been most interesting to me hasn’t been the screener itself, but how it changed the conversation. In one study using case examples, we gave school data teams both their usual screener reports and ESSY reports. With ESSY, every team talked about students' strengths; with their usual reports, only about half to two-thirds did. Teams thought about what might be happening across settings before jumping to diagnoses. And rather than asking for more data, they got right to planning.

‍

Of course, the report didn't make those decisions. The teams did. But fuller information helped them see more of the student and what’s going on around them.

‍
Where you might start

‍
You don't need a new tool to begin exploring. Here are three things you could try this month:

‍
1. Think back to your last data meeting. How much time went to student strengths? To context?
2. Take stock of what you screen. Which parts of the whole child does your current process
capture, and which are known only to individual teachers?
3. Follow one student's story. Choose a recent referral and ask: did the support match what was driving the concern, or just the behavior we saw?

‍
For schools looking for a tool built around these ideas, we're excited that the ESSY Whole Child Screener has been integrated into the Cascades platform so these data can sit alongside other data and within a slick assessment to intervention platform. But the real shift starts with the questions we ask.

‍
In the end, screening isn't about sorting students. It's about getting them the right support sooner, so they can thrive. Every student needs a team that takes the time to ask why.

‍