All articles
For NDIS providers

Choosing NDIS reporting software: a plain checklist

A handwritten checklist on a clipboard beside a closed laptop and a pen on a desk.
Photo by RDNE Stock project on Pexels

9 min read

A plain checklist of questions to ask any reporting tool before you buy: where each number comes from, who owns the data, and what the tool can show at audit time. No prices and no rankings.

Before you buy NDIS reporting software, ask four plain questions: where does each number come from, who owns it, what can the tool show at audit time, and can you take your data with you if you leave. This checklist is for NDIS providers to read out loud in a demonstration. No prices, no rankings.

In short

  • Ask where each number comes from, who owns the data, what the tool shows at audit time, and how you export it.
  • A reporting tool measures almost nothing itself. Every figure is read from a system you already run, so the data source list matters most.
  • Put data ownership in the contract: who holds it, where it is stored, who may see it, and what happens when the agreement ends.
  • A dashboard shows where things stand at the last load. An audit-ready report can be re-created for a past date.
  • Compare tools by sending every vendor the same written questions and scoring the answers against your own systems.

Where the numbers come from

NDIS reporting software gets its numbers from systems you already run: rostering and payroll, your client management system, the finance ledger, the incident register, and the spreadsheets people keep on the side. A reporting tool rarely measures anything itself, so the quality of your reporting is set by the quality of those sources.

Ask for a data source list, line by line, for the numbers you care about. For each one:

  • Which system does this figure come from, and which field in it?
  • How does the data get across: a file export you send, a report the vendor collects, or a direct link the two vendors set up together? A tool that can connect to your rostering system is not the same as a tool that already reads it. Ask what the setup involves and who does the work.
  • How often does the data load, and at what time of day? "Up to date as at last night's load" is an honest answer. Anything that sounds instant deserves a second question.
  • What happens when a source file is late or missing? Does the report show yesterday's figure with no warning, or does it say the data did not arrive?
  • Who fixes a wrong number, and how long does a fix take to appear in the report?

If a vendor cannot name the source of a figure in one sentence, nobody in your organisation will be able to either. That is where trust in reporting usually breaks. Our post on five mistakes that make new provider reports untrusted covers what that failure looks like in practice.

Who owns each number inside your own organisation

Every number in a report needs a named owner inside your provider, and the software should make that owner visible. Ownership here means two things, and both matter: who decides what the number means, and who is accountable when it moves the wrong way.

The definition is the harder half. "Utilisation" can mean billed hours over rostered hours, or billed hours over funded hours, or something else again. Two managers using the same dashboard with two definitions in their heads will argue about the chart instead of the service. Ask the vendor:

  • Can we write our own definition beside each measure, in our own words, and can a reader see it without leaving the page?
  • Can we change a definition later, and does the change record when it took effect, so older reports still make sense?
  • Can we name a person or a role as the owner of a measure?
  • Can two teams have different views without two versions of the truth underneath?

A tool that records definitions and owners turns a reporting argument into a short conversation.

Who owns the data once it is in the tool

Data ownership is a contract question, so ask for it in writing before you buy, not after. You want the agreement to say plainly that your provider owns the data you put in, that the vendor holds it on your behalf, and what the vendor may and may not do with it.

The questions worth asking:

  • Where is the data stored, and in which country? Personal information sent overseas brings extra obligations under Australian Privacy Principle 8 (Australian Privacy Principles quick reference, OAIC, as at September 2026).
  • Who at the vendor can see participant level data, under what conditions, and is that access logged?
  • Is our data used to train anything, or pooled with other organisations for comparison? If the answer is yes, ask to see the clause.
  • What happens at the end of the agreement: how long is the data kept, how is it returned, and how is it destroyed? Australian Privacy Principle 11 covers securing personal information and destroying or de-identifying it in certain circumstances (same source, as at September 2026).
  • How would the tool help you answer a request from a participant who asks what you hold about them, which sits under Australian Privacy Principle 12 (same source, as at September 2026)?

