State Visibility Into District Incident and Case Data

Wisconsin’s case study in the Learning Agenda Playbook carries a title that sums up a problem many state education agencies share: “You Can’t Lead What You Can’t See.” For school safety, well-being and civil rights, what states often can’t see is what happens in district incident and case records.

Wisconsin: building an information foundation first

Wisconsin’s Department of Public Instruction chose its four-year-old kindergarten programs as a priority. According to the case study, early childhood programs ran across multiple systems, agencies and partners, which made it difficult to know who was being served, how programs operated, or what outcomes they produced.

Instead of moving straight to policy changes, the team started by understanding what information already existed. It inventoried the department’s data, partnered with the state Department of Children and Families on targeted data collection using federal grant funds, and studied other states’ early childhood approaches with help from REL Midwest. The team gathered what it learned into a living “Key Learnings” document and framed its learning question around whether the information currently collected gives the state the oversight it needs.

Kansas: from separate silos to one system

Kansas faced a different version of the same issue. Its case study describes how accreditation, federal identification, at-risk accountability and comprehensive needs assessments had operated as separate structures instead of an integrated system. The Kansas State Department of Education’s team asked how to bring those parts into alignment and built a school improvement logic model to map how they relate. The result was a shared language across divisions and clearer opportunities to reduce duplication.

The same problem, applied to incidents and cases

Incident and case data often has both problems at once. It’s fragmented, like Wisconsin’s early childhood information, and siloed, like Kansas’s improvement structures:

• Every district collects it differently. One district’s intake form doesn’t match another’s, and categories like “harassment” or “threat” aren’t defined the same way.
• Each department keeps its own records. Title IX, student conduct, special education, HR and safety teams often use separate spreadsheets or inboxes, even when the same student or incident is involved.
• Reports are rebuilt by hand. When a board, a state agency or an investigator asks for numbers, staff reconstruct them from scattered records.

As a result, a state agency asking basic questions — how many reports, how quickly they’re resolved, where patterns are emerging — has little it can rely on. Step 3 of the playbook, which asks teams to inventory existing data and identify knowledge gaps, tends to surface this quickly.

Oversight without exposure

Visibility doesn’t mean a state should see every case. Incident and case files contain some of the most sensitive information schools hold, including student education records protected by the Family Educational Rights and Privacy Act (FERPA). A workable model separates two levels of access:

• District staff work individual cases and see the details they need to do that work.
• State staff see patterns across districts, such as volume, timeliness, outcomes and trends, without student names.

That separation protects students, and it makes districts more willing to participate, because sharing patterns doesn’t mean giving up control of their records.

What a consistent cross-district view requires

Wisconsin and Kansas both found that understanding the system came before improving it. For incident and case data, a usable statewide view depends on a few basics:

• Shared case types and definitions across participating districts
• A date recorded for each stage, from intake to resolution
• Outcomes captured in a consistent format, not only in narrative notes
• Reporting that rolls up automatically instead of being assembled by hand
• Permissions that keep each district’s cases visible only to that district

This is the model Casearoo is built around: districts and campuses manage their own cases, while state departments of education get roll-up reporting across them. For districts, the same structure solves the everyday problems described in why Title IX teams outgrow spreadsheets and email and what education case management is. For the kinds of questions a state might ask of this data, see Student Well-Being Data: What State Learning Agendas Need.

Key takeaways

• Wisconsin found early childhood information spread across systems and agencies, and built an information foundation before changing policy.
• Kansas found school improvement structures operating as silos and mapped them into one system.
• Incident and case data is often both fragmented across districts and siloed across departments.
• States need patterns, not student names. Scoped access lets districts share without giving up control of their records.
• A consistent view requires shared definitions, dated stages, structured outcomes and automatic roll-up reporting.

Sources

1. Learning Agenda Playbook, “You Can’t Lead What You Can’t See: Wisconsin Builds the Information Foundation for 4K Decision-Making”
2. Learning Agenda Playbook, “From Fragmentation to Coherence: Kansas’s Journey to a Unified School Improvement System”
3. Learning Agenda Playbook, “Step 3: Identify Key Knowledge Gaps”

How Casearoo handles this: case management for state education agencies.