For Australian NDIS providers

The shift, the note
and the claim are
one record.

Most of what a provider gets wrong is bookkeeping, not care. The support was delivered. The worker turned up. What costs money and registration is everything that happens around it — a claim that never lands, an allowance that never reaches payroll, a deadline counted from the wrong moment.

Rostering · Participants · Notes · Claiming · Compliance — in one place.

caredesk.app/today Today — shifts running now, what is unfilled, and the money delivered but not yet claimed
Coordinator, today
Three gaps that cost money and registration

None of them are about the care you give.

They are about what happens around it — and none of them are visible on an ordinary roster.

Gap one

Delivered, never claimed

Under PACE there are no service bookings. Nothing reserves a participant's funding for you. A claim only lands if the shift ran, a note exists, and you are on that participant's my providers list for that support category. Miss one and it waits silently. Funding is released in periods too — unspent doesn't roll forward, so underspend is a live problem with a date on it.

Gap two

SCHADS breaches nobody sees

A client cancels inside seven days and the worker is still paid. A sleepover is interrupted and the interruption is paid work. Morning and evening on one day is a broken shift. Under ten hours between engagements is a rest break breach. Rates rise every July. None of it shows on a normal roster.

Gap three

A clock already running

Reportable incident deadlines run from the moment the provider became aware — not when it happened, not when the investigation finished. Counting from the wrong moment is itself the breach, and it is the most common notification failure in the sector.

The care happens here. The record of it shouldn't live in six places.
Field one

The awareness timestamp is the most important field in the product.

When a worker raises an incident, the first field is when did you become aware. It is set by the system, it cannot be edited, and every deadline counts from it. Change it and the original stays visible as an amendment with a reason.

Became aware
— · awaiting report
🔒 System-set · immutable · amendable only with a reason
Stage 1 notification
24 hours from awareness
Stage 2 report
5 business days
Participant and nominee told
A separate obligation, tracked separately
Press it. The clock starts from that moment.

Restrictive practice where harm occurred is 24 hours, not 5 days. Telling the participant and their nominee is a Practice Standards requirement in its own right — the most commonly missed obligation in the sector, because notifying the Commission feels like the finish line.

Why this one field decides everything.

Every other date in a compliance system is derived. If the moment of awareness is editable, every deadline downstream is editable, and the evidence pack stops being evidence.

So it is set by the clock when the report reaches you, it is immutable once saved, and an amendment never overwrites the original. An auditor can see both, and see who changed it and why.

The deadline is shown as a ring and plain words — due 9:40pm tomorrow — never a percentage and never a siren. In a disability services product, a red alert against a participant's name reads as blame.

Calm, not alarmingNo red anywhere Amber carries urgency
Everyone is asleep. Someone is awake nearby, and the clock has already started.
Nine on the desk, six in a pocket

Every screen, at full size, explained.

Pick one from the list. Each is the real designed screen — click it to open it full size.

Where the AI stops

Two thirds of providers don't trust AI near a compliance decision.

That objection is reasonable. So the boundary is built into the product rather than written into a policy — and it's shown on the surface, not buried in terms.

It will

  • Flag a note that may meet a reportable threshold.
  • Draft a Stage 2 report for your review.
  • Check a note is written in observable terms rather than conclusions.
  • Surface a pattern across notes that nobody has raised.

It will never

  • Decide whether something is reportable.
  • Submit anything to the Commission.
  • Alter the awareness timestamp.
  • Write a progress note as though it were the worker.
Six living registers

A blank register is evidence against you.

An auditor reads the entries, not the policy. A quality improvement register with no entries doesn't demonstrate compliance — it demonstrates the opposite. Care Desk shows you the empty one before they find it.

Evidence is a by-product of working properly, not a document you write in a panic.
Who sees what

A support worker cannot see money, and cannot submit to the Commission.

Permissions aren't a settings page nobody opens. They're part of the shape of the product.

Role
Sees
Cannot
A home, not a facility. The software should know the difference.
Why now

Registration became mandatory for all SIL providers on 1 July 2026.

A cohort of previously unregistered providers now has to produce evidence they have never had to produce before — and the evidence an auditor wants is a by-product of running the business properly, not a document you write the week before.

The evidence pack is assembled as you work, not the week before the audit.
Book a walkthrough

Thirty minutes, and we look at your actual desk.

Not a demo reel. We go through where your claims are held, which SCHADS exceptions are sitting in this fortnight's roster, and what your registers look like to an auditor. You get a written summary either way.

No demo reel. We look at your desk.
Thirty minutes, and you get a written summary either way.