A weekly quality review should leave a small SIL team with fewer unanswered questions: which concerns need attention, who is handling them, and what will show whether the response worked?
It can be a short, focused working session. It should not become a meeting where everyone reads a spreadsheet aloud or repeats private information that the group does not need.
The routine below is a suggested starting point for a small service. Thirty minutes, a weekly cadence and the proposed sample sizes are practical choices, not prescribed NDIS requirements. Adjust them to the risks, participants and complexity of your supports. Urgent safeguarding concerns and reporting deadlines must be handled when they arise, not held for this meeting.
Establish what the review is meant to support
The Core module expects a proportionate quality management system, an internal audit program and improvement informed by evidence and feedback. A weekly operational review can help coordinate that work; it does not replace the internal audit program. NDIS Commission: quality management.
SIL providers should also check the current SIL supplementary module against their registration and transition arrangements. Its four areas include supported decision-making, safeguarding, practice governance, and agreements about housing and support. This article offers a meeting method, not a complete assessment against those standards.
Write a one-sentence purpose at the top of the review record: “Identify unresolved quality concerns, check recent actions and agree the next work needed.” That gives you a reason to stop a discussion drifting into unrelated scheduling or general business updates.
Prepare a small review pack
Ask one person to assemble the pack before the meeting. It needs enough information to support decisions, without copying every underlying record.
Include open incidents and complaints, actions due or overdue, significant participant feedback, recent service changes, and selected checks of how agreed procedures are working. Give every item a source reference. “Concern raised at handover” needs a date and retrievable record, not just a verbal recollection.
For each item, show the current owner, last update and next decision needed. Separate an unreviewed report from an assessed concern and a completed action awaiting verification. Otherwise, a single “open” total can hide very different work.
Keep access proportionate. The person responsible for participant support may need the full record; a wider governance summary may need only the issue, action and status. Do not turn a meeting pack into a second uncontrolled collection of participant files.
Use a five-part agenda
| Suggested time | Discussion | Required output from the meeting |
|---|---|---|
| 0–5 minutes | Any concern requiring immediate escalation? | Confirm the responsible person and action already underway |
| 5–12 minutes | What has been reported or changed? | Identify issues needing assessment or coordinated follow-up |
| 12–20 minutes | What did a small sample of practice show? | Record the evidence, limitations and any finding |
| 20–27 minutes | Which actions are overdue or ready for review? | Retain, revise, escalate or close with reasons |
| 27–30 minutes | What happens next? | Read back owners, dates and evidence expectations |
The times are a planning aid. If a concern needs a confidential case discussion, allocate the appropriate people and time separately. Do not rush a safeguarding decision because the agenda says five minutes.
Bring participant experience into the review
Start with what people have said about their home and support, including concerns that have not become formal complaints. Record whether a view came directly from the person, through their preferred communication method, or from someone speaking about their experience.
The SIL supported decision-making standard centres the participant's own decisions and accessible communication. It does not make a provider meeting the decision-maker for the household. NDIS Commission: supported decision-making.
Useful review questions include: “Have we heard from the person affected?” “Did we communicate the change in a way that worked for them?” and “What are we still assuming?” If the answer is missing, assign a suitable conversation rather than treating a staff view as participant agreement.
Private concerns do not need to be raised in a house meeting. Give people a way to speak without other residents or workers hearing sensitive details.
Sample an actual process, not just the existence of a policy
Choose one manageable question each week. For example: can workers find the current approved instructions for a recent non-clinical change? Can you follow a complaint from acknowledgement to the promised next contact? Is there evidence that a completed corrective action changed practice?
State the sampling boundary. “Reviewed two recent handovers from House A” is more useful than “handovers checked.” It tells a later reviewer what you looked at and what you did not.
For a small team, you might start with two records and one discussion with a relevant worker. That is an exploratory sample, not a statistically representative finding or an official audit sample. If it reveals a repeated problem, expand the check appropriately rather than concluding that all other records must be fine.
Keep the worker discussion curious and specific. Ask them to show how they find an instruction, rather than asking “You know where the policies are, don't you?” Record difficulties as process evidence, not an automatic judgement about the worker.
A fictional review that leads to useful work
Imagine Example Supports, a fictional provider operating two SIL houses. At a weekly review, the team notices that two workers used different versions of an appointment-preparation checklist. One was downloaded before the checklist changed. A participant had also asked why they were being asked the same preparation questions twice.
The team does not record “staff reminded” and close the item. It identifies two uncertainties: where the old checklist remains available, and whether the revised process reflects the participant's preferred way to prepare.
They create three actions:
| Action | Owner | Completion evidence |
|---|---|---|
| Check the person's preferred preparation approach | Their nominated team lead | Dated record of the conversation and agreed next step |
| Replace obsolete blank copies in the two known locations | Document owner | Location check and current-version record |
| Check the revised process on the next two relevant occasions | A reviewer who did not make the change | Sample references, findings and any remaining gap |
The service sets dates appropriate to the actual arrangements. Until verification occurs, the action remains “implemented; effectiveness check due.” No one claims the change has already worked.
This example is invented. Its sample size and timing are not a standard for every provider.
Check training and safeguards through practice
A course completion date can show attendance. A quality review should also ask what evidence is available about how the relevant practice is being used. The SIL practice governance standard links worker development and competence with the support people receive in their homes. NDIS Commission: practice governance.
For specialised or clinical support, use the relevant authorised assessment and supervision arrangements. A general weekly meeting cannot certify clinical competence or invent a new clinical instruction.
Likewise, review emerging household concerns without assuming that “no complaints” means everyone feels safe. The SIL safeguarding standard includes review with participants and attention to risks within the home. NDIS Commission: safeguarding. Use your established escalation process where concerns indicate harm or possible abuse.
Finish with decisions people can act on
Before closing the meeting, read back each action in this form: owner, next step, due date, evidence, reviewer. Ask the owner to confirm that they understand the task and have access to what they need.
Record an explicit decision for overdue work. Has the risk changed? Is an interim measure needed? Is the task blocked by someone else? If a date changes, retain the previous date and the reason. Repeatedly moving a deadline without a decision makes the register less useful.
Keep the final record short enough to revisit next week. A clear list of decisions and linked evidence is easier to use than a transcript of everything said.
For your first session, bring the open-action list, one participant-feedback theme and one sample question. Leave with a small number of concrete tasks. At the next session, begin by checking what happened to them.
For an example of recording an issue and retaining the next review, watch the ProviderQMS walkthrough.
Official sources reviewed 13 September 2026. Meeting durations, samples and workflows in this guide are suggestions, not a substitute for applicable standards or professional judgement.
Existing published source retained. Original source review: 2026-09-13. Citations appear in the guide above. The new layout does not imply a new regulatory review.