Write a result you can observe
“Update the form” describes an activity. “The next shift can identify unfinished tasks and who owns them” describes a result you can check. Start with the concern that triggered the action and the people affected. Record any immediate response separately from the longer-term improvement. Urgent safety or reporting work must follow the appropriate process while this improvement review proceeds.
Choose a proportionate test. Decide which records, conversations or observations will show whether the change is being used. Explain why the sample is suitable, who will review it and when enough use will have occurred. There is no universal sample size in this worksheet; a small convenience sample cannot prove organisation-wide effectiveness.
Keep implementation evidence separate
Implementation evidence might include an approved form version, a team briefing, a changed process or an access update. Identify exactly which version was introduced and when. Record who needed the change and how people who missed the first briefing were followed up. A document being available does not prove that a worker read it, understood it or used it correctly.
Connect the evidence to the action record without copying unnecessary personal information into a general review. Use identifiers or controlled links where appropriate. If a file changes, preserve the version that supported the original decision so a later reviewer can understand what was assessed.
Work through a fictional handover example
A fictional team notices that unfinished maintenance tasks are disappearing between shifts. It adds an owner and next-step field to the handover form, explains the change and starts using version two. The manager then samples later handovers from different shifts and checks whether unfinished tasks can be followed through.
The review finds that four sampled records name an owner, but one uses “someone to arrange”. The manager records the exception, checks its consequence and follows up with the team. This is a reason to adjust the response and retest, not to rewrite the sample as perfect. The example illustrates a method; the invented counts are not a recommended sample size or a real customer result.
Record the decision and the next check
State the evidence inspected, the exceptions found and the basis for the reviewer’s conclusion. Possible outcomes include implemented but not yet tested, improvement observed with limitations, further action required, or ready for closure under your process. Identify who is authorised to make the relevant decision. External audit findings may have separate closure requirements; follow the auditor’s actual instructions.
The Commission’s quality-management standard includes internal audit and continuous improvement. The worksheet below is our practical method for organising a review, not an official audit form. In ProviderQMS, ask to see the record, evidence and attributed review workflow against your example. A saved action or software status should never stand in for the underlying work.
Make it useful today
Your working checklist
Use example data here. Answers stay in this page until you choose to save a file. Closing the page loses unsaved answers. No account or email is required.
See the work in ProviderQMS
Bring one real improvement workflow to a ProviderQMS demonstration. See how the record, owner, evidence and review remain connected before choosing your annual plan.
Watch the workflow & explore plans →Sources and scope
Official and vendor sources provide context. The worksheet and example are our practical editorial method, not an official form, independent product certification or audit result. Check requirements that apply to your service.