How we work
How we work with aged care providers
Every project runs through the same stages, from a free assessment to a review after go-live. You see a written scope before any paid work, your staff test the system before it is used for real, and you can stop at each review point.
Reviewed 15 November 2026

In short
How we work with aged care providers is simple to describe: one workflow at a time, a written scope before money changes hands, and staff approval at every point that touches a resident, client or family.
A project starts with a free 30-minute assessment, moves to a short discovery with the staff who do the work today, and then to a written scope and quote. After you approve it we build, configure privacy and escalation controls, and run test sessions with your staff using real scenarios.
The system then goes live on a limited scope, such as after-hours calls only or one site, and we review the results against a baseline measured before launch. You supply access, approved content and a named owner. Your staff approve scripts, rules and outputs. We do not make care decisions or claim integrations we have not tested.
Stage 1: free assessment
The assessment is a 30-minute call with a manager who knows where the time goes in your service. We ask about your service type, number of residents or clients, staff structure, the software you use for care records, rostering and finance, and the admin tasks that cause the most pressure. Typical answers are calls at handover, enquiries in voicemail, sick-call shift fills, late progress notes and quarterly reporting.
At the end we tell you whether AI is a sensible fit for one of those tasks, what a first project might look like and what information we would need. Sometimes the honest answer is that a process change, a better phone system setting or a template would solve the problem without AI. We say so when that is the case.
Stage 2: discovery with the people who do the work
Discovery is where the real workflow gets written down. We talk to the receptionist, coordinator, admissions officer, clinical manager or finance officer who does the task now, and ask them to walk through recent real examples with identifying details removed. What comes in, in what form, what they check, who they send it to, and what goes wrong.
We also collect the baseline: a few weeks of call logs, enquiry counts, shift-fill records or report preparation time, depending on the workflow. Without a baseline nobody can tell later whether the change helped.
For example, a home care provider looking at sick-call shift fills might pull four weeks of roster changes and find that 60 visits needed a replacement worker, that each took a coordinator around 15 minutes of calls and texts, and that most of them happened between 6am and 8am. That is 15 hours of coordinator time over four weeks, concentrated in the busiest part of the day. Those are the numbers the new system is measured against.

