What an NDIS VA
actually does
The complete scope, task by task — plus the two categories that never leave your registered, screened staff no matter how capable your team member is.
Providers ask this question because the answer determines whether a hire is worth making, and most content on it is either vague or overstated. So here is the actual task list, drawn from the roles we run.
The short version: almost all non-participant-facing administration can be handled offshore, and it is usually the majority of a coordinator's week. What cannot move is anything requiring clinical judgement or a screened, qualified person in front of a participant.
That boundary is set by the NDIS Practice Standards and it is about the nature of the work rather than the location of the person — the same limits apply to an unqualified administrator sitting in your own office.
Who this is for
✓Worth your time if
- You are a registered or unregistered provider considering offshore support
- You want the task list before you commit
- Your coordinators are doing administration instead of participant work
- You need to explain the boundary to your board or your auditor
✕Probably not if
- You need participant-facing or clinical support
- Your service agreements and price guide mapping were never set up properly
- You want someone to hold your provider portal credentials
Everything an NDIS VA can handle
Grouped by function. Most providers hand over the first three within a fortnight and reach the rest by month three.
Bulk claim files prepared and submitted against service bookings, payments reconciled against services delivered, and every rejection diagnosed and resubmitted — wrong item number, expired booking, insufficient funds, duplicates.
Bookings created, extended before they expire and reconciled against plans. The single most common cause of a failed claim.
Invoices raised to plan managers in their required format and cadence, remittances tracked, unpaid invoices chased past terms.
Fortnightly rosters built against plans, worker availability and skill mix; change requests processed, gaps filled from your casual pool, and award conflicts flagged for you to decide.
Following up 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. Chasing and formatting only.
Service agreements prepared from your template, bookings created, consent and plan documents collected, participants set up in your system, welcome packs built.
Budget burn monitored per participant against plan end dates, under-utilisation flagged early enough to act on, and utilisation summaries prepared before plan reviews.
Worker screening clearances, first aid, insurances and training tracked with rolling expiry lists so nothing lapses quietly.
Evidence gathered and indexed against the Practice Standards continuously rather than in a scramble before an audit.
Claims submitted, paid, rejected and outstanding; utilisation by participant; roster versus actual — weekly rather than quarterly.
The two categories that never move
Set by the NDIS Practice Standards. These are about the work, not the location — an unqualified person in your own office could not do them either.
- Anything participant-facingDirect support, assessment, clinical decisions and behaviour support require an appropriately qualified worker with NDIS Worker Screening. Not an offshore role, ever.
- The clinical content of notesA VA chases, formats and flags gaps. What is written about a participant is written by the person who delivered the support.
- Incident and restrictive practice determinationsReportable incident decisions and safeguarding judgements go through your own chain with your registered staff.
- Provider portal credentialsNever shared. Claiming happens inside your practice software; the NDIS portal stays with your staff.
The order that works
Claiming first, notes last. This is the opposite of what most providers instinctively do, and the reason many NDIS handovers stall in week two.
Claiming, first
Every claim is checkable against a service booking, so competence is visible in a fortnight — and the recovered money usually covers the role. Nothing submitted without your review for the first month.
The rejection backlog
Point them at the aged rejections nobody has worked. Finite, measurable, self-funding, and it teaches your item mix faster than any training.
Plan-managed invoicing
Same systems, same skills, immediately measurable. Two clean cycles and the working rhythm is set.
Rostering
Once they know your participants and workers by name, rostering stops being abstract. Keep award interpretation with you; have them flag rather than resolve.
Intake paperwork
By now they understand 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 both need context to know which gaps matter and 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, let them buy context with it, and move to the judgement-adjacent work once they know your participants and your workers by name.