Operations Software for Aged Care and Retirement Living, Explained
Aged care and retirement living operations software is the system an operator uses to run the daily work of a community: requests, maintenance, incidents, complaints, bookings, communication and the records behind them. It connects the people being supported, the staff doing the work and the managers reporting on it. In Australia it is distinct from clinical care systems and from the finance systems that handle fees, contracts and exit entitlements.
On this page
- The Category Is Really Three Systems, Not One
- What Operations Software Covers, in Practice
- How a Request Moves Through It
- Why Generic Tools Stop Working at the Second Site
- What the Regulator Expects the Records to Show
- Who Adopts It, and What Adoption Actually Looks Like
- Where Conpago Sits in This Map
- Go Deeper
- Questions Operators Ask About Operations Software
At Conpago we have spent eight years inside Australian villages, homes and community care programs, and the first question a new operator asks is rarely "which product?" It is "which system should hold which record?" This guide covers what the category includes, what it leaves to other systems, how a request moves through it, what regulators expect the records to show, and how to tell whether you need it. It assumes you run one or more retirement villages, residential homes, home care or disability programs in Australia.
The Category Is Really Three Systems, Not One
Most Australian operators run three kinds of software, whether or not they bought them as one suite. Confusing them is the most common reason a project disappoints.
| System | What it is the record of truth for | Typical examples of records | Who lives in it |
|---|---|---|---|
| Care or clinical system | The person's health and support | Care plans, medication charts, assessments, progress notes used for funding claims | Nurses, care coordinators, clinical managers |
| Finance and property system | Money and the asset | Residence contracts, ingoing contributions, deferred management fees (the DMF, a fee accrued against the resident's contribution and paid at exit), exit entitlements, ledgers, asset registers | Finance, property, sales administration |
| Operations and engagement system | The daily work and the communication around it | Maintenance requests, incidents, complaints, feedback, shift and handover notes, broadcasts, bookings, the stages of a move-in or exit | Village managers, maintenance, frontline staff, residents, families |
Some vendors bundle all three. Many operators keep a specialist system for care and another for finance, then run operations on whatever is to hand: a shared inbox, a diary, a maintenance spreadsheet, a WhatsApp group for the gardeners. The operations layer is where the sector has the least software and the most paper.
The useful question when buying is not "does it do everything?" but "for each record we keep, which system is the truth, and how do the others see it?" We expand on that in How to choose a retirement village management platform.
What Operations Software Covers, in Practice
Seven jobs, present in some form in every operation we have seen.
Requests and Maintenance
A resident, family member or staff member raises a job, it is triaged, assigned, photographed and closed, and the person who asked can see its status without ringing the office.
Incidents, Complaints and Feedback
Structured capture with required fields, so a record is complete when it is lodged, and timed stages so a complaint or a reportable incident reaches the regulator inside the deadline.
Communication
Broadcasts, news, surveys and messages to residents, families and staff, with a record of what was sent, to whom and when. Escalation to SMS and email for the people who do not open apps.
Calendar, Events and Facilities
Shared spaces, services and events that residents can see and book themselves, with attendance and payments recorded.
The Resident Lifecycle
The stages from enquiry and waitlist through offer, contract, move-in, exit and unit refurbishment or resale, tracked as a workflow so nothing waits in someone's head.
Field Records
Shift notes, handovers, travel logs and job updates written on the worker's own phone, in the structure the operator sets.
Multi-Site Reporting and the Audit Trail
One queue across every community, with role-based views for each team and a recorded history of every item, so head office reads the same picture as each site.
How a Request Moves Through It
Take a leaking tap in Unit 14, a Tuesday morning.
The resident opens the app, taps Maintenance, chooses Plumbing, takes a photo and sends it. Twenty seconds. The request lands already triaged in the village queue with the unit, the category and the photo attached. A rule assigns plumbing to the maintenance lead and marks it as a 48-hour job. He sees it on his phone between two other jobs, accepts it, and the resident's screen changes from Received to Scheduled. He fixes it on Wednesday, photographs the repaired tap and closes the job; the resident sees Done, with the photo. The village manager never touched it. Head office sees it only as one row in a report: plumbing, 26 hours to close, within target.
Without the system, the same tap is a phone call to the office, a note on a pad, a verbal message to maintenance, two follow-up calls from the resident, and nothing to show an auditor three months later.
What one village's request volume looked like before and after automatic routing, measured across 1,500 requests.
Why Generic Tools Stop Working at the Second Site
A single village of sixty units with one experienced manager can run on a diary, a spreadsheet and a good memory for years. We have watched it done well. The break comes at one of two moments: the second site, or the first accreditation audit.
At the second site, the record splits. What the resident knows, what the office knows and what head office knows are three different things, and reconciling them becomes a job in itself. Process lives in the folklore of each site rather than in a system, so a new manager inherits a filing cabinet and a set of habits. When the manager who held it all leaves, so does the operation's memory.
At audit, the problem is reconstruction. The assessor asks for every complaint in the last year, what was done and when. If the answer is in emails, a spreadsheet and a notebook, someone spends a week building a record that should have built itself.
Generic helpdesk tools and CRMs are built for customers who want to be left alone after the ticket closes. A village or a care program is the opposite: the same person raises a request every fortnight, their daughter wants to see the status, the gardener and the plumber share the queue, and the regulator wants the trail. Those relationships are what sector-specific operations software is built around.
What the Regulator Expects the Records to Show
Software does not make a provider compliant. People do. What the software does is keep the record complete, timestamped and attributed as the work happens, so the deadline is met with evidence rather than reconstruction. The clocks it has to keep are specific:
- Residential aged care and home care: under the Serious Incident Response Scheme (SIRS), Priority 1 incidents must be reported to the Aged Care Quality and Safety Commission within 24 hours and Priority 2 incidents within 30 days. The Aged Care Act 2024 and the Support at Home program both commenced on 1 November 2025.
- Disability (NDIS): registered providers must notify the NDIS Quality and Safeguards Commission of a reportable incident within 24 hours of key personnel becoming aware, then lodge a detailed 5 Day form within five business days. Every incident, reportable or not, must be recorded in an incident management system. The detail is in NDIS incident reporting, explained for providers.
- Retirement villages: each state and territory regulates villages under its own Retirement Villages Act, covering contracts, disclosure, fees and dispute handling. Complaint records and timeframes are the operational evidence those regimes expect.
Who Adopts It, and What Adoption Actually Looks Like
Adoption is the number this category is judged on, and it is the number most often fudged. Downloads are not adoption. Adoption is the share of residents or staff using the system to do real work within days of launch, and it depends on two things: the interface, and the launch.
For residents in their 70s and 80s the interface means large type, high contrast, a handful of big tiles and no nested menus. Residents raise their own requests and watch progress themselves, and can choose to give a family member consent-based visibility of their schedule, events and request status; the resident controls who sees what. The launch means someone in the room: a demonstration in the community hall, then one-on-one sessions for anyone who wants them. Launched that way, Conpago has seen 60 per cent of a village's residents active within 30 hours, and 60 to 70 per cent within days.
For staff, the interface is the phone already in their pocket, with required fields that make the record complete and nothing to remember.
Where Conpago Sits in This Map
Conpago is the operations and engagement layer. It is not a clinical record and it is not a finance ledger, and we do not pretend otherwise. The Conpago App for residents, participants, clients and families and the Conpago Dashboard for staff and leadership are two surfaces on one shared record, so the resident, the maintenance lead and head office are reading the same item. Workflow Studio is the engine underneath: a no-code builder that configures the stages, fields, timers and approvals of each process around how the operator already works. Conpago Alloy connects it to the CRM, care, finance and property systems the operator keeps, including Dynamics 365, Salesforce, AlayaCare, TurnPoint and Urbanise, two-way, with those systems staying the record of truth.
The resident lifecycle runs end to end on the operations layer: enquiry, waitlist, offer, contract, move-in, maintenance, complaints, exit, refurbishment and resale. The contract document is versioned and signed in Conpago, and the finance system it feeds stays authoritative for the money.
The platform is ISO 27001 certified, hosted in Australia on AWS Sydney, and covered by the Privacy Act 1988. Pricing is a proposal shaped to your sector and size after a demo rather than a public rate card, and you pay for the products you switch on. Details are in the Trust Centre and on Pricing.
Go Deeper
A CRM records enquiries, prospects and sales. It rarely holds the maintenance request a resident raised yesterday, the complaint with a 20-day clock, the incident a support worker logged on shift, or the broadcast families received. If those live in email, spreadsheets and phone logs, that is the gap operations software fills, connected to the CRM rather than replacing it.
A pilot community can be live within weeks when the process is mapped first and launched in person. Conpago configured 11 resident-lifecycle workflows for a tender panel in three weeks, and resident adoption at a launch reached 60 per cent within 30 hours. A staged rollout then adds communities one at a time against the same workflows.
Yes, when the app is built for them and launched in the room with them. Large type, high contrast and one-touch requests remove the barriers; in-person launch sessions remove the fear. Conpago sees 60 to 70 per cent of residents using the app within days of a village launch, and families can be given consent-based visibility of requests and events.
No. Clinical records belong in a care system and fees, contracts and exit entitlements belong in a finance system. Operations software runs the daily work and the communication around it, and a two-way integration layer keeps the care and finance systems as the record of truth, so nobody re-keys information between them.
Related reading
Bring the process that lives in a spreadsheet.
Tell us how it runs today and we will show you the same process running in Conpago, from the request to the report.
Book a DemoBuilt on a foundation you can trust.
Enterprise ready: Conpago is ISO 27001 certified and Australian owned, with every record held in AU data centres. Security is audited annually, not assumed.
ISO 27001 Certified
Externally audited information-security management. Controls reviewed annually.
Data Sovereignty
Australian owned and Australian based. All data held in AU data centres and covered by the Privacy Act 1988.
ISO 42001 (AI)
Certification underway. AI governance held to the same external standard as our security.