Building the Record: Complaints, Training, and Your Patients

The question you're actually being asked is never whether you were perfect. It's whether you knew, and what you did about it.

A dated record is the only thing that answers that question. Not your intentions, not the program you meant to build — the record. Here's how to build one without it consuming your whole role.

Log it, solve access first, fix the defect separately

Whatever channel a complaint or accommodation request arrives on — the patient-relations line, a portal message, front desk, a family member on the phone — log it the day it arrives. An unlogged complaint is the worst fact that can exist in any file, because it means the record shows you didn't know when the truth is you did.

Acknowledge fast — in this sector, sometimes within the hour, because a patient who can't read tonight's discharge instructions has a same-day problem, not a next-sprint one. Solve their actual access first, by whatever means available, while the underlying fix gets scheduled on its own track. A nurse walking through discharge instructions verbally and confirming teach-back is real, complete access — even though the portal rendering is still broken. Those are two separate tracks, and treating them as one is how people end up waiting for a system fix when what they needed was a phone call.

Reproduce and classify: isolated, or systemic? A broken template outranks a broken page, because fixing the template fixes every instance of it. Close the loop with the person — tell them what changed, not just that something did.

Twelve columns, filled in every time

Date received. Channel. Person and contact, or anonymous. Item affected. The barrier in the person's own words. Assistive technology involved, if known. Access provided now, and the date. Systemic or isolated. Corrective action and owner. Target date. Resolution date. What the person was actually told. That last column is the one people skip, and the one that matters most.

Training tied to system access, not a once-a-year course

Short, role-specific, repeated. Content authors need headings, alt text, and the document checker. Whoever buys software needs to demand and actually read an ACR (opens in new window). Clinical staff need the telehealth accommodation path — interpreters, captioning — documented and rehearsed, not discovered mid-visit. Tie publishing rights to completed training; it's the only enforcement mechanism that reliably works, and record every completion, because in year one it's one of the only metrics you'll have.

The people this is actually for

Find your local disability organization. Offer a standing invitation and pay them for structured testing time, the same way you'd pay any other consultant. Bring them your top patient tasks before launch, not after a complaint tells you what you missed. Report back what changed because of what they found. One genuine relationship like this surfaces more real barriers than any scanner, and it changes what your program actually is — not a compliance exercise managed around a deadline, but a service for people who are still here whether or not they ever file a complaint.

This isn't legal advice on what your specific grievance procedure needs to contain — verify the details against HHS's own guidance (opens in new window) and your counsel. When a complaint names a specific page or document, ask Luke to take a first pass at it while you're logging the entry.

Previous: how to read a VPAT · Next: reporting up, your maturity roadmap, and the budget ask

---

Sources: HHS Guidance on Section 1557 (opens in new window) · Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · Accessibility Conformance Report (ACR) overview (opens in new window) · HHS Final Rule — Nondiscrimination in Health Programs and Activities (opens in new window)