IndyForms blog

TLC Support WA Case Study – IndyForms

IndyForms — Thu, 08 Oct 2026 14:00:00 GMT

A small, owner-operated NDIS provider covering one of the largest service areas in the country — from Kalgoorlie to Bunbury and Perth — TLC Support WA uses IndyForms to manage staff onboarding, compliance and client documentation across a dispersed team, all from one place.

About TLC Support WA

TLC Support WA is a small, owner-operated disability support provider founded by Tiani Lange, a former education support assistant who moved into business ownership before returning to the disability sector when a friend needed help navigating the newly-introduced NDIS scheme. What started as one family’s request grew into a provider now employing more than 25 support workers across the Goldfields, South West and Perth regions of Western Australia.

TLC takes on only a handful of new clients each year so that every family gets genuine, personalised attention — recruiting and managing support staff on their behalf, guiding them through NDIS funding, and handling the ATO, Work Health & Safety and Fair Work Commission obligations that come with running what is, in effect, a small employment operation inside every client’s home. TLC also reinvests up to $15,000 a year back into client equipment, home modifications and allowances, on top of its day-to-day coordination work.

The challenge: a small team, a huge service area, and constant compliance change

Regional WA is not an easy place to run a disability support business. TLC’s team is spread across a footprint that would take the best part of a day to drive end-to-end, supporting families who each effectively become a first-time employer the moment they take on a support worker. Every one of those working relationships needs a service agreement, an onboarding pack, a code of conduct sign-off and an ongoing compliance trail — on top of managing rate changes as the SCHADS Award is updated.

Founder Tiani Lange has spoken publicly about how exposed regional providers are to this kind of regulatory load, describing the administrative side of proposed NDIS provider registration as a costly “tick and flick exercise” that risks pushing independent support workers out of the sector altogether (ABC News, June 2026). For a provider whose entire value proposition is untangling that complexity on behalf of families, the paperwork couldn’t be allowed to become TLC’s own bottleneck.

Before IndyForms, our biggest headache was the number of clients and staff contacting us because they weren’t sure how to complete or return a form. Compared with DocuSign, we find IndyForms much easier to use and navigate, and forms are completed with far fewer questions or issues. Being able to save a form and come back to it later has been a real time-saver too — people don’t feel pressured to finish everything at once, and our admin team spends far less time explaining the process or chasing incomplete forms. The service is second to none: Dan and the team are always willing to answer questions, and will even help complete work we’re unable to do ourselves. That level of personal support has made a genuine difference to our business.”

Tiani Lange, Founder, TLC Support WA

The solution: one system for onboarding, compliance and client care

TLC now runs the full lifecycle of a support worker or a client relationship through IndyForms — from the first enquiry to ongoing compliance checks — using role-specific templates built for the realities of the NDIS workforce:

Tailored HR onboarding. Separate onboarding workflows for different roles — including a dedicated Part Time Contract pack and a Quality & Compliance Coordinator pack — so new hires get exactly the paperwork their role requires, not a generic one-size-fits-all form.
Service agreements and rate changes, e-signed. Service agreements are issued and signed digitally, and SCHADS Award rate movements go out as a Rate Increase Notification & Acknowledgement form — giving TLC a signed, timestamped record that every worker has been notified and has acknowledged the change.
Code of conduct, done consistently. A standing Code of Conduct Checklist keeps expectations consistent across a team that rarely works in the same room together.
Referrals from outside the business, handled the same way. A Referral for Services Form is shared externally with allied partners and support coordinators, so new client enquiries land in the same system as everything else — instead of in a separate inbox to chase up.
Client voice built into the workflow. Staff Profile Forms and a Client Satisfaction Survey keep both sides of the relationship — the worker and the family — documented and reviewable over time.

Every submission triggers an automatic notification to the right person — Tiani, an enquiries inbox, or the client themselves — so nothing waits for someone to remember to follow up, and every document sits in one audit-ready record instead of scattered across email threads and paper files.

The impact

For a provider covering three regions with a small central team, that consolidation matters more than it would for a metro-based business with staff in one office. Onboarding, compliance sign-off and client documentation now move through the same repeatable process regardless of where in WA a worker or client is based, with a clear record of what was sent, when it was actioned, and who acknowledged it — exactly the kind of trail a provider needs as NDIS compliance requirements continue to tighten.

That leaves TLC’s small team doing what they set out to do: spending their time on families, not on paperwork.

Audit-ready, always.

See how IndyForms can bring your onboarding, compliance and client documentation into one place.

Book a Demo

Your AI Is Brilliant. It's Also Locked Out of Your Business. - IndyForms

Dan Scanlan, CEO IndyForms — Wed, 16 Sep 2026 14:00:00 GMT

You’ve connected Claude or ChatGPT to your calendar. Your inbox. Maybe a dozen Zaps that fire off automatically before you’ve had your coffee. Your AI stack can draft the email, book the meeting, summarise the call.

Then someone hands you a signed consent form. An incident report. A compliance checklist that has to be filled in by an actual human, on the actual day, with an actual signature. And your AI just stops. It has no idea any of that happened.

That’s not a small gap. For most businesses, that paperwork is the business — the real-world, human-generated data your operations, your compliance, and your customer relationships actually run on. And until now, it’s lived in a separate universe from the AI tools you’ve built everything else around.

We just closed that gap. Here’s how.

Quick refresher: what is MCP, and why does it matter?

MCP (Model Context Protocol) — is the new open standard that lets AI models like Claude and ChatGPT connect directly to real tools and real data, instead of just guessing from whatever you paste into a chat box. Think of it as the missing wire between “AI that can reason” and “your actual business systems.”

