How to Switch from a Spreadsheet-Based NDIS Operation Without Losing the Audit Trail

Most small-to-mid NDIS providers stay on spreadsheets 18 months longer than they should. Not because the spreadsheet works — it stopped working at ~15 workers — but because the spreadsheet IS the audit trail. Switching software means risking 12 months of evidence the auditor expects to see.

If you've been running rostering, claims, progress notes, and compliance tracking across 4-6 spreadsheets (sometimes more), you already know the cost: the operations manager spending 8-12 hours/week reconciling, the bookkeeper missing PACE rejections, the audit prep that consumes the team for two weeks every year. But the fear is real and worth naming: a botched migration leaves you unable to produce a clean audit pack for the months before the switch.

This post is the operational framework providers who've made the switch successfully use. It's not vendor-specific — the pattern works whether you migrate to Tendaroo, ShiftCare, SupportAbility, or any other NDIS platform.

Why spreadsheets feel safer than they are

The spreadsheet's strength is also its risk profile:

• One source of truth, sort of. Everyone in operations knows where the master file is. Until the maternity-leave cover saves a copy locally and the team works off two versions for a fortnight.
• No vendor lock-in. You own the data, you can export at any time. Except when the macros break and no one remembers who wrote them.
• Cheap. Until you calculate the operations manager's hourly rate × 10 hours/week of reconciliation.
• Audit-tested. You've been audited before with it. So the temptation is to never change.

The hidden cost compounds in three places:

1. Worker compliance tracking scattered across HR sheet + manager memory + email
2. Plan funding burndown updated weekly, manually, with maths errors
3. PACE claim reconciliation never quite caught up to actual paid amounts

The "audit pack survived" benefit is real but increasingly rare. What we hear most from providers in the 15-30 worker range: "we passed our last audit but it took two weeks of preparation and we know we couldn't do it again at our current pace." That's the signal you've outgrown the spreadsheet.

The 4 audit-trail risks when migrating from spreadsheets

Auditors don't care which software you use. They care that you can produce, on demand:

1. Versioning — what was the rostered hours for shift X on date Y? The spreadsheet has the latest version. If someone updated the cell between then and now, the original is gone. Software with proper change-tracking preserves both.
2. Completeness — every shift delivered must have a progress note. The spreadsheet might list 200 shifts; the progress notes might be in 200 separate Word documents in a SharePoint folder. The auditor wants the pairing.
3. Time-locked snapshots — what was the participant's plan status on the date the support was delivered? Plans expire and get replaced. The current version isn't what you should be billing against for past shifts.
4. Signatures and acknowledgments — Code of Conduct signed by each worker at hire AND annually. NDIS Worker Orientation Module completion dates. Restrictive practice authorisation versions.

The fear isn't unjustified: a migration that doesn't preserve these four dimensions leaves you with software that works going forward but an audit pack that has a hole where the spreadsheet years used to be.

The 3-step migration pattern that keeps the audit trail intact

Providers who've migrated cleanly all follow the same operational pattern. The vendor matters less than the discipline.

Step 1 — Freeze the spreadsheet and lift it as an artefact

Before importing anything into the new software:

• Snapshot the spreadsheet as PDFs. Every sheet, every tab, as of the cutover date. This becomes the "as of [date]" reference document. Store the PDFs in three places: cloud drive, encrypted local backup, and printed-out hard copy in your compliance folder.
• Export every cell to CSV. Even if you'll only import a subset, the CSVs are your fallback if you ever need to reconstruct a row from before the switch.
• Document the spreadsheet structure. Which sheet held what, which columns meant what, which workers were tracked where. A one-page "spreadsheet index" written at cutover saves you a week of forensics during an audit 18 months later when nobody on the team remembers.

The spreadsheet, frozen and archived, is now your historical audit pack for everything before the cutover date. Software handles everything after. The two stitch together as one audit record because you can produce both halves on demand.

Step 2 — Import only the master-record data, NOT the historical transactions

The mistake providers make: trying to import every shift, every progress note, every claim from the spreadsheet into the new software. This creates new problems (data quality issues compound, the new system gets polluted with messy historical rows) without solving the audit problem (the spreadsheet PDF + CSV already covers the historical period).

What to import into the new software:

• Participant master list — current participants, NDIS numbers, plan dates, plan management type, funding category breakdowns, current goals, current Service Agreement
• Worker master list — current workers, NDIS Worker Screening Check dates, qualifications with current expiry dates, NDIS Worker Orientation Module completion date
• Service item catalogue — mapped to the current NDIS Pricing Arrangements (the live one from ndis.gov.au, not the stale codes that have been in your spreadsheet for 18 months)

