NDIS and WorkCover admin: report writing, claim evidence and the money you cannot see

Because the report is assembled from memory and scattered files, not from the notes that already exist. A clinician finishes six sessions. The notes live in the practice management system. The outcome measures live in a spreadsheet or a PDF the client emailed. The goal wording lives in the plan document. The funder wants a specific structure, specific headings and specific justifications. So someone opens a blank template on a Sunday and rebuilds a story that was already written down in pieces. The rebuild is the cost. Not the clinical thinking. The cost is transcription, formatting and hunting for evidence you already recorded. This is a complaint described in public discussion rather than a measured statistic. One Australian physiotherapist on r/physiotherapy, posting to gather feedback for an AI report-writing side project they are building, framed the aim carefully: "The goal isn’t to replace or automate the report entirely, but to act as a supportive “collaborator” that can help reduce admin burden while still following all relevant guidelines." That framing is the right one. The clinical reasoning is not the bottleneck and should not be delegated. The assembly is the bottleneck.

The gap between doing the work and proving you did the work starts costing money instead of costing time. The National Disability Insurance Scheme Amendment (Integrity and Safeguarding) Bill 2025 passed the Senate on 31 March 2026. The Department of Health media release announcing it, "Senate passes tough new laws to protect the NDIS from fraudsters, predators and shonks", set out two changes that matter to providers in consecutive paragraphs: "The Bill will also modernise NDIS claims by introducing mandated electronic claim forms to prevent fraud and abuse of the system at the expense of participants." And: "It also creates a new power for the National Disability Insurance Agency to request evidence before claims are paid." Treat that as the design brief regardless of exactly how the legislation finishes its passage. Electronic claim forms mean structured fields, which means a claim either matches the record or it does not. Evidence requested before payment means the evidence has to be findable on the day, not reconstructable in a fortnight. Practices that capture evidence at the point of service are barely affected. Practices that assemble it at audit time absorb the whole cost. The practical version is unglamorous. Every billable service should have, at the moment it is marked complete: the service date, the participant, the line item, the practitioner, the duration, the note, and any consent or travel record attached. If any of those are filled in later from memory, that is the exposure.

It can draft them. It should not sign them. The workable pattern is narrow. A draft is generated from notes and outcome measures that already exist in your system, structured into the funder's required headings, with every claim in the draft traceable to a source note. The clinician then edits and signs. Nothing goes to the funder without a human approving it. The pattern that fails is the open-ended one: a clinician pasting notes into a general chatbot, getting fluent prose back, and having no record of which sentence came from which session. That is also where privacy exposure lives, because participant health information should not be leaving your systems into consumer tools. Compare the three approaches on evidence traceability, sign-off and privacy. Writing from memory into a blank template gives weak traceability. Pasting notes into a consumer chatbot gives none and creates high privacy exposure. Generating a draft from your own records, edited and signed by the clinician, is the only one that survives an audit conversation. It is also the least impressive to demo, which is part of why it gets skipped.

Because the employer has quietly passed the funder's payment cycle onto the person who spent the money. A support worker posting on r/NDIS described it directly: "At first my employer basically said I’d be reimbursed. Now they’re saying they can’t give me a clear timeframe and that it depends on when they get money back from the NDIS. In the meantime I’m stuck with a big credit card bill racking up interest that I can’t really afford." This is a cashflow design failure, not a payroll failure. The employee is being used as an unsecured lender because the business has no visibility of when its own claim will be paid. Nobody decided that. It emerged from the absence of a claim-ageing view. Two things fix most of it. First, reimburse on the payroll cycle rather than on the funder cycle, and treat the funder claim as a separate business problem. Second, make the claim visible so the business can answer how old a claim is and what is blocking it in seconds. If you cannot answer that question, waiting on the funder is unfalsifiable. It might be true. It might mean nobody lodged the claim. Both look identical from the outside.

Track your clock and the funder's clock separately. Your clock: days since the service was delivered, days since the claim was lodged, days since the last chase. The funder's clock: the statutory or published timeframe attached to the decision you are waiting on. A participant on r/NDIS described what happens when the agency's own clock runs out. Note that this is a participant, not a provider, and the 28 days is the timeframe for a decision on a plan reassessment request, not for claim payment: “The NDIA "did not make a decision" about whether to conduct the plan reassessment within 28 days which is their decision timeframe, so it was automatically rejected. The automatic rejection then went automatically to internal review, which was also a rejection.” The transferable point is that a lapsed timeframe only becomes usable if you recorded when it started. You cannot control the agency's process. You can control whether you know the date the clock started, because that is the only thing that turns a complaint into a documented position. A simple claim-ageing view covers the basics. Record the service date as the starting point for every downstream deadline. Record the lodged date, and leave it blank until lodgement actually happens, because a blank shows the claim never left the practice. Show days since lodged, the blocking item such as a missing note, consent or service agreement, and one named owner rather than admin. The value is not the dashboard. The value is that a blank lodged date becomes visible on day three instead of day sixty.