Plenty of software is racing to plug into it. Most of what’s landing first is the easy stuff — calendars, email, generic databases. The hard part was always going to be connecting AI to the messy, human, compliance-grade data that regulated and service-based businesses live and die by. Forms. Signatures. Records. Audit trails.

That’s the part we built.

The problem: your business runs on human data your AI can’t touch

Automation is only as good as the data feeding it. You can build the smartest workflow in the world, but if it can’t see whether a form was actually submitted, whether a checklist was actually completed, or whether a policy was actually signed off by a real human — it’s automating on a guess.

That’s the gap that’s been quietly limiting every “AI-powered business” pitch of the last two years. The models got smarter. The human layer — the forms, the sign-offs, the day-to-day paperwork that proves work actually happened — stayed exactly where it was: offline, siloed, and invisible to the tools meant to be running your business.

IndyForms is already where that data lives. Now your AI can see it too.

IndyForms has always been the place your team, your families, your clients and your frontline staff actually do the paperwork — digitised, tracked, and turned into a single source of truth instead of a filing cabinet. With MCP, that same data becomes something Claude and ChatGPT can query, act on, and trigger workflows against, in real time.

In plain terms: the forms your people fill out stop being a dead end. They become a live channel between your humans and your AI.

Some of what that unlocks:

Ask your AI, not your team. “Has every staff member signed off on the updated policy?” “Which incident reports are still open?” Claude can check IndyForms directly and answer — no chasing anyone down.
Compliance that watches itself. Connect an automation that flags overdue forms before they become a problem, instead of finding out during an audit.
Real follow-through, not just reminders. Form submitted → IndyForms captures it → your AI drafts the follow-up, updates the record, or kicks off the next step. No copy-pasting between five different tabs.
One version of the truth, everywhere. Real-time updates and version control mean your AI is always working off the current form, not a printout from three weeks ago.

This is what “make the paperwork as easy as possible” actually looks like when you take it all the way — not just digitising the form, but making sure the data inside it can go to work the second it’s submitted.

Other platforms have forms. IndyForms is the data layer your AI runs on.

Plenty of tools will sell you a form builder. Almost none of them were built to be the compliance backbone of a regulated business — and none of them were sitting on the kind of structured, audit-ready human data that’s actually worth connecting an AI to.

That’s the difference. IndyForms isn’t adding a chatbot to a form. We’re making the forms themselves a first-class citizen in your AI stack — so audit-readiness stops being a scramble, your staff and families stay in the loop without more admin on your plate, and the automations you’ve already built finally have the human data they were missing.

This is rolling out now

MCP support is landing on IndyForms first, ahead of the pack, because we built the platform for exactly this kind of data. If you’re already running your business on Claude, ChatGPT, or an automation stack — and you’re tired of it stopping cold at anything that needs a human signature — this is the piece you’ve been missing.

Want in early?

Reach out and we’ll get you connected before it’s everywhere.

Get Early Access

Together We Can International Case Study – IndyForms

IndyForms — Sat, 12 Sep 2026 14:00:00 GMT

Together We Can International are a progressive community organisation supporting neurodivergent young people to build confidence, connection and independence through employment support and social inclusion.

The challenge:

Before IndyForms, Together We Can International was running on a system that just wasn’t built for a team spread across multiple locations. Logins didn’t play nicely with multiple hubs, and information and documents ended up tracked and stored separately from one place to the next. That made it genuinely hard to manage things consistently across all three hubs — and harder still for staff to quickly find what they needed, when they needed it.

Since moving to IndyForms, it has really streamlined the way we create, send and manage our forms. Having access across the team, along with the management overview, has made it much easier to keep track of where things are at across our different locations.

We’ve also found the ability to easily amend documents, use simple drop-downs and have pre-filled sections particularly useful. It has made the process much more efficient and reduced the amount of repetitive admin involved.

The feedback from staff using IndyForms has also been positive… Overall, IndyForms has made managing our documentation much more streamlined and accessible, particularly as we’ve continued to grow across multiple locations.”

Jasmine Reynolds, Head of Service Delivery at Together We Can International

The solution:

Since moving to IndyForms, Together We Can International now creates, sends, and manages every form from one place. Head of Service Delivery Jasmine Reynolds and her team get full visibility across the organisation, while frontline staff get the day-to-day tools that actually make their jobs easier: forms they can amend on the fly, simple drop-downs, and pre-filled sections that cut out the repetitive admin altogether.

Today, that setup covers the full participant journey — intake and referral, consent, medication, compliance documentation, and provider service agreements — plus community feedback and program-specific waivers, all built and managed for them by the IndyForms team.

The results:

One login, every hub.
No more information silos between locations — the whole team works off a single source of truth.
Management oversight without the chasing.
Jasmine’s team can see where things stand across every hub, in real time.
Admin that gets out of the way.
Editable documents, drop-downs and pre-filled fields have taken a big chunk of repetitive admin off staff plates.
Usage that’s scaled with them.
Together We Can’s provider service agreements alone have run into the thousands of submissions — with intake, consent and compliance forms handling hundreds more, all without adding admin headcount.
Room to grow.
As they take on more hubs and a larger volume of participant documentation, the system is built to scale with them — including upcoming AI-powered reporting the team is already looking forward to.

Running documentation across multiple hubs, sites or teams?

See how IndyForms brings it all onto one system.

Book a Demo

Peak Coordination Case Study – IndyForms

Dan Scanlan, CEO IndyForms — Thu, 10 Sep 2026 14:00:00 GMT

Peak Coordination is an NDIS provider delivering Specialist Support Coordination and Psychosocial Recovery Coaching.

