Why care technology must be built by operators

I never set out to build software. I set out to run a good disability support business. The software came later, because the tools available to me kept failing at exactly the moments that mattered.

A rostering system that could not tell me a worker's screening was about to expire. A notes app that let staff write anything, in any format, and then left me to defend those notes in an audit. A payroll tool that treated a sleepover like an ordinary shift and quietly underpaid my team.

Each of those tools was built by capable people. None of them was built by someone who had ever been audited, ever stood in a participant's home at 2am, or ever had to explain a SCHADS calculation to a support worker who had been paid wrong.

That gap is the whole story of care technology.

Regulated work is different work

In most industries, software can be built from the outside in. You interview users, map a workflow, ship something and iterate.

Regulated care does not work that way. The rules are layered: legislation, practice standards, pricing arrangements, an industrial award, state screening requirements and your own policies. The rules interact. A single shift can touch all of them at once.

If the people designing the system do not understand those layers, they build software that looks right and is wrong. Wrong in ways that only show up when an auditor asks for evidence, a participant makes a complaint, or a worker checks their payslip.

What operators know that outsiders miss

Compliance is a workflow, not a report. Outsiders bolt compliance on at the end, as a dashboard. Operators know it has to be built into the moment the work happens. The best time to capture a progress note properly is during the shift, not three days later.

Edge cases are the normal case. Broken shifts, sleepovers, travel between clients, a participant in hospital, a worker covering at short notice. In care, these are not exceptions. They are Tuesday.

Every field has a consequence. When an operator designs a form, they know which answer will be read by an auditor, which will drive a payment and which will end up in a complaint file. That changes what you ask and how you ask it.

The frontline has no time. Support workers are not sitting at desks. Software that adds five minutes to every shift will be worked around, and the workaround becomes the risk.

Why this matters more now

The NDIS is moving firmly toward evidence. Providers will be expected to keep claim records for years, enrol, register and show their working. That makes the quality of your systems a compliance question, not just an efficiency question.

When the system is built by people who understand the obligations, good practice becomes the easy path. When it is not, every obligation becomes extra work layered on top of a tool that was never designed for it.

How I built differently

I built LAMA CMS over five years from inside District 360. Every feature started as a real problem in a real service: a missed screening, a payroll error, an audit finding, a coordinator drowning in spreadsheets.

We did not guess at requirements. We had them, every week, in the work. We used every feature in our own services, with our own staff, before anyone else saw it. When an audit report came back, we turned the findings into the roadmap.

That is not a marketing line. It is the only way I know to build software that holds up when it is tested by the people who regulate us.

What to ask before you buy

If you are choosing a system for a regulated care business, ask the vendor:

1. Who on your team has run a registered provider, and for how long?
2. Show me how your system evidences a single claim, from service agreement to invoice.
3. How does it handle a broken shift, a sleepover and travel under the award?
4. What happens when a worker's screening or training expires mid roster?
5. When the rules change, how fast does your product change, and who decides?

The answers will tell you whether the software was built for the work, or built near it.

Technology in regulated industries has to be built by people who carry the consequences of getting it wrong. In care, those people are operators.