Support at Home

HCP Transition and CHSP Coexistence: A Provider Guide

Published Updated 4 min readStatura Care

Home Care Packages and CHSP should not be treated as one migration. Support at Home replaced Home Care Packages from 1 November 2025. CHSP continues separately and has been extended to 30 June 2029 under the government announcement of 21 August 2026. The announcement does not establish a universal July 2029 migration date.

For providers delivering both programs, the software task is shared client and workforce coordination with distinct agreements, funding and reporting. This revised guide separates those jobs. Sources checked 6 September 2026.

Reconcile HCP transition history

For clients who moved from HCP to Support at Home, retain the source records for their transition classification, applicable transitional treatment and opening balances. Do not infer a person's financial treatment from a label or an old package level alone.

Reconcile the history with the current record and retain the basis for corrections. Ask your finance and care-management teams to review exceptions together. Use current official guidance for date-effective contribution rules rather than copying a historic rate into every record. Review our Support at Home scope and transition workflow as part of that evaluation.

Keep CHSP as a distinct program

CHSP reporting should follow CHSP activities and requirements, not be reshaped into SAH quarterly budgets or contribution categories. A shared client profile does not mean all services share a funding model.

Build an explicit service-level view of the program, approval, agreement and reporting route. If one program changes or ends, check what must remain active for the person. The CHSP planning guide provides suggested scenarios for testing this with software suppliers.

Review agreements and reporting now

The CHSP extension does not postpone every current operational obligation. The Department's agreement and plan guidance describes the November 2026 transition milestone. The current CHSP DEX guide sets out program-specific reporting definitions.

Keep separate work lists for client-document reviews, service-record exceptions and reporting corrections. Assign an owner to each unresolved item. Check client-copy delivery, not only internal document storage, and preserve submission outcomes rather than treating an export as acceptance.

Test continuity during a software change

Use representative synthetic records to test intake, changed services, hospital pauses and a program ending while another continues. Compare source and destination records after a trial migration. Preserve older agreement versions and explain which history will remain in an archive.

Agree acceptance criteria before a full import: client counts, sample care histories, opening financial records, permissions and unresolved exceptions. A staged implementation can still require substantial reconciliation; do not assume that shared data removes the need for review.

Evaluate Statura Care for your provider

Statura Care offers a shared operating-record approach for care, workforce and finance. The CHSP software page covers client, service, contribution and DEX reporting workflows. Arrange a demonstration using your provider's service mix.

Bring the programs and service types you deliver to a software discussion. Review the implementation approach and use the evaluation workbook to compare responsibilities, interfaces and evidence with other suppliers.

Bring the work you need to improve.

Show us where your team spends time today. We’ll walk through the relevant care, workforce or finance workflows and discuss what a move to Statura would involve.