The site visit is three months out. You know what you're supposed to have. But somewhere between this semester's CALIPSO entries, last semester's supervision logs, and the session notes living in three different places, the picture isn't as clean as you'd like.
That's a familiar scenario for a lot of university SLP programs. And here's the thing: meeting CAA accreditation documentation requirements isn't conceptually hard. The standards are clear. The challenge is operational — building a workflow that keeps your program ready to demonstrate compliance at any point in the cycle, not just in the weeks before a deadline.
This post covers what the CAA actually scrutinizes, the deficiency areas programs get cited for most often, and how to build documentation habits that hold up when it counts.
What the CAA Is Actually Looking For Across Your Documentation
Most program directors think of speech language pathology accreditation as an event: submit the annual report, host the site visit, wait for feedback. But the CAA's standards are continuous obligations, not periodic checkboxes.1
The standards span governance, curriculum, faculty, students, and resources. Documentation requirements show up across all of them. A few of the most foundational:
Student outcome data must be published on the program website with specific wording, updated by January 1 each year. This includes Praxis pass rates, graduation rates, and employment outcomes, labeled explicitly as "Student Achievement Data" or "Student Outcome Data."
Clinical clock hours must be verified by a CCC-SLP. The minimum is 400 hours per student, with 25 observation hours required before practicum begins. The records supporting this need to exist and be traceable, not just tallied in CALIPSO at semester's end.
Supervisor credentials and co-signatures are required on all session documentation before it enters the official clinical record.
Clinical site compliance must be documented for both on-campus and external placements (Standard 3.6). Each site needs to be on record as meeting ethical and regulatory standards.
One more thing worth noting: a revision to Standard 3.4 took effect in October 2025. Programs submitting after that date now need documented evidence of person- and family-centered approaches in the curriculum and in actual clinical practice, not just a reference in the program handbook.2
Compliance isn't what you submit. It's what you can produce if the CAA asks.
Five Documentation Areas Programs Actually Get Cited For
According to the CAA's compliance trend reports, certain deficiencies show up repeatedly across accredited programs.3 These aren't edge cases. They're patterns worth knowing about before a site visit surfaces them.
Standard 1.9: Accreditation display on the program website. The website must include a specific accreditation statement, the degree the accreditation covers, and CAA's full name, address, and phone number.4 This is one of the most frequently cited deficiencies in compliance trend data, and it's also one of the simplest to fix. A program coordinator who checks the website two weeks before a site visit and finds the statement missing is looking at a gap that's been there for months.
Standard 4.7: Student progress documentation. Programs must maintain audit-ready records of each student's coursework completion, clinical hours, and KASA competency benchmarks throughout the entire accreditation cycle.5 Not just at annual report time. A spreadsheet updated at semester end doesn't meet this standard if a compliance review arrives in November.
Supervisor co-signatures. All session documentation must be co-signed by a CCC-SLP before it becomes part of the official clinical record. That means every SOAP note, every progress note, every evaluation written by a student needs a supervisor signature before it's final. If you can't produce a clear co-signature trail for every session, that's a gap in your ASHA accreditation standards compliance, whether or not it's ever asked about.
Standard 3.6: Clinical site records. Each clinical site, on-campus and external, must be documented as compliant with ethical and regulatory standards. This data goes into the CAA worksheet manually. Programs that treat this as a once-a-year exercise often find the records are incomplete or out of date.
Annual report accuracy. Annual reports are due February 1 or August 1, depending on the program's cycle.6 Errors or missing data trigger compliance notices. Programs that manually compile this data in the final weeks before the deadline are the most exposed to gaps.
The Student-Supervisor Documentation Loop — Why Most Programs Struggle Here
The documentation workflow in a university clinic is fundamentally different from a private practice. Students write the session notes. But supervisors are legally responsible for those notes before they become part of the official record. That creates a two-step approval loop — student submits, supervisor reviews and co-signs, note is finalized — that has to run across an entire cohort's caseloads, every session.
Without a system that tracks note status, supervisors have no central view of what's been submitted, what's pending, and what's been signed. The default becomes chasing people down by email or text, or walking the hall at the end of clinic day trying to remember which students still have notes outstanding.
At site visits, the CAA expects to see evidence that this workflow actually happened — not just that session notes exist, but that the co-signature trail is intact and the supervision oversight is documented throughout.
Most CSD programs use CALIPSO for clinical hours tracking and KASA competency documentation, and they should. But CALIPSO doesn't handle CSD program documentation at the session level. It doesn't manage the note approval workflow, the co-signature trail, or billing. Programs running CALIPSO alongside paper notes or a generic EMR end up with their compliance evidence split across multiple systems — which means reconciling it manually when it matters most.
An EMR built for the university model, with built-in supervisor notification, approval workflows, and document completion verification, closes that gap. Students enter notes directly, supervisors get notified and can review and co-sign without switching tools, and the record of who approved what and when is part of the system, not a separate spreadsheet.
How to Keep Your Program Audit-Ready Between Report Cycles
The programs that struggle most during site visits aren't the ones with poor documentation. They're the ones with documentation scattered across tools and workflows that were never designed to produce a university clinic compliance trail on demand.
Three practices that make a real difference:
1. Treat documentation as a continuous workflow, not a deadline sprint. Build visibility into what's complete and what's pending at all times. Not just in the three weeks before an annual report is due, but every week of the semester. Supervisors shouldn't have to guess what's still outstanding.
2. Consolidate your session documentation and supervision records. If co-signatures, session notes, and clinical hours live in different places, your audit-readiness depends on whoever can manually pull them together. That's fragile. One system that covers session documentation, approval workflows, and reporting eliminates the reconciliation problem entirely.
3. Run a documentation audit cadence by semester. A monthly or per-semester review surfaces gaps while there's still time to address them. A practicum coordinator who sets a standing calendar reminder to check for unsigned notes and incomplete records catches those gaps before they become patterns. A program that first reviews documentation in the three weeks before a site visit sometimes finds problems going back two semesters.
EMR software designed for university clinics can surface documentation gaps in real time, generate compliance-relevant reports without manual spreadsheet work, and give supervisors a live view of what's pending across the full caseload. When the University of Wisconsin-Milwaukee needed a specific compliance report built on a tight timeline, ClinicNote turned it around in under a week. That's the kind of capacity that changes how a program operates going into a site visit.
Ready When the CAA Comes Knocking?
CAA accreditation documentation requirements aren't about generating more paperwork. They're about having a traceable workflow that produces evidence when it's asked for, without a last-minute scramble.
The most common compliance gaps aren't caused by not knowing the standards. They're caused by workflows that were never designed to maintain a continuous compliance trail.
ClinicNote was built specifically for university clinic environments, including the supervisor approval loop, student caseload restrictions, and the reporting capabilities that make compliance data accessible without manual compile work. If you're ready to see how it works in practice, get a demo and we'll walk you through how other university speech language pathology EMR programs use it to stay audit-ready year-round.
Sources
- https://caa.asha.org/reporting/standards/
- https://caa.asha.org/siteassets/files/accreditation-standards-for-graduate-programs.pdf
- https://caa.asha.org/reporting/standards/standards-compliance-trends-2023-summary/
- https://caa.asha.org/ask-the-caa/public-information
- https://caa.asha.org/ask-the-caa/maintaining-student-records/
- https://caa.asha.org/reporting/accreditation-reporting-procedures/