What a Parent's Attorney Looks For in a Case File (And Why Most Districts Don't Have It)

I've sat across the table from a lot of parents over the years. Most of them just wanted to understand what happened to their kid. But every so often, a parent showed up with an attorney instead of a question, and the tone of the meeting changed completely.

When that happens, the conversation stops being about the incident. It becomes about the file.

Here's what I mean. An attorney representing a parent in a school discipline matter isn't asking "was my client guilty." They're asking a narrower, more dangerous question: can the district prove it followed its own process? In Massachusetts, that means demonstrating compliance with MGL c. 71 §37H, §37H½, §37H¾, or 603 CMR 49.00, depending on the case type. Not "we're pretty sure we did the right thing." Prove it, in writing, with dates.

That's the moment most districts realize what they actually have on file.

What's usually in the folder

After 20-plus years in buildings and at the district level, I can tell you what a typical case file looks like when an attorney requests it. It's rarely one thing. It's an email thread with the parent, another email thread with the counselor, a Word document that got saved three different times with three different filenames, a handwritten note from a hallway conversation, and an administrator's memory of a phone call that never got documented at all.

Individually, none of that is dishonest. It's just how investigations actually happen in a busy building. But laid side by side, in front of an attorney trained to find gaps, that folder tells a very different story than the one you intended. Missing dates. No clear notice of charges. No documented opportunity for the student to respond. No timestamp showing when the two-prong bullying determination was actually made versus when it was written up after the fact.

Attorneys don't need to prove the district did something wrong. They just need to show the district can't prove it did things right. That's a much lower bar, and it's the one that actually gets districts into trouble.

What they're actually checking for

Strip away the specifics of any individual case, and the questions are almost always the same:

• Was the student given proper notice, and can you show when?
• Was there a documented opportunity to respond before a consequence was imposed?
• If the student had an IEP or 504 plan, was that flagged before a removal decision, and was a manifestation determination properly triggered?
• For a bullying complaint, was the two-prong determination actually made, and were both families notified as required?
• Is there a consistent, timestamped record of who did what, and when, from intake to resolution?

None of these are complicated questions. They're the same nine or ten checkpoints every trained administrator already knows belong in a compliant investigation. The problem isn't that administrators don't know the rules. It's that knowing the rules and having a system that forces you to document them, every time, under pressure, in the middle of a chaotic school day, are two completely different things.

Why "we already have a process" doesn't hold up

I hear this a lot from districts. And I believe them. Most districts do have a process, usually a binder, a checklist, or a set of templates that district counsel put together years ago.

The problem isn't the process. It's that the process lives outside the actual work. It's a reference document, not a system. Nothing stops an administrator from skipping a step during a chaotic Tuesday when three things are happening at once. Nothing timestamps when a decision was actually made versus when it was written down. Nothing flags, automatically, that a student's IEP status should have triggered a manifestation determination review before a suspension was finalized.

A process that depends entirely on an individual administrator remembering every step, every time, across every building, isn't really a system. It's a hope.

What this actually costs a district

This isn't an abstract risk. It's the difference between a case that gets resolved quietly and one that turns into a formal complaint, a hearing, or worse, a pattern an attorney can point to across multiple cases in the same district. Once one case reveals inconsistent documentation, the next question is always the same: how many other cases look like this one?

That's the question that keeps superintendents up at night. Not any single case, but the pattern.

The fix isn't more training

I want to be clear about something, because I think it gets missed. This isn't a training problem. I've worked with excellent, well-trained administrators who still couldn't produce a clean file under pressure, not because they didn't know what was required, but because nothing in their day-to-day workflow made compliance the path of least resistance.

The fix isn't another PD session on due process. It's a system that makes the compliant path and the easy path the same path, so that every administrator, regardless of experience level, produces a defensible record without having to remember every statutory requirement in the middle of a crisis.

That's the gap I built IncidentMethod to close.