Participants

One record, and the
right people see it.

Participant information is scattered across rosters, notes, plans and inboxes. That is a quality problem before it is an admin problem, because the support worker who needs context most often has the least.

Book a leak check

The record

Plan, goals and
what was delivered.

Plan start and end, funded supports, goals, and the history of what has actually been delivered against them. Kept as one record rather than assembled from four systems when a review comes around.

Access follows the person's role, so a support worker sees what they need for the shift and not the rest.

Plan dates

renewal is never a surprise

Plan end dates tracked, so a review is prepared for rather than discovered.

Goals

linked to what was done

Supports recorded against the goal they serve, which is what a review actually asks about.

Access

by role, not by trust

Sensitive information is limited by design rather than by everyone agreeing to be careful.

The rest of the family

Same build, shaped for
a different trade.

Each one is the same idea — your quoting, your jobs, your invoicing, in one system you own — fitted to how that trade actually works. Built in Brisbane by Kindra AI.