Article Image

The Budget Wants Evidence Most Care Programs Cannot Produce

Samuel Wyndham · 8th September 2026

The 2026–27 federal budget quietly raised the bar on what your program has to prove.

Most of the coverage went to the headline numbers — beds, packages, savings. The part that matters if you run a funded program is smaller and further down: the money is increasingly attached to whether you can demonstrate something, not just deliver it.

What the Budget actually says

On aged care, $565.1 million is going to sector quality, safety and viability, sitting inside a $3.7 billion package that also funds up to 5,000 new beds a year and accelerates the release of Support at Home packages. On the NDIS, the direction is oversight: more scrutiny of providers and payments, stronger investigative and enforcement capability inside the NDIA, and new regulatory controls — against a projected $37.8 billion in scheme savings over four years.

Read those two together and the shape is obvious. There is money in the system, and there is a much sharper set of eyes on who gets to keep it.

Three words keep appearing: quality, safety and viability.

The first two everybody expects. Viability is the one people skim past, and it is the one that will catch programs out.

Viability is not a finance question

It is easy to read "viability" as an accountant's word — margins, reserves, whether the balance sheet holds up. That is part of it, and the financial reporting obligations on aged care providers already run in that direction.

But in practice it means something broader and more uncomfortable: your program has to work, and you have to be able to show that it works.

Not describe it. Not assert it in a narrative section of an annual report. Show it, with data that was captured at the time, by the people doing the work, in a form somebody outside your organisation can check.

Here is the problem, and it is worth saying plainly:

The evidence the government needs in order not to cut your program is exactly the evidence most programs cannot produce.

Why paper will not survive this

I have sat in enough back offices to know what report season actually looks like in a program that runs on paper, spreadsheets and goodwill. Three things go wrong, every time.

Too much follow-up. The information exists, but it exists in pieces, and each piece is held by a person. So report time becomes a chase — ringing the coordinator who was at the remote site in June, asking the support worker to remember a visit from four months ago, waiting on somebody who is on leave. The data is not missing. It is just distributed across humans who have moved on.

Too many places. A form here, a shared drive there, a WhatsApp thread, a paper file in a cabinet at a second site, a spreadsheet somebody built themselves because the official system did not do what they needed. Nobody designed this. It accumulated.

Report time is a nightmare, and what you report may not even be true.

That last one is the real risk, and it is the one I would lose sleep over.

An inaccurate report is worse than a slow one

When a funder is assessing quality, safety and viability, a late report is an administrative problem. An inaccurate one is a credibility problem.

And the way inaccuracy gets in is almost never dishonesty. It is reconstruction. When the underlying record is thin, somebody sits down at the end of the quarter and builds the number from memory, from partial notes, from what feels about right. Everyone in the chain is acting in good faith. The number still ends up wrong.

Then it gets worse: that number becomes the baseline. Next quarter is compared against it. A year later there is a trend line built on a figure somebody estimated on a Thursday afternoon.

If your reporting is reconstructed rather than recorded, you are not just risking a bad quarter. You are risking the moment somebody checks.

What to do about it, starting this week

If I were running a funded program right now, I would do one thing before anything else, and it is not buying software.

List every place your data comes from.

Every form, every book, every spreadsheet, every phone that photographs a signature, every whiteboard somebody photographs at the end of a shift. Walk the actual process and write down where information is created — not where you think it is stored.

That list is usually longer than management expects, and the surprises are the informal ones: the workarounds staff invented because the real system was too slow. Those are not a discipline problem. They are a design brief.

Then digitise those sources — at the point of capture, not afterwards. The distinction matters more than any product choice. Data typed up later is data reconstructed later. Data captured while the work is happening is evidence.

When the government asks, you want to know exactly where it is — not be rummaging through someone's desk drawer.

Paper for thinking, not for proving

There is a fair objection here, and it is one I have made myself. I recently wrote about throwing out my AI tools and going back to a journal and a pen, and I meant it.

Both things are true, and the line between them is clean. Paper is excellent for thinking — for holding a problem in your own head instead of outsourcing it. Paper is terrible for proving, because proving is a collective act across time and people, and paper does not travel.

Your notebook is yours. Your evidence belongs to everyone who will ever audit it.

The window

Nothing in the Budget lands tomorrow. Funding measures phase in, regulatory changes get consultation periods, and the reporting expectations tighten by degrees rather than overnight.

That is the opportunity. Programs that start mapping and digitising their data sources now will be answering questions comfortably in twelve months. Programs that wait will be doing it under assessment, which is a much more expensive way to find out that your intake form was never capturing the field the funder cares about.

If you want a hand working out where your program's data actually lives and what it would take to make it reportable, come and have a chat with us — we do this work with health and community providers across WA, including outcome reporting for funded programs. Or get this kind of thinking weekly.

Want to see how you can upgrade your IT and be even more productive?