What an NDIS provider
should delegate first
Every provider we work with is drowning in the same four things, and almost all of them try to delegate in the wrong order. Here is the sequence that works, why claiming comes first, and where the line sits under the NDIS Practice Standards.
NDIS providers have a particular problem: the administrative load scales faster than the billable hours. Add ten participants and you add ten service agreements, ten sets of progress notes to chase, ten more claim lines a fortnight, and roster changes that arrive by text at 6am.
Most providers respond by hiring a local admin person at $75,000 all-in, or by absorbing it themselves at night. Both are expensive. The third option — an offshore team member doing the non-participant-facing half — works well, but only if you hand it over in the right order.
The wrong order is what we see most often: providers start with progress notes because that is what annoys them most. It is the worst first task. Notes require clinical judgement about what is worth recording, and a new starter has no context for that. Claiming, by contrast, is rule-bound, immediately verifiable, and the thing costing you real money every fortnight.
Who this is for
✓Worth your time if
- You are a registered or unregistered provider with more than about fifteen active participants
- Your claiming runs late, or you have written off claims because nobody chased the rejection
- Your coordinators are doing rostering and invoicing instead of participant work
- You are growing and the next hire would otherwise be another local admin
✕Probably not if
- You need someone to make participant-facing clinical or support decisions
- You have fewer than about eight participants — the admin load probably does not justify a role yet
- Your service agreements and price guide mapping have never been set up properly (fix that first)
- You want someone to hold your NDIS portal credentials — that is not how this works
What an NDIS admin VA actually does
Ordered by how quickly providers hand each one over. The first three are usually live within a fortnight.
Preparing and submitting bulk claim files against service bookings, reconciling what was paid against what was delivered, and working the rejection list — wrong item number, expired booking, insufficient funds — instead of letting it age. This is where providers lose the most money to simple inattention.
Building the fortnightly roster against participant plans and worker availability, processing change requests, filling gaps from your casual pool, and flagging anything that breaks a SCHADS award condition for you to decide on.
Not writing them — chasing them. Following up support workers who have not submitted, checking notes are attached to the right shift and service item, formatting them consistently, and escalating gaps before an audit finds them.
Preparing service agreements from your template, creating service bookings, collecting consent and plan documents, setting up the participant in your system, and building the welcome pack. The conversation stays yours; the paperwork does not.
Monitoring budget burn per participant against plan end dates, flagging under-utilisation early enough to do something about it, and preparing the utilisation summary a coordinator needs before a plan review.
Raising invoices to plan managers on their required format and cadence, tracking remittances, and following up anything unpaid past terms.
Keeping worker screening clearances, first aid certificates, insurances and training records current, with a rolling expiry list so nothing lapses quietly.
What must stay with your registered staff
The line under the NDIS Practice Standards is about participant-facing decisions and clinical judgement, not about geography. An offshore team member can prepare almost anything administrative; they cannot make the calls that require a qualified, screened person.
- Participant-facing supportsAny direct support, assessment or clinical decision requires an appropriately qualified worker with NDIS Worker Screening. That is not an offshore role.
- Restrictive practice and incident decisionsReportable incident determinations, behaviour support decisions and safeguarding judgements stay with your registered staff and go through your own reporting chain.
- Portal credentialsNever share your NDIS provider portal login. Your VA works in your practice system — Splose, ShiftCare, Lumary, Brevity — as their own named user, and claim files are reviewed before submission.
- Clinical content of notesA VA chases, formats and flags. What goes in a progress note about a participant is written by the person who delivered the support.
The order to hand it over
Claiming first, notes later. This is the opposite of what most providers instinctively do.
Claiming, first
Start here even though it feels like the scariest one. Every claim is checkable against a service booking, so competence is visible within a fortnight, and the money it recovers usually covers the role by itself. Nothing is submitted without your review for the first month.
Invoicing plan-managed participants
Same skill set, same system, immediately measurable. Two clean cycles here and the working rhythm is established.
Rostering
Once they know your participants and workers by name from claiming and invoicing, rostering stops being abstract. Keep award interpretation decisions with you and have them flag rather than resolve.
Intake paperwork
By now they know how a participant flows through your system, so preparing agreements and bookings is mechanical. You still take the intake conversation.
Note chasing and compliance registers
Last, because it needs enough context to know which gaps matter and enough standing with your support workers for the follow-up to land. Give them your name behind it.
Starting with progress notes
It is the task that irritates providers most, so it is the one they try to hand over first — and it fails almost every time. A new starter cannot judge whether a note adequately describes the support delivered, so either they escalate everything and you have gained nothing, or they wave things through and you have an audit problem. Claiming has none of that ambiguity: the claim either matches the service booking or it does not. Hand over the rule-bound work first, buy the context, then move to the judgement-adjacent work once they know your participants.