Build in the order that removes silent failure, not the order that looks most advanced. First, the claim-ageing view. Lowest effort, highest early return, because it exposes what is actually broken. Second, an evidence completeness check at the point of service, flagging any service marked complete without a note, consent or duration. Third, report drafting from existing notes with clinician sign-off enforced. That is the highest time saving, but it is only worth doing once the underlying notes are reliable. Fourth, reimbursement decoupled from the funder cycle, which is mostly a policy change supported by the ageing view. Steps three and four are tempting to attempt first, because they are the ones people feel. They both depend on step one being true.

Three worth taking seriously. Report drafting can degrade clinical writing. If a clinician stops thinking because the draft reads well, quality drops and the funder eventually notices. The mitigation is that the draft must cite its source notes, so editing means checking rather than skimming. Practice management vendors are building some of this, and some of it will arrive in your existing software. Building around the edges of your system, rather than replacing it, keeps you from paying twice. Small caseloads may not justify the work. If you lodge a handful of claims a month, a shared spreadsheet with a lodged date column is the correct answer and anything more is overhead.

Someone who stays. One failure mode is not technical. A consultant builds a workflow, hands over a login, leaves, and a year later nobody can explain why the claim report excludes a service type. The practice goes back to the spreadsheet. The durable version is one or two of your own people, usually a practice manager and a senior clinician, who understand both the funder rules and the tools. The skill that transfers is diagnosis and process mapping, working out where the evidence is actually created and what silently fails, not learning any particular tool. Rules change. NDIS pricing and claim requirements change. The person who mapped the process can adapt it. The person who only knows which buttons to press cannot. That is the argument for capability transfer over a retainer. Funder compliance is not a project that finishes.

Can I use ChatGPT to write NDIS progress reports? Not with participant health information in a consumer tool. The safer pattern is drafting inside systems you control, from notes already recorded, with the clinician editing and signing before anything reaches the funder. The draft should cite the source notes so review means checking rather than skimming. What evidence should be attached to an NDIS claim? At minimum, the service date, participant, line item, practitioner, duration and the clinical note, plus any consent or service agreement the line item requires. Capture these when the service is marked complete. Anything filled in later from memory is the part that fails an audit request. Should we reimburse staff before the funder pays us? Yes, in almost all cases. Reimbursing on your payroll cycle keeps staff out of your cashflow gap. The funder claim is a separate business problem to solve with visibility and follow-up, not something to pass down to the person who paid the expense. How do I know if a claim was actually lodged? Record a lodged date as a required field, separate from the service date. A blank lodged date on a service delivered weeks ago is the clearest signal that something never left the practice. Without that field, an unlodged claim and a slow funder look identical. Do we need new software for this? Often not. If the data already sits across a practice management system, a spreadsheet and an email inbox, the work is connecting what exists and adding the missing dates and checks, not replacing the clinical system your team already knows. Who should build it, an agency or our own staff? Your own staff, if you want it to survive rule changes. Funder requirements shift, and whoever built the process needs to be present to adjust it. A practice manager and a senior clinician trained to map and maintain the process outlast any external build.

Government source: Department of Health, "Senate passes tough new laws to protect the NDIS from fraudsters, predators and shonks", media release from the Minister for the NDIS, Jenny McAllister, 31 March 2026, on the National Disability Insurance Scheme Amendment (Integrity and Safeguarding) Bill 2025 (https://www.health.gov.au/ministers/senator-the-hon-jenny-mcallister/media/senate-passes-tough-new-laws-to-protect-the-ndis-from-fraudsters-predators-and-shonks). Reddit threads quoted, attributed to the subreddit rather than to individuals: r/physiotherapy (https://www.reddit.com/r/physiotherapy/comments/1mfn8oj/could_an_assistive_ai_make_report_writing_easier/), r/NDIS (https://www.reddit.com/r/NDIS/comments/1s97r7y/support_worker_in_vic_out_of_pocket/), r/NDIS (https://www.reddit.com/r/NDIS/comments/1uytall/currently_going_through_tribunal_waiting_for/). The r/NDIS thread at https://www.reddit.com/r/NDIS/comments/1s8l2hx/finally_at_least_they_listened_to_many_of_us/ is where the Department of Health release above was reposted, but the quoted words are the department's, not a redditor's. No statistics are cited in this article. Where patterns are described, they are described as complaints observed in public discussion, not as survey findings. The quoted material is NDIS-specific. WorkCover and insurer-funded reporting is discussed here because the same report-and-evidence pattern applies, not because separate WorkCover evidence is cited.