Their mission is straightforward: help people living with disability access ethical, appropriate support that lines up with their own goals, preferences and needs. Everything they do is built around four values — Listening, Collaboration, Action, Compassion.

That recovery-focused, person-first approach is exactly why the paperwork behind it can’t be an afterthought. Consent, service agreements, support plans, crisis plans — every one of them touches a real person’s care. Peak Coordination needed those documents to be as reliable and responsive as the service itself.

The challenge:

Support coordination runs on documentation. Every participant needs a consent form, a service agreement and schedule of supports, a support plan, often a safety assessment and crisis plan, and — eventually — an exit form. Layer in NDIS-specific consent requirements, plan variation and plan reassessment requests, medication administration records, and a small team can end up spending as much energy chasing paperwork as they do supporting participants.

For a provider whose whole model is built on being responsive and person-centred, that’s the wrong trade-off. Peak Coordination needed one place to run the whole participant journey — something their team could fill in fast, participants could actually engage with, and management could trust was accurate and current without anyone chasing a spreadsheet.

Linking with IndyForms has streamlined our processes and given us the ability to complete forms face-to-face or remotely, so we can tailor to what works for our clients and ensure their NDIS funding is used appropriately. The forms are user-friendly for our staff, which keeps our compliance managed at the highest level — vital for us as an NDIS registered provider. Giving our staff the ability to complete relevant forms without management involvement has freed up a huge amount of time, compared to the previous forms provider we used, which relied heavily on management.”

Nathan Hall, Owner / Director at Peak Coordination

The solution:

Peak Coordination didn’t have to build any of this themselves. The IndyForms team worked directly with them to build out the entire client lifecycle — not a single intake form bolted onto an old process, but the full journey from first contact through to exit:

My Intake — the first touchpoint with a new participant
Client Consent Form and NDIS Consent Form — capturing consent the way the NDIS expects it
Service Agreement and Schedule of Supports — the core agreement underpinning every engagement
Support Plan — the working document behind day-to-day coordination
Client Safety Assessment and Crisis Plan — sensitive, high-stakes documentation done properly
Medication Administration Record — clinical detail captured alongside everything else
Plan Variation Request Form and Plan Reassessment Request Form — new NDIS-specific forms, built by the IndyForms team to replace the old change-of-situation notice, keeping records current as circumstances change
Client Satisfaction Survey — published as a public form so participants can give feedback directly, without needing an internal login
Exit Form — closing the loop when a participant’s engagement ends

Every internal, sensitive document — consent, safety assessments, medication records — stays locked down, while the satisfaction survey is the one form opened up publicly, so feedback is one click away for the people whose opinion matters most. And because IndyForms built and maintains the whole suite, Peak Coordination’s team never had to become forms specialists — new forms and changes go through IndyForms, not an internal project.

The results:

Since rolling out its refreshed forms suite, Peak Coordination has put real volume through IndyForms in a very short window — strong, steady submissions across the service agreement, safety assessment and crisis plan, client consent form and support plan, plus a high completion rate on the public client satisfaction survey.

That’s not the ramp-up curve of a system still finding its feet — it’s what it looks like when a team’s day-to-day workflow moves onto a platform that fits how they already work. The result for Peak Coordination: one single source of truth across the entire participant journey, sensitive documents handled with the care they require, and a team spending its time on people, not paperwork.

Solutions for every industry

Peak Coordination is just one example of how IndyForms can streamline business operations to make a big impact on service delivery. Whether you’re a not-for-profit or charitable organisation, or a large corporate, IndyForms can help your business to transition from labour-intensive and unsustainable paper-based processes to a digital system that will significantly reduce your team’s workload and improve your efficiency and productivity.

To find out more about how our dedicated support staff can customise the right approach to managing your operational needs, contact us today.

Book a Call

Document Management vs CRM: What's the Real Difference? - IndyForms

Dan Scanlan, CEO IndyForms — Mon, 17 Aug 2026 14:00:00 GMT

If you’ve ever tried to store a signed contract in your CRM, or hunted through a CRM’s file tab for a policy document from three years ago, you’ve already felt the problem this post is about. CRMs and document management systems (DMS) both hold important business information, and on the surface they can look interchangeable — both have contacts, both let you attach files, both promise to keep your team organised. But they’re built to solve two very different problems, and using one to do the other’s job is usually where things start to fall apart.

Here’s the difference, and why most growing businesses end up needing both…

A CRM is built to manage relationships

A Customer Relationship Management System — HubSpot, Salesforce, Zoho, and similar tools — exists to track people and the sales or service journey they’re on. Its core objects are contacts, companies, deals, and tickets. It’s built to answer questions like: who’s this lead, what have we said to them, where are they in the pipeline, and what’s the next touchpoint?

A CRM is exceptional at that job. Pipeline stages, email sequences, activity timelines, and forecasting are all things a CRM does far better than any general-purpose tool. What it’s not built for is being the permanent, auditable home for the documents your business is legally or operationally required to keep. Most CRMs treat file attachments as a side feature bolted onto a deal or contact record — there’s no real version control, no structured retention policy, and no way to prove to an auditor that a document hasn’t been altered since the day it was signed.

A document management system is built to manage records

A Document Management System — this is where IndyForms sits — exists to manage the lifecycle of a document or form itself, independent of any one deal or contact. That means capturing information through digital forms, routing it for review or approval, collecting an electronic signature, storing the finished record securely, and retaining it for however long compliance requires — five, fifteen, even twenty-five years, depending on your industry.

