The site visit notification comes, and most clinic directors immediately think of the submission package: the clinical handbook, student and faculty handbooks, course syllabi, survey data, committee minutes, Praxis pass rate reports. That list is real, and pulling it together takes real time.
But there's another layer that's easier to overlook. The actual clinical record is also on the table. The notes your graduate students wrote last semester. The supervisor co-signatures on each one. The documentation showing 25% direct supervision was provided for each client. The credential records confirming your adjunct supervisors held a current CCC-SLP at the time they supervised.
That's ASHA accreditation EMR documentation territory. And how well your system produces, stores, and surfaces those records has a direct effect on your CAA compliance.
Most clinic directors know the list of documents that need to be ready 30 days before a site visit: handbooks, syllabi, recruitment materials, faculty meeting minutes, admissions procedures, employer and alumni surveys, compiled student assessment data.1 It's a substantial list.
What gets less attention is that the clinical record is equally in scope. Site visitors are evaluating whether your program produces documentation that demonstrates student knowledge and skill development over time. That means actual patient records, written by students, reviewed and co-signed by qualified supervisors. It means evidence of formative assessment over a student's training, not just final grades.
The complication most programs run into is that two separate systems manage this. Clinical hours tracking, KASA documentation, and competency verification typically live in one platform. The actual patient record — SOAP notes, treatment plans, evaluation reports, supervisor sign-offs — lives somewhere else entirely. Sometimes in a separate EMR, sometimes in a shared drive or paper files.
Site visitors look at both. A meaningful way to test your current setup: how long would it take to pull every note written and co-signed by a specific supervisor for a three-month period? If the answer isn't "a few minutes," there's a gap worth addressing before your next review.
Understanding exactly what needs to be in the clinical record helps you evaluate whether your current system is actually producing it. These are the five types most likely to come up during a speech language pathology clinic accreditation review:
SOAP notes with supervisor co-signatures. Every student-authored note needs a co-signature from a clinician who holds a current, valid CCC at the time of supervision.2 That co-signature needs to be in the record and traceable, with a timestamp showing when the review and approval happened. A paper log doesn't give you that audit trail.
Treatment plans and evaluation reports. These need to be dated, linked to the correct client and student clinician, and retrievable by semester, disorder category, or supervisor if needed.
Evidence of formative assessment. CAA distinguishes between formative assessment (ongoing, throughout a student's training) and summative assessment (comprehensive evaluation at key milestones).3 Your EMR's clinical notes are part of that evidence trail, and how they're organized determines how easily that evidence can be demonstrated.
Supervision records. The 25% direct supervision requirement per client contact isn't just a number to hit — it needs to be demonstrable from the documentation itself.4 If a site visitor asks you to show that a specific student received 25% direct supervision for a specific client during a specific semester, your system needs to answer that question.
Supervisor credential records. Every supervising clinician must hold a current CCC-SLP and a current state license at the time of supervision. That includes adjuncts at external practicum sites, where credential tracking tends to be the least systematic and where a lapsed certification is most likely to be caught retroactively rather than in advance.
There's no shortage of CAA accreditation requirements around SLP clinic documentation software — there's just a shortage of systems designed specifically to meet them. Most EMR options built for speech-language pathology work well for private practice: HIPAA compliant, solid documentation templates, good scheduling and billing. But university training clinics are a fundamentally different environment.
For one, they operate under HIPAA and FERPA simultaneously. Patient records are healthcare records; student training records are education records. Most private practice EMRs are designed for one regulatory environment, not both.
Then there are university IT requirements. Multi-factor authentication, IP address restrictions, role-based permission sets — many commercial tools don't support these out of the box. An EMR that fails your IT department's review doesn't get implemented, no matter how polished it looks in a demo. Some clinic directors have spent an extra semester managing paper records after a rejected IT approval while restarting their search.
Student caseload restrictions are another gap. Graduate students should only have access to records for their assigned patients. It's a privacy and compliance requirement, and it's one that private practice tools rarely implement at the system level.
Supervisor co-sign workflows deserve particular attention. University clinics don't just need a signature field — they need the co-sign to function as a tracked queue. Supervisors should be notified when notes are ready for review, the approval trail should be visible and timestamped, and the record should confirm that the sign-off happened at a specific time by a credentialed clinician. That's a meaningfully different feature requirement than adding a second signature line to a template.
CAA's enforcement process is clearly defined. A program that fails to meet standards or submit required reports can be placed on administrative probation for an initial period of one year, with a maximum of three years before accreditation is withdrawn.5
That probationary status isn't private. It appears in CAA's public records and is visible to prospective students evaluating programs. For a graduate program competing for applicants, it's a reputational event that outlasts the probationary period itself.
The deeper stakes are for students already enrolled. Graduates of a program that loses CAA accreditation cannot qualify for CCC-SLP certification, and in most states they cannot obtain a license to practice.6 An entire cohort's clinical career path is affected by a program's accreditation compliance EMR practices, or lack of them.
Documentation failures — missing co-signatures, supervision percentages that can't be demonstrated from the record, lapsed supervisor credentials that weren't caught in time — are the type of compliance issues that both trigger enforcement and are preventable with the right systems in place.
If you're evaluating whether your current system is set up for accreditation compliance, here's a practical checklist. These are baseline requirements to verify before committing to any tool:
Supervisor notification and co-sign approval workflow. Not just a signature field — a tracked queue where supervisors are notified when notes are ready for review, and the record shows who approved what and when.
Document completion verification and gap reporting. The ability to pull an instant report showing which documentation is incomplete or unsigned. You want to find gaps before a site visitor does.
Role-based permissions with student caseload restrictions. Students should access only their assigned patients. This is a compliance requirement, not a configuration preference.
University IT compatibility. MFA and IP address restrictions need to be built in. Confirm your IT department's requirements before evaluating any tool, and confirm the vendor can meet them before you get to implementation.
Custom reporting with reasonable turnaround. Accreditation prep should be a scheduled report pull, not a two-week project. A system that can build or adapt reports quickly when a new compliance need surfaces is worth the ask during demos.
Fast student onboarding. New cohorts arrive every fall semester. If the basics take weeks to learn, documentation quality suffers in the early weeks of each term, and supervisor time shifts from clinical education to software troubleshooting.
One clarification that comes up often: CALIPSO and a clinical EMR are complementary tools, not competing ones. CALIPSO handles clinical hours tracking, KASA documentation, and competency verification. Your EMR handles the clinical record — the notes, the treatment plans, the supervisor workflows. Most CAA-accredited programs need both, and evaluating an EMR through that lens makes the choice clearer.
The programs that find site visits manageable aren't the ones that work hardest in the three weeks before a visit. They're the ones that built documentation workflows that produce the right records continuously, so there's nothing to scramble for when the notification arrives.
That's what an EMR designed for university clinic compliance actually does: it creates the paper trail that accreditation reviewers look for, as a byproduct of the clinical work your students and supervisors are already doing.
ClinicNote is used by more than 117 university speech clinics, including programs that have used it to prepare for CAA site visit reviews. Features like supervisor co-sign workflows, document completion verification, and role-based permission sets are built specifically for university training environments. When the University of Wisconsin-Milwaukee needed a custom compliance report on short notice, it was built in one week.
If you'd like to see how it fits your accreditation documentation workflows, we're happy to walk through it. Schedule a demo.