It's the end of a long clinic day, and there's a stack of student SOAP notes waiting on your signature. Co-signing SLP notes can feel like the last small task between you and the door. But it isn't a small task, and it isn't a rubber stamp.
When you co-sign a student's note, you're saying you take full responsibility for that patient's care.1 That's the weight behind every signature. So it's worth getting clear on who has to co-sign what, when it has to happen, and how the rules shift depending on your setting and the payer involved.
Here's how supervisor sign-off should actually work, and how to keep the trail clean enough to stand up to an audit.
Co-signing is simple to describe and easy to underestimate. The supervising SLP, someone who holds the CCC-SLP, reviews the supervisee's documentation and signs it. That signature confirms the work was reviewed and that the supervisor takes responsibility for the care described.1
In a university clinic, all student session documentation gets co-signed before it becomes part of the official clinical record. Every SOAP note. Every progress note. Every evaluation. Until your signature is on it, the note isn't final, and it isn't part of the patient's chart.
That's the part people miss. The co-signature isn't paperwork that follows the record. It's the thing that turns a student's draft into a real clinical record. And because you're accountable for everything your supervisees document, the signature is also your proof that oversight happened.
So when we talk about SLP supervisor sign off, we're really talking about responsibility, made visible. The rest of this post is about the details, because the requirement stays the same while the specifics change.
"Co-sign everything" is a safe default. But the why and how often depend on who you're supervising.
Graduate students. Student clinicians work under your license. Their session notes, evaluations, and treatment plans all need your co-signature before they're finalized.3 ASHA also sets the bar for who can supervise: you need the CCC-SLP, at least nine months of experience after certification, and two hours of professional development in clinical supervision.3 (For the full picture of what supervisors need to track and when, see our guide to ASHA supervisor documentation requirements.) The supervisor co-signature is what ties the student's work back to a qualified clinician.
Clinical fellows. A clinical fellow holds a provisional credential and is further along than a student, so the picture is different. As a CF mentor, your job includes reviewing diagnostic reports, treatment records, and plans of treatment, and giving a formal feedback session at least once during each segment of the CF experience.2 Whether you co-sign a given note depends on the setting and the payer rather than a single blanket rule. A CF mentor in a hospital tracking which treatment records they've reviewed this segment is doing the same core job as a university supervisor, just with a more independent clinician.
SLPAs. Assistant documentation also needs supervisor review and sign-off, with the exact expectations set by ASHA guidance and your state's rules.
The common thread is countersigning SLP documentation as evidence of supervision. What changes is the level of independence and the frequency, not the principle.
This is where supervisors get tripped up, so it's worth slowing down.
Under Medicare Part B, a student isn't a separate provider. The student is treated as an extension of the supervising SLP.1 For the service to be billable, the qualified practitioner has to be in the room guiding the student, not treating another patient or working on something else at the same time.1 Co-signatures are required when that direct supervision happened.
Why does this matter for your signature? Because Medicare reviewers look for signed and dated documentation from the person responsible for the care. If the signature doesn't meet their requirements, they can deny the associated claims.45 A missing or non-compliant co-signature isn't a clerical hiccup in that case. It's a denied claim.
Settings add another layer. A school, a university clinic, and a private practice each carry their own documentation expectations on top of whatever the payer requires. What satisfies one won't automatically satisfy the next.
There's a practical reason this confuses people. A student's note and a clinical fellow's note can look identical on the page, but the billing logic behind them isn't the same. A student is billed through you. A clinical fellow, depending on credential and setting, may bill under their own provisional license. Same note, different rules for whose signature has to be on it and why. When you supervise both at once, it pays to know which bucket each session falls into before the claim goes out.
One honest caveat: treat this as orientation, not legal advice. State licensure rules and your own facility's policies sit on top of everything here, and they can be stricter.6 When in doubt, check your state board and your compliance team before you set a clinic-wide habit.
Knowing the rules is half of it. The other half is a workflow that actually holds up week after week, across a rotating group of students.
A few things make the difference:
Picture the realistic version. You're a supervisor with a full caseload, reviewing a student's queue in the ten minutes between sessions. You can do that well when the system shows you exactly what's pending and lets you review, give feedback, and sign in one place. You can't do it well when sign-off depends on you remembering to circle back later.
Most sign-off problems aren't dramatic. They're small habits that quietly add up until an audit or a denied claim brings them to the surface. A few worth watching for:
None of these are hard to fix. They mostly come down to reviewing in real time and using a system that shows you what's waiting.
We built our collaboration tools around this exact problem, because university clinics kept telling us where the old way broke down.
In ClinicNote, students and supervisors work together in real time. A student can draft a note, you can review it and leave feedback before it's finalized, and the back-and-forth happens inside the record instead of over email. Direct note entry comes with supervisor notification and approval, so a note doesn't quietly become final without your sign-off.
When you do sign, the supervisor co-signature locks the documentation into the real client record. From there, document completion verification shows you what's been reviewed and what's still outstanding, and reporting on documentation gaps gives you a clear picture for audits. The review queue is visible, and the trail is provable. That's what "better together" means to us in practice: oversight that's built into the workflow instead of bolted on at the end of the day.
Co-signing SLP notes comes down to one idea: your signature is your responsibility for the care. The rules shift by supervisee and by payer, and a workflow you can trust is what keeps you audit-ready instead of audit-anxious.
If you take one thing from this, make it this: default to co-signing everything before a note is final, and keep the trail dated and locked. That's good practice whether or not you ever use our software.
If you'd like to see how supervisor sign-off works when it's built for teaching clinics, take a look at how ClinicNote supports university programs, or talk to our team.