How to Run Effective Team Meetings in Support Work

Support teams meet less often than most workplaces, because half the team is usually on shift somewhere else and getting everyone in a room at once is genuinely hard. That scarcity makes it more important, not less, that the meetings which do happen are worth the time it took to arrange them. A team that walks out having heard the same updates they could have read in a group chat learns fast that meetings aren't where decisions actually get made, and stops paying attention accordingly.

Coordinating team meetings sounds like the least glamorous part of frontline leadership. It's also one of the few regular moments a whole team is in the same place, which makes it worth doing properly rather than defaulting to habit.

Why do most team meetings in support work fail to change anything?

The common failure is treating the meeting as a broadcast rather than a working session. Updates get read out, everyone nods, and the meeting ends without a single decision actually being made in the room. The fix isn't a longer meeting, it's a shorter one built around fewer things that genuinely need a group discussion, with information that could be a message sent as a message beforehand instead.

What should actually be on the agenda?

A useful agenda has three kinds of items, and keeping them separate matters. Decisions that need the team's input, a genuine problem with the roster, a change to how a routine is run. Learning that's worth sharing across the team, without breaching anyone's privacy, what worked in a hard shift, a pattern several workers have separately noticed. And a short round of anything urgent that can't wait until the next meeting. Pure information, the kind nobody needs to discuss, belongs in a message sent ahead of time, not read aloud to a room.

How do you run a meeting when half the team is on shift?

Accept that not everyone will be in the room, and build the meeting so absence doesn't mean exclusion. Circulate a short written summary of decisions afterward, not just minutes nobody reads, and make sure whoever missed it can act on what changed without chasing someone down. Rotating the meeting time occasionally so the same casuals aren't always the ones missing out is a small thing that signals the meeting is meant to include the whole team, not just whoever happens to be rostered on office days.

How do you turn a meeting decision into something that actually happens?

A decision made in a meeting and never followed up is functionally the same as no decision at all. Assigning who owns the follow-through, and by when, in the room, before everyone disperses back to their shifts, is what separates a meeting that changes practice from one that's just a pleasant hour. Opening the next meeting with a quick check on what happened to last time's decisions closes the loop and tells the team their input actually goes somewhere.

How CORA's course fits into this

CORA's course Coordinating Team Meetings, part of the Leadership & Workforce Sustainability stream in the course library, works team leaders through practical agenda design, facilitation and follow-through, the unglamorous middle skill of frontline leadership that rarely gets any formal training of its own. It builds understanding and judgement, not a replacement for an organisation's own governance or meeting policies.

If you're mapping this 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.

Sources and further reading

• NDIS Practice Standards, Core Module: Provider Governance and Operational Management, NDIS Quality and Safeguards Commission

This page is general information for team leaders and providers, not a substitute for your organisation's own governance or meeting policies.