What Student Data Do Principals Actually Need (And What Just Looks Good at Board Meetings)

Your plan is gone by 9:15 on Monday morning. A parent is waiting. A teacher is covering for someone who called in. There is a situation from Friday that resurfaced. You are not leading from data. You are running from fire to fire with no early warning system telling you which fires were visible a week ago and which ones nobody captured. That is the principal's actual problem with student data, and it has nothing to do with whether your dashboard is sophisticated enough. The problem is that almost everything principals are given to look at is a lagging indicator. Attendance reports. Discipline tallies. Benchmark scores. All of them tell you what already happened. None of them tell you what is happening right now, in room 214, with a kid three teachers have each mentioned quietly in the last two weeks but nobody has connected. You need to know before it becomes a crisis. Most systems are not built to help you do that.

The edtech industry has spent a decade selling principals on dashboards. The dashboards got better-looking every year. The decisions did not.

There is a specific kind of data meeting that happens in schools across the country. A principal sits down with a report that is thirty-seven pages long, generated by a platform that cost more than the reading interventionist's salary, and tries to figure out what to do differently on Tuesday. The report is full of numbers. Attendance broken down by demographic subgroup. Discipline incidents sorted by category. Benchmark performance by teacher, by grade, by standard. It is comprehensive in the way that a photograph of a fire is comprehensive. It tells you something happened. It tells you nothing about what to do next.

The question underneath all of it, the one the report cannot answer, is: what is actually going on with our kids right now? Not last quarter. Now.

94 Percent of Principals Report Using Data Regularly. Almost None of Them Trust It.

A 2019 survey from the Education Research Alliance at Tulane found that nearly all school leaders report using student data regularly in their decision-making. The same survey found that a much smaller share believed that data actually reflected what was happening in their schools. That gap is not an accident.

The data principals are given is, almost universally, data collected for compliance purposes. State reporting requirements, federal accountability systems, and board presentation cycles drive what gets measured and when. The result is a set of metrics that are defensible in public and largely useless for daily leadership. Hattie (2009) synthesized over 800 meta-analyses covering millions of students and found that the variables with the highest impact on student outcomes were relational and instructional. Not demographic. Not attendance-threshold. The things that move outcomes are things like feedback quality, teacher-student relationships, and the kind of early, responsive intervention that requires someone to notice something before it shows up in a number.

Lagging indicators, by definition, cannot power that kind of response. By the time a chronic absenteeism flag triggers in your system, the student has been gone more than ten percent of the year. The window for early intervention closed months ago.

Why the Dashboard Your Board Loves Is Probably the One Failing Your Teachers

Bryk and Schneider (2002) spent years studying school improvement in Chicago, and their central finding was that relational trust, not curriculum, not professional development, not technology, was the differentiating factor between schools that improved and schools that did not. In a 2010 follow-up, Bryk expanded on the infrastructure requirements for improvement, and the argument holds here: a school's information architecture either supports or undermines the trust conditions that make improvement possible.

Here is what undermines it. A dashboard built for board presentations asks different questions than a dashboard built for school leadership. A board dashboard optimizes for defensible metrics reported at quarterly intervals. It shows trends. It shows comparisons to prior years. It shows the school in the best available light. It is not wrong that a board needs this. The problem is that most schools have exactly one information system, and it was built for that audience.

When the only data infrastructure a school has is designed for external reporting, principals start making internal decisions with external reporting data. They start treating attendance percentages and discipline category counts as leading indicators of student need, which they are not. A student can be fully present, never disciplined, and in crisis. That student is invisible to a compliance-reporting system.

The reasonable objection here is that principals cannot build a second data system from scratch. Nobody has time for that. That is exactly right. The answer is not a second system. The answer is a different kind of first system, one that captures what teachers and counselors already know, in the moment they know it, and surfaces it to the principal before it becomes a documentation exercise. The technology for that exists. What most schools lack is the cultural permission to treat teacher observation as data worth capturing formally.

Darling-Hammond (2017) described the conditions for effective professional learning as nested in a culture where observation and reflection are treated as legitimate sources of knowledge. That same principle applies here. A teacher who notices something about a student and has nowhere to put it except a hallway conversation is not failing the system. The system is failing her. And the principal, downstream, is making decisions without the most current and specific information available in the building.

Fullan (2018) named this the coherence problem. Most schools have data flowing upward to administrators and almost none flowing laterally or back to the people generating it. The people with the richest information about students are classroom teachers. The information architecture treats them as data entry workers rather than as primary sources.

A Middle School That Stopped Mistaking Compliance Data for Operational Intelligence

A 650-student middle school. Title I. A principal three years into the role who had invested real effort in building a data culture. Monthly data meetings. A dashboard subscription. Teacher teams that met weekly to review numbers.

