Skip to content
FUSSHAUS

NDIS progress reports, written from the notes your team already takes.

Shift notes and plan goals go in. A draft report for every participant comes out, ready for your coordinator to check and send. Data never leaves Australian servers.

reports.yourprovider.com.au
Works with
  • ShiftCare
  • Zoho CRM
  • Microsoft 365
Brevity, Lumary and Careview on request

How it works

01

Notes and goals come in

On the first of the month the system pulls last month's shifts and notes from ShiftCare, and each participant's plan goals and contacts from your CRM or spreadsheet.

02

A draft is written against the goals

Every participant gets a report in your voice, structured around their own plan goals. A checking step blocks anything that names another participant, invents a goal, or includes detail that should not go to a family.

03

Your team approves

A coordinator opens the dashboard, reads each report next to the notes it came from, and approves it, asks for a change in plain words, or rejects it. Nothing goes out without a person.

04

Reports go out on your letterhead

Approved reports become PDFs on your letterhead and go from your own email address to the guardian and support coordinator on file. A copy is kept against the participant record.

Privacy and compliance

Participant information is sensitive, and the NDIS Quality and Safeguards Commission expects providers to protect it, registered or not. Here is exactly how the system handles it.

Where data is stored
In a database hosted in Sydney, on Australian infrastructure.
What the AI sees
Stand-ins only. Names, NDIS numbers and addresses are swapped out before any text reaches an AI model, and swapped back after. Real identifiers never leave Australia.
Training on your data
None. We do not use your data to train AI models, and the commercial terms we use with our AI provider do not train on it either.
Who approves reports
A named person on your team, every report, every month. Each approval is logged with who and when.
Access
Read-only keys that you issue from your own ShiftCare and CRM accounts, and that you can revoke at any time.
Privacy and standards
Built around the Privacy Act and the Australian Privacy Principles, and to support your NDIS Code of Conduct and Practice Standards record-keeping. Your organisation stays accountable. We give you the evidence, a list of the providers we use, and a paragraph for your privacy policy.

What it does not do

  • Make clinical or behavioural judgements, or give legal or compliance advice.
  • Send anything without a person approving it.
  • Submit anything to the NDIS portal, or change what is in ShiftCare.
  • Fix missing data. Gaps show up on a monthly list so your team can fix them.
  • Reduce what your team is accountable for.

Five questions to ask every vendor, including us.

These are the questions we would ask if we ran a provider. Here are our answers.

01Where is participant data stored?

In Sydney. The one thing that crosses the border is de-identified text, and only to the AI provider.

02What does the AI model actually see?

Stand-ins for names, NDIS numbers and addresses. If a record cannot be de-identified, it is held back, not sent.

03Does a person approve every report?

Yes. The system drafts and your team decides. Each approval is logged.

04Is our data used to train AI?

No.

05What happens if we leave?

You export your data and your reports. Your data is then deleted from our systems under the terms of the agreement.

Common questions

Where does our participant data go?

Your shift notes and goals are temporarily stored in a local database here in Australia. Before any text reaches an AI model to generate your reports, names, NDIS numbers and addresses are swapped for stand-ins, and swapped back after. Real identifiers never leave Australia. We give you a subprocessor list and a paragraph for your privacy policy as part of setup.

We use ShiftCare. Does it need anything special?

No. We connect with an API key you issue from your own account, read only. Your mentors keep writing notes the way they do now. If you are on Brevity, Lumary or Careview, ask, the same pattern applies.

Does this replace the coordinator's sign-off?

No. Every report is read and approved by a person on your team before it goes anywhere. The system removes the drafting, not the accountability. The dashboard records who approved what and when.

Does it meet the NDIS Practice Standards?

The Practice Standards apply to your organisation, not to a tool. What the system gives you is the evidence: every report is tied to the participant's plan goals, approved by a named person, and logged with the time. Unregistered providers are still bound by the NDIS Code of Conduct, and the same record helps there too.

Can our staff just use a public AI tool for this?

Pasting participant details into a public AI tool is a privacy risk, and the NDIS Quality and Safeguards Commission expects providers to protect participant information when they use AI. Here, identifiers are swapped for stand-ins before any text reaches an AI model, and a person approves every report.

Is our data used to train AI models?

No. We do not use your data to train AI models, and the commercial terms we use with our AI provider do not train on it either.

How is it priced?

Every provider's setup is a little different, so we quote each one. Tell us roughly how many participants you report on and where your notes live, and we will come back with a fixed quote. Never hourly.

What happens in the first month?

A dry run. We generate a full month on your real data, you read every report, and nothing is emailed to anyone. Expect gaps: most providers find a third of participants have no goals or no guardian email on file. The data-quality list tells you who, and coverage climbs from there.

What about billing the report time to plans?

Providers can only claim the time actually spent. A report your staff review in five minutes can only be billed for five minutes. We say this up front because it changes the maths: families' plans pay for less, and more of a shrinking budget goes on actual support.

Who builds and supports it?

Fusshaus is a three-person Adelaide studio. You deal with the people who build and run the system, from the first call to the monthly check-in. We host it, and we keep it working when ShiftCare or your CRM changes.

Do you work with providers outside Adelaide?

Yes. Everything is done remotely, and the system is built for providers anywhere in Australia.

Tell us about your reports.

Business name and a rough participant count is enough. You will get an email in the next few minutes with how it works, and we will follow up to talk through a quote.