Why Student Support Data Has Outgrown Spreadsheets

By: Matt Barrow
Director of Services, Pearl Education

Student support has changed. The systems many districts rely on haven’t kept pace.

In 2025, Indiana retained 3,040 third graders under the state’s new reading proficiency law. Nearly 7,000 more were promoted through good-cause exemptions. Every one of those decisions—whether a student was retained or promoted—required documentation. Districts needed to demonstrate what interventions the student received, when families were notified, what the reading plan included, and whether required assessments had been administered appropriately.

This is the environment student support data now supports. And it highlights a growing reality: many of the tools districts rely on today were designed for a very different set of expectations.

Fourteen states currently have third-grade retention laws tied to reading proficiency, and several more have enacted legislation that will take effect over the next few years. Individual policies continue to evolve. Tennessee has softened portions of its retention requirements. Michigan repealed its policy in 2023, although legislation has recently advanced to reinstate it.

While the details vary by state, the broader trend is consistent. Student support is becoming more accountable. Districts are increasingly expected to document interventions, maintain defensible records, and demonstrate continuity of support across multiple years.

For many districts, that work is still being managed with spreadsheets.

What Today’s Accountability Environment Demands

When a student is identified as being at risk of retention, that designation triggers far more than an intervention plan. It creates a series of instructional, operational, and compliance responsibilities that span multiple teams, systems, and school years.

Consider everything that may need to be documented:

Screening and diagnostic assessments across kindergarten through third grade, including results, dates, and administrators.
Individual reading improvement plans with signatures, goals, and documented revisions.
Delivery of required interventions, whether that includes daily reading instruction, small-group phonics, or high-dosage tutoring.
Summer reading camp participation, including attendance, instructional hours, curriculum, and instructors.
Parent notifications delivered according to state timelines.
Assessment results across multiple testing windows.
Documentation supporting any good-cause exemption determination.

Each of these components contributes to a decision that districts may need to explain to families, support during an appeals process, or provide during a state audit.

A spreadsheet provides a snapshot of information at a single point in time. It was never intended to serve as the long-term system of record for decisions that can shape a student’s educational trajectory.

Student Support Is No Longer a Single Program

Reading retention laws illustrate the challenge clearly, but they are only one example of a much broader shift.

Today’s districts are often managing multiple student support initiatives simultaneously—including MTSS, high-impact tutoring, reading interventions, dyslexia screening, summer learning, credit recovery, and other state-funded acceleration programs.

Each initiative may have its own funding source, reporting requirements, implementation expectations, and stakeholders. Yet many involve the same students, educators, and instructional goals.

That creates a growing need for districts to connect information across programs rather than managing each initiative independently. Student support is no longer a collection of isolated interventions. It has become an interconnected system that requires shared visibility and reliable documentation.

Where Spreadsheets Begin to Break Down

The people who built these spreadsheets understand their limitations. They built them because they solved an immediate problem, and because the expectations surrounding student support were different when many of these processes were established.

As those expectations have grown, the gaps have become more difficult to ignore.

Spreadsheets typically do not update in real time. The dashboard an MTSS coordinator built reflects the last time someone refreshed the file, not necessarily what happened yesterday.

They also tend to depend heavily on the person who created them. When that individual leaves the district, undocumented formulas, personal naming conventions, and broken links often leave the next team rebuilding processes from scratch.

Integration presents another challenge. Reading intervention data may live in one spreadsheet. Tutoring participation may exist in a provider portal. Assessment results are housed in the student information system. Someone eventually combines everything manually to answer a question, meaning the picture is often incomplete before it is even finished.

Role-based access can also become difficult to manage. Either everyone with the file has visibility into all student information, or access becomes so restrictive that files are emailed back and forth between staff. Beyond being inefficient, that introduces unnecessary privacy concerns and creates FERPA risks districts work hard to avoid.

Perhaps most importantly, spreadsheets rarely provide the audit trail today’s accountability environment expects. When districts are asked who entered a score, when a reading plan changed, or whether a required family notification was delivered on time, those answers are often difficult to verify with confidence.

They also struggle to preserve continuity over time. Information about interventions delivered in second grade often lives in one teacher’s file. Third-grade teams create another. The complete story of a student’s support has to be reconstructed whenever someone needs it.

Those tradeoffs were manageable when student support data was primarily used for internal coordination.

Today, that audience increasingly includes district leadership, state agencies, families, auditors, and, in some cases, legal proceedings.

A Broader Policy Shift

Retention laws are one visible example of a larger policy movement.

Science of Reading legislation, dyslexia screening mandates, MTSS documentation expectations, and post-ESSER accountability initiatives are all moving in a similar direction. States are asking districts to demonstrate not only which supports were available, but which supports students actually received, when they received them, and how those supports contributed to outcomes.

Education researchers have highlighted another challenge: many state longitudinal data systems still cannot reliably connect interventions with long-term student outcomes because the underlying intervention data is inconsistent or incomplete.

That same challenge exists within many districts.

If interventions cannot be documented in ways that are consistent, connected, and retrievable, districts are being asked to make increasingly important decisions using infrastructure that was never designed for today’s accountability expectations.

What Districts Should Be Building Toward

The conversation is ultimately larger than software.

It is about building student support infrastructure that reflects how districts now operate and what policymakers increasingly expect.

Whatever technology a district uses, today’s environment increasingly requires systems that can:

Update in real time so student support reflects current implementation.
Provide visibility across district, school, grade, program, and individual student levels.
Preserve institutional knowledge despite staff turnover.
Integrate student information systems, assessment platforms, and external tutoring or intervention providers.
Support role-based access so educators, administrators, providers, and auditors each see only the information they need.
Maintain a defensible audit trail that documents meaningful changes over time.
Follow students across schools and grade levels so intervention history builds rather than restarts.

Most districts are still working toward that vision.

The encouraging news is that the need has become increasingly visible. Accountability requirements continue to evolve, and they are making clear that reliable student support data is no longer simply an operational convenience—it is becoming foundational to instructional decision-making, compliance, and long-term program effectiveness.

For years, spreadsheets have served districts well as practical tools for coordinating student support. But today’s expectations require something different.

The question is no longer whether student support data will become more important. It already has.

The question for district leaders is whether the infrastructure supporting that work is evolving quickly enough to keep pace with the responsibilities districts now carry.

Is Your Student Support Data Built for Today’s Accountability Expectations?

As student support programs grow more complex and reporting requirements continue to evolve, many districts are rethinking how they manage intervention, implementation, and outcome data.

If you’re evaluating whether your current systems can support the visibility, documentation, and accountability your teams need, we’d be happy to share how districts are building a more connected approach to student support.

Schedule a conversation with Pearl Education to explore practical strategies for modernizing student support operations and data management.