The short answer
An incident is the one thing you cannot afford to write up badly, and the honest test of an app is whether it helps you get a full, factual record down while the shift is still in front of you, not from memory that night. If you work on your own, the tool I would look at first is Sparks Scribe, because its Safeguards tier is built to capture a notable action or incident in real time, walk you through the next steps, and keep the whole record, at $39 a month including GST for one person. The other tools here with real incident workflows, ShiftCare, Astalty and Visualcare, are built and priced for agencies, providers and care organisations, while Bugal and EasyAs do not publish incident reporting at all. Disclosure: I make Sparks Scribe, and I also run a provider that has to stand behind these records, so read my verdict on it knowing that, and check every competitor claim against each vendor's own pages.
I run an NDIS support provider, so I have taken the phone calls. A fall in the bathroom. A near miss with medication. A participant who lashed out because their whole day had fallen apart. In the moment the worker is not thinking about compliance, they are managing the person in front of them, exactly as they should be. But an hour later, or worse the next morning, someone has to write down what happened, and the quality of that record is quietly decided by how much has already blurred.
That is the lens I bring to these apps. Not feature count, not how modern the dashboard looks, but one narrow question: does this thing help a real person get an honest, complete incident record down before the details soften? Below I look at six tools by name, with prices for a single person and details taken from each vendor's public pages in July 2026. One of them is mine, so treat my verdict on it as a founder's, and check the rest yourself.
What actually happens when something goes wrong on a shift?
Time is the enemy of a good incident record. In the ten minutes after something happens, a worker can tell you the order of events, the exact words that were said, what they did first and second, who they rang. By the next day a lot of that has smoothed over into "the afternoon" and "they seemed alright after". None of that is dishonesty. It is just how memory works under stress, and it is the gap where records go thin.
There is a second thing people get wrong, and it matters before you compare any app. No app files your reportable incident with the NDIS Commission for you. That notification is made by the registered provider through the Commission's own channel, inside the Commission's timeframes. What software can do is capture the record cleanly, in the moment, and hold it, so that when a person does lodge, there is something honest and complete to lodge from. Keep that split in mind as you read: the app holds the record, a person still makes the report.
What would I look for in an incident app?
Here is the checklist I actually use, and it is short on purpose:
- Can you capture it in the moment? The single biggest factor in a good record is how little time passed between the event and writing it down. Native mobile matters here, because the office is the front seat of a car.
- Does it guide the next steps? A worrying moment needs more than an empty box. Something that prompts you for what you did, who you told, and any injury stops the important parts from falling through when your head is full.
- Does it keep a full, dated record you cannot quietly rewrite? The whole value of an incident record is that it is fixed in time. If it can be edited later with no trace, it is worth less to everyone, including the worker.
- Is it built and priced for how you work? A tool built for an agency pulls toward rostering, escalation chains and admin roles. If you are one person, you are paying for a structure you do not have.
- Where does the data live? An incident record holds some of the most sensitive information you will ever write about someone. Read the privacy policy before anything goes in.
I do not score on how many features a tool lists. A long feature list is easy to build and easy to ignore in the ninety seconds after something has gone wrong.
What does a strong incident record look like?
Here is the same event written two ways, both deidentified. The difference is not writing talent. It is when it was written, and whether anything walked the worker through the parts that matter.
The second one captures who, what, when and where, the harm, the immediate action, who was told, and the follow-up. That is not because the worker is a better writer on their good days. It is because it was written while the detail was still there, with something prompting the parts that are easy to forget. That is what I mean when I say an app should help.
Where I am coming from
I run an NDIS support provider and I am a parent of NDIS participants, so I read incident records from both sides: the worker writing one at the end of a hard shift, and the provider who has to stand behind it later. I also make one of the six apps below, Sparks Scribe. I have kept every competitor detail to what each company publishes, and said so plainly wherever I could not verify something.
Which apps handle NDIS incident reporting, and who are they built for?
I looked at six tools Australian support workers and providers actually use. Two are built for a single worker, three are built for organisations, and one is invoicing only. Here is where each lands.
1. Sparks Scribe: incident capture built for one worker
Straight up: this one is mine. Sparks Scribe was built in Australia by Sparks Support Pty Ltd for independent support workers rather than agencies. The Safeguards tier ($39 a month including GST) is the part built for this job: it captures a notable action or incident in real time, guides you through the next steps, and keeps the full record. Inside it are incident reports, per-client risk profiles, restrictive-practices flagging, and consent forms you can sign in the app.
You do not have to be on Safeguards to write an incident up, though. From the $15 Essentials plan there is a built-in Incident Report note template, with the AI drafting from your typed or spoken words and a plain in-app prompt to check it before you save. It stays your record, written under your name, from your account. A few plain facts to sit alongside that: the app holds a 5.0 App Store rating, more than 90,000 shifts have been booked through it, its data is stored in Australia, and the 14-day trial unlocks every feature with no card. There is no free tier.
My verdict: the one tool here built and priced for a single worker to capture the incident in the moment and keep the record, rather than to run an agency's compliance queue. That is exactly the gap it is meant to fill, so weigh it knowing I built it.
2. ShiftCare: agency incident management with an escalation chain
ShiftCare is a care-management platform for agencies, and its incident handling reflects that. You set up customisable incident forms, and submitting one creates an incident ticket, sends an email alert, and, if nobody actions it, escalates up to a risk manager and then a general manager. That escalation chain tells you exactly who it is for: an organisation that has a team lead, a risk manager and a general manager. As with every tool here, the formal notification to the NDIS Commission is still made by the provider through the Commission's portal; ShiftCare's own help material makes the same point, that its reportable field is an internal marker rather than a submission.
The sticking point for a solo worker is the pricing floor. Every ShiftCare plan carries a minimum of five licences, even if you are the only user, and the invoicing you would want sits on the Professional plan, which works out at roughly $65 to $75 a month excluding GST for one person depending on billing. You pay as if you had a team of five.
My verdict: an agency incident workflow with an escalation chain, priced for a team of five. If you work alone, most of what you are buying is structure you do not have.
3. Astalty: a provider's incident register
Astalty is built for NDIS providers and support coordinators, and its incident handling reflects that. Incidents reported by staff flow into an Incident Register without anyone re-keying them, you can mark whether an incident is reportable to the NDIS Quality and Safeguards Commission, and the register can be filtered and exported for a review or an audit. It is a register meant to be run by someone whose job includes running it.
The economics suit an organisation. The standard seat is $64 per user per month, with a restricted support-worker profile at $30. For a lone worker that is coordination depth, and a price, aimed at a role you may not be filling.
My verdict: a provider-grade incident register, priced per seat for a provider. Suited to an organisation with a compliance function; heavy and expensive if you are one person.
4. Visualcare: an enterprise care platform
Visualcare is a care-management platform sold to care organisations, with rostering, awards interpretation, client and worker management, and compliance logging that takes in incidents and audit-ready records. It is enterprise software, and it is sold like it: there is no public pricing, you request a demo and a quote, and I could not find a solo plan anywhere on its pages.
My verdict: enterprise incident and compliance logging built for a care organisation, not a single worker, with no public price and no solo plan I could verify. If you are one person, this is simply not aimed at you.
5. Bugal: built for solo workers, but no incident feature published
Bugal is one of the few here built for sole traders and micro-providers, with a free-forever plan capped at two invoices a month and a $35 Solo plan. On price and audience it sits closer to a single worker than the agency tools do. But its published feature list, client management, service agreements, shift management, invoicing, expense tracking, and shift notes and reports, does not mention incident reporting. It is a web-based platform, and I could not find a native App Store or Google Play listing in July 2026, which matters when you want to capture something one-handed in the moment.
My verdict: priced and built for solo workers, but with no incident reporting on its published pages the shift record is where it stops. For incidents you would need something alongside it.
6. EasyAs: NDIS invoicing only
EasyAs does one job, NDIS invoicing, from $19.95 a month on its website. On incidents there is nothing to weigh: across its website and both app-store listings there is no mention of incident reporting or progress notes at all. There is nowhere in the product to capture, guide or store an incident, so that record would live somewhere else entirely.
My verdict: fine at the invoice, but it is not an incident tool. It covers the bill, not the incident behind the shift.
How do these apps compare at a glance?
Collected from public pages in July 2026. "Price for one person" is the real monthly cost for a sole trader, not the headline per-user rate. The three middle columns are the parts that actually matter in an incident: catching it in the moment, being walked through the next steps, and keeping the full record.
| App | Price for 1 person | Real-time capture | Next-step guidance | Full record kept | Built for |
|---|---|---|---|---|---|
| Sparks Scribe | $39/month incl GST (Safeguards); incident note template from $15 Essentials | Yes, in the moment | Yes, guides the steps | Yes: incident reports, risk profiles, restrictive-practice flags | One worker |
| ShiftCare | Roughly $65 to $75/month ex GST (Professional, min 5 licences) | Worker logs in the mobile app | Admin escalation chain, not worker prompts | Yes, team-oriented (provider still lodges to the Commission) | Agencies |
| Astalty | $64/month standard seat ($30 support-worker profile) | Staff report into the register | Reportable-to-Commission flag | Yes: filterable, exportable register | Providers, coordinators |
| Visualcare | Not published (pricing on application) | Not verified for a solo worker | Not verified from public pages | Yes: audit-ready logs | Care organisations |
| Bugal | Free (2 invoices/month) or Solo $35/month | Not published | Not published | No incident feature listed | Solo workers |
| EasyAs | From $19.95/month on their website | No | No | No incident feature | Invoicing only |
All details collected from each vendor's public website in July 2026 and simplified for comparison; prices and plans change, so check the vendor's own pricing before deciding. "Not verified" and "not published" mean I could not confirm the detail from official public pages and chose not to guess.
Frequently asked questions
What is the best NDIS incident reporting app for a solo support worker?
For one person, I would look at Sparks Scribe first, because its Safeguards tier is built to capture a notable action or incident in real time, point you to the next steps, and keep the full record, and it is priced for a single worker at $39 a month including GST. The other tools here with real incident workflows, ShiftCare, Astalty and Visualcare, are built and priced for agencies, providers or care organisations. I make Sparks Scribe, so treat that as a founder's view and check every competitor detail against each vendor's current pages.
Does an incident reporting app lodge my report with the NDIS Commission?
Generally no, and this trips people up. These apps capture and organise the incident record. The formal notification of a reportable incident is still made by the registered provider through the Commission's own channel (PRODA), inside the Commission's timeframes. ShiftCare's help material, for example, notes the app does not submit directly to the Commission and its reportable field is an internal marker. Astalty lets you flag an incident as reportable in its register. Either way, a person in your organisation still lodges it. Check the NDIS Quality and Safeguards Commission's guidance for what and when you must report.
Can you capture an incident while the shift is still happening?
This is the whole point, and it is what Sparks Scribe's Safeguards tier ($39 a month including GST) is built for: capturing a notable action or incident in real time, guiding you to the next steps, and keeping the record. Separately, from the $15 Essentials plan you can write an incident up on the spot using the built-in Incident Report note template, with the AI drafting from your typed or spoken words and a prompt to check it before you save. For the team tools, a worker usually logs the incident in a mobile app and it flows to an admin to action.
Do ShiftCare and Astalty do NDIS incident reporting?
Yes, and both are built for organisations rather than one person. ShiftCare's public pages describe customisable incident forms where submitting a form creates an incident ticket, emails the team lead, and escalates to a risk manager and then a general manager if it is not actioned; every ShiftCare plan carries a minimum of five licences. Astalty describes an Incident Register that fills itself as staff report incidents, lets you mark whether an incident is reportable to the Commission, and keeps a filterable, exportable audit trail; its standard seat is $64 a month, with a restricted support-worker profile at $30.
Do Bugal or EasyAs have incident reporting?
Not on anything I could verify in July 2026. Bugal is built for solo workers, but its published feature list (client management, service agreements, shift management, invoicing, expense tracking, and shift notes and reports) does not mention incident reporting. EasyAs is an NDIS invoicing product, and its website and app-store listings do not mention incident reporting or notes at all. If either has added it since, check their current pages.
How much does NDIS incident reporting cost for one person?
It depends whether the tool is built for one worker or for an organisation. Sparks Scribe's Safeguards tier is $39 a month including GST for a single worker. The others with real incident workflows are priced for teams: ShiftCare works out at roughly $65 to $75 a month excluding GST for one person because of its five-licence minimum, Astalty's standard seat is $64 a month, and Visualcare does not publish pricing and is sold to care organisations. Bugal and EasyAs are cheaper but do not publish incident reporting.
What should an NDIS incident record include?
As a rule of thumb, a good record captures who was involved, what actually happened in plain factual terms, when and where, any injury or harm, what you did straight away, and who you notified, kept as a dated record you do not go back and quietly edit. The NDIS Quality and Safeguards Commission sets the rules for reportable incidents and their timeframes, so check the Commission's guidance for your obligations. Sparks Scribe's Safeguards tier is designed to capture this at the time rather than from memory hours later.
Where is my client data stored with these apps?
It varies, and an incident record holds some of the most sensitive information you will ever write about a participant, so read each vendor's privacy policy before you enter anything. Sparks Scribe stores its data in Australia. I have not verified the hosting locations of the other tools in this comparison from their public pages, so ask each one before you commit.