Key points

  • Support coordinator burnout is a systemic problem, not a personal failure. Underfunded hours, admin overload, and emotional labour all contribute
  • A full-time Level 2 SC can realistically manage 25 to 35 participants. Level 3 specialist coordinators should cap at 15 to 20
  • Batching tasks, using templates, and setting firm boundaries on availability are the most effective daily workload strategies
  • If you are consistently working unpaid hours to keep up, the caseload is too high. That is a management problem, not a you problem

Why support coordinator burnout is so common

If you are burning out, you are not alone. Support coordination has one of the highest turnover rates in the NDIS sector, and the reasons are structural.

The funding math does not add up

NDIS plans typically fund 20 to 40 hours of support coordination per year. That is roughly 1.5 to 3 hours per month per participant. In that time, you are expected to review the plan, connect providers, resolve service gaps, write progress notes, handle crises, and prepare for plan reviews. For participants with complex needs, 3 hours a month is nowhere near enough.

So what happens? You absorb the gap. You take calls after hours. You write reports on weekends. You do unpaid work because the alternative is letting a participant fall through the cracks.

Emotional labour is constant

You are not just coordinating services. You are often the one person a participant trusts. When a provider drops them, when funding runs out, when a family is in crisis, you are the first call. That emotional weight builds up over months and years. Most SCs did not sign up for a desk job. They came into this work because they care about people. That same care is what makes burnout hit harder.

Admin eats your billable hours

For every hour you spend with a participant, there is often another hour of admin behind it. Progress notes, service agreements, provider research, emails, phone tag with the NDIA. None of this is invisible to you, but it is invisible to the people setting your caseload targets.

Realistic caseload numbers

There is no official NDIA guideline that says “an SC should carry X participants.” That absence is part of the problem. But based on sector benchmarks and what experienced coordinators report, here are realistic numbers.

Level 2 Support Coordination

A full-time Level 2 coordinator can manage 25 to 35 active participants if:

  • Most participants have straightforward plans
  • There is admin support available (even part-time)
  • The coordinator is not also doing intake, marketing, or business development
  • Plans are spread across different review cycles (not all due in the same month)

If you are carrying 40 or more Level 2 participants full-time, something is going to slip. Either your work quality drops, your hours blow out, or both.

Level 3 Specialist Support Coordination

Specialist coordinators working with high-complexity participants (psychosocial disability, justice system involvement, housing instability) should carry 15 to 20 participants at most.

These participants need more contact hours, more crisis management, and more inter-agency coordination. A caseload of 25 specialist participants is a burnout timeline, not a business plan.

What affects your real capacity

The number of participants you can carry depends on more than just headcount. Consider:

  • Plan complexity. Ten participants with SIL, behaviour support, and housing needs is a bigger caseload than twenty participants with stable community access plans
  • Plan review timing. If eight participants have reviews in the same month, that month will break you
  • Geographic spread. Driving two hours between participants eats time that could go to coordination
  • Admin support. If you are doing your own invoicing, filing, and CRM updates, subtract 5 to 8 hours a week from your available coordination time
  • Crisis frequency. Some caseloads are predictable. Others involve weekly emergencies. Budget for the reality, not the plan

Signs you are overloaded

Burnout does not arrive all at once. It builds gradually, and by the time you recognise it, you have usually been in it for weeks. Watch for these signs.

Work signs

  • You are consistently behind on progress notes by more than two weeks
  • You dread returning participant calls
  • You are making errors in service agreements, dates, or funding calculations that you would not normally make
  • Your inbox has unread emails from a week ago that you keep pushing to tomorrow
  • You are working evenings or weekends just to stay afloat, not to get ahead

Personal signs

  • You feel detached from participant outcomes. You used to care about the wins, now you just want the task done
  • Headaches, poor sleep, or stomach issues that seem to track with work stress
  • You are short-tempered with colleagues, family, or participants
  • You have stopped doing things outside of work that you used to enjoy
  • Sunday afternoon dread is now Sunday morning dread

The test

Ask yourself: if a new referral landed in your inbox right now, would you feel energised or panicked? If the honest answer is panicked, you are at or past capacity.

Workload management strategies

These are not wellness tips. They are operational strategies that experienced SCs use to survive unsustainable systems.

Batch your admin

Stop switching between participant calls and report writing throughout the day. Context switching is expensive. Instead:

  • Morning block (2 hours): Calls, emails, and participant contact
  • Midday block (1.5 hours): Progress notes and documentation for the calls you just made
  • Afternoon block (2 hours): Provider research, service agreement drafting, plan review prep

Batching similar tasks together means you write faster, think more clearly, and lose less time to mental gear-shifting.

Build a template library

