Supervision & coaching

How to Coach and Give Feedback to Support Workers

The best coaching for a support worker happens in the days right after a shift, in a short specific conversation, not once a year in a formal review.

A team leader who only talks to a worker about their practice once a year, at a scheduled review, is trying to shape behaviour with feedback that's sometimes eleven months old. By the time it arrives, the worker barely remembers the shift being discussed, and the moment where a different choice might have helped someone is long gone. Coaching that actually changes anything happens close to the event, small, frequent, and specific enough that the worker can see exactly what to do differently next time.

That's the gap in a lot of frontline supervision. Team leaders are usually promoted because they were good support workers, not because anyone taught them how to give feedback well, and the skill doesn't arrive automatically with the title. Left without a framework, most default to one of two extremes: silence until something goes wrong, or a vague "great job team" that doesn't tell anyone what to repeat.

What does coaching actually mean for a frontline team leader?

Coaching is different from performance management, and mixing the two up is one of the more common mistakes new leaders make. Coaching is developmental. It happens continuously, applies to workers doing fine as much as workers who are struggling, and is about building capability before there's a problem to solve. Performance management is what happens when a specific concern needs addressing directly, which CORA covers in its own right in Addressing Performance & Building Accountability. A team leader who only ever manages performance and never coaches is running a fire brigade, not a team.

When should a team leader have a coaching conversation?

The useful moments are closer than most leaders think. A debrief after a shift that didn't go to plan. A quick note after reading a case file that shows a worker handled something well. A five-minute chat before a new worker's first solo shift with someone who has complex support needs. None of these need a meeting room or a diary invite. They need a team leader who notices, and who says something in the same week rather than saving it up.

Waiting for the scheduled supervision session to raise something that happened three weeks ago teaches workers that feedback is an event, not a normal part of how the team operates. The teams that get this right treat coaching as a habit woven through the roster, not a calendar appointment.

What makes feedback land, rather than get brushed off?

Specific feedback is the whole game. "Good job today" tells a worker nothing they can repeat on purpose. "The way you gave him two options instead of just doing the transfer for him, that's exactly the kind of thing that builds his independence, keep doing that" tells them precisely what worked and why it mattered. The same precision matters when something needs correcting. Naming the actual behaviour, the actual moment, and the actual impact, without attaching it to the worker's character, is what keeps a hard conversation from turning into a wall.

It also has to run both ways. A team leader who only ever delivers feedback and never asks a worker how a shift felt from their side is missing half of what actually happened in the room.

The five-minute test

If a piece of feedback takes longer than five minutes to deliver and still doesn't tell the worker exactly what to do differently next time, it probably isn't specific enough yet. Say the behaviour, say the impact, and stop there.

How do you build accountability without micromanaging?

Accountability sits on clarity, not supervision hours. A worker who knows exactly what's expected, who has had it explained rather than assumed, and who gets consistent feedback when the standard slips, tends to hold themselves to it without anyone standing over their shoulder. Micromanagement usually shows up when clarity was skipped, and the team leader is trying to compensate with control instead.

The other piece is following through. A team leader who raises something once and never checks back in signals, however unintentionally, that the standard was optional. Circling back, even briefly, on whether a change actually stuck is what turns a conversation into an outcome.

How CORA's course fits into this

CORA's course Supervising Support Workers: Coaching, Feedback & Accountability, part of the Leadership & Workforce Sustainability stream in the course library, works frontline leaders through realistic coaching and feedback scenarios, building the supervisory capability that's usually left to be picked up on the job. It builds understanding and judgement. It doesn't replace an organisation's own supervision policy or performance framework, and CORA doesn't certify or sign off a leader's competence, that call sits with the provider.

If you're mapping coaching alongside the rest of the Leadership & Workforce Sustainability stream for your team leaders, the Pathway Builder is a free tool that maps it for you, no sign-up required. Or request a demo if you'd rather talk it through.

Individual membership

One seat, for one support worker. Full access to the CORA course library, plus your own credential register to upload and track your certificates, and settings you manage yourself. The Workforce Capability Report is part of the organisation plans, not the individual membership. Standalone, and not combinable with organisation tiers.

See how CORA covers coaching and the rest of Leadership & Workforce Sustainability

Browse the full course library, or get in touch if you want to talk through what your team leaders need right now.

Try the Pathway Builder Browse the course library

Common questions

What's the difference between coaching and performance management?

Coaching is developmental and ongoing, building a worker's capability whether or not there's a problem to solve. Performance management responds to a specific concern that needs addressing directly. Most frontline leaders need both, but confusing one for the other either turns every conversation into a discipline meeting or lets real concerns drift because nobody wants to be the bad guy.

How often should team leaders check in with support workers?

There's no single mandated frequency, but a useful rule is to talk about practice close to when it happens rather than saving it all for a scheduled review. Short, regular check-ins, weekly or after significant shifts, keep feedback relevant and stop small issues building up unaddressed for months.

What should a team leader do if a worker gets defensive during feedback?

Slow down and check whether the feedback was specific enough to be useful. Vague feedback often reads as an attack because there's nothing concrete to respond to. Naming the exact behaviour and its impact, rather than a general impression, usually reduces defensiveness because the worker has something clear to engage with rather than a feeling to fend off.

Does the NDIS require regular supervision of support workers?

Yes. Under the NDIS Practice Standards, registered providers must have human resource management systems that provide timely supervision, support and resources to workers relevant to the scope and complexity of the supports they deliver. How that supervision is structured is up to the provider, but it has to happen, and it has to be documented.

Sources and further reading

This page is general information for team leaders and providers, not legal or HR advice. Always follow your organisation's own supervision and performance policies.

← Back to the course library