Document Inventory and Triage: A Permission Slip Is a Participation Problem

Nobody remediates everything. The defensible position is a dated, prioritized queue, not a promise to fix it all.

At some point you'll get handed a number — thousands of PDFs across every school in the district — and it'll feel impossible. It isn't the number that matters. It's the smaller number left after two gates, and getting there is the actual work.

Gate one: should this even be a document?

Retire whatever's superseded or unopened in two years. Replace with an actual web page whatever never needed to be a PDF — most permission slips and notices fall in this category. Recreate from the source file wherever it still exists; fixing a scanned PDF by hand is always more expensive than re-exporting properly from whatever made it. In a typical district document estate, this gate alone clears a meaningful share of the total before a dollar gets spent on remediation, and the decisions are permanent.

Gate two: does an exception actually apply?

The federal rule's exceptions (opens in new window) cover archived content and certain preexisting documents. Test them item by item, in writing, with a named decision-maker — never by folder sweep. And remember the crucial limit: an exception removes the default obligation to have already fixed something. It never removes your duty to provide that content accessibly the moment a specific parent or student asks.

One trap specific to this sector: the password-protected exception covers documents about one specific student or account, not your LMS or curriculum platform generally. Don't let anyone claim the whole learning platform is exempt because students log in to use it.

Then rank what's left, weighted by participation

Rank survivors by traffic, by stakes, and by complaint volume divided by effort — with "stakes" reading differently here than in most sectors. A permission slip a parent can't read isn't just an accessibility gap. It's a consent that can't actually be given, which means it's a participation problem, not a paperwork one. Weight your queue accordingly: enrollment forms, permission slips, and IEP-adjacent paperwork ahead of general informational content, even where the general content technically sees more traffic.

A named complaint overrides all of that math, every time. And system-generated documents — automated notices out of your student information system, for instance — go to the vendor track. That's a code change, not an editing job, and hand-fixing it repeatedly while the platform keeps generating new broken ones is a losing trade.

This isn't legal advice on how these exceptions apply to your specific document flows — verify against your own counsel. If you want a fast first read on where a document actually stands before you triage it by hand, ask Luke to take a look. See our methodology for how we verify claims like these.

Previous: your first 90 days · Next: procurement language that actually works

---

Sources: 28 CFR 35.201 — Exceptions (opens in new window) · 34 CFR Part 104 — Section 504 Regulations (opens in new window) · Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · U.S. Access Board — Revised 508 Standards (opens in new window)