By October of year three, she was ready to admit the meetings were not working. Teachers came prepared. They had looked at the numbers. And then the conversation would stall because the numbers did not tell anyone anything actionable. Attendance was down in sixth grade. Okay. Why? The platform did not know. The benchmark scores in math were flat. Okay. What was actually happening in those classrooms? The platform did not know that either.

What the platform did not capture was that three sixth-grade boys had been quietly regrouping around a new social dynamic since September, and two teachers had each noticed it, and neither of them had a place to put that observation that would connect it to the attendance dip. The counselor had a sense of it too. These three people had collectively enough information to understand what was happening. The data system had none of it.

The friction point was structural. Each person's observation lived in a separate conversation. There was no mechanism for those observations to reach the principal in a form she could act on before the attendance dip became a chronic absenteeism flag. When it did become a flag, three weeks later, the intervention felt reactive, because it was.

The school's counselor later said the hardest part wasn't knowing something was wrong, it was that there was no legitimate channel for a soft concern that wasn't yet a referral. She had a hunch about one of the three boys as early as the second week of September. He was a seventh grader the previous year who'd been reliably engaged, and something had shifted. Not dramatically. Not reportably. Just enough that she noticed. There was no form for that. No field in the platform. No prompt in the weekly team meeting that would have surfaced it. So it stayed in her head until it became a meeting with parents and a documented attendance intervention six weeks later. The information existed. The architecture didn't know what to do with it.

What Technology Cannot Fix Here

The data problem in schools is partly a technology problem. It is mostly a culture problem.

A principal who does not follow up when teachers share concerns will have teachers who stop sharing concerns. That is not a dashboard issue. Bryk and Schneider (2002) are unambiguous that trust is built through human behavior over time, through leaders who act on what they are told and protect the people who tell them uncomfortable things. No platform changes that dynamic. If the culture of a school treats a teacher's observation as an audit risk rather than as intelligence, a better reporting tool will produce the same defensive, sanitized data as the form it replaced.

Pulse does not solve the culture problem. That is worth saying clearly. What changes with a tool like Pulse is the friction of honest capture at the moment of observation, for schools where the culture is already pointed in the right direction. The technology is only as good as the trust conditions around it.

What Leading-Indicator Data Actually Looks Like in Practice

The distinction between lagging and leading indicators is not complicated in theory. It gets complicated when you try to operationalize it inside a school that has been building compliance-reporting infrastructure for twenty years.

Leading indicators in schools are the data points that precede an outcome rather than document it. They are early signals. A student who has stopped participating in a class she used to engage in. A teacher who has mentioned a specific kid in two separate conversations with different adults in the same week, not because anything dramatic happened, but because something small keeps snagging their attention and they can't quite name it yet, which is exactly the moment that matters. A counselor who flagged something on a Tuesday and has not heard back by Thursday. None of these appear in a benchmark report. All of them are more predictive of what happens next than the benchmark report is.

Edmondson (1999) established that the precondition for this kind of information to surface is psychological safety. Teachers who feel safe sharing uncertain, unfinished observations share more specific ones. Specific observations are leading indicators. Vague, sanitized documentation is a lagging indicator dressed up as current data. The platform you use to collect teacher observations either creates conditions for specificity or it does not.

What a principal actually needs is a live view of what teachers are noticing right now, organized by student and surfaced before it requires a formal intervention process. Not a thirty-seven-page report. Not a quarterly trend analysis. A way to answer the question: which students are three adults independently worried about this week, and do those three adults know about each other? That question, answered consistently, is more valuable than any dashboard metric a board has ever asked about.

Voice-based observation capture is built around exactly this. A 30-second note on the walk to the parking lot, from the teacher who just watched something happen, reaches the people who need it before the school day ends, not after a form is submitted at 10pm from memory.

Information That Helps You Lead, Not Just Report

The honest version of a principal's data need is simple. Before a parent calls angry, know. Before a student disappears from engagement, know. Before a situation requires a formal meeting with documentation and district involvement, know.

That requires data flowing from the people closest to students, in real time, in a form that surfaces patterns across observers rather than siloing observations by classroom. Ingersoll and Merrill (2010) identified administrative burden as a primary driver of teacher attrition. Every observation process that adds forms to a teacher's evening is compounding that burden. The collection mechanism has to be light enough that teachers actually use it honestly, not just compliantly. It is worth noting that the schools most likely to have honest data cultures are often not the ones with the best platforms, they are the ones where the principal has made it safe to say something uncertain out loud.

Principals who use Pulse describe the shift as moving from reactive to anticipatory. Not because the platform is predictive in some technical sense, but because it surfaces qualitative teacher intelligence in time to act on it. The board still needs its report. That report should not be the primary tool a principal uses to understand what is happening in her school on a Tuesday morning.

The question worth sitting with is not whether your dashboard looks good. It is whether, right now, you could name the three students your teachers are most quietly worried about, and whether your data system helped you know that, or whether you found out in a hallway. If your current platform cannot close that gap, here is what a different kind of data infrastructure looks like for school leaders.