Keeping a communication audit trail for NDIS and aged care

A worker calls in sick, you contact the affected clients, and everyone moves on. Six weeks later a complaint arrives – “nobody told me my visit was cancelled” – or a quality review asks how you handled it. If those calls went out from a Care Partner’s personal mobile, there is nothing to show. Increasingly, in both aged care and disability support, “we told the client” needs to be something you can prove, not just something you remember.

Record-keeping in the sector has tightened, and the communication around a changed visit is part of the record like anything else. Here is what has changed, why contact records matter, and what an audit-ready trail actually looks like.

What has changed

Aged care: Support at Home and the strengthened standards

From 1 November 2025, Support at Home replaced Home Care Packages under the new Aged Care Act 2024, and the strengthened Aged Care Quality Standards took effect – more detailed and more measurable than the standards they replaced. The program puts far more weight on evidence that a service actually happened: care notes, sign-in and sign-out records, attendance logs and similar confirmation are now expected, and claims have to be backed by documentation. The Aged Care Quality and Safety Commission is the regulator that checks it.

NDIS: keep the record, keep it safe, keep it for years

Registered NDIS providers already have to keep complete, accurate records of the supports they deliver and their interactions with participants. Participant records are generally kept for at least seven years (for a child, until they turn 25), and records of incidents and complaints are held for seven years too. Just as important is how: records should be access-controlled, backed up, and tamper-evident – with an audit trail of who created, viewed or changed each one and when – and never altered after the fact in a way that misrepresents what happened.

Why the communication counts, not just the visit

It is easy to think of record-keeping as being about the care delivered. But when a plan changes, the communication is the care for that moment – and it is exactly what gets questioned later. Most disputes are not about whether a worker was unavailable; they are about whether the client was told, when, and what was offered. A phone call or a text about a changed visit is part of that client’s record, and if it only ever existed on someone’s personal phone, it effectively did not happen as far as an auditor or a complaints process is concerned.

The records that get pulled are almost always the same handful of situations:

• A complaint or dispute – “I was never notified” – where you need to show what was sent and when.
• An audit or quality review against the standards.
• Continuity when staff change and the next person needs to see what the client was already told.
• Simply demonstrating you acted reasonably when a plan changed at short notice.

What an audit-ready communication trail looks like

• Captured automatically. Every call and text – the ones you send and the replies that come back – recorded as it happens, so nothing depends on someone remembering to write it down.
• Complete and time-stamped. Who was contacted, when, on which channel, the outcome, and what was said or offered.
• Tamper-evident and access-controlled. Only authorised staff can see it, and it cannot be quietly rewritten later.
• Retained and exportable. Kept for the period your program requires, and produced on demand – so answering a complaint or an audit is a search, not a scramble through phones and memories.

The manual trap

The reason this is worth attention is that the default – a Care Partner working down a list on a personal mobile – produces no usable record at all. There is no log, no timestamp, no way to show the client was reached, and nothing to hand a regulator. The record only exists if the system you use captures it by default; goodwill and good intentions are not evidence.

Where automation does the heavy lifting

This is one of the clearest cases for automating client notification. When calls and texts go out through a system rather than a personal handset, the trail builds itself: every contact is logged, kept in one place, access-controlled, and exportable when someone asks. You are not adding an admin task – you are removing the risk that the admin never happened.

The Nearness Alert System was built this way. Every call and every text, in both directions, is recorded against the right client, and the whole history can be exported as a spreadsheet or PDF, filtered by client or worker and by date. When someone asks “did anyone actually contact them?”, the answer is a report, not a guess.