Stage 3: written scope and quote
You receive a written scope before any paid work starts. It describes what the system will do and what it will not do, which channels it covers, which staff receive its outputs, which data it touches and where that data is stored, the escalation rules, the integrations involved and how success will be measured.
Where the project connects to named software such as a care management, rostering or finance system, the scope states what that system's API allows and what we have confirmed. If a connection has not been tested, the scope says so and describes the fallback, such as a shared inbox, a secure form or a scheduled file export. The quote is based on that scope, and changes to scope are agreed in writing.
Check whether this fits your service
A free 30-minute video call. We look at your call volumes, systems and where staff time goes, and tell you whether this is the right first step. No resident information needed.
Stage 4: build, staff testing and go live
We build and configure the system in a test setting first. For a phone agent that means the greeting, approved answers, intake questions and escalation list. For a documentation tool it means the templates, the review screen and who can approve. For a reporting workflow it means the data sources, the calculations and the output format.
Your staff then test it. They ring the phone agent with real scenarios, including emergencies and difficult family calls. They dictate sample progress notes and check the drafts. They run last quarter's reporting data through and compare the output with what was lodged. We fix what they find and test again. Nothing goes live until the manager who owns the workflow signs it off.
Go live is deliberately narrow: after-hours calls only, one site, one team or one report. The wider rollout comes after the first review.
Governance and privacy controls
Aged care providers handle health information, which the Privacy Act treats as sensitive information. Every project includes these controls as standard:
- A data flow map showing what personal information each part of the system receives, where it is processed and stored, and for how long
- Australian-region hosting where the underlying services allow it, with any exception named in the scope
- Least access: each component sees only the data its task needs
- Human approval for any output that goes into a care record, to a family member or to a regulator
- Escalation rules for urgent or safety matters, tested before go-live
- Call recording and transcripts only if you switch them on, with callers told and retention matched to your records policy
- A written description of the system for your board, clinical governance committee and privacy officer
What we need from you and what your staff approve
A project needs a small amount of your time, at the right points. The table shows what we ask for and what stays under your staff's control.
| What the provider supplies | What staff approve |
|---|---|
| A named owner with authority over the workflow | The written scope and any later changes |
| Access to the relevant phone, email or software accounts | Scripts, greetings and approved answers |
| Baseline data for the chosen workflow | Escalation lists and on-call rules |
| Current policies, procedures and templates | Templates for drafts and summaries |
| Staff time for discovery interviews and test sessions | Go-live after testing |
| Your privacy officer's review of the data flow map | Each output that reaches a record, family or regulator |
Review after go-live
We review the system with you after the first weeks of live use. We compare the results with the baseline, read through a sample of outputs such as call summaries or draft notes, and ask the staff using it what has changed for them. Misrouted calls, unclear drafts and rules that fired at the wrong time are fixed.
The review ends with a decision that is yours: keep it as it is, extend it to more hours, sites or teams, change it, or switch it off. After that, we agree a review rhythm, usually quarterly, so the system keeps up with changes in your policies, staff and funding rules.
How it works in practice
- 1
Discovery and baseline
Walk through the current workflow with the staff who do it, and measure it before anything changes.
- 2
Written scope and quote
A document describing what will be built, the data involved, integrations, controls and how success is measured.
- 3
Build and staff testing
Configure in a test setting, then staff test with real scenarios until the workflow owner signs off.
- 4
Narrow go live
Start with limited hours, one site or one team, with outputs going to the agreed people.
- 5
Review and decide
Compare results with the baseline, fix issues, and decide whether to extend, change or stop.
Common questions
How do you implement AI in an aged care organisation?
Start with one repeated admin task, measure it, scope the change in writing, build and test it with the staff who do the work, go live on a narrow scope and review the results before extending it.
How long does an aged care AI project take?
It depends on the workflow and on integrations. A phone agent using inboxes for summaries is quicker than a workflow that writes into a care management system. The written scope sets out the stages and dependencies for your project.
Who approves what the AI does?
Your staff. The workflow owner approves scripts, rules and templates and signs off go-live. Qualified staff approve any output that reaches a care record, a family member or a regulator.
What do we need to provide?
A named owner, access to the relevant systems, baseline data, current policies and templates, staff time for interviews and testing, and a privacy review of the data flow map.
Can we stop the project if it is not working?
Yes. Each stage ends with a decision point. If the review after go-live shows the system is not helping, you can change it or switch it off.
What should our board know about an AI project?
What the system does and does not do, what data it uses and where that data is stored, who approves its outputs, how urgent matters are escalated and how results are measured. We provide this in writing.
Sources and further reading
- Australian Privacy Principles (Office of the Australian Information Commissioner)
- Health information and medical research (sensitive information) (Office of the Australian Information Commissioner)
- New Aged Care Act (Department of Health, Disability and Ageing)
Related pages
About Us
AI 4 Aged Care is part of the Yes AI group in Melbourne. We build AI tools that take routine administrative work off aged care staff, and we design every one of them so that qualified people stay in charge of care.
Services
Thirteen services across four areas of aged care administration. Each one targets a specific, repeated task, keeps a person in charge of decisions and can be started on its own.
AI Implementation Roadmap
Most AI projects in aged care that stall do so for organisational reasons: no owner, no baseline, staff who were not asked, or a first project that was too large. This roadmap sets out the stages from a readiness check to use across a whole provider, with the review points in between.
AI Governance for Aged Care Boards
Directors of aged care providers already carry legal governance duties for quality and safety. AI is now part of the operations those duties cover, and boards need a simple, regular way to oversee it.
Talk it through with us
A free 30-minute video call about where admin time goes in your service and which task is worth automating first. No obligation, and no resident information needed.