Why Your Support Worker Job Description Matters
This episode breaks down how a support worker position description can affect SCHADS Award classification, underpayment risk, and NDIS audit readiness. It also covers the practical details that make a role description clear, compliant, and aligned with the actual duties a worker performs.
Is this your podcast and want to remove this banner? Click here.
Chapter 1
The job description is doing more than hiring
Will, EnableUs Community
Welcome to the show. Winter, here's the tension: if your support worker job description is too vague, you can underpay someone by classifying them wrong. If it's too grand, you can oversell the role, attract the wrong candidates, and still mess up the classification.
Winter, EnableUs Community
[curious] And that is such a nasty double risk, hey. Too loose and you've got underpayment exposure. Too inflated and suddenly your "support worker" ad reads like a care coordinator, a behaviour specialist, and a life coach all rolled into one.
Will, EnableUs Community
Exactly. In the NDIS world, that document is not just a hiring ad in a nicer shirt. It becomes the foundation for your SCHADS Award classification decision, and it becomes audit evidence under the NDIS Practice Standards. So when providers treat it like admin wallpaper, they're missing the whole point.
Winter, EnableUs Community
[questioning tone] Hang on -- when you say "audit evidence," you mean an auditor can actually look at the position description and use that to judge whether your workforce practices are real, not just written down somewhere?
Will, EnableUs Community
[matter-of-fact] Yes. The Practice Standards expect documented workforce management practices across recruitment, induction, supervision, and performance management. Not just a policy sitting in a folder. The Commission wants to see that you assess worker suitability beyond the screening check, that you supervise workers delivering high-risk supports, and that you manage concerns about conduct properly. A role description is where that chain starts.
Winter, EnableUs Community
So if the role description says basically nothing -- "provide support to participants as required" -- then your induction's blurry, your supervision's blurry, and your performance reviews are, what, just vibes? [laughs softly]
Will, EnableUs Community
[chuckles] Pretty much. If the duties aren't clear, you can't show that the worker's qualifications match the job. You can't build a proper induction around real tasks. And when an auditor asks, "How do you know this person should be doing this support?" you've got no clean line from recruitment to practice.
Winter, EnableUs Community
The bit that sticks for me is Clause 13.2 of the SCHADS Award. Employers have to inform employees in writing of their classification when they start -- and if it changes later. Clause 13.2. That means the job description isn't optional fluff. It's one of the things making that written classification possible.
Will, EnableUs Community
[reflective] Yes, and that's where a lot of providers get caught. If your position description doesn't accurately describe the actual work, you cannot reliably classify the role. And once classification gets shaky, you're into underpayment risk, Fair Work attention, and reputational damage. That's a lot of risk from one lazy template.
Winter, EnableUs Community
[skeptical] I think some providers assume the worker screening check does more heavy lifting than it really does. Like, "they've got the check, so we're covered." But the Standards are broader than that. Suitability beyond the check, supervision for high-risk supports, conduct management... that's operational stuff.
Will, EnableUs Community
Right. The screening check is one gate, not the whole fence. And the surprising part is the humble job description touches all of it. It tells candidates what kind of organisation you are. It tells managers what to train and supervise. And it tells auditors whether your workforce system is deliberate or just improvised.
Winter, EnableUs Community
[softly] Also, candidates can feel vagueness straight away. If I read an ad that says "must be passionate, flexible, dynamic, willing to do anything," I don't hear passion. I hear chaos.
Will, EnableUs Community
[laughs] That's good. I hear chaos too. And the opposite is just as bad -- dressing up a routine support role with senior-sounding duties. Because then the candidate expects autonomy, program design, maybe key worker responsibilities, and the actual job is mostly personal care, transport, meal prep, community access. That's a trust problem before day one.
Winter, EnableUs Community
So the real question isn't "do we have a job description?" It's "does this document accurately describe the work, support the SCHADS level, and stand up in an audit?" If it can't do those three things, it's not finished.
Chapter 2
What a compliant support worker role actually needs to say
Winter, EnableUs Community
[briskly] Alright, let's make this practical. What does a compliant support worker job description actually need? First up: a clear title. Not just "Support Worker" if the level matters. Say "Support Worker Level 2," or "Senior Support Worker," or "Specialist Support Worker" if that's genuinely what it is.
Will, EnableUs Community
And that title should line up with the work, not just the branding. Then the reporting line: who does this person report to? Team Leader, Service Coordinator, provider-director in a smaller service. That sounds minor, but to an auditor it's evidence of your supervision framework.
Winter, EnableUs Community
[curious] The reporting line is one of those details providers skip because it feels obvious. But "obvious" isn't evidence. If a worker is delivering high-risk supports, an auditor wants to see who's supervising that work and how the line of accountability runs.
Will, EnableUs Community
Exactly. Then you've got the purpose of the role -- two or three sentences on why the position exists for participants. Not just a task list. Something like: this role supports participants to pursue daily living goals, personal wellbeing, and safe community participation in line with individual support needs. That values piece matters for candidate fit.
Winter, EnableUs Community
And then comes the bit everybody mucks up: duties. Be SPECIFIC. Don't write "provide personal care." Write hygiene support, meal preparation, medication prompting, mobility assistance. Don't write "support community participation." Write accompanying participants to appointments, social activities, or programs.
Will, EnableUs Community
[responds quickly] Yes -- those exact examples matter because the duties drive classification. Under SCHADS, workers are classified by stream, by level 1 to 8, by pay point, by employment type, and by qualification, experience, duties, and responsibilities. For most NDIS support workers, you're usually looking at either the Social and Community Services stream for community-based and program roles, or the Home Care stream for personal care and domestic assistance in a participant's home.
Winter, EnableUs Community
Wait -- those two streams, Social and Community Services versus Home Care, that's not just payroll trivia. That's the lens through which the role is understood, yeah?
Will, EnableUs Community
[matter-of-fact] That's right. And within that, the level matters. Fair Work Commission guidance is useful here: a role with typical disability support duties is consistent with Level 2. But when you add duties like participating in the development of individual programs, participating in behavioural management programs, or taking on key worker responsibilities, you're getting into Level 3 territory.
Winter, EnableUs Community
[flagging it] Level 2 versus Level 3 -- that's the number people should remember. Because if your ad casually throws in "develop participant programs" or "act as key worker" without thinking, you may have described a more senior role than you intended.
Will, EnableUs Community
And the reverse is dangerous too. If the worker is already doing those Level 3-style duties in real life, but the position description still reads like Level 2, you've got a misclassification problem in the other direction. If the role evolves, the job description and pay classification need to evolve too, and the employee has to be informed in writing of the change.
Winter, EnableUs Community
[skeptical] Which is why generic templates are so risky. If your description could belong to any care provider in Australia, it probably says nothing useful about your participant cohort, your service environment, or the actual complexity of the supports.
Will, EnableUs Community
Yep. Then qualifications and skills: make them real, not aspirational. For many Level 2 to 3 support worker roles, Certificate III in Individual Support or equivalent is preferred, but not always mandatory. First Aid and CPR are typically required where personal care is involved, especially in home settings and particularly if the participant has complex support needs.
Winter, EnableUs Community
And the mandatory compliance section should be brutally clear. NDIS Worker Screening Check for all risk-assessed roles. NDIS Worker Orientation Module certificate. Working With Children Check where applicable. Right to work in Australia. Then any role-specific qualifications or registrations. No one should be guessing what has to be done before commencement.
Will, EnableUs Community
[calm] That's the key phrase -- before commencement. Put every pre-employment check and certification in one place. It cleans up onboarding, and it shows an auditor your recruitment controls are real. Pair that with a hiring rubric that maps the role criteria to your assessment methods, and now you've got strong Human Resources Management evidence under the Core Module.
Winter, EnableUs Community
I really like that phrase, "maps the role criteria." Because it means the story hangs together. The ad says the worker will do mobility assistance and medication prompting. The interview tests for that. The checks verify suitability. The induction trains it. The supervision watches it. That's a workforce system, not a scramble.
Will, EnableUs Community
[warmly] And it helps with attraction too. The right candidates tend to trust specificity. If they can see, clearly, this role involves hygiene support, appointments, social participation, reporting to a Team Leader, mandatory screening, maybe First Aid and CPR -- they can self-select in or out honestly.
Winter, EnableUs Community
[reflective] Which is why this document quietly shapes more than hiring. It shapes pay, onboarding, supervision, audit outcomes, and even who decides to apply. If your job description is the first story you tell about your workforce, it's worth asking... what story is it actually telling?