We recently launched Teiro — a workforce management platform for Australian disability support providers, aged care operators, and community health organisations. It handles scheduling, carer communication, compliance tracking, and client records in a single mobile-first tool.

Building it taught us things about software development in the care sector that we didn't expect going in.

The tools most care providers use would shock you

Before writing a line of code, we spent time with care coordinators watching how they actually worked. The pattern was consistent: a spreadsheet for the roster (shared, not always in sync), a WhatsApp group for communicating with carers, a shared drive full of Word documents for compliance records, and a coordinator's personal phone as the de facto communications system.

This isn't because care organisations don't know better tools exist. They do. Most have tried at least one. The problem is that the workforce management tools on the market were largely designed for hospitality, retail, or construction — and adapted for care with the rough edges left on. They handle the basic scheduling problem but don't understand care-specific constraints: NDIS support ratios, participant compatibility, qualification requirements by support type, the audit implications of every communication.

So coordinators use the general tools for the parts that work, and fall back to WhatsApp and spreadsheets for the parts that don't. The result is a hybrid that's worse than either.

Compliance isn't a feature — it's the foundation

In most industries, compliance features are something you add to a product that already works. Audit logs, access controls, record retention — they come after the core workflow is built.

In care, compliance is the core workflow. An NDIS provider is operating under the NDIS Practice Standards, the NDIS Code of Conduct, the Privacy Act, and potentially state-based disability legislation. Everything the software does — who can see what, how incidents are recorded, how communications are stored — has compliance implications.

We had to build the audit trail, the access controls, and the record-keeping before we built the features people would see. The scheduling board is what coordinators notice. The immutable activity log underneath it is what makes the scheduling board safe to use in a regulated environment.

The lesson: if you're building software for a regulated industry, map the compliance requirements first. They'll constrain your data model, your permission system, and your infrastructure choices in ways that are very expensive to retrofit later.

Real-time matters more than we expected

We knew real-time updates would be important. We didn't appreciate just how much of the product's value depended on them.

Care scheduling is dynamic in a way that shift work in other industries often isn't. A support worker calls in sick at 6am; a coordinator needs to find a replacement, check qualifications, confirm the replacement is available, and notify the participant's family — all before the shift starts at 8am. If the coordinator makes a change and the carer's app updates in 30 seconds, that's a usable system. If it updates when the carer next opens the app, it isn't.

We used Laravel Echo with Pusher for real-time updates throughout the platform. The coordinator's scheduling board reflects changes the moment they happen; carer notifications land within seconds. Building this properly from the start — rather than bolting on real-time later — made a significant difference to how the product felt in use.

The mobile app is the product (for half the users)

We built Teiro as two distinct applications with different design priorities: a web-based scheduling and coordination tool for office users, and a native iOS/Android app for carers in the field.

The carer app is used on the go, often in poor connectivity, by people who aren't primarily tech workers. It needs to be fast, reliable offline, and require minimal training. GPS check-in, shift notes, incident reporting, document upload, signature capture — all on a phone, in a client's home, with one hand.

React Native with Expo let us build a native-quality app from a single codebase. We built offline support throughout — carer data syncs when connectivity allows, not when it's required. A carer's day shouldn't stop because a client's home has poor reception.

The lesson: when half your users are mobile-first, mobile isn't a secondary channel. The mobile app's quality directly determines whether carers actually use the system or fall back to text messages.

Why the audit trail is the most important feature nobody talks about

When we showed early versions to care coordinators, they got excited about the scheduling board. When we showed it to operations managers and compliance leads, they got excited about the communications log.

Care organisations live in fear of regulatory investigations. When the NDIS Commission investigates an incident or a complaint, they want to see evidence: what was communicated, when, by whom, with what response. If that evidence is in WhatsApp, it's gone — message histories deleted, numbers changed, no way to reconstruct the timeline.

Teiro routes all staff communication through the platform: SMS from the organisation's number, email logged against the relevant carer and client records, call notes recorded with timestamps. Everything is stored, searchable, and exportable as a PDF audit pack. That feature doesn't appear on any screenshot. It's the reason several organisations decided to switch.

Building for a sector that needs it

The care sector employs hundreds of thousands of Australians and supports some of the most vulnerable people in the community. It runs on spreadsheets.

There's genuine opportunity to build software that makes coordinators' jobs less chaotic, reduces compliance risk for providers, and ultimately frees up more time for actual care delivery. We're still early with Teiro — we're learning from providers using it, shipping improvements weekly, and being honest about what it does and doesn't do yet.

If you're running a disability support service, aged care organisation, or community health provider and the spreadsheet description sounds familiar, Teiro is worth a look. If you're building software for the care sector and want to compare notes on the technical decisions, get in touch.

---

See also: Teiro case study · What does an NDIS provider app need? · Healthcare data compliance · Audit trail · Real-time updates