MySienna

The problem

A support coordinator's tooling is usually an accident of history. A calendar in one place, appointments in another, client files on a shared drive, service agreements chased over email, case notes in a separate document. Five tools, a dozen tabs, and one very long day.

None of those tools is bad. The problem is that the participant exists in all five of them and is identical in none. Coordination is a job about keeping track of people, and the software was making that harder rather than easier.

What we built

Eight modules that share the same participant record: participant management, scheduling and appointments, billing and invoicing, NDIS bulk claims, e-signature and forms, incidents and compliance, budgets and funds, and goals and tasks.

The word doing the work in that sentence is share. They are not eight products with integrations between them. There is one participant, and each module is a different question asked of the same record — which is why nothing has to be re-keyed and why the modules cannot drift out of agreement with each other.

The parts that were genuinely hard

Business-day arithmetic, taken seriously

The NDIS Commission expects reportable incidents inside twenty-four hours, and certain matters within five business days. "Five business days" sounds trivial until you write it: it has to know about weekends, and public holidays, and which state's public holidays, and what happens when an incident is recorded at 4:58pm on the Thursday before Easter.

We decided the coordinator should never have to do that arithmetic. The deadline is computed when the incident is recorded and shown as a countdown on the record itself. This is a small feature that quietly removes an entire category of compliance failure.

E-signature as a feature, not a subscription

Consent forms and service agreements are the beginning of every engagement, and the industry norm is to bolt on a per-seat e-signature vendor — a second bill, a second login, and a signed PDF that lives outside the system that needs it.

Building it in meant taking on the parts that make an electronic signature actually hold up: clear evidence of intent, the IP address and timestamp recorded against the act, and the document frozen as a PDF at the moment of signing so what was agreed to cannot quietly change afterwards. The result is that a signed agreement is part of the participant's record rather than an attachment someone has to find.

The full claim loop

Claims are where coordination software usually stops and a finance tool starts. MySienna runs the loop end to end: agency-managed claims are exported as a validated bulk file for the government portal, the pricing catalogue is synced when it changes each first of July, and remittance is reconciled back against the billables that produced it.

Invoices for plan-managed and self-managed participants come off the same billables, so the same delivered service never has to be described twice in two different formats.

A history that cannot be quietly rewritten

Disability records are among the most sensitive held by any Australian business, and the question at audit is not only what the record says now but what it said before. Every write is recorded with the user, the timestamp and the before-and-after state, in an append-only log that is hash-chained so tampering is detectable rather than merely discouraged.

Alongside it: Australian data residency, field-level encryption for the most sensitive fields with organisation-scoped keys, multi-factor authentication, role-based access, and isolated tenants so one organisation can never reach another's records.

Restraint as a design position

The hardest engineering decision on this product was what not to build. The market is crowded with platforms that do everything and are learned by nobody. MySienna is deliberately the simple one: the features a coordinator actually needs, working the way they would expect, with no AI gimmicks and no learning curve — because software that a team can pick up in an afternoon gets used, and software that needs training does not.

One system, three jobs

Coordinators need their caseload front and centre. Finance needs to turn delivered services into invoices and claims and watch budgets across the organisation. Owners need multi-organisation separation, role-based access and an audit trail for every change. Those are genuinely different products from the user's point of view, served by one record underneath.

What it demonstrates

MySienna and CareOp sit in the same sector and solve different jobs, which is the point. The reusable engineering underneath — one authoritative record, computed compliance, a government claiming integration that reconciles, and a tamper-evident history — is the shape of most serious operational software, whatever industry it serves.

← All case studies