None of this is legal advice. Read the official principles and take advice on how they apply to your service.

What the tool can show at audit time

At audit time you need evidence for a past period, not a picture of today, so ask whether the tool can re-create a report exactly as it stood on a given date. That single question separates reporting tools quickly.

Registered providers are measured against the NDIS Practice Standards, which are grouped into modules covering matters such as provider governance and operational management (NDIS Practice Standards, NDIS Quality and Safeguards Commission, as at September 2026). Auditors work from evidence, and evidence has a date on it. Useful questions:

  • Can we produce this report as at 30 June last year, with the data as it was then, not as it is now?
  • Does every export carry the date range, the source systems and the time the data was loaded, printed on the page?
  • Can we see who changed a definition, a target or a threshold, and when?
  • Can we attach a note to a figure explaining an exception, so the explanation travels with the number?
  • Can a report be marked as reviewed and approved by a named role, with the date?

Audit-ready reports are boring by design. Every figure carries its source and its date, and nothing about it changes after the fact without leaving a mark.

How you get your data back out

Ask for a full export of your own data, on demand, in an open format, at no extra charge, and ask to see one during the trial rather than taking the answer on trust. Switching costs are paid at the end of a relationship, and they are agreed at the start of one.

Test for these:

  • A complete export, not just what is on the screen: history, definitions, thresholds and notes.
  • An open file format such as CSV, readable without the vendor's software.
  • No fee, no notice period beyond something reasonable, and no dependence on goodwill.
  • A written statement of how long you keep access after the agreement ends.

If exporting your own data needs a support ticket and a quote, you do not really hold it.

How to compare tools without prices or rankings

Compare reporting tools by sending each vendor the same written list of questions and scoring the answers yourself, rather than reading rankings written by someone who does not know your systems. A ranking cannot know that your rostering data lives in one system and your incidents in another.

A simple way to run it:

Step What to do
1 List the ten numbers your board and your service managers actually use.
2 For each one, write the source system and the person who owns the definition.
3 Send the same questions from this checklist to every vendor, in writing.
4 Score each answer as yes, no, or "with work", and note who does the work.
5 Ask for a trial using two of your own real exports, not the vendor's sample data.

The trial is where most of the truth comes out. Sample data always looks tidy. Your data has a service that closed in March, a pay code nobody can explain, and three spellings of the same suburb. Before you start, it helps to know where NDIS admin time goes, and how to measure it, so you can tell whether a tool removes work or moves it. You can also read how we think about reporting for NDIS providers.

Common questions

Where does NDIS reporting software actually get its numbers from?

NDIS reporting software reads its numbers from the systems you already run: rostering, payroll, client management, finance and your incident register. Very little is measured by the reporting tool itself, so ask for the source of each figure, field by field, and ask how and how often the data loads.

Who owns the data once it is in a reporting tool?

Your provider should own the data it puts into a reporting tool, with the vendor holding it on your behalf, and the agreement should say so in plain words. Check where the data is stored, who at the vendor can see participant level information, whether it is used for anything else, and what happens to it when the agreement ends.

Can we export our own data if we switch reporting software later?

Ask for a full export in an open format, on demand and at no extra cost, and test one during the trial. A complete export includes history, definitions and thresholds, not just the figures currently on screen.

What is the difference between a dashboard and an audit-ready report?

A dashboard shows where things stand as at the last data load and is built for a quick look. An audit-ready report is fixed to a period, carries its source systems, date range and load time on the page, and can be produced again months later with the same result.

How do we compare reporting tools without a price list or rankings?

Compare tools by asking every vendor the same written questions about data sources, ownership, audit evidence and export, then scoring the answers against your own systems. Finish with a trial on two of your own exports, because a rank order written by a stranger cannot know which systems you run.

Sources

Questions about your own reporting?

Tell us what you need to see each week. We will show you how it could look, using our example company.