Resident data, taken seriously.

• Higher Everyday Living (HEDL) opt-ins (drinks, breakfast, Wi-Fi, Foxtel) are recorded against the resident profile, not held in a manager’s spreadsheet, and roll into the daily charge automatically.
• Per-resident dislikes captured separately from clinical allergens, so personal preference is honoured without losing safety signal.V2 preview
• Standing breakfast / lunch / dinner orders editable by care staff; the kitchen receives them automatically each morning.V2 preview

• Single resident record per facility — no duplicate clipboards by shift, by wing, or by language.
• Open-text dietary, cultural, and religious preference fields on the resident profile, so context is not lost when staff change shifts.

Roadmap: Structured cultural / language metadata, and surfacing those preferences on every order screen, is on our roadmap.

• Allergens captured as structured dietary tags; resident profiles surface them prominently on the residents list and on every order screen.
• Resident-absence flow keeps meal counts honest — no phantom trays, no missed meals — and is auditable per shift.
• IDDSI fluid (0–4) and texture (3–7) levels exposed on the order screen, kitchen ticket, and PCA/GSO print-out so staff cannot serve a non-compliant tray by accident.V2 preview
• Clinical "watch out" notes (aspiration, choking, anaphylaxis, diabetic) render with high-contrast warnings on every surface that touches that resident.V2 preview

• Row-level security in the database scopes every read and write to the resident’s facility and the staff member’s role.
• Audit log table records inserts, updates, and deletes against clinical and resident records for review by the registered provider.
• All resident data hosted in Sydney (ap-southeast-2); no resident data leaves Australia.

• Day-75 trial-end alert drafts a family message providers can copy into their existing communications tool, creating a written record.
• Family contact captured on every resident profile; available to care staff alongside clinical context.
• Feedback / complaint flow on our roadmap; in v1 providers should continue to use their existing complaints management system as required by the Act.

• Family contact field is the v1 anchor for the registered-supporter relationship under the new Act.
• Standing meal preferences travel with the resident, so connection to comfort foods is not lost when staff change shifts or wings.V2 preview

Roadmap: A first-class "registered supporter" record (with My Aged Care alignment) is on our roadmap.