NDIS mandatory registration 2026 — what Mable workers need to know

Why Mable workers specifically?

Mable is the largest online platform connecting NDIS participants with independent support workers in Australia. Until now, Mable has operated as an unregistered platform — which meant less regulatory oversight and fewer documentation requirements for the workers using it.

That’s changing. From 1 July 2026, all online platform providers — Mable, Hireup, Kynd, and others — must be registered with the NDIS Quality and Safeguards Commission. Registration means audits. Audits mean your notes need to be good enough to withstand professional review.

This isn’t a theoretical risk. The Commission has the power to audit any worker’s documentation on a registered platform. If your notes don’t meet the NDIS Practice Standards, you become a compliance problem for Mable — and that directly affects your ability to get work through the platform.

What’s different about Mable’s current shift notes?

If you’ve been using Mable’s built-in shift notes field, you already know it’s basic. There’s no structure, no prompts for goal linking, no incident detection, and no compliance formatting. Most workers type a few sentences describing what happened and move on.

That was fine when Mable was unregistered. It won’t be fine after July.

A typical Mable shift note might look like: “Took James to the shops and the park. He was happy today. No issues.” That’s three sentences. It doesn’t mention which NDIS plan goals the session supported, what choices James made during the session, what his presentation was like, or how the activities related to his support plan. An auditor would flag this immediately.

What auditors actually look for

The NDIS Practice Standards set out what documentation needs to contain. Auditors assess notes against these standards, not against what you think is “detailed enough.” They look for evidence that the participant’s rights, choices, and preferences were respected. They look for links between activities and NDIS plan goals. They check that incidents, safety concerns, and restrictive practices were documented with appropriate detail. They verify that private information was handled properly and that the session details match what was claimed for payment.

None of this requires you to write a novel. It requires structure. A well-structured note can be shorter than a long, rambling shift note and still pass an audit, because it hits the right compliance points.

What Mable is likely to do

Mable hasn’t announced exactly how they’ll respond to mandatory registration, but the direction is clear. As a registered provider, Mable will be responsible for the quality of documentation across their entire workforce. They can’t afford to have workers producing notes that would fail an audit.

Expect Mable to either introduce stricter documentation requirements within their platform, provide guidance on what notes need to contain, or both. Workers who are already producing structured, compliant notes will be in a much stronger position than those scrambling to change their habits after July.

There’s also a competitive angle. If you’re producing audit-ready notes and another worker isn’t, participants and coordinators will notice the difference. Good documentation makes you a safer, more professional choice — and that translates to more bookings.

What you need to do before July 2026

1. Stop writing shift notes. Start writing case notes.

A shift note describes what happened. A case note documents how the session supported the participant’s NDIS plan, what choices they made, what goals were addressed, and any safety or wellbeing observations. The difference is structure and purpose, not length.

2. Link your sessions to plan goals

Every session you deliver should be connected to at least one NDIS plan goal where relevant. If you took someone grocery shopping and their plan has a goal about building independence in daily living, that connection needs to be in the note. This is how the NDIS justifies funding — your notes are the evidence that supports are “reasonable and necessary.”

3. Document incidents properly

If something happened during a session — a fall, a behavioural episode, a near-miss — it needs to be documented with enough detail that a supervisor or auditor can understand what happened, what you did, and what follow-up is needed. “He had a fall but he was fine” is not enough. When did it happen? Where? What did you do? Was anyone notified?

4. Know what doesn’t belong in a note

Private details about the participant’s personal life, family conflicts, relationships, or finances don’t belong in clinical documentation unless they directly affect how the next worker delivers support. The Australian Privacy Act requires you to only collect information that’s reasonably necessary for the support being provided. An audit will flag notes that contain unnecessary private information.

5. Build the habit now

Don’t wait until July to start writing better notes. Every note you write between now and the deadline could be reviewed in an audit. The earlier you switch to structured documentation, the more compliant notes you’ll have when the time comes.

What a Mable shift note looks like vs. what an audit-ready note looks like

Typical Mable shift note:

“Community access with Sarah. Went to the library and then the park. She enjoyed the outing. No problems.”

Audit-ready case note from the same session:

A structured CLIO Framework™ note would include the session context (date, time, duration, location, service type), how Sarah presented and what choices she made during the session, what activities occurred and which plan goals they supported, and an oversight section confirming no incidents or safety concerns. Same session, same information from the worker — but structured in a way that meets every compliance requirement an auditor checks for.

The timeline is short

July 2026 is roughly 100 days away. If you’re a Mable worker who’s been writing basic shift notes, now is the time to change. Not because the notes you’ve been writing were bad — they were fine for an unregistered platform. But the rules are changing, and your documentation needs to change with them.