What NOT to import:

• Historical shifts (lives in the frozen spreadsheet)
• Historical progress notes (lives in your document storage)
• Historical claims (lives in your PACE export history + bookkeeper records)
• Historical incidents (lives in your incident register PDFs)

This separation keeps the new software clean and the audit pack continuous: software produces the post-cutover record, frozen spreadsheet produces the pre-cutover record, both are date-bounded.

Step 3 — Run a 30-day parallel record period

For the first 30 days after cutover:

• Run all rostering, progress notes, and claims through the new software (it's now the source of truth)
• ALSO maintain the spreadsheet in shadow mode — update it weekly with the same data
• At end of week 4, reconcile the two — they should match
• If they don't, the new software has a configuration issue you need to fix BEFORE you stop the parallel record

Most providers we've talked to want to skip this step. Don't. The 30-day parallel run is what catches the 80% of configuration mistakes that would otherwise hide until your next audit. After Day 30, archive the parallel spreadsheet (it's now part of the frozen historical record) and the new software is your sole live system.

The audit-pack benefit: if you're audited within 12 months of switching, you produce frozen spreadsheet (pre-cutover) + parallel spreadsheet (30 days post-cutover) + software exports (Day 31 onwards) as three contiguous date-bounded artefacts. The auditor's job is easier than it would have been with a single messy migration.

What breaks the audit pack post-migration

Even providers who follow the 3-step pattern can break the audit trail with these common mistakes:

• Updating the frozen spreadsheet. Once it's frozen at cutover, it stays frozen. If you find a typo, document the correction in a separate "corrections log" — never edit the snapshot.
• Losing track of the spreadsheet PDFs. Three storage locations isn't paranoia. One ransomware incident, one hard-drive failure, one departed staff member who archived the cloud drive to their personal Google account — and the historical audit pack is gone.
• Mapping NDIS support items to the wrong codes during import. The catalogue refreshes annually on 1 July. If you import using last year's codes, every claim from cutover forward is wrong until you re-map. Always import against the current Pricing Arrangements.
• Skipping the parallel run. The 30-day shadow period feels redundant. Then the auditor asks about a specific shift in week 2 post-cutover and you can't produce the same record from both systems. Skip → discover problem 11 months later.
• Letting workers keep using the spreadsheet "for now". If anyone is still updating the spreadsheet after Day 30, you have TWO partial audit trails neither of which is complete. Hard cutover.

The 7-question pre-migration self-check

Before you start the migration, answer these honestly:

1. Do I have all the spreadsheets in one place, with one person owning each?
2. Do I have at least 12 months of progress notes paired to their shifts, in some retrievable form?
3. Do I have current copies of every worker's compliance documents (Screening Check, First Aid, Manual Handling, Orientation Module completion)?
4. Do I have current Service Agreements for every active participant?
5. Do I know which NDIS Pricing Arrangements version my spreadsheet uses?
6. Do I have a named person who will own the migration end-to-end (not "the team")?
7. Do I have a 60-day window where I can run parallel records without missing claim cycles?

If you scored 5 or below, the migration project should be preceded by 4-6 weeks of data hygiene work. Switching software while the underlying records are messy guarantees you import the mess and the audit pack inherits it.

If you scored 6-7, you're ready to migrate cleanly.

What Tendaroo does about spreadsheet-to-software migrations

We've helped providers through this exact pattern. Our migration playbook builds in the freeze-the-spreadsheet step, gives you the import CSV templates that map to the current NDIS Pricing Arrangements automatically, and runs the 30-day parallel reconciliation against your spreadsheet to catch configuration mistakes before they reach the audit pack.

If you're sitting on a spreadsheet-based operation that's growing past its limit and you want to walk through the migration framework with someone who's built the tooling for this specifically: start a 30-day free trial — no credit card, no demo gate. We're founder-led right now, so the onboarding call is with someone who has been in the middle of these migrations and can tell you straight which step is hardest for your specific operational shape.

And if you want the operational reference doc your team should be working from during the migration: the NDIS Audit Preparation Checklist (PDF) covers the audit-trail continuity requirements in depth, and the PACE Claim Reconciliation Template (PDF) is the spreadsheet template that survives the freeze step and becomes your post-cutover reconciliation discipline.