<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by CTARS on Medium]]></title>
        <description><![CDATA[Stories by CTARS on Medium]]></description>
        <link>https://medium.com/@ctars?source=rss-ff4948cc3f90------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aHv8fBTdGKLnM3VsU_8wMg.png</url>
            <title>Stories by CTARS on Medium</title>
            <link>https://medium.com/@ctars?source=rss-ff4948cc3f90------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:17:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ctars/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Still Using Spreadsheets to Run Your NDIS Business? Here’s What That’s Actually Costing You]]></title>
            <link>https://medium.com/@ctars/still-using-spreadsheets-to-run-your-ndis-business-heres-what-that-s-actually-costing-you-d9500eef850d?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9500eef850d</guid>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[client-management]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 06:01:50 GMT</pubDate>
            <atom:updated>2026-06-23T06:01:50.796Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me be real with you for a second.</p><p>If you’re still tracking NDIS participant budgets on Excel, logging incidents in a Word doc, and chasing paper forms across three different folders, you already know something’s off. You’re not saving time. You’re just used to the pain.</p><p>And that’s the problem. We get used to slow. We forget what smooth looks like.</p><p>This piece is for NDIS providers and out-of-home care (OOHC) organisations who are running lean, feeling the admin squeeze, and wondering if there’s a better way to manage it all. Spoiler: there is.</p><h4>The Hidden Cost of Manual Client Management:</h4><p>Running an NDIS disability services business is not simple. You’ve got participant goals to track, NDIS budgets to monitor, incident reports to file, medication logs to maintain, and compliance audits creeping up on you every year.</p><p>Do all that on paper or a patchwork of tools and things fall through the cracks.</p><p>Not because your team isn’t trying. They are. But manual systems just weren’t built for this level of complexity.</p><p>Here’s what providers tell us happens when they’re not using proper <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a>:</p><ul><li>Staff spend hours a week on admin instead of direct care</li><li>Incidents get logged late, or not at all</li><li>NDIS budget tracking is always slightly behind</li><li>Compliance prep before audits becomes a mad scramble</li><li>Billing errors lead to underclaims or rejected payment requests</li></ul><p>This isn’t a people problem. It’s a systems problem.</p><h4>What NDIS Providers Actually Need From Software:</h4><p>A lot of software out there promises everything and delivers a confusing mess of features that don’t quite fit how disability services actually works.</p><p>The real questions to ask are:</p><p><strong>Does it handle NDIS billing integration?</strong> Uploading payment claims manually to the myplace portal takes forever. Good <a href="https://ctars.com.au/ndis-client-management-software/">disability support software</a> should remove that step entirely, letting you process NDIA-managed participant claims without the back and forth.</p><p><strong>Can it track participant goals and outcomes?</strong> Goal tracking isn’t just a nice feature. It’s part of demonstrating value to participants and meeting your obligations under the <a href="https://www.ndiscommission.gov.au/providers/registered-ndis-providers/provider-obligations-and-requirements/ndis-practice-standards">NDIS Practice Standards</a>. Providers need a clear record of where a participant started, what support was delivered, and what changed.</p><p><strong>Is it built for compliance?</strong> The <a href="https://www.ndiscommission.gov.au/">NDIS Quality and Safeguards Commission</a> requires registered providers to meet specific reporting standards. Missing a mandatory report or filing an incident late can put your registration at risk. You want software that has compliance baked in, not bolted on.</p><p><strong>Does it work for your whole team?</strong> Not just admin. Support workers in the field, coordinators, clinical staff. If the tool only works well at a desk, it’s not a disability services tool. It’s an admin tool.</p><h4>Why OOHC Providers Have Different Needs (And Why That Matters)</h4><p><a href="https://ctars.com.au/out-of-home-care/">Out-of-home care software</a> is a different beast entirely.</p><p>You’re managing children in respite, interim or long-term placements. The regulatory environment is complex. In New South Wales alone, providers must comply with Department of Communities and Justice requirements while also managing carer relationships, placement stability records, and critical incident reporting.</p><p>A generic case management tool won’t cut it here. The language is different. The workflows are different. The stakes are higher.</p><p>What OOHC providers need is a system that understands the sector. One built by people who’ve actually worked in it.</p><h4>What Makes CTARS Different From Generic Tools:</h4><p><a href="https://ctars.com.au/">CTARS</a> has been around since 2010. It was built by clinicians and human services staff, not by software developers who read a few white papers on disability support.</p><p>That matters a lot more than it sounds.</p><p>When software is designed by people who’ve sat in case reviews, filed incident reports, and tracked NDIS budgets for real clients, the tool feels different. The language makes sense. The workflows match what actually happens on the ground.</p><p>Here’s what’s included:</p><p><strong>Client budget management</strong> — track NDIS plan budgets in real time so you’re never caught off guard by overspend</p><p><strong>Scheduling and billing</strong> — manage rosters and generate invoices without bouncing between tools</p><p><strong>Incident management and reporting</strong> — log incidents quickly and generate compliant reports without starting from scratch every time</p><p><strong>Medication management</strong> — reduce risk with structured medication tracking that gives you a clear audit trail</p><p><strong>Custom form builder</strong> — create the forms you actually need, not just the default ones that don’t quite fit</p><p><strong>Real-time alerts and notifications</strong> — so nothing falls through the cracks when a client’s status changes</p><p><strong>NDIS billing integration</strong> — the optional add-on that eliminates the myplace portal headache for NDIA-managed participants</p><p>The whole thing is cloud-based, ISO 27001 accredited, and has two-factor authentication. Your client data is safe. You can access it anywhere.</p><p>You can <a href="https://ctars.com.au/product-tour/">see exactly how CTARS works</a> with a 30-minute personalised demo. No pressure. No sales pitch with slides that don’t match your actual situation. Just someone from the team, who has clinical or human services experience, walking you through it.</p><h4>“But We’ve Already Got a System”</h4><p>Fair enough. Switching software is a real pain. We hear that a lot.</p><p>But here’s the thing. Most providers who say this are using a system that kind of works. Not well. Just… kind of. And they’ve adjusted everything around its limitations instead of fixing the actual problem.</p><p>CTARS does custom implementation for every new client. So you’re not just getting software dumped on you and left to figure it out. The setup is built around how you work, not the other way around.</p><p>If you’ve been searching for <a href="https://ctars.com.au/ndis-client-management-software/">best NDIS software Australia</a>, or comparing <a href="https://ctars.com.au/product-tour/">disability services case management tools</a>, the thing to check is how the implementation actually works. A tool is only as good as how well it fits your team.</p><h4>The Compliance Risk Most Providers Underestimate:</h4><p>Here’s a thing people don’t talk about enough. As NDIS compliance requirements get tighter under the Commission’s oversight framework, providers who rely on manual systems are carrying real risk.</p><p>One missed incident report. One participant complaint that wasn’t documented properly. One audit that turns up gaps in your records. These things have consequences.</p><p>The <a href="https://www.ndiscommission.gov.au/providers/registered-ndis-providers/provider-obligations-and-requirements/ndis-practice-standards">NDIS Practice Standards and Quality Indicators</a> are not suggestions. They’re requirements. And when an auditor arrives, you need records that are complete, organised, and easy to produce.</p><p>Good NDIS provider software keeps you audit-ready all the time. Not just when the auditor calls.</p><p>CTARS has embedded forms and processes designed around compliance requirements. Providers using it can demonstrate best-practice standards without the last-minute panic. See the <a href="https://ctars.com.au/pricing/">CTARS pricing</a> to find a plan that works for your organisation size.</p><h4>How to Know If You Actually Need to Switch:</h4><p>You probably already know. But here’s a simple check.</p><p>In the last month, did your team:</p><ul><li>Spend more than an hour looking for a document that should have taken two minutes to find?</li><li>File an incident report late because the process was too clunky?</li><li>Have trouble knowing exactly how much of a participant’s NDIS budget had been used?</li><li>Manually re-enter data from one system into another?</li></ul><p>If any of those sound familiar, you’re ready to look at something better.</p><p>You can <a href="https://ctars.com.au/">start a free trial of CTARS</a> with no credit card required. You’ll get access to pre-loaded sample data so you can see how it actually works with real (well, fake-but-realistic) client records and forms. No commitment. No sales pressure.</p><p>Or if you want to see it with someone walking you through your specific use case, <a href="https://ctars.com.au/">book a demo</a> and spend 30 minutes with a team member who gets the sector.</p><h4>One More Thing:</h4><p>CTARS integrates with tools you might already be using. Xero. MYOB. NetSuite. EasyEmployer. So you’re not starting over on your accounting or payroll side. You’re just filling the gap where client management has been letting you down.</p><p>It’s used for 6000+ clients across Australia. It’s Australian-owned and operated. And it’s been around long enough to know that what NDIS and OOHC providers need has changed a lot since 2010 and the software has changed with it.</p><p>If you’re an NDIS provider or OOHC service wondering whether your current setup is actually holding you back, the easiest thing to do is <a href="https://ctars.com.au/">check out CTARS</a> and have a conversation with their team.</p><p>Sometimes the admin chaos is just the cost of doing business. And sometimes there’s a tool that makes it go away.</p><p>Worth finding out which one it is.</p><p>CTARS is a cloud-based NDIS and OOHC client management system based in Sydney, Australia. Learn more at <a href="https://ctars.com.au/">ctars.com.au</a> or read more on the <a href="https://ctars.com.au/blog/">CTARS blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9500eef850d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What the First Two Weeks of July 2026 Actually Look Like for an NDIS Provider]]></title>
            <link>https://medium.com/@ctars/what-the-first-two-weeks-of-july-2026-actually-look-like-for-an-ndis-provider-8ba09df7b24b?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ba09df7b24b</guid>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Fri, 19 Jun 2026 10:03:23 GMT</pubDate>
            <atom:updated>2026-06-19T10:03:23.427Z</atom:updated>
            <content:encoded><![CDATA[<p>July 1, 2026 is the most operationally complex start-of-year in NDIS history. New pricing takes effect. Mandatory SIL registration begins. The 90-day claims window starts. Social participation budgets start reducing. This is a plain-language journal of what those first two weeks actually look like — and what separates providers who handle it smoothly from those who do not.</p><p>Every 1 July, the NDIS resets.</p><p>New pricing. New financial year. New billing runs. Usually manageable.</p><p>This July is different.</p><p>This July, the mandatory registration deadline for SIL and platform providers coincides with new pricing, the beginning of social participation budget reductions, the start of the 90-day claims window, and the first SCHADS wage adjustment plus 12 percent superannuation flowing through to billing. All at once.</p><p>Here is what the first two weeks of July actually look like, and what the difference is between a provider who handles it and one who does not.</p><h4>Monday July 1: The new rates take effect and registrations become mandatory</h4><p>The 2026–27 NDIS Pricing Arrangements take effect. The price limit for a standard Level 1 support worker on weekday daytime increases by approximately 3.95 percent to around $70.23 per hour. Every support type has a new rate. The old rates stop being valid.</p><p>For a provider whose <a href="https://ctars.com.au/ndis-client-management-software/">NDIS billing</a> system updates rates automatically, Monday morning is a normal billing morning. The new rates are live. The first session logged on July 1 claims at the correct rate. No manual intervention.</p><p>For a provider whose billing requires manual rate updates, Monday is a maintenance day. Someone spends the morning updating every item code in the billing configuration. Any session billed before that update is complete is billed at the wrong rate. If six workers deliver sessions before 10am and the billing update is not done until noon, six sessions need to be reviewed.</p><p>At the same time, mandatory SIL registration begins. SIL providers who are not registered as of July 1 cannot legally deliver SIL supports. Providers who made it through the registration process are starting the new year registered. Providers who are still waiting on audit outcomes are in a legal grey area that requires urgent attention.</p><h4>Tuesday, July 1 to Friday, July 4: The first billing run of the new year</h4><p>The first billing run of the new financial year is the most important one.</p><p>It sets the pattern for the next twelve months. If it goes out cleanly, on time, at the right rates, with the right codes, it signals to plan managers and the NDIA that your service is running properly. If it goes out with errors, late, or at wrong rates, the first month of the new year starts with a queue of corrections.</p><p>The 2026–27 Temporary Transformation Payment loading is being phased down. If your service has been claiming TTP, you need to confirm you are still eligible and using the correct line items. Claiming TTP without meeting the benchmarking requirements is a compliance breach that the digital payment system will now detect.</p><p>Travel claim rules have also tightened. You can generally claim up to 30 minutes of travel time in metro areas (MMM1–3) and 60 minutes in regional areas. Any travel claims that exceed these limits will be flagged under the new payment scrutiny system.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> that validates claims before submission — checking rates against the new PAPL, checking TTP eligibility, checking travel limits by geographic zone — means these errors are caught before submission, not after rejection. Claims without supporting documentation get rejected, creating 4 to 6 week payment delays. CTARS integrates directly with <a href="https://www.xero.com/au/">Xero</a> and <a href="https://www.myob.com/au">MYOB</a> so financial records update automatically when the first billing run is processed.</p><h4>Week 1: The 90-day claims window is now running</h4><p>From December 1, 2026, the time to make a claim for supports under a participant’s plan reduces from 2 years to 90 days.</p><p>But July 1 is when the behaviour that creates that compliance problem actually starts. Any session delivered in July and not claimed within 90 days after December 1 will be forfeited. Providers who develop a billing backlog in July — even a two-week backlog — are building a problem that will become visible in late September.</p><p>The right response is to establish a billing cycle discipline in week one. Sessions delivered Monday to Sunday. Billing submitted by the following Wednesday. Financial records reconciled by Friday. That 10-day cycle means every session is claimed well within any future claims window.</p><p>A connected <a href="https://ctars.com.au/ndis-client-management-software/">client management system</a> where sessions flow automatically into the billing run makes this cycle achievable for any provider. A manual system where someone cross-references a rostering app against a billing spreadsheet every fortnight is structurally unable to run a 10-day cycle at scale.</p><h4>Week 1: Social participation budgets start reducing</h4><p>From October 1, social participation budgets will reduce progressively as plans renew. But the plans that renew in October were set in motion at the start of July. Participants whose plans run July through June receive the current budget for this plan period. Participants whose plans renew after October begin receiving the reduced allocation.</p><p>Week one is when you map your participant caseload against this timeline. Which participants have plans renewing after October? Those are the ones whose July progress notes matter most for their plan review case. The documentation you build in July is the evidence that supports their funding at reassessment.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au.</strong></a> See how budget tracking, billing cycles, and participant plan mapping work in a system built for exactly this kind of transition period. No credit card.</p><h4>Week 2: New framework planning begins rolling out for some participants</h4><p>Adults already in the scheme will transition gradually based on their plan review dates. From mid-2026, the new framework planning begins for some participants. Not all. Gradually, based on when plans come up for review.</p><p>For providers in week two of July, this means checking which participants are approaching plan review and whether those reviews will fall under the old framework or the new one. Participants transitioning to new framework planning need I-CAN-ready documentation — notes that demonstrate support dependency, not just worker activity.</p><p>Providers who built that documentation habit in June are ready. Providers who are starting now have some ground to make up. The documentation from the first sessions of July starts building the evidence picture for reviews in October, November, and December.</p><p>You cannot afford to manage two completely different planning systems manually for five years. A system that handles mixed plan types — some participants on old framework plans, some transitioning to new framework — without requiring different workflows for each is the operational infrastructure this year demands.</p><h4>Week 2: The mid-term audit cycle continues</h4><p>For providers who registered or renewed their registration in late 2024 or early 2025, the 18-month mid-term audit falls in the second half of 2026. Some of those mid-term audits will be scheduled in July and August.</p><p>Providers who do well in NDIS audits are not the ones who prepare the hardest in the final week. They are the ones who build compliance into their daily operations and keep their documentation current all year round.</p><p>If a mid-term audit notification arrives in week two of July, the evidence it needs is the documentation built in the preceding eighteen months. Not in the two weeks of intensive preparation before the auditor arrives.</p><p>Worker clearances should be current because the system flagged expiries in advance. Incident records should be complete because workers logged them at the time. Service agreements should be current because renewal prompts fired when participant plans changed. Progress notes should be structured and goal-referenced because the template prompted workers to capture them that way.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> that maintains these records continuously means the mid-term audit is a review of a functioning system, not a reconstruction of one.</p><h4>What the difference is:</h4><p>A provider with connected systems enters July 1 with rates updated automatically, a billing cycle that runs on a 10-day pattern, worker clearances that are current because the system tracks them, progress notes that are I-CAN ready because the template builds that habit, and a caseload map that shows exactly who is approaching plan review and when.</p><p>A provider without connected systems enters July 1 with a rate update to do manually, a billing run that takes all of Thursday, worker clearances to audit manually from a spreadsheet, progress notes that describe worker activity, and no clear picture of which participants are approaching new framework transitions.</p><p>Same regulatory environment. Same reform pressures. Different operating position.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how connected systems make the transition into the new financial year a managed process rather than a reactive one.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.</p><p>See the <a href="https://ctars.com.au/product-tour/">product tour</a> to understand how July 1 looks in a connected system. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>The providers who handle July smoothly are not the ones who prepared the hardest in the final week. They are the ones who built the right systems months earlier.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au.</strong></a> Full platform. Built for the first two weeks of July 2026 and every week after that. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong> </a>Walk through what July 1 looks like inside CTARS and what your preparation checklist needs to include.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If your team has not yet mapped what July 1 means for billing, registration, and documentation, share this with your operations lead and billing coordinator today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ba09df7b24b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nine Things Every NDIS Provider Should Complete Before 30 June.]]></title>
            <link>https://medium.com/@ctars/nine-things-every-ndis-provider-should-complete-before-30-june-9205aec19182?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/9205aec19182</guid>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[incident-management]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 07:17:45 GMT</pubDate>
            <atom:updated>2026-06-17T07:17:45.334Z</atom:updated>
            <content:encoded><![CDATA[<h3>Nine Things Every NDIS Provider Should Complete Before 30 June. How Many Has Your Organisation Done?</h3><p>The end of the financial year is a natural reset point for NDIS providers. Worker clearances, service agreements, budget utilisation, plan horizon mapping, incident register reviews, and compliance records all benefit from an annual check. With July 1 bringing new pricing, new registration requirements, and new reform milestones, the stakes of a thorough June review are higher than in any previous year. This is the practical checklist.</p><p>Most NDIS providers know the financial year end as a billing event.</p><p>Rates change. Service agreements need updating. The first billing run of the new year needs the right codes.</p><p>But June is also the right time to run a broader operational review. The kind that surfaces gaps before they become compliance findings, catches worker clearances that are about to lapse, identifies participants whose budgets need attention, and maps your caseload against the reform timeline heading into the second half of 2026.</p><p>Nine things. Work through them before June 30. Here is the list.</p><h4>1. Run a worker clearance audit</h4><p>The first wave of five-year NDIS Worker Screening Checks started expiring in February 2026. Providers who have not audited their team’s clearance status since then may have workers delivering services with expired checks right now.</p><p>Pull every worker’s clearance status, issue date, and expiry date from your records. Flag anyone whose clearance expires before December 2026 and initiate renewal immediately. The renewal process takes four to eight weeks. A clearance that expires in September needs to be in process now.</p><p>Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> should hold every worker clearance with an expiry alert that fires automatically before the date. If you are currently discovering clearance gaps by manually checking a spreadsheet, you are at risk of missing them.</p><p>This is not just an end-of-year task. From July 2026, the April 2026 amendments require worker screening verification at the time of each service delivery, not just at employment. A clean clearance register going into the new year is the foundation of the rest of your compliance calendar.</p><h4>2. Review every active service agreement</h4><p>Pricing is reviewed annually but updates can occur throughout the year.</p><p>Every service agreement that specifies a fixed dollar rate needs to be reviewed against the new 2026–27 pricing once it is published in late June. Agreements that reference the current NDIS price limit rather than a fixed rate update automatically. Those that specify a dollar figure need to be reissued.</p><p>Beyond the rate change, June is a good time to check whether every participant still has a current, signed service agreement. Agreements that were not updated when a participant’s plan changed are a compliance gap. Agreements where the support categories no longer match what is being delivered are a billing risk.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> that holds service agreements against participant profiles with version history and renewal prompts makes this audit fast. Pull a list of agreements expiring or last updated more than twelve months ago. That is your renewal priority list.</p><h4>3. Check participant budget utilisation across your full caseload</h4><p>Track service delivery against budgets in real time and flag participants approaching 80 to 85 percent budget utilisation.</p><p>June 30 is when most annual plans end. A participant whose plan expires on June 30 with 40 percent of their budget unspent is a participant who may receive a reduced plan next year. The NDIA uses utilisation data as a signal about support needs. Consistent underspend signals that the current budget may be more than required.</p><p>Run a budget utilisation report across every participant whose plan ends before or around June 30. Identify anyone significantly under or over-utilising their plan. For underspenders, document the reason — whether it is supply constraint, changed circumstances, or a gap in service delivery your organisation could address. For overspenders, check whether a period limit adjustment or plan review is warranted before the plan expires.</p><p>This report should take two minutes in a connected <a href="https://ctars.com.au/ndis-client-management-software/">client management system</a> that shows real-time budget utilisation per participant. If it takes two hours of manual calculation, that is the first thing to fix going into the new year.</p><h4>4. Map your caseload against the new framework transition timeline</h4><p>Some participants will transition to the new framework in mid-2026. Others will not move until 2028 or later. You cannot afford to manage two completely different planning systems manually for five years.</p><p>June is the right time to map which participants in your caseload are likely to transition to new framework planning first, and what that means for your documentation and billing.</p><p>New framework planning begins rolling out from April 2027 for adult participants with less complex needs. Participants approaching plan renewal in the second half of 2026 or early 2027 may be among the first affected. Know who they are now so you can ensure their documentation is I-CAN ready before their review arrives.</p><p>Pull a list of every participant’s plan end date. Flag those expiring in the October 2026 to June 2027 window. These are the participants whose progress notes need to demonstrate support dependency evidence right now, not at review time.</p><h4>5. Review and close every open incident record</h4><p>An incident register with open records — incidents logged but not resolved, incidents without corrective action notes, incidents where the Commission notification status is unclear — is an audit finding waiting to happen.</p><p>The <a href="https://www.ndiscommission.gov.au/rules-and-standards/managing-and-reporting-incidents">NDIS Commission</a> expects incident records to be complete and closed with documented corrective action. Before June 30, pull every incident record that is not in a resolved state. For each one: complete the resolution record, document the corrective action taken, and confirm whether a Commission notification was submitted if required.</p><p>A clean, closed incident register going into July is the operational baseline for the new audit cycle. Any mid-term audit in the coming year will check this register first.</p><h4>6. Run a goal tracking health check for plan review season</h4><p>June and July are peak plan review season. Many participants have annual plans that align with the financial year. Before their reviews arrive, pull the goal tracking history for every participant with a plan review due in the next three months.</p><p>Ask whether the progress notes tell a coherent story. Are goals being actively tracked? Are workers referencing goals in their session notes? Is there evidence of functional progress or change over the plan period?</p><p>If the answer is no for more than a quarter of your approaching reviews, your review preparation load in July is going to be significant. If the answer is yes, your reviews will be straightforward.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS billing</a> and goal tracking in a connected system means this check is a report, not a manual review of every participant file. Pull the goal tracking summary. Identify the gaps. Assign follow-up to coordinators before the reviews arrive.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au.</strong></a> Run all nine checklist items on real sample data inside CTARS. See what end-of-year operational health actually looks like. No credit card.</p><h4>7. Confirm your July 1 billing system readiness</h4><p>The 2026–27 NDIS Pricing Arrangements and Price Limits will be published in late June. Before you can confirm your billing system is ready for July 1, you need to check three things.</p><p>First: does your billing system update rates automatically when new pricing is published, or does someone have to manually update every item code?</p><p>Second: are all worker qualification levels correctly mapped to the right billing codes? Any qualification changes since July 2025 — new staff, upgraded qualifications, changed registration types — need to be reflected in the billing configuration.</p><p>Third: have all service agreements been reviewed against the new rates so you are not charging participants at old rates from July 2?</p><p>The official <a href="https://www.ndis.gov.au/providers/pricing-arrangements">NDIS Pricing Arrangements</a> page is where the new document will appear. Bookmark it. Check it the day it is published. Your billing system should do the rest automatically.</p><p>CTARS integrates directly with <a href="https://www.xero.com/au/">Xero</a> and <a href="https://www.myob.com/au">MYOB</a> so when rates update, your financial records update with them.</p><h4>8. Complete your end-of-year compliance report</h4><p>Before June 30, pull together a brief internal compliance summary for your leadership team. How many incidents occurred in the past twelve months? How many were reportable to the Commission? What were the corrective actions? How many complaints were received? What improvements did they drive?</p><p>This is not a Commission submission. It is internal governance documentation. It demonstrates that your organisation reviews its compliance data, learns from it, and makes decisions based on it. That is exactly what the NDIS Practice Standards continuous improvement requirement asks for.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> that holds incident records, complaint records, and improvement actions in structured, retrievable format means this summary is a reporting exercise, not a reconstruction project.</p><h4>9. Check that new framework documentation habits are in place before July 1</h4><p>Flag participants approaching 80 to 85 percent budget utilisation and track service delivery against budgets in real time. Plan reassessment restrictions mean under-budgeted plans cannot be fixed mid-cycle.</p><p>The biggest operational challenge of the reform period is not a single deadline. It is the transition from documenting what workers did to documenting what participants need and what happens without the support.</p><p>Before July 1, review five random progress notes from across your caseload. Ask whether they would satisfy an I-CAN assessor’s question about support dependency. If most of them describe worker activity rather than participant support need, that habit needs to change before the new framework starts affecting plan reviews.</p><p>That documentation habit change does not require a training program. It requires a note template that asks the right questions. A template that prompts workers to capture what the participant needed help with and what would have changed without the support.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how connected systems produce the documentation that plan reviews and compliance audits require.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.</p><p>See the full operational dashboard on the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>Nine items. Two weeks left. Start with whichever one your organisation is most likely to have missed.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au.</strong> </a>Full platform. All nine checklist items supported through daily operations. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong></a> Walk through your end-of-year checklist with someone who understands NDIS operations and what each item requires.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. Share this with your operations lead, billing coordinator, and quality manager together. These nine items touch every part of your service.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9205aec19182" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2026–27 NDIS Pricing Update Is Three Weeks Away.]]></title>
            <link>https://medium.com/@ctars/the-2026-27-ndis-pricing-update-is-three-weeks-away-33047618dde0?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/33047618dde0</guid>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <category><![CDATA[incident-management]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 07:29:20 GMT</pubDate>
            <atom:updated>2026-06-16T07:29:20.105Z</atom:updated>
            <content:encoded><![CDATA[<h3>The 2026–27 NDIS Pricing Update Is Three Weeks Away. Here Is What Your Organisation Needs to Do Before July 1</h3><p>The 2026–27 NDIS Pricing Arrangements and Price Limits will be published in late June 2026 and take effect on 1 July 2026. Every NDIS provider in Australia must update their billing rates, service agreements, and systems before that date. Providers who miss this update will be billing at wrong rates from day one. This is the practical preparation checklist.</p><p>Every 1 July, NDIS providers face the same annual compliance task.</p><p>New pricing is published. Old rates stop being valid. Every service agreement, every billing system, every invoice template needs to reflect the updated rates before the first session of the new financial year.</p><p>It sounds straightforward. In practice, for providers still running manual billing processes or using generic invoicing tools that do not update automatically, the first week of July is a compliance scramble.</p><p>The 2025–26 pricing update included a 3.95 percent increase in standard support prices — the largest single-year increase in recent years. It also introduced national standardised therapy rates, changed travel billing to 50 percent for therapy providers, and updated cancellation rules. Providers who were not prepared lost revenue in the first billing cycle and created compliance issues in their service agreements that have been running forward ever since.</p><p>The 2026–27 pricing update has not been published yet as of mid-June 2026. The 2026–27 PAPL is expected to be published in late June 2026 and take effect on 1 July 2026. But there is preparation you can do right now, before the new rates are published, that will significantly reduce the scramble when the document drops.</p><p>Here is the preparation checklist.</p><h4>Step 1: Know which rate categories apply to every service you deliver</h4><p>The NDIS Support Catalogue has grown in complexity each year. The 2025–26 catalogue restructured several line items and introduced new codes for some support types. The 2026–27 catalogue will likely do the same in areas under reform pressure.</p><p>Before the new catalogue is published, map every support type your organisation delivers to the current item code. For each service type, know: the current item code, the current rate, who can deliver this support (qualification requirements), and whether travel is billable for this item.</p><p>This mapping exercise is not something you can do in a day under pressure. It is something you can do in the week before the catalogue drops so that when the new document is published, you are comparing like-for-like rather than starting from scratch.</p><p>Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> should hold the current item code for each service type against the billing configuration. If your billing team is selecting codes manually at claim time rather than having them mapped from service type, that manual selection process needs to be audited before July 1.</p><h4>Step 2: Review every active service agreement before the rates change</h4><p>An outdated spreadsheet is a slow leak in your compliance hull that could sink your NDIS provider status before the June 2026 audit cycle begins.</p><p>The same is true of an outdated service agreement. Charging a rate that differs from the rate in the service agreement is a breach of the NDIS Terms of Business. When rates change on 1 July, every service agreement that specifies a dollar rate rather than “the current NDIS price limit” needs to be reviewed and updated.</p><p>Before the new pricing is published, identify every participant whose service agreement specifies a fixed rate. These are the agreements you will need to update once the new PAPL is live. If you have 40 participants and 35 of their service agreements specify dollar rates, you have 35 updates to prepare and send for signature before 1 July.</p><p>Some providers use service agreement language that references “the current NDIS Pricing Arrangements and Price Limits” rather than a specific dollar figure. That approach means the service agreement does not need to be reissued each July — the rate updates with the pricing change automatically. For providers who have not done this, adding this language in the next round of service agreement renewals will reduce the July workload in future years.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> that holds service agreements against participant profiles with version history means you can identify every agreement containing a fixed rate and prioritise them for review before the cutover.</p><h4>Step 3: Prepare your billing system to update rates without manual re-entry</h4><p>Superannuation rises to 12 percent on 1 July 2026. SCHADS Award movements will flow through to the pricing update. The calculation behind the new price limits involves Fair Work Commission wage review outcomes, the superannuation guarantee change, and the NDIA’s own cost model inputs.</p><p>For providers whose billing system requires manual rate updates, 1 July is a rate maintenance day. Someone opens the billing configuration, changes the rate for each item code, checks it against the published catalogue, and signs off. For a provider with multiple support types, multiple worker qualification levels, and multiple geographic rate zones, this takes time and creates error risk.</p><p>The question to ask your billing system: does it update NDIS pricing automatically when the NDIA publishes the new PAPL? Or does someone in your organisation have to manually update rates?</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS billing</a> that integrates with current pricing and updates rates automatically means the first billing run of the new financial year goes out at the correct 2026–27 rates without manual intervention. CTARS integrates directly with <a href="https://www.xero.com/au/">Xero</a> and <a href="https://www.myob.com/au">MYOB</a> so financial records reflect updated rates automatically.</p><h4>Step 4: Update worker qualification-to-billing-code mappings</h4><p>Indexation is calculated from Fair Work Commission SCHADS Award movements, superannuation guarantee changes, and the NDIA’s cost-model inputs.</p><p>The rate a worker can bill under is determined by their qualification level. An OT bills at a different rate than a support worker. A specialist support coordinator bills at a different rate than a standard support coordinator. When the pricing changes, the rate for each qualification level changes. If your system maps worker qualifications to billing codes, those mappings need to reflect the new rates.</p><p>This is especially important for allied health providers following the national standardisation changes from 2025–26. The rate for an OT at one qualification level in Victoria is now the same as in Queensland, but the code needs to be correct for the national rate to apply.</p><p>Your worker profiles in a connected <a href="https://ctars.com.au/ndis-client-management-software/">client management system</a> should hold the qualification level and map it to the correct billing code automatically. When the new pricing drops, you update the rate in the configuration and it flows through to every worker at that qualification level.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au.</strong></a> See how automatic pricing updates, service agreement management, and worker qualification mapping work in one connected system. No credit card.</p><h4>Step 5: Notify participants of the rate change before July 1</h4><p>When prices change, participants have a right to know before the new rate is charged to their plan. The notification requirement is not just a courtesy. It is a consent and transparency obligation under the NDIS Terms of Business.</p><p>For plan-managed participants, the plan manager will manage the rate change from their side. But the service agreement between the provider and the participant still needs to reflect the new rate before the first invoice at the new rate is submitted.</p><p>For NDIA-managed participants, the new rate flows through the portal automatically from 1 July. But your service agreement still needs to be updated to reflect the changed rate.</p><p>Participant notification does not need to be a formal legal letter. A clear written communication — email or letter — explaining that NDIS pricing has changed from 1 July, what the new rate will be for their supports, and that their plan manager or NDIA will apply the new rate automatically is sufficient. It becomes the consent record you attach to the updated service agreement.</p><h4>Step 6: Check the new PAPL the day it is published and compare it to what you expected</h4><p>When the 2026–27 PAPL is published in late June, the comparison exercise matters.</p><p>The NDIS Price Guide, now officially called the NDIS Support Catalogue sets the maximum prices that registered NDIS providers can charge for funded supports.</p><p>Check every support type you deliver against the new PAPL. Not just the standard support hourly rate. The cancellation rules. The travel billing provisions. The non-face-to-face rules for allied health. The group support billing codes. Any of these can change independently of the headline rate increase.</p><p>The official <a href="https://www.ndis.gov.au/providers/pricing-arrangements">NDIS Pricing Arrangements</a> page is where the new document will appear. Bookmark it. Check it the day it is published. Compare it section by section against the current document if you can. Or compare it against your current billing configuration to identify any codes that changed.</p><p>Providers who discover a mid-year pricing change three months after it took effect have been billing at the wrong rate for three months. The digital payment system now being rolled out will catch these discrepancies faster than ever before.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how connected systems make annual pricing updates a routine event rather than a scramble.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.</p><p>See the <a href="https://ctars.com.au/product-tour/">product tour</a> to understand how automatic pricing updates work. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>The 2026–27 pricing is coming in three weeks. The providers who are ready on July 1 are the ones who prepared in June.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au.</strong> </a>Full platform with automatic pricing updates. Be ready for July 1 before June ends. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong></a> Talk to someone who can walk you through the July 1 pricing update process inside CTARS and what your preparation checklist looks like.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If your billing system requires manual rate updates every July and it is already mid-June, share this with your billing coordinator and operations lead today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33047618dde0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NDIS Complaints Management Is One of the Most Commonly Failed Audit Requirements: Here Is Why]]></title>
            <link>https://medium.com/@ctars/ndis-complaints-management-is-one-of-the-most-commonly-failed-audit-requirements-here-is-why-48902a56cba0?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/48902a56cba0</guid>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[document-management]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 06:32:54 GMT</pubDate>
            <atom:updated>2026-06-15T06:32:54.204Z</atom:updated>
            <content:encoded><![CDATA[<p>Complaints management under Module 2B of the NDIS Practice Standards is one of the most frequently cited gaps in provider compliance assessments. Auditors check your policy, interview your staff, and examine your complaint records. If any element is missing or incomplete, you risk a non-conformity finding. This is a plain-language guide to what a functioning complaints system actually requires — and what most providers are getting wrong.</p><p>Most NDIS providers have a complaints policy.</p><p>Most of those policies are not a complaints management system.</p><p>The distinction matters because Module 2B of the <a href="https://www.ndiscommission.gov.au/providers/ndis-practice-standards">NDIS Practice Standards</a> requires a complaints management and resolution system. Not a policy document. A system. One that receives complaints, records them, investigates them, resolves them, notifies the complainant of the outcome, and uses the learning from complaints to improve practice.</p><p>A four-page policy in a folder satisfies none of those requirements. What satisfies them is evidence that each of those things actually happened for each complaint your organisation received.</p><h4>What Module 2B actually requires?</h4><p>The complaints management requirements under Module 2B apply to all registered providers delivering supports other than specialist disability accommodation.</p><p>The standard requires that providers have a system that is accessible to participants. Accessible means participants know it exists, know how to use it, and are not discouraged from using it. A provider who makes the complaints process difficult to find, or who responds to complaints in ways that discourage participants from raising further concerns, is in breach regardless of what the policy says.</p><p>It requires that complaints are recorded. Every complaint, regardless of how minor it seems, needs a record. The date it was received. Who made it. What it was about. What happened in response. What the outcome was. What the complainant was told.</p><p>It requires that complainants are informed of the outcome and of their right to escalate to the <a href="https://www.ndiscommission.gov.au/complaints/make-complaint-about-provider-or-worker">NDIS Commission</a> if they are not satisfied.</p><p>And it requires that complaints feed into the organisation’s continuous improvement system. The data from complaints should drive meaningful changes to practice.</p><p>That last requirement is the one most providers miss. A complaint is recorded and resolved. The file is closed. No connection is made to any change in practice. An auditor reviewing the complaint file will ask: what changed as a result of this complaint? If the answer is nothing, that is a continuous improvement gap.</p><h4>What auditors are actually checking?</h4><p>Auditors assess Module 2B by reviewing your policy, interviewing staff, and examining complaint records.</p><p>The staff interview question matters more than most providers realise. A worker asked “what would you do if a participant told you they were unhappy with their support?” should be able to describe the complaints process clearly. Not the policy. The process. Who do they tell? How does the participant make a formal complaint if they want to? What happens after that?</p><p>If workers cannot answer these questions, it signals that training has not been embedded, even if the policy was signed at induction. This is consistently one of the most frequently cited gaps in NDIS provider compliance assessments. Not a missing policy. Workers who do not know the process.</p><p>The complaint records examination is the third component. Auditors look for:</p><p>Complaints that have no resolution record. A complaint received and then no follow-up. That is a gap.</p><p>Complaints that were resolved but the complainant was not informed. Another gap.</p><p>Complaint data that shows no connection to any improvement action. The system is recording but not learning. Another gap.</p><p>And critically: patterns of complaints about the same issue. A provider who has received three complaints about the same worker’s conduct, each resolved individually, but with no investigation into whether there is a systemic issue, has failed the continuous improvement obligation.</p><p>Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> should hold complaint records against the relevant participant or worker profile, with a complete record from receipt through to resolution and improvement action. Not in a separate complaints spreadsheet that nobody links to participant records.</p><h4>The continuous improvement connection:</h4><p>The NDIS Practice Standards explicitly require providers to demonstrate continuous improvement. Sources of improvement data include incident trends, complaint analysis, worker feedback, participant surveys, and audit findings.</p><p>For complaints specifically, the requirement is that complaint data drives meaningful changes to practice. Providers who document their improvement journey — including what prompted each change, what was done, and what the outcome was — give auditors compelling evidence of a mature compliance culture.</p><p>What this means operationally: every resolved complaint should have a linked improvement action. Even if the improvement action is “no systemic issue identified, individual worker briefed.” That four-word note demonstrates that someone reviewed the complaint for broader implications and made a considered decision.</p><p>A complaint about a worker arriving late twice should produce: a resolved complaint record, a worker briefing note, and a review note determining whether the lateness was isolated or reflects a rostering or supervision issue. Three records. Linked. Demonstrating that the complaint informed practice, not just an apology.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> that links complaint records to improvement actions — and holds both against the relevant profile — means the continuous improvement requirement is visible in the records rather than asserted in the policy.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au</strong></a><strong>.</strong> See how complaint records, improvement actions, and practice standards evidence work in a connected system. No credit card.</p><h4>What providers cannot do:</h4><p>Providers cannot prevent, discourage, or obstruct a person from making a complaint. This is a serious breach. Doing so is not just a Module 2B failure. It is a potential Code of Conduct violation.</p><p>In practice, discouragement can be subtle. A manager who responds to a participant’s verbal concern by explaining why the concern is not valid, without offering to record a formal complaint, may be inadvertently discouraging the process. A worker who tells a participant “I will sort this out, you do not need to put in a formal complaint” is doing the same thing.</p><p>All providers, registered and unregistered, must comply with the obligation not to obstruct complaints. The April 2026 NDIS Amendment Act expanded the Commission’s powers to detect this kind of conduct. Participants can complain directly to the <a href="https://www.ndiscommission.gov.au/complaints/make-complaint-about-provider-or-worker">NDIS Commission</a> at any time. A provider who has been discouraging formal complaints may have no record of the issues the Commission has already been informed about.</p><h4>What a functioning complaints system looks like:</h4><p>Participants know how to make a complaint and are told about the process at intake and in the service agreement. Every complaint is recorded with date, description, and the complainant’s details. Investigation steps are documented. The outcome is communicated to the complainant in writing. The right to escalate to the Commission is provided. Improvement actions are linked to the complaint record. The complaint data is reviewed periodically for patterns.</p><p>That is the system the <a href="https://www.ndiscommission.gov.au/sites/default/files/2024-09/complainthandlingguidelinesforproviders_0.pdf">NDIS Commission’s complaints handling guidelines</a> require. It is also the system that, when it works properly, makes your service better. Complaints are participants telling you something is not meeting their standard. Organisations that treat that information as operational intelligence rather than administrative burden improve faster than those that treat it as a compliance checkbox.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> that holds complaints records, resolution notes, complainant notifications, and improvement actions in a structured, retrievable format means this system is not an annual exercise before an audit. It is how your organisation processes feedback every time a participant has a concern.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how structured systems produce the continuous improvement evidence Module 2B requires.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.</p><p>See how it works on the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>A complaint is a participant telling you something that needs to improve. Your records need to show you heard them and did something about it.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au</strong></a><strong>.</strong> Full platform. Complaint records, improvement actions, and continuous improvement evidence in one system. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo</strong></a><strong>.</strong> Talk to someone who understands what Module 2B requires and how CTARS supports a functioning complaints management system.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If your last complaint was resolved with an apology and no linked improvement action, share this with your quality lead today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48902a56cba0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What NDIS Duty of Care Actually Requires, Not the Policy Version. The Daily Operations Version]]></title>
            <link>https://medium.com/@ctars/what-ndis-duty-of-care-actually-requires-not-the-policy-version-the-daily-operations-version-84bb4c10ed82?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/84bb4c10ed82</guid>
            <category><![CDATA[ndis-service-providers]]></category>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[incident-management]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 06:53:19 GMT</pubDate>
            <atom:updated>2026-06-12T06:53:19.332Z</atom:updated>
            <content:encoded><![CDATA[<p>Duty of care in the NDIS is a legal and ethical obligation placed on providers to take reasonable steps to prevent foreseeable harm to participants. The April 2026 amendments expanded the Commission’s powers specifically to respond to breaches of these obligations. This is not a policy guide. It is a plain-language explanation of what duty of care requires at each moment of a participant’s day, and how records demonstrate it is being met.</p><p>Every NDIS provider understands duty of care in principle.</p><p>You are responsible for the safety of the people you support. You take reasonable steps to prevent harm. You act professionally and ethically. You train your workers. You follow the right procedures.</p><p>Most providers understand this. But understanding it and demonstrating it continuously are two different things.</p><p>The April 2026 NDIS Amendment Act expanded the Commission’s powers to detect, prevent and respond to breaches of provider obligations. The Commission is moving from a reactive model — responding to complaints — to a proactive intelligence-led model that looks for patterns. A provider whose records consistently show the right things happening at the right times is a provider the Commission’s monitoring passes over. A provider whose records have gaps, inconsistencies, or patterns that suggest obligations are not being met is a provider that attracts attention.</p><p>Duty of care is demonstrated through records. Not through policies. Through what your records show happened, when it happened, and who was responsible.</p><p>Here is what that looks like across a participant’s day.</p><h3>Before the session: preparation demonstrates duty of care</h3><p>Duty of care begins before a worker arrives at a participant’s property.</p><p>A worker who knows nothing about a participant’s support needs, health conditions, or communication preferences before their first session is a compliance risk. Not because the worker is irresponsible. Because the organisation did not give them the information they needed to deliver support safely.</p><p>Delivering services safely and competently means ensuring supports are provided by suitably trained, qualified, and supervised staff who know what they are walking into.</p><p>What duty of care requires here: a current, detailed participant profile that workers can access before each session. Medication information. Behavioural support plans. Communication preferences. Known risks. Recent incident history.</p><p>What records demonstrate it: worker access logs showing the worker viewed the participant profile before the session. Notes from a briefing or handover if the participant had a recent health change. A training record showing the worker was trained on the participant’s specific support needs.</p><p>Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> should hold all of this against the participant’s profile and show worker access from a phone before the session begins.</p><h3>During the session: observation and response demonstrates duty of care</h3><p>Duty of care during a session is not about surveillance. It is about the worker being present, attentive, and responsive to what they observe.</p><p>A worker who notices a participant seems confused or is showing signs of physical distress and does not act is failing a duty of care obligation — even if nothing bad happens as a result of that session.</p><p>Acting professionally and ethically at all times means respecting participant dignity, privacy, consent, and rights in every interaction.</p><p>What duty of care requires here: workers who observe unusual behaviour, physical concerns, or environmental risks flag them immediately and appropriately. Observations are recorded in progress notes, not held in the worker’s memory for later.</p><p>What records demonstrate it: a progress note that includes observations about the participant’s presentation, any concerns raised, and any actions taken. A note that says “standard session delivered” without any observation of how the participant actually presented tells the Commission nothing about whether duty of care was exercised during that session.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> that structures progress notes to include participant presentation and any concerns observed means the duty of care record is built during the session, not reconstructed afterwards.</p><h3>When something goes wrong: incident response demonstrates duty of care</h3><p>Duty of care is most visibly tested when something goes wrong.</p><p>A participant falls. A worker observes signs of neglect or abuse. A medication error occurs. A participant becomes distressed and the situation escalates.</p><p>In each of these moments, duty of care requires that the worker responds appropriately, documents what happened immediately, and escalates through the correct channels.</p><p>What duty of care requires here: an incident record created at the time of the event, not the following day. A timestamped record that shows the worker acted promptly. Escalation to the coordinator within a timeframe consistent with the seriousness of the incident. Notification to the <a href="https://www.ndiscommission.gov.au/rules-and-standards/managing-and-reporting-incidents">NDIS Commission</a> where the incident is reportable, within the required timeframe.</p><p>What records demonstrate it: the incident record timestamp. The escalation log. The Commission notification with its submission timestamp. The corrective action documented against the incident record.</p><p>A provider whose incident records show consistent same-day logging, clear escalation trails, and timely Commission notifications is demonstrating duty of care under the Commission’s new intelligence-led monitoring model. A provider whose incidents are logged days after the event, without escalation notes, is demonstrating the opposite.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Incident management</a> accessible from a worker’s phone means the timestamp on the incident record reflects when it actually happened.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au.</strong></a> See how pre-session profiles, progress note observation fields, and incident management work in one connected system. No credit card.</p><h3>After the session, documentation is the duty of care record</h3><p>After the worker leaves, the session becomes a record. And the record is what the Commission, the participant, and any future audit will rely on.</p><p>A progress note written from memory two days after a session is not a duty of care record. It is a reconstruction. The distinction matters because the Commission’s proactive monitoring model looks at documentation patterns. Consistent same-day or same-shift notes are a different pattern to notes logged in batches three days later.</p><p>What duty of care requires here: progress notes submitted at the time of the session or within the same shift. Notes that reflect what actually happened, what was observed, and what the participant’s presentation was.</p><p>What records demonstrate it: note timestamps that fall within the session delivery window. Note content that is specific to the participant, not generic. A documentation pattern that is consistent across the plan period.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> within a purpose-built system that workers access from their phone at the end of each session means the documentation pattern is clean as a matter of course.</p><h3>Between sessions: monitoring demonstrates ongoing duty of care</h3><p>Duty of care does not pause between sessions.</p><p>A coordinator who notices a participant’s support hours are being underutilised, who sees an incident pattern emerging, or who identifies that a participant’s goals have not been updated since a significant life change has an obligation to act on those observations.</p><p>Protecting participants from harm includes identifying risks before they become incidents. The Commission’s proactive model is specifically designed to catch providers who are reactive rather than vigilant.</p><p>What duty of care requires here: regular review of participant records for patterns that require attention. Budget utilisation reviews that identify whether a participant is receiving the support their plan funds. Goal reviews that ensure the plan still reflects the participant’s current circumstances.</p><p>What records demonstrate it: coordinator review notes. Goal review records. Budget monitoring logs. Evidence that changes in a participant’s situation triggered a support plan review.</p><p>A connected <a href="https://ctars.com.au/ndis-client-management-software/">client management system</a> that surfaces participant alerts — period balance approaching limit, goal overdue for review, incident pattern flagged — means the monitoring is systematic rather than dependent on whoever happens to notice something on a given day.</p><h3>What the 2026 amendments changed</h3><p>The April 2026 NDIS Amendment Act is now in force. It expanded the Commission’s powers to detect, prevent and respond to breaches of obligations. It confirmed that all providers, registered or not, must comply with the Code of Conduct and duty of care obligations.</p><p>The records standard has not changed. The Commission’s ability to detect whether those records meet the standard has improved significantly.</p><p>For providers who have been meeting their duty of care obligations but not documenting them consistently, this is the year to close that gap. The obligation you are meeting in practice needs to be visible in your records.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how structured systems produce the documentation that demonstrates duty of care across every session, every participant, every day.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.</p><p>See it on the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>Duty of care is not demonstrated by your policies. It is demonstrated by what your records show happened, every day, for every participant.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au.</strong></a> Full platform. Every duty of care moment documented through daily operations. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong></a> Talk to someone who understands what duty of care looks like operationally and how CTARS records demonstrate it across every participant interaction.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If the Commission asked for duty of care evidence for three random participants tomorrow, share this with your team and ask whether your records would answer the question.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84bb4c10ed82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI and NDIS Documentation: What Your Organisation Needs to Understand Before It Creates a Problem]]></title>
            <link>https://medium.com/@ctars/ai-and-ndis-documentation-what-your-organisation-needs-to-understand-before-it-creates-a-problem-185e306f26ef?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/185e306f26ef</guid>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 06:21:20 GMT</pubDate>
            <atom:updated>2026-06-11T06:21:20.276Z</atom:updated>
            <content:encoded><![CDATA[<p>The NDIS Quality and Safeguards Commission issued an AI transparency statement in February 2026. The NDIA has become more alert to AI-generated allied health reports as part of its fraud detection and assurance work. AI-generated documents presented as a clinician’s professional opinion without adequate review could be characterised as misleading conduct. This is a plain-language guide to what AI means for NDIS providers right now — what helps, what risks, and what your organisation needs to have in place.</p><p>AI tools are being used inside NDIS services right now.</p><p>Voice-to-text apps transcribing session notes. Scheduling platforms with intelligent rostering suggestions. Documentation tools that rephrase or summarise progress notes. Report templates that generate structured clinical language from bullet point inputs.</p><p>Most of these tools are genuinely useful. Some of them are creating compliance problems providers do not realise they have. And the February 2026 NDIS Commission AI transparency statement means the regulatory environment has caught up with the technology faster than most providers expected.</p><p>Here is what you need to understand.</p><h4>What the Commission actually said in February 2026?</h4><p>The NDIS Quality and Safeguards Commission issued an AI transparency statement in February 2026. It was the first formal signal that the Commission is paying attention to how AI is being used in NDIS-funded services.</p><p>The statement signalled growing scrutiny of AI use in participant documentation, clinical records, and service delivery. It did not ban AI tools. It established that the professional and organisational accountability for documentation is not transferred to the AI tool that helped produce it.</p><p>That distinction matters operationally. If your support worker uses a voice-to-text tool to transcribe their progress notes, that is helpful and the accountability remains with the worker who reviewed and submitted the note. If your allied health professional submits an AI-generated functional capacity assessment without substantive clinical review, that document carries their professional registration number and their legal accountability regardless of how it was produced.</p><p>The NDIS Code of Conduct obligations of honesty, integrity, transparency, and acting with care apply directly to clinical documentation. A letter or report presented as the clinician’s professional opinion but substantively AI-generated, without adequate review, could be characterised as misleading conduct. That is true even if the document is factually correct.</p><p>Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> is where your documentation lives. Whatever AI tools your workers use to draft notes, the final record in the system carries your organisation’s compliance accountability.</p><h4>What the NDIA is detecting?</h4><p>The NDIA has become noticeably more alert to AI-generated allied health reports as part of its fraud detection and assurance work.</p><p>The specific concern is not that AI was used. It is that AI-generated documents often read as templated output — generic clinical reasoning, recycled phrasing, conclusions that do not specifically reflect the individual participant. Documents that read this way carry audit and reputational risk even when the underlying clinical view is sound.</p><p>For functional capacity assessments, progress reports, and plan review supporting evidence, the NDIA is looking for documentation that demonstrates genuine clinical reasoning about a specific person. A report that could plausibly describe any participant with a similar diagnosis does not satisfy that standard, regardless of what tool produced it.</p><p>This is also relevant to the I-CAN support needs assessment model rolling out from 2027. For many people with disability, automation tends to work best for average cases and disability is rarely average. The assessments that produce the best outcomes for participants will be those grounded in specific, individual, clearly reasoned documentation from the providers who actually know them.</p><p>The implication for providers is this: AI can help workers find the right words. It cannot replace the specific clinical observation that gives those words credibility.</p><h4>The difference between AI that helps and AI that risks:</h4><p>This is the practical question most providers have not yet answered clearly.</p><p>AI tools that reduce administrative friction without replacing professional judgment are genuinely useful. Voice-to-text reduces the time it takes to log a progress note. Intelligent spell-check and grammar assistance makes notes more readable. Smart prompts that remind workers to include goal references or functional observations improve documentation quality without replacing clinical thinking.</p><p>These tools work because they help the worker record something they actually observed and thought. The clinical content is still the worker’s. The AI made it faster or clearer to express.</p><p>AI tools that generate documentation from minimal input and present it as clinical evidence are different. A tool that takes a few bullet points and produces a full functional capacity assessment without the clinician substantively reviewing and revising every clinical claim is a tool that has replaced professional judgment rather than supported it.</p><p>The NDIS sector does not need more AI hype. It needs working tools that reduce admin load without introducing new risk. That is the benchmark.</p><p>Purpose-built <a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> uses structured templates and prompts that help workers document more completely and consistently. That is the kind of AI-adjacent assistance that improves records without creating accountability gaps. The worker still writes the note. The template structure ensures it captures what matters.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au.</strong></a> See how structured note templates improve documentation quality without replacing worker judgment. No credit card required.</p><h4>What your organisation needs to have in place right now?</h4><p>The Commission’s AI transparency statement creates three practical obligations for NDIS providers.</p><p>The first is an AI use policy. If any workers in your organisation are using AI tools to assist with documentation, your organisation needs a policy that covers which tools are permitted, what review process applies before AI-assisted documentation is submitted, and who holds accountability for the final record.</p><p>This does not need to be a lengthy document. It needs to be clear about one thing: no AI-generated document is submitted as clinical or professional output without substantive human review by the accountable person.</p><p>The second is worker awareness. Workers who are using voice-to-text, smart note apps, or AI writing tools need to understand that the professional accountability for what they submit rests with them, not with the tool. A progress note submitted with a single tap after AI generation without review is still a progress note that carries that worker’s accountability under the <a href="https://www.ndiscommission.gov.au/rules-and-standards/ndis-code-conduct">NDIS Code of Conduct.</a></p><p>The third is record integrity. Your <a href="https://ctars.com.au/ndis-client-management-software/">document management software</a> should be the single authoritative source for participant records. Any AI-assisted documentation that enters the system should do so through the same structured workflow as any other record — timestamped, attributed to the responsible worker, and stored against the correct participant profile.</p><h4>The AI-enabled assistive technology framework:</h4><p>In February 2026, the NDIA released a new framework for AI-enabled Assistive Technology, developed by CSIRO’s Australian eHealth Research Centre. The framework establishes six key principles for safe and effective AI-enabled AT and was informed by interviews with participants, families, carers, and service providers.</p><p>This framework is specifically about assistive technology used by participants, not about provider operations tools. But it signals the direction the NDIA is taking on AI generally: principle-based, participant-centred, and accountability-preserving.</p><p>For providers evaluating any AI tool, the same principles apply: is the tool transparent about what it produces? Does it preserve human accountability for the outcome? Does it handle participant information consistently with Australian Privacy principles?</p><p>The <a href="https://www.oaic.gov.au/privacy/the-privacy-act">Australian Privacy Act</a> requires that personal information is handled appropriately regardless of what tools were used in its processing. Participant data fed into a third-party AI tool may be subject to overseas data handling rules depending on where that tool’s servers are located.</p><p>CTARS is ISO 27001 certified with all data stored on Australian servers. Any AI functionality within or connected to your client management system should meet the same standard for data sovereignty and security.</p><h4>What this means practically?</h4><p>AI in NDIS provider operations is not going away. The tools will get better. The question is not whether to use them but how to use them without creating documentation integrity problems.</p><p>The providers who navigate this well are the ones who establish clear policies now, before a Commission inquiry or an NDIA audit question forces the issue. The providers who will struggle are the ones who let workers use whatever tools they find helpful without organisational oversight of what those tools are producing.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how structured documentation systems maintain record integrity through any tool changes your workers make.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians who understood documentation accountability before AI tools existed.</p><p>See how structured documentation works on the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>AI tools can make your workers faster. They cannot take on your organisation’s accountability. Make sure your policies reflect that clearly.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au.</strong></a> Full platform. Structured documentation that maintains accountability regardless of how notes are drafted. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo</strong></a><strong>.</strong> Talk to someone who understands how AI tools interact with NDIS documentation accountability and what your organisation needs to have in place.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If any of your workers are currently using AI tools to help write progress notes or clinical reports, share this with your clinical lead and compliance manager before your next team meeting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=185e306f26ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What a Well-Run NDIS Service Actually Looks Like on an Ordinary Wednesday in 2026]]></title>
            <link>https://medium.com/@ctars/what-a-well-run-ndis-service-actually-looks-like-on-an-ordinary-wednesday-in-2026-b0d8ba6eadd5?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0d8ba6eadd5</guid>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 05:09:49 GMT</pubDate>
            <atom:updated>2026-06-10T05:09:49.619Z</atom:updated>
            <content:encoded><![CDATA[<p>More than two-thirds of NDIS providers are operating at a loss. The providers who are profitable and growing in 2026 are not doing extraordinary things. They are doing ordinary things extremely well, through systems that make the ordinary things the easiest things. This is a portrait of what that looks like.</p><p>Wednesday, 8:40 am. A disability support coordinator opens her laptop. She has seventeen participants on her caseload. Before she takes her first call, she checks the dashboard.</p><p>Three things catch her eye.</p><p>One participant’s funding period balance is at 78 percent of his quarterly limit with 11 days left in the period. She sends a quick message to his plan manager to flag it before any more sessions are scheduled.</p><p>One worker’s police clearance expires in 19 days. She creates a task to follow up. It takes forty seconds.</p><p>One participant has a plan review in six weeks. Three months of structured progress notes are already built in the system. The review preparation will take a few hours, not a week.</p><p>By 9 am, she is on her first call.</p><p>This is what a well-run NDIS service looks like on an ordinary Wednesday.</p><h4>The intake that takes 20 minutes, not two days:</h4><p>At 10:30 am, a new referral arrives. A community visitor has referred a participant with autism and complex daily living support needs. The coordinator opens the participant management module.</p><p>She creates the profile. She enters the current plan details, funded support categories, period limits, and budget totals. She uploads the plan as a document attached to the profile. She assigns two workers from the rostered team and flags their profiles so they can see the participant record before the first session.</p><p>A service agreement template generates from the system. She reviews it, adjusts the rate for the correct support category, and sends it for digital signature.</p><p>By 11 am, the new participant is onboarded. The workers have access to the full profile. Nothing is in an email thread. Nothing is in a shared folder. Nothing depends on the coordinator remembering to brief someone.</p><p>The <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> did not make the coordinator work faster. It made the work happen in the right place the first time so it did not need to be done again later.</p><h4>The billing run that takes 45 minutes:</h4><p>At 1pm, the billing coordinator starts the fortnightly billing run.</p><p>Every session delivered in the past two weeks was logged by workers at the time of delivery, from their phones, with the correct support type selected. The system mapped each session to the correct <a href="https://www.ndis.gov.au/providers/pricing-arrangements">NDIS Pricing Arrangements</a> item code automatically. Travel claims were generated at 50 percent with separate line items where applicable.</p><p>She reviews the billing run summary. One session is flagged — a worker selected a weekend rate for a shift that crossed midnight on a Friday. She corrects it in two minutes. Everything else is clean.</p><p>Claims go out at 1:45 pm. The plan manager for three of the participants will process invoices within three to five business days. NDIA portal claims will batch within 48 hours.</p><p>When payments arrive, they will post automatically to the organisation’s accounts in <a href="https://www.xero.com/au/">Xero</a>. No manual reconciliation. No Friday afternoon matching exercise.</p><p>The billing coordinator is done with the billing run before 2 pm. She spends the rest of the afternoon on three participant reviews.</p><p>This is not a small organisation with unusually simple billing. This is a 35-participant service delivering core supports, community access, and support coordination across two postcodes. The billing takes 45 minutes because <a href="https://ctars.com.au/ndis-client-management-software/">NDIS billing</a> is structured around session delivery, not around manual reconstruction.</p><h4>The incident that was managed before lunch:</h4><p>At 11:15 am, a support worker called in to report that a participant had a fall during a community access session. The worker logged the incident from her phone while still at the location. It was timestamped at 11:17 am, attached to the participant’s profile, and flagged to the coordinator.</p><p>The coordinator reviewed it by 11:30 am. The incident was classified. The follow-up action was assigned. The Commission notification pathway was initiated for a reportable incident under the <a href="https://www.ndiscommission.gov.au/rules-and-standards/managing-and-reporting-incidents">NDIS Commission’s reportable incidents framework</a>.</p><p>By 3 pm, the initial notification was submitted. The participant’s family had been contacted. The corrective action for the session environment had been documented against the incident record.</p><p>If an auditor asked for this incident record in six months, it would take under a minute to retrieve. Timestamped, complete, resolved, with the corrective action documented. That is what continuous compliance looks like in a <a href="https://ctars.com.au/ndis-client-management-software/">client management system</a> that treats incident management as a daily operational function rather than a periodic compliance project.</p><h4>The plan review that was ready before the meeting:</h4><p>At 3 pm, the coordinator opens the plan review preparation for the participant whose review is in six weeks.</p><p>She pulls the goal summary report. Twelve months of progress notes, structured against four goals. Each note shows what the participant was working on, what changed in the session, and what they can do now that they could not do six months ago.</p><p>The evidence of functional progress is there. Not because anyone assembled it for the review. Because it was built session by session through a note template that prompted workers to capture it that way.</p><p>She writes the review summary in 90 minutes. It reflects a real picture of the participant’s year. Specific progress. Specific remaining needs. Specific recommendations for the next plan.</p><p>She sends it to the participant’s support coordinator.</p><p>Providers who achieve an average 156 percent ROI on their technology investments do not achieve it through a single dramatic efficiency gain. They achieve it through dozens of small frictions removed simultaneously. The billing that takes 45 minutes instead of two days. The incident response that is complete by afternoon. The plan review that is 90 minutes instead of three days. Every one of those time savings adds up to a direct financial return.</p><h4>What made this Wednesday possible?</h4><p>Nothing exceptional happened today. No special preparation. No audit coming. No crisis driving efficiency.</p><p>The coordinator checked the dashboard and caught two risks before they became problems. The billing ran cleanly because session records were complete. The incident was handled promptly because the tool was on the worker’s phone. The plan review will be ready in six weeks because the evidence was being built for the full twelve months that preceded it.</p><p>Competitive advantage will increasingly favour organisations that invest early in governance, workforce capability, and technology-enabled delivery. That is true. But the advantage is not strategic in the boardroom sense. It is operational. It is Wednesday at 8:40am and knowing what your team needs to do before the first call.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> built around the daily rhythm of disability support delivery — not bolted onto a generic platform — is what makes this Wednesday possible for providers who have built it, and unavailable for providers who have not.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how connected systems produce the evidence that this Wednesday generates as a matter of course.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Used for over 6,000 clients nationally.</p><p>See how the Wednesday dashboard works on the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service size.</p><p><strong>This Wednesday is available to every NDIS provider. The question is what it takes to build it.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au</strong></a><strong>.</strong> Run your own Wednesday on real sample data. See what the dashboard shows when the records are right. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong></a> Walk through an ordinary Wednesday inside CTARS. See what your team’s day could look like.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If your Wednesday looks different from the one described here, share this with your operations lead and ask which part you want to fix first.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0d8ba6eadd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Before You Sign Up for Any NDIS Software, Five Questions That Expose What You Are Actually Getting]]></title>
            <link>https://medium.com/@ctars/before-you-sign-up-for-any-ndis-software-five-questions-that-expose-what-you-are-actually-getting-8c81e8922707?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c81e8922707</guid>
            <category><![CDATA[ndis-service-providers]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[cloud-management]]></category>
            <category><![CDATA[document-management]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 05:46:30 GMT</pubDate>
            <atom:updated>2026-06-09T05:46:30.155Z</atom:updated>
            <content:encoded><![CDATA[<p>As of March 2026, the NDIS supports over 630,000 participants across Australia. The Commission’s audit activity has increased sharply. Manual compliance tracking is unsustainable for most providers. And the software market is crowded with platforms that look similar in a demo but operate very differently in practice. These five questions will tell you more about a platform than a 30-minute product tour ever will.</p><p>Every NDIS software demo looks good.</p><p>The presenter knows the platform. The data is clean. The billing run in the demo takes four minutes. The incident gets logged in thirty seconds. Everything works smoothly because it was designed to work smoothly in that specific controlled context.</p><p>Then you go live. And you find out what the demo did not show you.</p><p>The session note that takes fourteen minutes because the mobile interface is clunky. The billing error that cannot be traced because the session log and the financial record are in different systems. The audit request that takes three days to respond to because nobody indexed the records properly.</p><p>The gap between demo quality and operational quality is where most software purchasing mistakes live. The five questions below are designed to close that gap before you sign anything.</p><h4>Question 1: Show me what happens when a billing claim is rejected</h4><p>Not describe it. Show you.</p><p>Ask the presenter to demonstrate, in the live system, what happens when the NDIA portal returns a rejection on a specific claim. Where does the rejection appear? How does the billing administrator find out? What are the exact steps to identify the error, correct it, and resubmit?</p><p>This matters because manual compliance tracking has become unsustainable for most providers and payment rejection rates for manual NDIS billing averaged 14 percent in 2025. A platform that handles rejections smoothly is a different operational experience from one that sends an email notification and leaves the rest to the billing admin.</p><p>A good answer looks like: the rejected claim surfaces in the billing dashboard with the specific error identified, the correction can be made without rebuilding the entire submission, and the corrected claim can be resubmitted in under five minutes.</p><p>A red flag answer looks like: “we send you a notification and you can then re-enter the claim.” That is the process you already have. You are not buying a process. You are buying something better than the process you already have.</p><p>Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> should make the rejection-to-resubmission cycle a 5-minute task. Not a 45-minute one.</p><h4>Question 2: Show me a worker note submitted at 9 pmon a phone with two bars of mobile signal</h4><p>This is the real-world test that most demos never run.</p><p>Ask the presenter to open the platform on a mobile phone in the demo room, not on a desktop with a full keyboard. Ask them to log a progress note as a support worker would at the end of a shift. On the phone. In the session note template. With goal selection and submission both included.</p><p>Watch how many steps it takes. Watch whether the worker needs to navigate away from the note to find the participant’s goals. Watch whether the note template is optimised for mobile or whether it is a desktop form squeezed into a small screen.</p><p>This matters because incident management and rostering are the two features that have the most impact on daily operations, followed by participant management and NDIS claiming. Workers who cannot submit quality notes from their phone at the end of a shift will not submit quality notes. They will write something brief from memory later. That brief note becomes your plan review evidence. That plan review evidence determines your participant’s next budget.</p><p>If the mobile experience is genuinely good, the presenter will not hesitate to demonstrate it. If they redirect to the desktop, you have your answer.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> built mobile-first means the session note a worker submits at 9pm from a regional property is as structured and complete as one submitted from a desktop at 9am.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au.</strong></a> Test the mobile note experience yourself on real sample data. No credit card required.</p><h4>Question 3: Show me the billing for a Saturday SIL sleepover with travel</h4><p>This is the technical depth test.</p><p>SIL billing involves multiple shift types at different rates. A Saturday sleepover is a specific billing scenario with its own line item, its own rate, and its own rules. If the platform cannot handle this correctly automatically, it cannot handle SIL correctly.</p><p>Ask the presenter to walk through how the platform bills a Saturday sleepover shift for a SIL participant, including any travel component. Ask which item codes it generates automatically and which require manual selection. Ask what happens when the shift crosses midnight into Sunday.</p><p>General rostering software does not understand SCHADS Award rates and generic invoicing tools cannot validate NDIS line items against the current Price Guide. A platform built specifically for NDIS has this mapped. A platform adapted from a generic tool will require manual selection at billing time.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS billing</a> that maps shift types to item codes automatically from session scheduling means the SIL Saturday sleepover generates the correct claim without a billing admin making decisions that should be made by the system. CTARS integrates directly with <a href="https://www.xero.com/au/">Xero</a> and <a href="https://www.myob.com/au">MYOB</a> so the financial records update automatically once the claim is processed.</p><h4>Question 4: Show me where participant data is stored and what the security certification is</h4><p>Every NDIS software platform says it is secure. Not every platform can prove it with a verifiable certification.</p><p>Ask directly: where is participant data physically stored and what is the security certification? Is the data stored in Australia? Can you show me the certification on a publicly verifiable register?</p><p>The <a href="https://www.oaic.gov.au/privacy/the-privacy-act">Australian Privacy Act</a> requires that personal information transferred overseas is protected to an equivalent standard. The NDIA’s own guidelines expect participant data to be stored and managed to an appropriate standard. A platform that cannot confirm Australian data storage or cannot point to a verifiable certification is a compliance risk you are taking on.</p><p>CTARS holds ISO 27001 certification which is the international information security management standard and is verifiable on the public JAS-ANZ register. All participant data is stored on Australian servers. The answer takes thirty seconds and points to a public register, not a marketing claim.</p><p>If the answer to this question is “our data is secure” without a verifiable certification or a specific server location, that is a gap worth noting.</p><h4>Question 5: What happens on 1 July when the NDIS pricing changes?</h4><p>This is the operational continuity test.</p><p>Ask the presenter what happens to your billing codes and rates on the day the new NDIS Pricing Arrangements and Price Limits come into effect each July. Do rates update automatically across all service types and worker qualification levels? Or does someone in your organisation need to update them manually?</p><p>The <a href="https://www.ndis.gov.au/providers/pricing-arrangements">NDIS Pricing Arrangements</a> are updated annually. Sometimes they change in July and again mid-year. Every time they change, every billing code that references an updated rate needs to be current before the first session of the new period is billed.</p><p>A platform where rates update automatically on the first day of the new pricing period means your billing admin does not need to manually update hundreds of rate configurations on 1 July. A platform where rates require manual updates means your billing admin is spending the first week of every financial year doing nothing but rate maintenance, and any session billed before the update is complete is billed at the wrong rate.</p><p>The answer to this question tells you a lot about whether the platform was built by people who understand how NDIS billing works in practice.</p><h4>The question you do not need to ask, but should think about</h4><p>Every platform on the market right now has a response to the 2026 reform environment. Mandatory registration expanding. Digital payment system rolling out. 90-day claims window from December.</p><p>Some platforms are genuinely built for what the NDIS requires in 2026. The NDIS regulatory environment in 2026 is going through its biggest transformation since the Commission was established in 2018. Some platforms are playing catch-up.</p><p>The question you should ask yourself after any demo is: did this platform feel like it was built for the sector it serves, or did it feel like a generic tool that has been adapted for NDIS? The difference shows up in the five questions above. It also shows up in the terminology the presenter uses, the specific compliance scenarios they can answer without looking anything up, and the speed with which they can demonstrate operations your team will run every week.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how connected systems produce the continuous compliance evidence the 2026 environment demands.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians who understood NDIS operations before they wrote a line of code.</p><p>See every one of these five questions answered on the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> for what fits your service.</p><p><strong>The demo is not the product. These five questions are.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au</strong></a><strong>.</strong> Test every one of these five scenarios on real sample data. No credit card required.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong></a> Ask us all five questions directly. See the answers in the live system. Bring your hardest scenario.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c81e8922707" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Most NDIS Providers Are Running a Risky Business Right Now, and What Actually Changes That]]></title>
            <link>https://medium.com/@ctars/why-most-ndis-providers-are-running-a-risky-business-right-now-and-what-actually-changes-that-d8ead00e8663?source=rss-ff4948cc3f90------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8ead00e8663</guid>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[document-management]]></category>
            <category><![CDATA[client-management]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[ndis-service-providers]]></category>
            <dc:creator><![CDATA[CTARS]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 06:06:52 GMT</pubDate>
            <atom:updated>2026-06-08T06:06:52.700Z</atom:updated>
            <content:encoded><![CDATA[<p>Nearly two-thirds of NDIS providers are not profitable. The 2026 reforms are cutting revenue in the social participation category while adding compliance costs. $45 million in Quality Supports Program grants is available for providers who meet the eligibility requirements. This is a plain-language business sustainability guide for NDIS provider directors who are thinking clearly about the next two years.</p><p>Running an NDIS service is not just clinical work. It is a business.</p><p>Most providers know this intellectually. Fewer treat it that way operationally. The evidence is in the numbers. Nearly two-thirds of NDIS providers are not profitable. Margins average around 2 percent across the sector. Staff turnover costs more than $50 million a year in direct onboarding expenses alone, before the indirect costs of continuity disruption.</p><p>The 2026 reform environment is not making this easier. Social participation budgets are being cut from October. Plan management revenue is being squeezed. Mandatory registration is adding compliance costs. And the digital payment system is closing the gaps that made it possible to sustain manual processes without immediate financial consequence.</p><p>But the providers who are building genuinely sustainable services in 2026 are doing something specific. They are treating financial sustainability as a systems problem, not a margin problem. Here is what that means.</p><h4>The quality revenue pipeline most providers are not accessing:</h4><p>The NDIA’s Quality Supports Program is distributing more than $45 million in grant funding to selected NDIS providers of therapy supports, supported independent living, and support coordination. Forty-four registered providers from across Australia are participating in the SIL pilot, sharing detailed financial and operational information with the NDIA as part of a quality evaluation.</p><p>That program rewards providers who can demonstrate quality outcomes, financial transparency, and operational rigour. Providers in the pilot share detailed financial and operational data. The NDIA uses that data to understand what quality service delivery actually costs and to inform future pricing decisions.</p><p>For providers who are not in the pilot, the lesson is directional. The government is moving toward a model where quality providers receive better pricing and funding access. The pathway to that model is demonstrable quality — structured outcome evidence, clean financials, transparent operations.</p><p>The <a href="https://www.ndiscommission.gov.au/about-us/grants">NDIS Commission</a> also administers grants to help NDIS providers meet their quality and safeguarding responsibilities. These are not large grants, but they are available to registered providers who meet the criteria.</p><p>The providers accessing these funding streams are not the largest in the sector. They are the ones whose financial and operational records are clean enough to pass scrutiny.</p><h4>Where the money is actually leaking right now:</h4><p>Before diversifying revenue, most providers need to stop the leaks.</p><p>The three biggest financial leaks in the average NDIS provider are billing errors, unbilled sessions, and staff turnover. Most providers know about billing errors. Fewer have quantified the cost of unbilled sessions and the ongoing cost of turnover.</p><p>Billing errors at a 14 percent rejection rate on $40,000 per month in claims means $5,600 per month in delayed or lost revenue. Some of that is recovered eventually. None of it arrives on time. The cash flow delay compounds across every fortnight.</p><p>Unbilled sessions happen when workers deliver sessions that never make it into the billing run. The session was delivered. The worker was paid. The claim was never submitted. This happens when session logging is disconnected from billing — the record exists somewhere, just not in the right format at the right time.</p><p>From December 2026, the claims window shrinks to 90 days. Sessions delivered and not claimed within 90 days are forfeited. For providers with any billing lag, this change converts missed submissions from a solvable problem into a permanent revenue loss.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS billing</a> that flows automatically from session delivery records means every delivered session is in the billing run. The claim window cannot expire on a session that was never logged correctly, because sessions are logged at delivery.</p><p>CTARS integrates directly with <a href="https://www.xero.com/au/">Xero</a> and <a href="https://www.myob.com/au">MYOB</a> so financial records update automatically. The gap between what you delivered and what you claimed is visible in real time, not discovered at the end of a quarter.</p><h4>The service mix question you need to answer before October:</h4><p>The social participation funding cut from October 2026 is not evenly distributed across provider types. Providers whose revenue is concentrated in community access, group activities, and social programmes are the most exposed.</p><p>The question is not whether to respond. The question is what response makes financial sense for your specific service.</p><p>Three options exist.</p><p>The first is diversification into protected support categories — core supports, SIL, complex daily living, and behaviour support. These categories are not being cut. Providers who add or expand these services before October reduce their dependence on the category that is being reset.</p><p>The second is positioning for the Inclusive Communities Fund. The $200 million fund will support community organisations running participation activities. Organisations with a community or not-for-profit structure are better placed to access it. If your structure allows for this positioning, the consultation period opening in July is when it matters.</p><p>The third is rightsizing. Some providers may be better served by reducing their social participation programme volume now and redeploying staff and infrastructure toward higher-margin, protected service types.</p><p>All three require the same starting point: knowing your current revenue breakdown by support category. Your <a href="https://ctars.com.au/ndis-client-management-software/">NDIS client management software</a> should be able to show you the billing split by support category across the last three months in under two minutes.</p><p><a href="https://ctars.com.au/"><strong>Try CTARS free at ctars.com.au</strong></a><strong>.</strong> See your revenue breakdown by support category, billing accuracy, and cash flow in one connected system. No credit card.</p><h4>The system’s investment that pays for itself:</h4><p>Most providers evaluate software as a cost. The right frame is return on investment.</p><p>The billing errors at 14 percent rejection rates cost more per month than a CTARS subscription at most provider sizes. The admin hours spent on manual billing reconstruction cost more. The compliance remediation cost of a single audit finding costs more. The staff turnover cost of two workers leaving because of poor systems costs significantly more.</p><p>The ROI calculation for a provider billing $40,000 per month looks like this. Reducing billing rejections from 14 percent to 2 percent recovers $4,800 per month in previously delayed revenue. Eliminating four hours of manual billing reconstruction per fortnight at a coordinator rate of $40 per hour saves $320 per month. Reducing one worker exit per year by improving the admin experience saves $3,200 in onboarding costs divided across twelve months, or $267 per month.</p><p>That is roughly $5,400 per month in recoverable value from a software change at a mid-size provider. Against a subscription that costs a fraction of that.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">NDIS compliance software</a> that maintains continuous compliance also reduces the cost of audit preparation. A provider who spends three weeks before each audit reconstructing records they should have been building all year is spending significantly more on compliance than one whose records are current daily.</p><h4>The commissioning model changes your financial position permanently:</h4><p>From October 2027, plan management commissioning begins. From July 2028, support coordination commissioning begins. For providers with these service lines, the financial model is changing structurally.</p><p>Plan management spending is being cut 30 percent through the commissioning process. Support coordination spending is also being reduced. The providers who make the commissioned list will receive a contracted revenue stream from the government-selected panel. The providers who do not make the list will operate in a shrinking open market.</p><p>The selection criteria for both panels will be published through consultation in 2026 and 2027. But the evidence base that determines selection — outcome documentation, financial transparency, compliance history — is being built right now in every session note and billing record your team produces.</p><p><a href="https://ctars.com.au/ndis-client-management-software/">Document management software</a> that produces clean, retrievable, structured records means your commissioning case is built continuously as part of daily operations. Not assembled under pressure when the application opens.</p><p>Read more about <a href="https://ctars.com.au/blog/a-comprehensive-guide-to-ndis-reporting-requirements/">NDIS reporting</a> requirements and how connected systems reduce the financial overhead of compliance across every part of your operation.</p><p>CTARS has supported NDIS and <a href="https://ctars.com.au/out-of-home-care/">out-of-home care providers</a> across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.</p><p>See the <a href="https://ctars.com.au/product-tour/">product tour</a>. Check the <a href="https://ctars.com.au/pricing/">pricing page</a> to see what the ROI looks like for your service size.</p><p><strong>Financial sustainability is not a margin problem. It is a systems problem. Fix the systems and the margin follows.</strong></p><p><a href="https://ctars.com.au/"><strong>Start your free trial at ctars.com.au.</strong></a> Full platform. See the financial impact of connected systems on your billing, compliance, and revenue. No credit card.</p><p><a href="https://ctars.com.au/"><strong>Book a 30-minute demo.</strong></a> Talk to someone who understands the financial sustainability challenges of running an NDIS service in 2026 and what your systems need to do about them.</p><p>Originally published on the CTARS blog at <a href="https://ctars.com.au/blog/">ctars.com.au/blog</a>. If your organisation has not done a revenue category breakdown in the last three months, share this with your director and finance lead today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8ead00e8663" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>