How to document harm when services disappear

Faith’s daughter lost her day program with six weeks’ notice, the kind of notice that reads as generous on a policy memo and lands as a demolition in a family’s actual week. Faith spent those six weeks scrambling for coverage, not filing paperwork, because paperwork felt like a luxury she didn’t have time for while she was rebuilding her daughter’s entire daily structure from nothing. Three months later, exhausted, having missed eleven days of work, she finally sat down and built the file she should have started on day one. This is the post about what that file contained, and about why four specific categories of documentation are what turn a quiet family unraveling into evidence anyone else has to take seriously.

Harm from a service cut rarely announces itself

Here’s what the bureaucratic metrics won’t tell you: when a service disappears, the harm that follows almost never shows up as a single dramatic event with an obvious paper trail. It shows up as a skill that quietly stops being used and eventually stops being possible. It shows up as sleep that gets worse over six weeks instead of overnight. It shows up as a caregiver who starts missing partial shifts, then full days, then loses a promotion she was up for. None of that generates an incident report on its own. All of it is real, documented harm if someone writes it down before it fades into “that was a hard stretch” in everyone’s memory.

This is not because agencies or courts don’t care about this kind of harm. It’s because the systems that adjudicate these disputes, appeals boards, legislative committees, ombuds offices, run on documented facts, and quiet unraveling doesn’t generate documented facts by default. You have to generate them.

The timeline: the spine everything else attaches to

Start with dates. The day the service ended. Every notice you received, with the date it arrived and what it said. Every appeal you filed and its outcome. This sounds obvious, and it is, which is exactly why it’s the piece most families skip when they’re in the thick of the actual crisis. Faith rebuilt hers from old text messages and calendar entries three months later. It took a weekend, and it would have taken twenty minutes if she’d built it the week the notice arrived.

Functional regression: naming what was working before

The single most persuasive piece of documentation in a service-loss case is a specific, dated comparison of what your family member could do before the cut and what changed after. Not “she’s struggling more.” Specific: “Before March 3rd, she independently prepared her own breakfast five mornings a week. As of April 20th, she requires full physical assistance and has had two kitchen safety incidents.” The specificity is what makes it undeniable. Vague decline invites argument. Specific, dated regression does not.

Safety incidents: the category that changes the conversation

Falls, elopement events, injuries, and ER visits that started or increased after a service ended belong in their own dated log, separate from the general regression narrative. Safety incidents move a conversation from “quality of life concern” to “documented risk,” and documented risk gets a faster response from every audience this file might reach, an appeal reviewer, a legislator’s staff, or an ombuds investigator.

Caregiver impact: the harm that’s easiest to erase

Missed work hours. Reduced shifts. A promotion that didn’t happen. Sleep loss with documented health effects, if you’ve seen a doctor about it. This category gets left out of most families’ documentation entirely, because caregivers are trained, by the whole culture around this work, to treat their own exhaustion as beside the point. It is not beside the point. Caregiver impact is real, measurable economic and health harm, directly caused by a service elimination, and it belongs in the file with the same specificity as everything else.

What the file is actually for

Faith’s file didn’t get her daughter’s day program back. I want to be honest about that rather than promise a happy ending that didn’t happen for her specific family, because false reassurance isn’t what this voice does. But eight months after she built it, a state disability rights organization compiling testimony for a legislative committee reviewing day program funding cuts asked local families for documented examples. Faith’s four-category file, specific and dated, was one of the ones used. Two families in neighboring counties got their programs restored after that hearing. Faith’s daughter’s program stayed closed. The documentation still did something, just not the something Faith originally needed it for.

That’s the honest truth about this kind of documentation. It doesn’t always fix your specific problem. It builds the evidence base that fixes the next family’s problem, and sometimes, if you’re persistent and a little lucky, it fixes yours too. Start the file today, whether the cut already happened or is still a rumor on next year’s budget memo. The version of you three months from now, exhausted and trying to reconstruct a timeline from memory, will be grateful you did.

Jim Palasty is the founder of OASIS for Autism and a single father of an adult autistic daughter in Michigan.