Welcome to the show -- Winter, if the NDIS Commission asked your business for incident records, staff training evidence, and claim-linked service notes TODAY, and all of it lived across spreadsheets, emails, and someone's phone... that is not an admin problem anymore. That's a compliance problem. "Today" is the bit that gets me. Not at the next audit, not when you've got two weeks to tidy things up -- on demand. And once you said incident records and service notes in the same breath, I could already feel the mess. Because if those two don't line up, the story of what happened doesn't line up either. Exactly. And that's where 2026 really changes the conversation. The Commission is moving toward a more rigorous, data-driven approach to compliance monitoring. So instead of relying mainly on periodic audits and self-reported information, providers need documented evidence that shows CONTINUOUS compliance. Not a polished binder once a year. Evidence that's available when asked. Continuous compliance sounds tidy as a phrase, but in practice it means your software has to keep receipts. Like, every roster change, every note, every worker credential, every incident log. You're not just buying convenience. You're buying a way to prove what happened, when it happened, and who did it. Yes -- and a folder of scattered documents is no longer enough. That's especially true because the NDIS Commission is also reviewing the NDIS Practice Standards, and new SIL Practice Standards are being developed and tested ahead of 1 July 2026. If the standards shift, providers with integrated systems can adapt much faster than businesses stuck stitching together manual processes. 1 July 2026 -- that's a proper deadline-shaped date. And I think this is where smaller providers sometimes get caught, because ad hoc systems can look fine right up until they absolutely don't. A sole trader can survive on clever workarounds for a while. Then one more participant comes on, one more support worker joins, one incident lands on a weekend, and suddenly the whole thing starts rubbing against itself. That's the collision point. Rostering touches billing. Billing touches NDIS claims. Claims need accurate service delivery data. Staff compliance affects who should've been rostered in the first place. Incident reporting has to connect back to participant records and often to staff records too. When those systems are disconnected, you don't just waste time -- you create gaps in evidence. Let me try to say that back. So the danger isn't, "our admin team's a bit busy." It's more like: your roster says one thing, your shift notes say another, your claim says a third thing, and then an auditor asks for the chain between them. Is that basically it? Almost. The chain is the key, but also the speed. If you need three people and half a day to reconstruct a single support event, that's a warning sign. Good systems let service delivery data feed straight into rostering and billing, so the record is connected by design, not rebuilt later from memory. Rebuilt later from memory is the phrase that makes me a bit nervous, honestly. Because in care settings, memory is not a control. It's just... hope. That's well put. And it's why software selection has moved out of the IT bucket. In 2026, your software stack is part of your governance model. It affects whether claims are accurate, whether worker checks are current, whether incidents are recorded properly, and whether you can demonstrate all of that with confidence. And confidence matters because auditors can tell when a business is narrating from clean records versus scrambling. We've all seen the digital version of the junk drawer. Six tabs open, three duplicate files, one spreadsheet called Final_v2_REAL. Final_v2_REAL is far too real. But the bigger point is this: the right stack helps you operate better day to day, sure, yet the hidden win is that it turns compliance from a reactive clean-up job into an ongoing operational habit. So if you're shopping for software, where do you actually start? Because this is where people get dazzled by glossy demos and forget to ask what the business genuinely needs. Start by mapping the core functions. For most registered NDIS providers, that's participant and case management, rostering and scheduling, billing and NDIS claims, staff compliance and training records, incident management, and reporting. If you don't map those first, you'll compare platforms based on features you noticed rather than functions you need. Participant management, rostering, billing and claims, staff compliance, incident management, reporting -- that's six buckets. And not every provider needs the same depth in all six. A small team isn't buying for the same reality as a mid-sized provider running multiple sites and support types. Right. Which leads to the first real tension: all-in-one versus best-of-breed. All-in-one platforms like ShiftCare, SupportAbility, Lumary, Brevity, and Flowlogic are designed as end-to-end systems. The appeal is one subscription, one source of truth, fewer handoffs, less double entry. SupportAbility, for example, brings rostering, billing, HR, and client data together in a single system, so service delivery data can feed directly into rostering and billing and help keep NDIS claims accurate. And that's the seductive bit, isn't it? One system, one login, one clean trail. But people still get tempted to patch together cheaper tools because each one seems "good enough." A scheduler here, a payroll app there, maybe a form builder for incidents. On paper it feels lean. On paper, yes. In practice, every extra handoff is a risk point. If your incident system doesn't talk to your participant record, or your roster doesn't feed billing, you've created little islands. Cheaper tools can work, especially for very small providers, but only if the compliance handoffs are genuinely controlled. Can I push on that? Because there are low-cost options that sound pretty capable. Imploy, for instance, has a free plan for up to five users, right? And that includes smart rostering, built-in payroll with Xero integration, AI-powered shift matching, and client records with audit-ready documentation. For a sole trader or tiny team, that's not nothing. Not at all. For small providers, that kind of entry point can make real sense. I'm not anti-cheap; I'm anti-fragmented. The question isn't whether a platform is expensive or affordable. The question is whether it covers the compliance-critical features. And those are non-negotiable. Let's name them. If I'm evaluating a platform and it cannot do incident reporting and management, that's a red flag. If it can't integrate with the NDIS portal for direct claims submission, another red flag. If pricing updates still rely on me manually checking the NDIS pricing catalogue... that's a headache with consequences. Yes -- and add audit-ready documentation, expiry reminders for staff certifications and worker screening checks, and secure document storage. Lumary is a useful example on the claims side because it offers real-time NDIS portal integration for instant line-item claims, automatic pricing updates, and compliance reporting without manual data entry. That's particularly attractive for medium and large providers that need scale. Real-time line-item claims -- that phrase tells you what modern software is supposed to remove: lag. Because lag is where errors breed. If a pricing rule changes and your platform updates automatically, that's one less place for a stale spreadsheet to quietly cost you money or expose you. And then there is mobile. Your support workers are not sitting at a desk. So a genuinely functional mobile app is now standard, not a bonus. You want GPS check-in, shift notes, incident logging, and real-time roster access from a phone. If the mobile app is clunky, workers delay entries, and delayed entries weaken evidence. GPS check-in is one of those features that sounds small until you think about what it proves. Not everything, obviously -- but it does anchor time and place. Same with real-time shift notes. They're not just notes anymore; they're part of the evidence trail. And before you sign anything, ask the questions vendors sometimes hope you won't ask clearly. Is data hosted on Australian servers? Does it integrate with PRODA and the NDIS portal? What does onboarding and training support actually look like? Is pricing based on users, participants, or both? And how quickly does the platform update when NDIS pricing or rules change? Australian servers, PRODA, users-versus-participants pricing -- those three alone can completely change the decision. Because a system can feel affordable until the pricing model scales badly, and it can feel polished until onboarding turns out to be "here's a help centre, good luck." Yes, the famous unsupported rollout. And that's where buying software becomes a strategic decision. You're not just asking, "Will staff use it?" You're asking, "Will this system help us stay claim-accurate, training-current, incident-ready, and audit-ready as the rules tighten?" I think that's the reframing I'd want every provider to sit with. In 2026, software isn't just the thing under your operations. It's part of how you demonstrate you're compliant, well-governed, and participant-focused -- continuously, not occasionally. And if that's true, then the interesting question isn't whether your software saves time. It's whether, when the standards shift again -- and they will -- your systems help you prove the quality of your service without scrambling. That's the bar now.
Audio Coursesby Jellypod