Where a CRM’s unit of work is “the customer,” a DMS’s unit of work is “the document” — the incident report, the employment contract, the client intake form, the consent record, the compliance certificate. IndyForms is built around this specifically: ISO 27001-certified security, Australian-hosted data, structured workflows and automation so nothing sits unfinished, and an AI assistant (Ask IndyAI) that helps compliance and admin teams find and act on records instead of digging through folders. None of that is a CRM’s job, and trying to force it into one usually means losing the audit trail that made the document worth keeping in the first place.

Why the two get confused

The confusion mostly comes from overlap at the edges. Both systems can hold a PDF. Both can send an email. Both can be described as “keeping everything in one place.” A sales team might even keep a signed proposal in the CRM deal record, which works fine — until that same document also needs to satisfy a workplace health and safety audit, an NDIS compliance check, or a five-year retention requirement, and now it’s buried inside a sales tool nobody outside the sales team can search.

The practical test is simple: if the record needs to survive independently of a customer relationship — outlasting the deal, the employee, or the client relationship it originated from — it belongs in a document management system, not a CRM.

How they work together

The two aren’t competitors; they’re complementary layers of the same operation. A typical setup looks like this: the CRM manages the relationship — the lead, the deal, the client — while IndyForms manages the documents that relationship generates, from intake forms and contracts to signed consent and ongoing compliance records. Integrations (via API or tools like Zapier) can connect the two, so a completed form in IndyForms can update a deal stage in the CRM, without either system trying to do the other’s job.

This division of labour is exactly what keeps both systems useful. Your CRM stays fast and focused on pipeline and conversations. Your document management system stays audit-ready, with every form, signature, and record retained, searchable, and provably intact whenever a client, regulator, or auditor asks for it.

Which one do you need?

If your team is chasing staff for missing forms, storing contracts across scattered email threads and shared drives, or dreading the next audit because nobody’s sure where a document actually lives, that’s a document management gap — not a CRM gap. Adding another CRM field for file attachments won’t fix it. What fixes it is a system purpose-built to manage the record from creation through years of retention.

IndyForms doesn’t replace your CRM, and it isn’t trying to. It picks up exactly where CRMs run out of road: the forms, signatures, and documents your business has to get right, every time, for as long as it takes.

Ready to see the difference in practice?

Book a demo or explore how IndyForms fits alongside the tools you already use.

Book a Demo

Getting Your NDIS Registration Audit-Ready with AI: A Practical Guide (Plus a Free Prompt) - IndyForms

Dan Scanlan, CEO IndyForms — Sun, 09 Aug 2026 14:00:00 GMT

Starting an NDIS business is exciting, until you hit the registration audit. Between the NDIS Practice Standards, worker screening requirements, and a document list that seems to grow every time you look at it, it’s easy to feel like you need a compliance consultant just to figure out where to start.

The good news is that a large chunk of the document preparation work — the policies, registers, and templates every provider needs — can be drafted with the help of an AI tool like Claude. Not as a replacement for proper compliance advice, but as a way to get from a blank page to a strong first draft in an afternoon instead of a month. Below is a plain-English walkthrough of what the audit actually involves, and at the end, a ready-to-use prompt you can copy straight into Claude to generate your own document set.

Verification or certification: which audit are you actually facing?

The NDIS Quality and Safeguards Commission runs two different audit pathways, and which one applies to you depends on the supports you plan to deliver.

Verification audits are the lighter-touch option: a document review with no site visit, generally used for lower-risk supports such as therapeutic supports and standard support coordination.
Certification audits are more involved: a two-stage process that includes an on-site visit, staff interviews, and direct observation of how you actually deliver supports. This pathway typically applies to higher-risk service types such as personal care, supported independent living (SIL), specialist behaviour support, and early childhood supports.

If you’re not sure which pathway applies to your services, that’s normal at this stage — it’s worth confirming against the current NDIS Commission registration group list before you apply, since the specifics do get updated from time to time.

What the Practice Standards actually ask for

Regardless of pathway, every provider is assessed against the NDIS Practice Standards Core Module, organised into a handful of outcome groups:

Rights and responsibilities — person-centred supports, respect for individual values and beliefs, privacy and dignity, dignity of risk, and safeguarding against violence, abuse, neglect, exploitation, and discrimination.
Governance and operational management — clear organisational structure, risk management, quality and continuous improvement, information management, financial management, and human resources (including worker screening).
Support provision — assessment and planning, the support plan itself, how supports are actually delivered, managing transitions, worker knowledge and skills, and medication management where relevant.

If you’re registering for SIL, there’s an additional module covering the support environment — the physical and household environment participants live in, their health and wellbeing, and how transitions in and out of a home are managed. Other supplementary modules apply if you’re delivering behaviour support, early childhood supports, or a handful of other specialist services.

The single most common reason providers fail an audit isn’t a missing policy — it’s a policy that exists on paper but isn’t actually being followed. Auditors are looking for three things together: a documented system, records showing it’s been implemented, and evidence that it’s producing a decent outcome for participants. A beautifully written incident management policy with no completed incident register behind it won’t get you through.

The document set you’ll actually need

Stripped back to essentials, most new providers need to produce:

A core policy suite: governance, risk management, quality and continuous improvement, privacy and information management, financial management, human resources, incident management, complaints management, a Code of Conduct, and safeguarding.
Registers and records: incident register, complaints register, risk register, continuous improvement register, worker screening register, and a training/induction record.
Participant-facing documents: a service agreement, an intake or referral form, a support plan template, consent forms, and a service exit or transition plan.
Anything specific to your registration group: for example, a medication management policy and health plan template if you’re delivering SIL, or a behaviour support plan template if you’re registering for specialist behaviour support.

That’s a genuinely long list for someone setting up a business for the first time, which is exactly the kind of drafting work an AI assistant is well suited to help with.

Using Claude to draft the first version

