Most of This Work Was Never in a System

Ask a district how it manages cases and the answer will be about one or two offices. Title IX has something, probably. Special education has something, because the paperwork was always going to force it. Everything else turns into a conversation about a shared drive.

That is not a criticism of anybody. It is the predictable result of how this software has been sold.

Start with a district's own reporting page

The quickest way to see the shape of the problem is to open the page where an institution tells people where to take a concern. Sacramento City Unified publishes one, and it is a good example because it is clear, well organized and genuinely trying to help.

It offers an escalation ladder — teacher, principal, district office, superintendent, board — and then six separate intake routes alongside it: a constituent services office, the state uniform complaint procedure, Title IX, an anonymous tip line, bullying, and a general resource page. Under the formal heading there are three distinct complaint types, each with its own process.

It also lists two Title IX Coordinators. One handles matters where personnel are involved. The other handles student-on-student. Same regulation, same office, two different people, two different queues.

Now notice what is not on that page. Attendance and truancy. Transportation. Athletics. Health services. Special education disputes. Records requests. Technology misuse. Restraint and seclusion. Every one of those produces case-shaped work in that same district, and none of them is where a parent would be sent from this page — because none of them is a complaint channel. They are operational functions that happen to generate cases.

Count the rest

Do that exercise properly and the list gets long. Count the functions that receive a report and then open something with a person who raised it, a person it concerns, a sequence of events, a decision at the end, and a record somebody may ask for a year later.

Civil rights and equity is several functions, not one: sex-based complaints involving students, the same involving employees, race and national origin, disability accommodations and grievances, services for English learners, and whatever umbrella complaint procedure the state runs.

Then the student-facing work. Conduct and discipline. Bullying and harassment. Threat assessment and behavioral intervention. Restraint and seclusion. Attendance. The homeless and foster youth liaison. Counseling and wellness referrals. Special education disputes.

Then employees. HR grievances. Employee misconduct. Discrimination complaints. Workers compensation. Contractual grievances.

Then the operational side, which is where people stop expecting it: school safety and law enforcement referrals, health services incidents, transportation, athletics, child nutrition, facilities and liability claims, technology misuse. And finally records requests and whatever escalates to a superintendent or a board.

In K-12 that runs to roughly twenty-eight functions. In higher education it comfortably passes forty once you add academic integrity, residence life, students-of-concern teams, bias response, ombuds, research integrity, financial aid appeals, grade appeals, student organizations and clinical placements.

No district has all of them, and no two draw the boundaries the same way. A small district might run this work in a dozen places. A large one, twenty-five or more. A university, past thirty.

Nobody buys thirty systems

This is the part that usually gets described wrong.

The familiar framing is fragmentation: too many systems, none of them talking to each other, data stranded in silos. That is a real problem and it is not the main one.

Nobody buys thirty systems. What actually happens is that most of these functions get no system at all. Two or three offices with a budget and an existing vendor relationship get software. The rest run on email, a folder, and a spreadsheet that one person maintains and nobody else fully understands.

Not because anyone decided that. Because there was never a product or a budget line for the attendance office's case records.

The integration problem assumes the records already exist somewhere structured. For most of this work, they do not.

The shape is the same every time

Put any two of those functions side by side and the differences are vocabulary and who is allowed to see the file.

Underneath, the shape does not move. Somebody reports something. Somebody is the subject of it. There are people who saw it, documents that bear on it, and a sequence of events that has to stay straight. Somebody decides. Something is owed afterwards — a notice, a meeting, a support, a follow-up — and somebody has to be able to show it happened.

That is one shape. It is why this software gets sold under so many different names: Title IX software, conduct software, behavioral intervention software, grievance tracking. Each one is named after whichever office had the budget, and each quietly assumes the other twenty-five functions are somebody else's problem.

The stages that shape moves through, from the first report to closure, are walked through in order in Case Management Workflow: From Report to Closure.

What changes if you accept that

Mostly the question you ask when you are buying.

It stops being which Title IX product and becomes what it would take for the twentieth function to sit in the same system as the first. That turns out to be a question about three unglamorous things.

• What it costs to add an office. Per-user pricing is what keeps the twentieth function out, and it is rarely discussed as a design decision.
• How precisely permissions can be drawn, so teams that should not see each other's files genuinely cannot.
• Whether somebody without a license can submit a report at all — because the people who receive reports are almost never the people who work them.

Those three decide whether a case system covers two offices or twenty. Almost nothing on a feature comparison page addresses any of them.

Sources

1. Sacramento City Unified School District, Complaints and Concerns — the reporting page described above, including its two Title IX Coordinator designations.
2. U.S. Department of Education Office for Civil Rights, Civil Rights Data Collection — the collection districts report discipline, restraint and harassment data into.

How Casearoo handles this: case management for any department.