Every school SLP has had some version of this conversation: you explain that your assignment is unsustainable, an administrator points at a number, and the number sounds fine to them. The disconnect is almost always the same. The administrator is counting caseload — how many students have speech-language services on an IEP. You are experiencing workload — everything you are actually required to do, of which direct therapy is one part.
Learning to make that distinction concrete, in writing, with data, is the single most useful advocacy skill in school-based practice. This article covers what the two terms mean, what the national data actually says, how to document your own workload, and how to bring a proposal that an administrator can act on.
Caseload and Workload Are Not the Same Number
Caseload is a headcount: students receiving services under an IEP. Workload is the full set of activities required to deliver and support those services. ASHA has long advocated a workload approach to school-based service delivery precisely because a headcount fails to capture the work.
A workload accounting includes, at minimum:
- Direct services to students on IEPs, individual and group
- Evaluations, reevaluations, and eligibility determinations
- IEP meetings, including preparation and follow-up documentation
- Progress monitoring, data analysis, and progress reporting cycles
- MTSS and intervention team participation, screenings, and consultations
- Collaboration with teachers, paraprofessionals, and related service providers
- Parent communication and prior written notice
- Medicaid billing and compliance documentation, where applicable
- Supervision of SLPAs, clinical fellows, or student clinicians
- Travel between buildings for itinerant assignments
- Required make-up sessions for missed services
Two SLPs with identical caseloads of 48 can have radically different workloads: one serves a single building with a stable population and no supervision duties; the other covers three buildings, runs 22 evaluations a year, supervises an SLPA, and sits on the district's MTSS committee. The headcount is identical. The job is not.
The Data You Can Cite
Advocacy is more effective when your local experience is anchored to national benchmarks. The ASHA 2024 Schools Survey is the most useful public source, and the figures below are the ones that carry the most weight in an administrative conversation.
- Median caseload: 50 students. Median caseload described as manageable by the same respondents: 40. (n of approximately 2,800.) That gap is the profession's headline finding — SLPs nationally are carrying about ten students more than they consider workable
- 76% ranked "large amount of paperwork" as their number one challenge — the top-ranked challenge in every facility type surveyed
- 66.1% cited high workload or caseload as a challenge, the second most common
- Only 24% reported not experiencing burnout, and 27% reported considering leaving the profession
- 79% are required to make up missed sessions — an obligation that consumes schedule capacity but appears nowhere in a caseload count
- Weekly time across tracked activities averaged 39.3 hours, including roughly 6.0 hours of documentation and 4.0 hours of diagnostics
Note what that last figure implies. Roughly ten hours of a typical week goes to documentation and evaluation before a single therapy session is delivered. Any staffing model that treats an SLP's week as therapy minutes plus a little overhead is arithmetically wrong.
Step One: Document Your Own Workload
National data establishes that the problem is real. Local data establishes that it is yours. You need both, and administrators respond far better to the second.
Track two to four consecutive weeks in a simple log with these columns: date, activity category, minutes, and a one-line note. Use a small, fixed set of categories so the totals are meaningful — direct service, evaluation, meetings, documentation, consultation and collaboration, travel, screening and MTSS, supervision, and other. Log in real time or at the end of each block; reconstructing a week from memory understates it by a wide margin.
A few practices that make the resulting log persuasive rather than dismissible:
- Include the unpaid time honestly, but report it separately from contracted hours. "38 contracted hours plus 6.5 hours outside the workday" is a much stronger sentence than a single inflated total
- Count meeting preparation and follow-up, not just the meeting itself. A 45-minute IEP meeting is rarely a 45-minute obligation
- Track the number of evaluations completed and pending, not just the hours. Evaluation volume is the variable administrators most often overlook
- Note every session missed for assemblies, testing, absences, and field trips, and the make-up obligation each one created
Step Two: Translate Workload Into Capacity
The most common advocacy failure is presenting a workload log as evidence of hardship. Administrators are not unsympathetic, but hardship is not something they can approve. Capacity is.
Convert your log into a capacity statement. The structure is: here are my available service minutes per week, here is what current IEPs obligate, here is the gap, here are the options. For example: "My schedule contains 1,150 available service minutes per week after evaluation and meeting time. Current IEPs obligate 1,420 minutes. I am 270 minutes short each week, which is why make-up sessions are accumulating."
That framing does three things a complaint cannot. It is verifiable, it identifies a compliance risk rather than a comfort problem, and it invites a decision instead of an argument.
Step Three: Bring Options, Not Just a Problem
Arrive with a menu. Most districts cannot add an FTE in the middle of a year, and a proposal that requires one is easy to defer. Options that are frequently within a building or district administrator's authority:
- Redistribute evaluations. Shifting evaluation assignments across the district's SLPs is often the fastest available lever
- Add SLPA support for implementation of established programs under supervision, where state regulations allow
- Protect scheduled documentation and planning time and stop assigning coverage duties during it
- Reduce building assignments to cut travel time, even if headcount stays the same
- Adopt a service delivery review for students whose IEP minutes no longer match their present levels — not as a cost-cutting exercise, but as clinically appropriate rightsizing at annual review
- Invest in documentation tooling that reduces the 6.0-hour weekly documentation figure. Tools that keep data collection, note generation, and progress reporting in one place remove re-entry, which is where much of that time goes
- Contract or itinerant coverage for a defined period to clear an evaluation backlog
Rank your options by what you would most want, but present all of them. An administrator who chooses the third option on your list has still solved part of the problem.
Talking About Caseload Caps
Many states set maximum caseload sizes in regulation, and some districts have negotiated caps in collective bargaining agreements. Know both before you negotiate. If your state has a cap and your assignment exceeds it, that is a compliance conversation with a defined answer, not a matter of professional judgment — and it should be raised through the channel your district uses for compliance, in writing.
Where no cap exists, ASHA's caseload and workload guidance and the national median-manageable figure of 40 give you an external reference point. Framing matters: "I am asking to be brought toward what SLPs nationally identify as a manageable assignment" lands differently than "my caseload is too high."
If you are negotiating a new position, caseload cap and evaluation volume are legitimate topics before you sign. Ask what the caseload has been for the past three years, how many evaluations the position completed last year, how many buildings are assigned, and whether make-up sessions are required. The answers tell you more about the job than the salary line does.
Documenting the Compliance Risk
This part makes some clinicians uncomfortable, and it should be done carefully and without threat — but it is the mechanism that produces change. When a workload prevents you from delivering IEP services as written, that is a district compliance exposure, not a personal capacity problem.
Report it factually and in writing: which students, how many minutes are outstanding, what you have done to make them up, and what you are requesting. Keep the tone collaborative and solution-oriented. You are not building a case against anyone; you are putting the district on notice of a risk it has the authority to fix, which is exactly what a professional in your position should do.
Playing the Long Game
Individual advocacy improves an individual assignment. Structural change requires collective data. If your district employs multiple SLPs, a shared workload analysis across all of them is dramatically more persuasive than one person's log — it removes the "that clinician is struggling" interpretation entirely.
Coordinate a common tracking template, aggregate the results, and present district-level findings to the special education director with a comparison against the ASHA benchmarks. Bring your state association into the conversation if the district is unresponsive; state associations track this and often have model language and legislative contacts.
With 27% of school-based SLPs reporting they are considering leaving the profession, retention is a budget argument as well as a professional one. Replacing an experienced school SLP in a tight labor market costs a district more than the accommodations that would have kept one. That is an argument administrators tend to hear.