Rather than asking Claude for a generic template one document at a time, it works better to give it one detailed prompt that interviews you about your business first — your structure, the supports you’re registering for, your likely audit pathway — and then generates the whole suite of documents tailored to what you told it, finishing with a self-assessment checklist mapped against the actual Practice Standards outcomes.

Here’s that prompt. Copy everything inside the box below into a new Claude conversation (Claude.ai, Claude Code, or Cowork all work — Cowork and Claude Code can generate real Word and Excel files rather than just text):

 
    Copy 
  
You are helping me prepare the full set of documents my new NDIS provider business needs to pass its NDIS Quality and Safeguards Commission registration audit. I am not an NDIS compliance expert, so guide me — don't just ask me to specify things I won't know.

Work through this in phases. At the end of each phase, show me what you've produced before moving to the next one, and let me correct anything.

PHASE 0 — Business profile

Ask me, one group of questions at a time (don't dump all of these on me at once):

1. Business name, ABN/ACN, business structure (sole trader, company, partnership, not-for-profit), state/territory, and whether I'm brand new or already trading informally.

2. Which NDIS supports/services I plan to deliver (e.g. support coordination, therapy supports, SIL/supported independent living, personal care, community participation, plan management, early childhood supports, behaviour support). If I'm not sure how these map to official "NDIS registration groups," ask me to describe what I'll actually be doing day to day and work out the likely registration group(s) with me.

3. Roughly how many staff/contractors I expect to have in the first year, and whether I'll deliver services personally or manage a team.

4. Whether I already know if I'll go through the "verification" or "certification" audit pathway. If I don't know, tell me — based on the registration groups from question 2 — which pathway is likely, and flag that this should be confirmed against the current NDIS Commission registration group list before I apply, since the specifics do change.

PHASE 1 — Compliance map

Based on Phase 0, give me a short plain-English rundown of:

- Which audit pathway applies (verification = document review only; certification = document review + on-site audit + interviews)

- Which NDIS Practice Standards modules apply to me (Core Module always applies; flag any supplementary modules — e.g. SIL, Specialist Behaviour Support, Early Childhood Supports — that apply to my specific services)

- A one-paragraph explanation of what "evidence" actually means for an NDIS audit (a policy on paper is not enough — auditors want to see the policy, records showing it's been followed, and an outcome for participants)

PHASE 2 — Core governance policy suite

Generate complete, ready-to-use draft policies (not just headings/outlines) covering the NDIS Practice Standards Core Module, tailored to my business details from Phase 0:

- Governance & Operational Management Policy (org structure, roles, conflicts of interest)

- Risk Management Policy + a starter Risk Register populated with likely risks for my service type

- Quality Management & Continuous Improvement Policy

- Information Management / Privacy & Confidentiality Policy

- Financial Management Policy (incl. NDIS claiming/billing controls)

- Human Resources Policy suite (recruitment, worker screening, induction, supervision, performance management)

- Incident Management Policy (incl. reportable incidents to the Commission)

- Complaints Management Policy

- Code of Conduct (aligned to the NDIS Code of Conduct)

- Safeguarding Policy (violence, abuse, neglect, exploitation, discrimination)

- Human and Legal Rights / Person-Centred Supports Policy

- Privacy consent and dignity of risk / supported decision-making policy

For each, briefly note which Practice Standard outcome it's evidencing.

PHASE 3 — Registers, forms, and records

Generate templates (as fillable tables/forms) for:

- Incident register

- Complaints register

- Risk register (if not already covered)

- Continuous improvement register

- Worker screening check register

- Policy/document control register (version numbers, review dates)

- Training and induction record

- Feedback form (participant/family facing)

- Incident report form

PHASE 4 — Participant-facing documents

Generate:

- Service Agreement template (plain-language, NDIS-compliant terms)

- Intake/referral form

- Support plan template (person-centred, goal-based)

- Consent form (information sharing, photos/media if relevant)

- Service exit / transition plan template

PHASE 5 — Supplementary module documents (only if relevant to me)

If my services from Phase 0 trigger any supplementary Practice Standards modules, generate the extra documents those modules specifically require — for example:

- SIL: household/tenancy agreement inputs, medication management policy, health and wellbeing plan template

- Behaviour support: behaviour support plan template, restrictive practice authorisation and reporting process

- Early childhood: family-centred practice policy, transition to school planning template

Tell me clearly if none of the supplementary modules apply to me.

PHASE 6 — Self-assessment and audit-readiness checklist

Produce a checklist mapping every Practice Standards outcome relevant to me against: (a) the document that evidences it, (b) whether I have it yet, (c) what "in practice" evidence I'll still need to collect once I'm operating (e.g. completed shift notes, signed plans) that a document alone can't provide.

PHASE 7 — Wrap-up

Give me a short list of things Claude cannot do for me and that I need a qualified person for: engaging an NDIS-approved auditor/quality auditor, final legal review of the Service Agreement and policies, confirming my exact registration group codes and audit pathway on the NDIS Commission Applications Portal, and setting up my PRODA account.

Throughout: if you have file-creation ability in this environment (Cowork/Claude Code), please build each document as an actual file (Word doc for policies, spreadsheet for registers/checklists) rather than just pasting text, and organize them into a logical folder structure I can hand straight to my auditor. If you're in plain Claude.ai chat without file tools, give me complete copy-pasteable text for each document instead.

Drafting the documents is step one. Actually using them is what gets you through the audit.

Remember the point made earlier: the most common reason providers fail an audit isn’t a missing policy, it’s a policy that exists on paper but was never actually followed. Claude can get you a strong first draft of every policy, register, and template in an afternoon — but a folder of Word documents sitting on someone’s desktop doesn’t generate the “in practice” evidence an auditor is actually looking for. That only happens when the documents are live: being version-controlled as they’re updated, being filled in as registers rather than left blank, and being signed by the people they’re meant to apply to.

This is exactly the gap IndyForms is built to close. IndyForms has Claude built directly into the platform, so you can run the same kind of generation described above — forms, registers, and (soon) policies — without ever leaving it, and what comes out is already living inside the system that will keep it audit-ready, not a Word document you have to remember to import somewhere. From there, IndyForms keeps every policy under proper version control so you can always show an auditor which version was in force on a given date, turns your registers (incidents, complaints, worker screening, continuous improvement) into digital forms that staff actually fill in as things happen rather than backfilling before an audit, and handles the signatures — service agreements, consent forms, induction sign-offs — natively, so there’s a verifiable record that a real person actually agreed to or acknowledged each document.

It’s also worth knowing that IndyForms keeps all data hosted in Australia and doesn’t use your data to train any underlying model. For an NDIS provider, that matters in a very concrete way: participant records, incident details, and behaviour support information are sensitive, and it means your team can safely use the built-in Claude to draft reports, summarise case notes, or generate documents from that private data without it leaving the country or being absorbed into a model somewhere else. The result is that “audit-ready” stops being a scramble you do once a year and becomes the ongoing, unremarkable state of your business.

What this does — and doesn’t — replace

Run through the prompt above and you’ll come out the other end with a complete first draft of your governance framework, registers, and participant-facing paperwork, organised against the actual Practice Standards outcomes an auditor will be checking. That’s a genuinely useful head start.

What it doesn’t replace is the human judgement your registration still depends on: engaging an NDIS-approved quality auditor, having a solicitor or compliance consultant give your service agreement and policies a final look, confirming your exact registration group codes and audit pathway through the NDIS Commission’s Applications Portal, and actually running your business in a way that generates the “in practice” evidence — completed shift notes, signed plans, a real incident register — that no amount of drafting can substitute for. Treat the AI-generated documents as the scaffolding, and IndyForms as the system that keeps the building standing.

This post reflects the NDIS registration process and Practice Standards structure as published by the NDIS Quality and Safeguards Commission at the time of writing. Registration group definitions and audit pathway mappings are updated periodically, so always confirm current requirements directly with the Commission before submitting your application.

Introducing Ask IndyAI: Secure, Onshore AI for Your Compliance Documents - IndyForms

Dan Scanlan, CEO IndyForms — Tue, 07 Jul 2026 14:00:00 GMT

For most compliance-heavy businesses, the hardest part of managing documents isn’t storing them, it’s finding what you need, when you need it. A staff member’s certification, a client’s incident history, a training record that quietly expired months ago. Searching manually eats hours every week, and it’s easy to miss something important until it becomes a problem at audit time.

That’s exactly the problem Ask IndyAI was built to solve.

What Is Ask IndyAI?

Ask IndyAI is IndyForms’ built-in AI assistant, designed to help you get answers, build tools, and stay on top of compliance without digging through folders or spreadsheets. Instead of manually searching or building forms from scratch, you can simply describe what you need in plain English.

Ask IndyAI can search across your forms and records using natural language, summarise long documents or policies in seconds, and pull out exactly the information you’re after rather than the file it happens to live in.

Beyond Search: Graphs, Tables, and Trend Analysis

Ask IndyAI also turns raw data into clear graphs and tables on request, and identifies trends across your records that would otherwise take hours to spot manually. Ask it to chart incident reports over the past six months, build a table comparing compliance rates across teams, or flag a rising pattern in client feedback, and get a clear, visual answer in moments. For compliance and operations teams, this turns raw form data into decision-ready insight without needing a separate analytics tool.

Design Forms and Create Action Items, Just by Asking

Ask IndyAI isn’t just for finding information, it can help you build and manage your workflows too. Describe the form you need, and Ask IndyAI can help design it for you, saving you from starting with a blank page. It can also create action items and tasks directly from a conversation, so if you spot an issue while chatting with Ask IndyAI, you can turn it into a tracked task on the spot rather than making a mental note and hoping you remember.

This is especially powerful for staying ahead of compliance requirements. You might ask Ask IndyAI to find every staff member with overdue first aid training, and it will search your records, flag who’s affected, and let you generate action items to get them recertified, all in one conversation instead of a week of cross-checking spreadsheets.

Powered by Claude, Hosted Onshore in Australia

Ask IndyAI is powered by Anthropic’s Claude, accessed via Amazon Web Services (AWS) Bedrock. This service is hosted onshore in Australia, meaning your data stays within Australian borders and remains subject to the same strict privacy and data-handling standards that apply to the rest of the IndyForms platform.

This sits alongside our existing infrastructure on Microsoft Azure, which continues to host the core IndyForms platform. Together, this means every part of your data, whether it’s stored, processed, or analysed by AI, stays onshore, encrypted, and compliant with Australian privacy law.

What You Can Do with Ask IndyAI

A few everyday examples of how teams are using it: finding every staff member with overdue first aid or manual handling training in seconds, designing a new incident report form just by describing what it needs to capture, summarising a lengthy policy document before a meeting, asking how many incident reports were logged last month and getting an instant, accurate answer, generating a quick chart to spot trends in client feedback or compliance submissions, and turning a flagged issue straight into an action item for the right team member.

Why Onshore AI Matters for Australian Compliance

For businesses operating under NDIS, aged care, or other regulated frameworks, data sovereignty isn’t a nice-to-have, it’s a requirement. Many AI tools process your data offshore, often without clear visibility into where it’s stored or who can access it.

Ask IndyAI was built differently. By running on AWS Bedrock’s onshore Australian infrastructure, it lets you take advantage of powerful AI capabilities without compromising on the data residency and compliance standards your organisation is held to. It’s the same principle behind our ISO/IEC 27001 certification: security and compliance built into every layer, not bolted on afterwards.

Try Ask IndyAI Today

Ask IndyAI is available now inside IndyForms, ready to help your team find answers, design forms, track action items, and spot compliance gaps before they become problems, all without your data ever leaving Australia.

Start Free Trial

Stop spending your admin hours on paperwork. There's a better way. - IndyForms

Dan Scanlan, CEO IndyForms — Sun, 19 Apr 2026 14:00:00 GMT

Australian health and care providers are discovering that a fully managed digital transformation – from document digitisation to automated workflows is the fastest path to focusing on what actually matters: their clients.

Your clients need your attention, not your clipboard

The reality for most health and care businesses is this: you didn’t get into the industry to spend your days chasing signatures, manually filing incident reports, or setting up access permissions for new staff. You got into it to support people. Yet for many providers, a significant chunk of every working week disappears into exactly that kind of administrative friction.

This is the core reason more and more Australian care businesses are opting for full-service digital transformation rather than trying to piece together solutions themselves. The appeal is simple – hand the setup to someone else, get a system that works, and get back to doing what you do best.

“The best system is one you don’t have to think about. It just works – from the moment a new staff member joins to the day a client’s care plan needs updating.”

What “plug and play” actually means for care providers

When we talk about a plug-and-play digital transformation, we’re not talking about handing you a login and a help article and wishing you luck. We’re talking about a fully managed rollout where our team does the heavy lifting so yours doesn’t have to.

That means we come in, understand how your organisation works and build a digital system that mirrors and improves your existing processes – from intake forms and staff onboarding documents through to incident reporting, shift handover notes, and compliance checklists.

Document digitisation

We convert your paper and non-saved forms into smart digital forms, ready to use from day one.

Workflow automation

Approvals, notifications, and escalations happen automatically — no manual follow-up required.

Permissions setup

Staff, managers, and administrators each see exactly what they need — and nothing they shouldn’t.

Ongoing support

As your organisation grows or requirements change, we’re here to adapt your system with you.

Why businesses are choosing managed setup over DIY

There’s a common misconception that digital transformation needs to be a long, drawn-out internal project. In reality, most providers who try to set things up themselves spend weeks — sometimes months — getting bogged down in configuration, permissions issues, and staff training before they ever see the benefits.

The businesses that get the fastest results are the ones who recognise their time is more valuable elsewhere and hand the setup to a specialist team. Think of it the same way you’d think about outsourcing your bookkeeping or your IT infrastructure. You don’t need to understand every detail of how it works. You need it to work — reliably, securely, and without disrupting your day-to-day operations.

IndyForms is built specifically for Australian health and care providers — which means we understand NDIS compliance requirements, aged care reporting, and the real-world workflows your team deals with every day.

What our digital transformation service looks like in practice

Discovery — We start by understanding your current processes: what forms you use, how approvals work, who needs access to what, and where the friction points are.
Document digitisation — Our team converts your existing forms, checklists, and templates into fully digital versions inside IndyForms — mapped to your exact requirements.
Permissions configuration — We set up your organisational structure, user roles, and access controls so every team member has the right level of access from day one.
Automation build — We configure your workflows, notifications, and approval chains so the system does the follow-up work automatically.
Team walkthrough — Once everything is live, we walk your team through the platform so they’re confident and ready to go.
Handover and support — You’ve handed a fully working system with documentation, and our support team remains on call as you grow.

Transparent, flat-rate pricing

One of the things care businesses appreciate most about our transformation service is the pricing model. There are no surprise charges, no scope-creep invoices, and no ambiguity about what you’re paying for. Our team charges a flat hourly rate for setup work — whether that’s digitising documents, configuring automations, or building out your permission structures.

You stay in control of your budget. You decide the scope. And because we work quickly and efficiently — having done this for dozens of similar organisations — you won’t be paying for a team learning on the job.

The result: more time for your clients

When your forms are digital, your workflows are automated, and your staff know exactly what they need to do — the administrative noise disappears. Managers stop chasing paper. Staff stop duplicating data entry. Compliance becomes something that happens as a natural by-product of your day-to-day operations, rather than a separate, stressful exercise at audit time.

That’s the real value of digital transformation done properly. It’s not about having the most sophisticated software. It’s about having a system that’s been set up thoughtfully for your organisation — and then getting out of the way so your team can focus on the people in their care.

If that sounds like what your organisation needs, we’d love to talk.

Ready to go fully digital?

Book a free discovery call with the IndyForms team and we’ll walk you through exactly what a transformation looks like for your organisation.

Talk to our team

Faster Compliance Documentation Doesn’t Increase Risk — It Slashes It (and Boosts Profitability) - IndyForms

Dan Scanlan, CEO IndyForms — Thu, 29 Jan 2026 14:00:00 GMT

There’s a stubborn myth in compliance-heavy industries: “If we speed up documentation, we increase risk.” In reality? The opposite is true.

When compliance documentation is slow, manual, and painful, risk goes up and profitability quietly leaks — because the people who should be running the business are stuck building an evidence trail instead.

This is exactly the problem IndyForms was built to solve.

The Real Risk Isn’t Speed. It’s Distraction.

Compliance managers, centre directors, operations leads, practice managers — whatever the title — aren’t paid to shuffle paperwork.

Yet in most organisations, they spend ridiculous chunks of time:

Chasing staff for forms and checklists
Following up for signatures
Recreating evidence after the fact
Searching inboxes for “proof”
Updating spreadsheets no one trusts
Printing/scanning/filing like it’s 2006

Every hour spent manually documenting compliance is an hour not spent managing staff, customers, quality, cash flow, or growth.

That’s not “being safe.”

That’s running the business with one hand tied behind your back.

Slow Documentation Creates Fake Safety

Manual compliance feels safe because it looks busy.

But when documentation is painful:

People delay it
People batch it
People backfill it from memory
People copy last year’s version and hope for the best

That’s how you end up with:

Missing records
Outdated policies in circulation
Incomplete incident reports
Training “done” but not proven
No clear audit trail

And those gaps only show up at the worst possible time — audits, incidents, complaints, investigations.

Fast Evidence Creation = Real Risk Reduction

Speeding up compliance evidence doesn’t mean cutting corners.

It means capturing evidence as the work happens, when it’s accurate, complete, and defensible.

That’s where IndyForms comes in – it helps businesses:

Digitise compliance processes into simple, guided forms
Automatically store evidence in the right place (no more “where did that go?”)
Ensure teams always use the latest version of documents and policies
Assign tasks to the right people with due dates
Trigger reminders and automations so nothing falls through the cracks
Produce clean, time-stamped audit trails without the admin headache

So instead of “Oh crap, we need evidence,” you’re always audit-ready — by default.

The Hidden Profitability Killer: Manager Time

Let’s talk money.

When senior staff are buried in documenting compliance:

Decisions slow down
Teams get less leadership
Clients and families get less attention
Issues don’t get addressed early
Quality slips
Revenue opportunities get missed

You end up paying high-value people to do low-value admin.

That’s a profit problem.

When compliance evidence becomes fast and automatic (again… what IndyForms is designed for), you get:

Less double-handling
Less rework
Fewer “we can’t find it” moments
Reduced audit prep costs
Managers back doing actual management

Less admin.
More output.
Higher profit.

Fast Compliance Improves Culture (Yes, Really)

Here’s an underrated truth:

When compliance is messy and time-consuming, staff resent it.

When it’s easy and embedded in the workflow, they engage with it.

Why?

Clear steps
No confusion
No paperwork panic
No “I didn’t know which version to use” excuses

IndyForms makes compliance easier to follow, which makes it more likely people actually do it properly — consistently — without the stress.

That lowers risk long before a regulator ever knocks on the door.

The Goal Isn’t More Documentation

Compliance isn’t about producing mountains of paperwork.

It’s about proving:

The right thing happened
At the right time
By the right person
Using the right process
With a reliable audit trail

Speed doesn’t harm that.
Speed supports it — if the system is built properly.

That’s the core philosophy behind IndyForms.

Bottom Line

Slow compliance documentation doesn’t make you safer. It makes you distracted.

Fast, structured, automated evidence creation reduces risk and improves profitability — because managers stop doing admin and start running the business again.

That’s exactly what IndyForms does – it speeds up compliance evidence, reduces gaps, and gives leaders their time back.

And honestly? Time is the only thing you can’t audit your way into getting more of.

Why We Built IndyForms (and Why It Took Years) - IndyForms

Dan Scanlan, CEO IndyForms — Tue, 20 Jan 2026 14:00:00 GMT

IndyForms wasn’t born in a boardroom… it was born out of frustration.

Before IndyForms existed, I owned and operated multiple businesses that were document-heavy and compliance-heavy. Think onboarding, audits, policies, incident reports, approvals, training records — the kind of paperwork that never stops and is never quite right when you need it most.

And like most businesses, we were doing it the “normal” way:

Paper forms
PDFs emailed back and forth
Spreadsheets pretending to be systems
Filing cabinets that only one person understood
And processes that lived in people’s heads (until they left)

It was slow. It was messy. And it was risky.

So instead of buying another off-the-shelf tool that almost worked, I did something different…

I Reverse-Engineered the Mess

I sat down and mapped every document, form, and compliance process we were running — start to finish.

Not just the documents themselves, but:

Who creates them
Who fills them out
Who signs them
Where they’re stored
How they’re tracked
What happens when something changes
And what breaks when people forget (which they always do)

What became painfully obvious was this:

The problem wasn’t the people.
The problem was the systems.

Most tools forced businesses to adapt to their way of working — not the other way around.

So we flipped it.

From Paper to Digital (Properly)

We didn’t just “digitise forms”, we rebuilt the entire workflow:

Paper → smart digital forms
Manual chasing → automated reminders
Static documents → living, trackable records
Version chaos → single source of truth
Compliance stress → audit-ready by default

Every feature in IndyForms exists because a real business needed it.

If it didn’t solve an actual operational problem, it didn’t get built.

Years of Refinement (and Still Improving)

IndyForms didn’t appear overnight, it took:

Years of testing in live businesses
Feedback from teams actually using it
Edge cases you only discover under audit pressure
And constant refinement as regulations, industries, and expectations changed

Each new feature wasn’t about being flashy — it was about being useful.

Better workflows.
Cleaner processes.
Less admin.
Less risk.

Software Built From the Inside Out

Most software is built by people guessing how businesses work.

IndyForms is built by someone who was buried in the paperwork and decided there had to be a better way.

That’s still how we build today:
Start with real business needs
Design simpler, smarter ways to do the work
Automate the boring, repetitive stuff
And give teams clarity instead of chaos

The Goal Hasn’t Changed

IndyForms exists for one reason – to remove unnecessary admin, reduce compliance stress, and help businesses run cleaner, calmer, and more confidently.

We’re not finished — and we probably never will be because as businesses evolve, so should the systems that support them.

And we’ll keep building IndyForms the same way it started – from the real world, not a whiteboard.