NDIS and disability
The buildable slice, and a straight answer about the rest.
NDIS software is a category full of people promising more than they can deliver. Claiming, plan management and price guide compliance are regulated, they change, and getting them wrong is a provider’s audit finding rather than a bug.
So we scope it properly. We build participant records, service agreements, rostering, evidence and reporting around the parts that must stay with certified products. That is a smaller promise than most of this market makes, and it is one we can keep.
Why the scope is narrow on purpose
Regulated work belongs with products that are certified for it.
The NDIS price guide changes. Claiming rules change. Registration groups and the evidence attached to them change. A bespoke system that hard-codes any of that becomes a liability the day it moves, and the provider carries the consequence, not the developer.
That is why claiming and plan management stay with specialist products. It is not caution for its own sake. It is the difference between a system that helps and a system that quietly puts your registration at risk.
What is left is not small
Rostering, service agreements, and proving you did the work.
Rostering is the operational heart of a support provider, and it is where most of the administrative cost sits: matching workers to participants by skill, gender preference, location and availability, then handling the constant reshuffle when somebody calls in sick.
Evidence is the other half. Progress notes against goals, shift notes, incident records and the documents an audit will ask for, held in one place and findable rather than scattered across email, paper and three different folders.
The scope
What gets built, and what we leave alone.
What we build for a provider
- Participant records with goals, supports, preferences and the people around them
- Service agreements with budgets tracked against what has actually been delivered
- Rostering that respects skills, gender preferences, location and availability, and copes with the Monday reshuffle
- Shift notes and progress notes tied to goals, so evidence is a by-product of the work rather than a separate job
- Incident recording with the fields your obligations actually require
- Worker records, qualifications and expiries, with reminders before they lapse
- Reporting for management and for audit preparation
What we will not build
- NDIS claiming or plan management. Regulated, frequently changed, and certified products exist
- Price guide logic. It moves, and a hard-coded copy of it is a future audit finding
- Payroll and SCHADS award interpretation. This is the single most common way disability providers get into trouble, and it belongs with a specialist
- Anything that would make us the reason a registration is at risk
Ask any vendor this question. What happens to your system when the price guide changes? If the answer is not immediate and specific, you are being sold a problem with a delay on it.
The sum
What the current stack costs, times sixty.
Do it on your own number
Count the rostering tool, the claiming product, the HR system, the document store and the spreadsheets that hold everything together. The total is usually the surprise.
Common questions
Answered plainly.
Do you build NDIS claiming software?
No. Claiming and plan management are regulated, the rules change, and certified products already do it. We build participant records, service agreements, rostering, evidence and reporting, and integrate with whatever handles your claims.
Why not just buy an all-in-one NDIS platform?
Often you should, and if one fits your service model we will say so. The providers who benefit from a build are the ones whose service model is unusual enough that every platform they trial needs a workaround, and the workarounds are where the compliance risk lives.
Can it handle SCHADS award rostering?
It can hold the roster and the shift data. It does not interpret the award, because award interpretation changes by legislation and errors become underpayment claims. That stays with a specialist payroll product, and we send it clean data.
Where does participant data live?
In Australia, on your own hosting account, with access control designed around who genuinely needs to see what. For a provider, being able to answer that question precisely is itself an audit asset.
How long does an NDIS build take?
Eight to fourteen weeks, longer than most of our projects, because rostering is genuinely complex and evidence requirements deserve care rather than speed.
Where to next
Bring the workaround.
Every provider has one: the thing the platform cannot do, held together by a spreadsheet and one person's memory. That is the brief, and twenty minutes on a call with it open tells us whether a build is worth your money.