Turning a Closed Complaint Into a Tracked Improvement

A complaint that only lives in an email thread tends to get resolved once and forgotten. The family feels heard, the roster moves on, and six months later the same thing happens again because nothing in your system actually changed. The fix is to log the complaint properly, close it with what you did, and then let that closure feed directly into a tracked improvement.

Here is how that looks in practice for a small provider called Riverside Supports.

1. Log the complaint as soon as it comes in

A participant's mother calls Riverside Supports to say a support worker arrived 40 minutes late, twice in one fortnight. The office admin opens Registers and chooses Record a complaint, fills in the short form with what happened and when, and saves it.

• Registers keeps every complaint, compliment and piece of feedback in one place.
• Only owners and admins can see the register.
• Compliments and feedback are kept too, but they are never opened or closed like a complaint.

2. Work it, then close it with what was done

Riverside's roster coordinator checks the shift records for both late visits and finds the worker had back-to-back shifts across town with no travel time built in. The admin opens the complaint, adds notes on what was found and what was done, saves without closing while they confirm the fix with the worker, then returns to add the day the family was told the outcome. Only then do they choose Close complaint.

• Save without closing keeps your notes while you are still working on it.
• A closed complaint stays exactly as it was closed, with who closed it and when.
• Home and the Registers menu show a reminder once a complaint has sat open for a week, so a late one does not slip through.

3. Turn the closed complaint into a tracked improvement

This is the step that actually changes how Riverside Supports works. When closing the complaint, the admin answers yes to Did this lead to a change, and writes what will change: a rostering buffer rule requiring a minimum travel gap between shifts for the same worker. That change is saved straight onto the Improvements tab in the same action, already linked to the complaint it came from.

• Most improvements come from closing a complaint or incident this way.
• An improvement can also be added on its own, from an audit, staff feedback or a policy review, using Add an improvement.
• Each improvement keeps a Came from link back to the complaint or incident that started it.

4. Move the improvement from Planned to Done

Riverside's improvement starts as Planned. Once the roster coordinator builds the buffer rule into the weekly roster, they open the improvement and move it to Doing. A few weeks later, once two full roster cycles have run without a late arrival from back-to-back shifts, they move it to Done and record the day it was actually done.

• Open an improvement any time to move it along: Planned, then Doing, then Done.
• Done asks for the day the change actually happened, not the day it was planned.
• Anyone checking later can open the improvement and see exactly where it came from and what state it is in.

Why this beats an email thread

An inbox has no status. Nobody can glance at it and see which complaints led to a real change and which ones were just apologised for. With the complaint closed and the improvement tracked, Riverside Supports has a plain record it can point to: a family raised a problem, here is what we found, here is the change we made, and here is proof it is in place. That is useful for the family, useful for new staff reading the register, and useful for Riverside itself the next time something similar comes up.

None of this makes a provider compliant on its own. Registers helps keep the operational record organised and connected; the provider is still responsible for how it actually handles complaints and makes decisions about its obligations.