Picture this: it's the last week of the semester. A student's clinical hours are logged in one system, her session notes are somewhere else, and her off-campus supervisor's co-signature is still pending. Nothing is wrong exactly, but nothing connects either. Finding the right SLP clinical hours tracking software is often framed as a counting problem. How do you tally 400 clock hours accurately? But the real challenge isn't the count. It's the gap between the hours log and everything else your program is responsible for.
If you're a clinic director or clinical supervisor, you've probably felt this. The clinical hours are technically documented. The documentation is technically complete. But they live in separate systems, and nobody can see the full picture at once.
What ASHA Actually Requires — and Where Tracking Gets Complicated
The ASHA clinical hours requirements for CCC-SLP certification aren't particularly mysterious, but they're easy to misapply.1
Students need 400 total supervised clinical hours: 25 hours of guided observation and 375 hours of direct client contact. Of those, at least 325 must be earned at the graduate level.1 That's the part most people know. Here's the part that causes problems: the 25% direct supervision rule applies per client, not globally.2 A student can have full independence with one client and still be out of compliance with another if the supervision ratio isn't met for that specific patient. It's not about averages. It's per relationship.
Sessions under 60 minutes don't round up either. A 45-minute session is 0.75 hours, not 1.2
All of this requires co-signature from a CCC-holding supervisor. That's manageable inside your clinic. For off-campus placements — a school district, a hospital, a community speech center — each site may have a different supervising clinician, and each one needs a separate, documented verification trail. Coordinating that across disconnected systems is where compliance risk quietly accumulates.
Then there's the CAA layer. ASHA accreditation requires that your program actually demonstrate it met clinical requirements — not just assert it. When CAA asks for evidence, that request doesn't come with a two-week lead time.3 The 2020 ASHA certification standards also added Alternative Clinical Education (ACE) as a pathway, allowing up to 75 hours from simulation or alternative experiences.1 Your systems need to be able to differentiate those hours from traditional ones.
Why Most University Speech Clinics End Up With Three Systems
CALIPSO is the industry standard for hours counting — used by the vast majority of university SLP programs — and it's genuinely good at what it does.4 It tracks supervised clinical hours by category, handles competency evaluations, and manages supervisor approval workflows. For what it was built to do, it works.
What CALIPSO doesn't handle: session documentation, scheduling, room management, billing education, or real-time supervisor feedback on student notes. So clinics layer in a separate EMR for documentation. That EMR wasn't built for training programs, so it doesn't talk to CALIPSO. Students try to reconcile hours counts against session notes manually. At semester-end, when access windows close and everyone needs data at once, the backup spreadsheet appears.
Speech pathology clinical hours are tracked in one place, clinical notes in another, and supervision approvals in a third.
The real cost isn't the software licenses. It's the coordination overhead — training new cohorts on three systems, routing approvals across platforms, manually reconciling what should be one connected record. If your students are maintaining a personal tracking spreadsheet alongside your official system, that's not a student problem. It's a system design problem.
What to Actually Look For in SLP Clinical Training Software
When you're evaluating software for your program, here's what actually matters:
Student caseload restrictions. Students should only have access to their assigned patients. This isn't a nice-to-have — it's a FERPA requirement and a liability issue. Most general EMRs don't have this at all because they weren't designed for training environments.
Co-signature workflows. When a student completes a session note, the supervising clinician needs to review it, leave feedback if needed, and co-sign within the same system. Not via email. Not by printing and scanning. The verification trail for supervised clinical hours should be automatic, not assembled after the fact.
Document completion verification. Can you see at a glance which sessions are missing documentation right now, rather than at the end of the semester when it's too late to address gaps? The difference between catching a missing note in week three and discovering it in week fifteen is significant.
Tiered permission sets. Students, supervisors, adjunct faculty, and administrators each need different access levels. This has to be configurable, not a workaround. A student should never see a patient file that isn't their assignment, and an adjunct supervisor should never accidentally have administrative access.
Accreditation reporting on demand. When CAA asks your program to produce evidence of clinical compliance, can your software generate that report quickly? Or does someone on your staff spend two days building it in Excel?
Both HIPAA and FERPA compliance. University clinics are subject to both.5 Most commercial EMRs are built for HIPAA only, because they were designed for private practice environments where FERPA doesn't apply.
How ClinicNote Fits Into a University SLP Program
ClinicNote is the clinical documentation and practice management layer. It generates the session records that clinical hours are built on, and it works alongside CALIPSO rather than replacing it. CALIPSO counts hours. ClinicNote handles what happens at the session level.
The supervisor workflow is built around training programs specifically. A student completes a session note and the supervising clinician is notified. The supervisor reviews it, leaves inline feedback, and co-signs — all within the same platform. The verification trail is automatic, and it's there when you need it.
Student caseload restrictions are built in. Students see only their assigned patients, which maintains real patient privacy in an environment where multiple students share a system. Permission tiers are configurable, so adjunct faculty, on-campus supervisors, and administrators each see what they're supposed to see.
When the University of Wisconsin-Milwaukee needed custom compliance reports for CAA accreditation on a tight timeline, ClinicNote built them within a week. That's not a coincidence — it's what happens when software is designed around the specific documentation demands of accredited training programs.
There's another benefit worth naming: students who train on an integrated EMR system graduate knowing how clinical documentation actually works in practice settings. A student who has only ever used paper logs is at a disadvantage walking into a hospital or school district that uses integrated systems. Experience with EMR is increasingly expected, and the platform your clinic uses shapes what students know when they leave.
ClinicNote serves over 117 speech clinics and 7,000+ users. The basics take about one to two hours of virtual training to master.
A Note on the Clinical Fellowship
When students graduate, their CALIPSO access ends. But CFY hours tracking doesn't.
The Clinical Fellowship requires 1,260 hours of clinical experience over a minimum of 36 weeks, documented per segment, with specific supervision logs.6 ASHA is clear that tracking is the fellow's own responsibility — not the employer's, not the CF mentor's. So most fellows default to spreadsheets, or they buy a tracking template from a blog or marketplace.
The gap is real. For private practices that hire new CF SLPs, using an EMR with documentation workflows that support the supervision relationship makes the fellow's tracking burden lighter and gives the CF mentor a cleaner record. That's not just a compliance benefit — it's a signal to candidates that your practice has thought about what their first year actually looks like.
One System Is Enough
The programs that handle clinical hours most reliably aren't using more software. They're using software where documentation, supervision, and compliance reporting live in the same place.
If your clinic is managing three systems to track one thing, that's a solvable problem. It's not a permanent feature of how SLP training programs have to work.
ClinicNote works with university speech clinics to consolidate documentation, supervisor workflows, and accreditation reporting — without replacing the tools that already work well. See how it works for speech clinics →
Sources
- https://www.asha.org/certification/2020-slp-certification-standards/
- https://www.asha.org/certification/certification-standards-for-slp-clinical-practicum/
- https://caa.asha.org/reporting/
- https://www.calipsoclient.com/overview.html
- https://www.hhs.gov/hipaa/for-professionals/faq/ferpa-and-hipaa/index.html
- https://www.asha.org/certification/clinical-fellowship/