For growing teams12 March 20262 min readBy Matthew Giglio
Supervision for allied health teams: a pre-meeting checklist and a 30-minute structure
For growing teams: what to prepare before supervision, and how to spend 30 minutes on decisions instead of reconstructing the week. The record should do the first pass.
Last reviewed 25 August 2026. First published 12 March 2026.
In short
- If the first 15 minutes are “talk me through the week,” the record is not ready.
- Use the checklist the day before. Use the 30-minute agenda in the room.
- Coach on visible delivery patterns, not on general reminders to “be consistent.”
This is for clinical supervisors on growing allied health or behaviour support teams. The outcome is a meeting that starts with signal. If you supervise only yourself, skip this.
Pre-supervision checklist (day before)
Open the client file. Do not wait to hear the story in the room.
- Recent session notes are present for the workers who delivered.
- You can see which planned strategies appeared, at least in outline.
- Follow-ups from last supervision are either done or still open — named, not remembered.
- You have one risk or incident thread, if any, with the note and the plan in the same view.
- You know which worker is covering next, and whether the record will make sense to them.
- You have one decision you actually need from this meeting (change the plan / coach delivery / leave it).
If you cannot tick the first two boxes, the meeting will be reconstruction. Fix the notes, then supervise. See behaviour support documentation.
30-minute meeting structure
| Minutes | Use them for | Do not use them for |
|---|---|---|
| 0–5 | Confirm the file matches the last week. Supervisor names the pattern they already saw. | “So, how did it go?” as the opening |
| 5–15 | One case. Separate plan quality from delivery consistency. | Rewriting the plan because cover notes were thin |
| 15–25 | Coaching: the specific step to restore (e.g. countdown card + write that it was used). | General “be more consistent” |
| 25–30 | Write the next-week expectation into the record. Owner and date. | Leaving the action in the conversation only |
Example opening (supervisor)
I read six supermarket sessions. Alex is documenting the two-minute warning. Jordan’s cover notes only mention verbal redirection. I want us to decide whether Jordan had the card, and to write the expectation so Friday cover is not a car-park briefing.
That sentence is the meeting. The plan-drift scenario is the same client.
Noteable can surface recent sessions and follow-ups on the client record so this prep is shorter. Treat that as a growing-team documentation layer, not as the reason Noteable exists for a sole trader. The checklist works in whatever system holds the notes.
Report week is easier when these decisions were written down. See clinical progress reports.
For growing teams
Give the next worker a better starting point.
Write your first note free. Capture what happened, review the draft, and keep the useful context with the client. Invite your team when you’re ready.
Free for 14 days. No card. First draft in under 2 minutes.
Read next
Behaviour support
Intervention fidelity in behaviour support: one plan-drift scenario and a supervisor checklist
For growing teams: a realistic drift scenario, warning signs, and a supervisor action checklist. Fidelity here means whether the agreed plan showed up in the session — not a dashboard score.
Read article
Clinical reporting
Clinical progress reports in allied health: weak claims vs evidence-supported claims
For growing teams: side-by-side report sentences, and a repeatable preparation workflow so report week is synthesis — not archaeology. Not a claim that any funder requires this format.
Read article
Documentation
Behaviour support documentation in Australia: a practical record checklist
For growing teams: a realistic session example, a record checklist, and primary NDIS Commission sources. Not legal advice. Noteable’s advanced documentation layer sits beside the practice software you already use.
Read article