Every support coordinator should have a set of ready-to-go templates. If you are writing progress notes, service agreements, or plan review reports from scratch each time, you are burning hours you do not have.

At minimum, build templates for:

  • Progress notes (one for routine check-ins, one for crisis events)
  • Service agreements
  • Plan review reports
  • Provider referral emails
  • Participant onboarding packs

Spend one day building these. You will save that day back within a month.

Set communication boundaries

You are not an emergency service. Unless a participant is in immediate danger (in which case, call 000), you do not need to be available at 9pm on a Tuesday.

Set and communicate clear boundaries:

  • Phone availability: 9am to 5pm, Monday to Friday
  • Email response time: within 2 business days
  • After-hours: voicemail with a message explaining your hours and emergency contacts

Put these boundaries in your service agreement. When participants and families know what to expect, most will respect it. The ones who do not are usually the ones who need the boundary most.

Use a task management system

A notebook or sticky notes will not cut it past 15 participants. Use a proper system, whether that is a CRM, Trello, Asana, or even a well-structured spreadsheet. Track:

  • Next action per participant
  • Plan review dates
  • Service agreement expiry dates
  • Outstanding reports
  • Hours used versus hours funded

Spending 15 minutes at the start of each week reviewing this list prevents the “what have I forgotten” anxiety that follows you home.

Reducing admin time

Admin is the silent caseload killer. Here are specific ways to claw back hours.

Progress notes: write them the same day

The longer you wait to write progress notes, the longer they take. A call you had this morning takes 5 minutes to document. A call from last Thursday takes 15 because you are trying to remember what was said. Same-day documentation is faster documentation.

Use voice-to-text for drafts

Dictate your progress notes into your phone immediately after a call or meeting. Even a rough voice memo gives you 80% of the content. Clean it up later during your admin block.

Standardise provider research

Build a provider shortlist for common referral needs: personal care, community access, allied health, SIL, plan management. Keep it in a shared document with contact details, availability, and notes on quality. When a participant needs a provider, you start from a curated list instead of searching from scratch every time.

Platforms like Carevo can help here. Instead of cold-calling providers to check availability, you can connect participants with vetted providers through the platform, cutting your research and phone time.

Group similar plan reviews

If you have any control over plan review timing, try to cluster reviews by complexity. Doing three straightforward reviews in one week is far more efficient than scattering them across a month mixed in with specialist reviews.

When to push back

This is the section nobody wants to write, and the one you probably need most.

Saying no to new referrals

You are allowed to say no. If your caseload is full, taking on another participant is not helping them. It is giving them a coordinator who is too stretched to do the job properly.

When a referral comes in and you are at capacity, say so directly:

“I appreciate the referral. My caseload is at capacity right now and I would not be able to give this participant the attention they need. Can I suggest [alternative SC] or put this on a waitlist for when I have space?”

This is professional, not selfish. A participant is better off waiting two weeks for a coordinator with capacity than being assigned to someone who is already underwater.

Having the conversation with management

If you work for an organisation and your caseload is set by someone else, you need to have a direct conversation. Come with data, not emotions:

  • “I am carrying 42 participants. The sector benchmark for Level 2 is 25 to 35.”
  • “I logged 12 hours of unpaid work last fortnight to keep up with documentation.”
  • “Three participants missed their plan review prep because I did not have hours to complete it.”
  • “My error rate on service agreements has gone up because I am rushing through them.”

Frame it as a quality and compliance issue, not a personal complaint. Organisations respond to risk. Missed plan reviews and documentation errors are audit risks. Unpaid overtime is a workplace law risk.

When to consider leaving

If you have raised the issue, provided the data, and nothing changes, that is information. Some organisations treat support coordinators as a billing machine. More participants means more revenue, and the coordinator’s wellbeing is an afterthought.

You did not get into this work to run yourself into the ground. A good SC who leaves a bad organisation and joins one that sets realistic caseloads will do better work for fewer participants than a burned-out SC trying to hold together an impossible workload.

Check where you stand

If any of this hit close to home, it is worth taking a few minutes to assess where you are right now.

Take the free Support Coordinator Burnout Assessment

The assessment covers caseload, admin load, emotional signs, and boundary health. It takes about 3 minutes and gives you a clear picture of whether you are managing, stretched, or in the red zone.

Summary

Burnout in support coordination is not about being weak or not caring enough. It is the predictable result of a system that funds too few hours for too much work. You cannot fix the system on your own, but you can protect yourself within it.

Set realistic caseload limits. Batch your admin. Build templates. Set boundaries and enforce them. And if the workload is genuinely unsustainable, say so out loud to the people who can change it.

Your participants need a coordinator who is functional, not one who is running on fumes.

More Resources for Support Coordinators