29/07/2026
Support at Home Assurance Plan 2025-27: Provider Record Review Checklist
Turn the Support at Home assurance plan into a practical provider record review covering prices, services, statements, evidence owners, and follow-up.
Guide record
How this guide is reviewed
CaresLink reviews guides for plain language, practical operational use, and consistency with official sources linked on the page.
- Published
- 29/07/2026
- Reviewed
- 29 July 2026
Free Support at Home pack
Download the Portal-Ready Admin Pack.
Use the editable workbook and B2G review prompts to record vendor versions, Client API questions, portal owners, test results, fallbacks, and source dates.
The Support at Home program assurance plan describes how government agencies plan to monitor program delivery, funding, pricing, and participant outcomes. For provider teams, the useful question is not simply what the plan says. It is which records, owners, and review steps should be easy to locate when an issue is raised.
This Support at Home assurance plan provider record review checklist turns the official themes into a practical internal starting point. It is a general operational resource only. It does not determine whether a provider is compliant, audit-ready, or eligible for payment.
What the assurance plan changes for document review
The assurance plan does not create one new universal form. It brings several existing operating records into the same review picture. Providers may need to connect a published price, an agreed service, evidence of delivery, a participant statement, a payment record, and the staff member who owns the next action.
A useful review should therefore test whether the team can follow one service from agreement to delivery and reporting without relying on one person's memory.
Provider record review map
| Review area | Records to locate | Practical question |
|---|---|---|
| Service and price | Published price, service agreement, price discussion record | Can the team show what was offered, discussed, and agreed? |
| Service delivery | Roster or service record, progress note, exception record | Can the team connect the billed service to a dated delivery record? |
| Participant information | Care plan, budget view, monthly statement, communication note | Can the participant see what was delivered, charged, and followed up? |
| Payment and claiming | Invoice data, claim status, adjustment note, retained evidence | Can finance explain an exception without rebuilding the history? |
| Governance | Procedure, record owner, review date, issue register | Is there a named person and a next review point for each open item? |
Five records to test first
Select one current service and compare the published price with the price discussed and recorded.
Match one delivered service to its roster, service note, invoice line, and monthly statement entry.
Check whether a price difference has a dated reason, participant communication record, and owner.
Review one adjustment, rejected item, or late claim and confirm where supporting records are retained.
Confirm that open actions have an owner, due date, status, and escalation path.
Build an evidence owner map
The same workflow often crosses care, administration, finance, and software teams. A simple evidence owner map can stop records from becoming disconnected.
| Record or question | Primary owner | Backup or reviewer | Review trigger |
|---|---|---|---|
| Published and agreed price | Operations or finance | Service manager | Price change or new service |
| Service delivery record | Service team | Coordinator | Missing or disputed entry |
| Monthly statement wording | Finance or admin | Participant contact owner | Statement issue or correction |
| Claim exception evidence | Finance or claims owner | System administrator | Rejection, late claim, or adjustment |
| Software test result | System administrator | Vendor contact | Release, configuration, or API change |
Use a small sample before a full review
Start with three to five service records that represent different risks. Include a routine service, a price variation, a late or adjusted claim, and a participant question if those examples exist.
Record what was found, what is missing, who owns the follow-up, and when the item will be reviewed again. Do not copy participant details into an external tool unless your organisation has approved that workflow.
Connect the review to existing CaresLink resources
Use the Support at Home Portal-Ready Admin Pack for invoice, statement, reporting, and software review prompts. Use the Price Discussion Record when the team needs a dated record of a price conversation. Use the Service Agreement Checklist and Care Management Contact Note to connect participant communication with the operational file.
Frequently asked questions
Does the assurance plan require one new provider checklist?
The official plan describes assurance activities and focus areas. It does not make the CaresLink checklist an official or universal form. Use it only as an internal review starting point.
Should every record sit in one system?
Not necessarily. The practical need is a clear link between records, owners, dates, and follow-up. Providers should use their own approved systems and access controls.
Is this an audit or compliance checklist?
No. This page is a general operational resource. It does not provide legal, compliance, financial, clinical, or professional advice.
How often should the review be repeated?
Set a review point that matches the organisation's risk, system changes, official updates, and local procedures. Record the next date and the person responsible.
Disclaimer
These resources are provided for general operational documentation and educational purposes only. They do not constitute legal, clinical, medical, compliance, or professional advice. Organisations should review and adapt all documents according to their own policies, procedures, registration requirements, funding arrangements, and regulatory obligations.
Free Word/Excel pack
Get the Portal-Ready Admin Pack
Enter your work email and the ZIP link will appear. Use the pack for vendor, portal, testing, fallback, and evidence-owner review prompts.