SDA participant death: A claim closure and incident checklist
The death of an SDA resident is first a human event, not an administration event. But once immediate support and family communication are underway, the provider still needs a precise operating record. Claims must stop at the right point, outstanding pre-death payments need evidence, reportable incident obligations may be triggered, vacancy payment eligibility has to be checked, rent contribution records need closure, and owner updates must avoid exposing sensitive participant information.
Why this needs a separate workflow
The NDIS guidance on participant death says NDIS funding cannot be used to pay for supports once the participant has died, and providers cannot claim for supports through an NDIS plan after the participant has died. The NDIA can help finalise outstanding payments or orders from before the participant died. For SDA providers, that creates an immediate control point: separate supports already delivered from anything that would be a new post-death claim.
There is also a safeguards pathway. The NDIS Commission says a reportable incident is an act or event that happened, or is alleged to have happened, in connection with delivering NDIS supports or services. Death of a person with disability is listed as a reportable incident, with 24 hour notification from when the registered provider became aware of the incident.
SDA providers therefore need one workflow that is compassionate, fast and evidence-led. It should not turn bereavement into a finance checklist, but it does need to prevent ordinary claims continuing, missed Commission notifications, unsupported vacancy claims, privacy breaches in owner reporting, and scattered records across finance, property, tenancy and incident systems.
Separate last delivered support from post-death activity
The first finance decision is not how to claim more. It is where normal SDA claiming stops. Record the date and time the provider became aware of the death, the confirmed date of death where known, the last SDA service period already delivered, the latest claim already submitted, any rejected or pending claim, and whether any claim relates only to pre-death support.
This matters because NDIS payment guidance for my providers lists a rejection reason where a provider claimed after the participant left the NDIS or died, within 90 days, and the item was not on the NDIS Bereavement Addendum. The pricing page also says the bereavement addendum lists the NDIS supports providers can claim after a participant has died. SDA teams should check the current addendum and the SDA pricing arrangements before treating any post-death amount as claimable.
A useful control is to freeze recurring claim automation for that participant immediately, then create a closure record for pre-death claims only. If finance later needs to submit an outstanding invoice or payment enquiry, the evidence should show the service dates, support item, dwelling, participant, plan relationship, agreement record and why the claim is not a new post-death support claim.
A practical SDA participant death checklist
The checklist should give operations, finance and compliance one shared record without putting unnecessary detail into owner or investor files.
Pause ordinary claims
Stop recurring SDA claim preparation, mark the participant record as deceased pending closure, and identify claims already submitted, paid, rejected or still unsubmitted for pre-death service dates.
Open incident triage
Record when the provider became aware, who made the internal notification, whether the death appears connected with SDA or another NDIS support, whether the Commission portal is required, and who owns the 24 hour decision.
Check external notifications
Confirm what has been notified to the NDIA, NDIS Commission, police, coroner, state or territory bodies, support partners, plan manager, nominee, executor or authorised representative, based on the provider's role and verified permissions.
Close agreement and RRC records
Record the service agreement status, last residence date, rent contribution ledger position, arrears or credits, bond or tenancy handling where relevant, and any estate or authorised-contact pathway before issuing final statements.
Prepare vacancy evidence
If the room becomes available, record the vacancy date, dwelling enrolment, resident count, NDIA vacancy notification, online form evidence, vacancy listing status and any person-specific adjustment claim evidence before finance acts.
Restrict owner updates
Owner reports should usually show vacancy status, claim closure, RRC ledger position, make-ready actions and expected next steps. Do not include cause of death, clinical detail or participant-identifying information unless an existing permission and purpose clearly require it.
Treat reportable incident timing as urgent
The NDIS Commission's detailed guidance says deaths connected with NDIS supports or services must be notified, and that the cause of death, whether it was expected, and the place of death do not change reportability once the connection is established. It also says providers do not need to establish the cause of death before reporting; they need to consider whether the death happened in the course of their involvement in providing supports or services.
For SDA providers, the connection question should be documented quickly. Was the participant living in an enrolled SDA home? What services did the SDA provider control? Was the provider also delivering SIL, tenancy support or other services? Were maintenance, environment, access, complaints, incidents, behaviour support boundaries, emergency response or support-partner handoffs relevant?
The record should show the decision path, not a perfect conclusion. Useful states include incident triage open, Commission notification required, Commission notification submitted, further information due, other provider reporting confirmed, external authority notified, internal review open and closed with no further SDA action.
Handle vacancy payment evidence carefully
The NDIS vacancy guidance says SDA vacancy payment eligibility is limited. It applies only where the relevant conditions are met, including that the home is enrolled for 2 to 5 residents, the eligible participant dies or otherwise vacates in specified circumstances, the room is available for another SDA-eligible participant, and the NDIA has been notified.
Providers must also tell the NDIA within 5 business days if there is an SDA vacancy. The evidence requirements include the NDIA vacancy notification auto-reply, notice or termination evidence, and the terminated service agreement with the last date the participant resided in the SDA. The guidance notes that if a participant has not provided signed termination, extra evidence they moved out may be needed, but this is not needed if the participant has died.
That still does not mean every vacancy becomes a claim. The provider should map the dwelling, resident count, vacancy date, room availability, listing status, eligible days, person-specific adjustment line item and payer pathway before submitting. Keep this evidence separate from ordinary monthly SDA claiming so later reconciliation can distinguish final pre-death claims from vacancy payment claims.
Close owner reporting without creating privacy risk
Owner and investor communication needs discipline. The owner may need to understand vacancy timing, final claim status, rent contribution closure, make-ready works, expected listing actions and cashflow assumptions. They do not usually need the participant's death certificate, medical information, family details, incident narrative or support-provider notes.
A privacy-safe owner update can say that a tenancy has ended due to a resident death, the room is being made ready, NDIA vacancy notification has been completed, claim closure is underway, and the provider will report eligible vacancy or replacement-resident progress when confirmed. Anything more should be checked against consent, contract terms and the provider's privacy policy.
The same discipline helps internal teams. Finance needs claim and ledger evidence. Compliance needs incident and notification records. Property teams need access, belongings and make-ready actions. Referral teams need vacancy status. These are connected records, but they should not all expose the same level of personal information.
How StepFree fits the workflow
StepFree SDA should help providers manage participant death workflows as controlled operating records: claim pause, pre-death claim evidence, incident triage, Commission notification status, vacancy evidence, RRC ledger closure, make-ready actions and privacy-safe owner reporting.
The practical value is reducing reconstruction. When the provider can see what stopped, what remains claimable, what has been notified, what evidence is attached and what owners can safely be told, a difficult event is less likely to become a second operational failure.
Conclusion
An SDA participant death requires care first, then controlled administration. Providers need to pause ordinary claims, separate pre-death supports from post-death activity, triage reportable incident obligations, notify SDA vacancies on time, close RRC and agreement records carefully, and keep owner reporting privacy-safe. A single workflow gives teams a defensible record while keeping the focus on respect, evidence and participant safeguards.
StepFree SDA can help providers manage claim closure, reportable incident triage, vacancy evidence, RRC ledgers and owner-safe reporting when sensitive SDA transitions occur.