Three things, three purposes

Updates go out. Chat stays private. Consent gets collected. None of them mix.

Updates

One post, every family informed

Staff post once. Every family member connected to that resident gets it instantly. It's not email, and it's not a portal families have to remember to check: it's a structured, timestamped record of what happened, and when. That record is also your evidence for Outcome 3.3, pulled on demand rather than assembled after the fact.

Family chat

A private space, just for the family

Families connected to the same resident can talk to each other privately: coordinating a visit roster, working through a decision together, checking whether anyone else saw Tuesday's update. Your staff aren't in this conversation, and Brenna doesn't read it. It's not a support channel and it isn't monitored. It's a space for families to be a family, without it becoming another thing your team has to manage.

Consent Module

Consent, collected once

Vaccination consent, general consent, and allied health access forms, collected and tracked in one place instead of chased down on paper.

Exact capture mechanism (e-signature vs. structured acknowledgement, and whether it feeds a connected clinical system directly) still needs confirming before this section is final.

Integrations

Connects into the systems you already run

Brenna integrates directly with eCase, ManadPlus, Telstra Health Clinical Manager, AlayaCare Residential, LeeCare, and Acredia. Person Centred Software integration is in development. Single sign-on through Microsoft Entra ID means staff use the credentials they already have, and employee roles and permissions are pulled automatically from the connected clinical system rather than set up twice.

See it running in a home like yours