How to Choose a Retirement Village Management Platform
To choose a retirement village management platform for more than one site, decide first which system will be the record of truth for each kind of information you keep. Then test the candidates against your own processes, your residents' ability to use them, the multi-site view head office needs, integration with the systems you are keeping, Australian hosting and security, and how the rollout will actually be run.
On this page
This guide is written for the operations director, group manager or village manager who has been handed the job of finding a platform, often after a second or third village has made the spreadsheets unworkable. It sets out the record-of-truth exercise, seven tests in the order we would run them, ten questions to put to every vendor and what a 30-day pilot should prove. It assumes you have read, or will read, what operations software covers.
Start With the Records, Not the Features
Every demonstration you sit through will be organised around features. Your evaluation should be organised around records, because the records are what you keep, audit and hand over when a manager leaves.
Before you see a single product, list every type of record your villages hold and write two things beside each: where it lives today, and where it should live. The table usually looks something like this.
| Record | Where it lives today | Where it should live |
|---|---|---|
| Maintenance requests | Email, phone log, maintenance spreadsheet | Operations platform |
| Complaints and feedback | Manager's inbox, a Word register | Operations platform, with timed stages |
| Residence contracts and DMF | Finance system, signed PDFs on a shared drive | Finance system (record of truth), with the stages tracked in operations |
| Waitlist and enquiries | CRM, or a spreadsheet | CRM if you have one; otherwise operations |
| Events, bookings, facilities | Paper sign-up sheets, a noticeboard | Operations platform, resident-facing |
| Broadcasts to residents and families | Letterbox drops, group emails | Operations platform, with a sent record |
| Incidents | Paper form, scanned | Operations platform, structured and timestamped |
Two things fall out of the exercise. You find out how many systems you are actually buying (usually one, connected to two you keep). And you have the list the demonstrations must be scored against.
Seven Things to Test, in Order
1. Fit to Your Processes
Bring your messiest process, the one that lives in a spreadsheet, a diary and someone's head, and ask the vendor to configure it in front of you. Ask how many weeks it takes to stand up your top ten workflows and who does the work. Our own data point: Conpago configured 11 resident-lifecycle workflows for a tender panel in three weeks using Workflow Studio, without a development project.
2. Resident Adoption, Measured Not Promised
Ask for adoption measured days after a real launch, as a share of residents, not downloads. Ask what the launch looks like: who is on site, for how long, and what happens for the resident who has never used a smartphone. Look at the resident screen yourself for type size, contrast and how many taps a maintenance request takes. Conpago's reference figure is 60 per cent of residents active within 30 hours of a village launch.
3. The Multi-Site View
Have them show you one queue across every community with a filter per site, role-based views so a village manager sees their village and head office sees everything, and a report that rolls up without anyone exporting to a spreadsheet. If the multi-site report is a monthly export, it is not a multi-site view.
4. The Audit Trail and the Compliance Clocks
Create a complaint in the demo and watch what the system records: who, when, what stage, what changed. Ask to see a timer on a stage, a reminder to the person whose step is waiting and an overdue flag. Then ask them to export the evidence an assessor would request. A system that cannot produce that in the demo will not produce it at audit.
5. Integration With What You Keep
Name the systems you are keeping (finance, care, CRM, asset management) and ask three questions: is the integration two-way, which system remains the record of truth for each record, and who maintains the integration when either side changes. A managed integration layer with named connectors is a different proposition from "we have an API". Conpago's Alloy has pre-built connectors for Dynamics 365, Salesforce, AlayaCare, TurnPoint and Urbanise, and custom connectors are scoped per customer.
6. Security and Data Residency
Ask for the ISO 27001 certificate, not the claim, and the date of the last external audit. Ask where the data is hosted (it should be Australian data centres), whether the platform supports your organisation's single sign-on, and how role-based access is set. Conpago's answers are in its Trust Centre: ISO 27001 certified, audited annually, hosted on AWS Sydney, covered by the Privacy Act 1988.
7. Implementation and What Happens After
Ask who turns up on site at launch, where support is based and in what hours, and how many customers have left in the vendor's history and why. Insist on a pilot at one village before committing the portfolio. Conpago runs Discovery, then a Pilot community, then a staged Rollout, then Advanced workflows, with an Australian-based team on site at each launch. No customer has left in eight-plus years.
Ten Questions to Put to Every Vendor
- For each record on our list, is your platform the record of truth, or does it read from another system? Which one?
- Configure our complaints process now, with our stages and our deadlines. How long did that take you, and could our quality manager have done it?
- What share of residents at your last three launches were using the app within a week, and how was that measured?
- Show us a request raised by a resident, assigned to a contractor and closed with a photo, and then show us that request in a head-office report.
- Which of our systems have you integrated with before, two-way, and who maintains the connector when their API changes?
- Where is our data hosted, who at your company can access it, and when was your ISO 27001 certification last audited?
- Who is physically at our village on launch day, and for how long?
- What does a 30-day pilot cost, what does it include, and what happens to the configuration if we proceed?
- How many customers have left you, and what did they move to?
- If we leave, how do we get every record and attachment out, in what format, and how long does it take?
What a Pilot Should Prove in 30 Days
A pilot is a single community, live, with real residents and real requests, against measures you wrote down before it started. Without the measures the pilot proves only that the software switches on.
| Measure | How to count it | A result worth continuing on |
|---|---|---|
| Office interruptions per day for request updates | Tally at the front desk for a week before and a week after | Halved or better. One village went from about 15 a day to under 2. |
| Time to log a simple job | Stopwatch, five jobs, before and after | Minutes to seconds |
| Resident adoption | Residents active in the app as a share of all residents, day 7 and day 30 | Above 50 per cent by day 7 with an in-person launch |
| Requests closed within target | Platform report | Visible, trending up, with no spreadsheet |
| Workflows live | Count of processes running end to end in the platform | Your top five, configured by week two |
Agree in writing what happens to the pilot configuration if you proceed: it should carry straight into the second village, not be rebuilt.
The Honest Trade-Offs
There are two shapes of answer in this market and each is right for somebody.
One suite for everything. One vendor, one login, one invoice. The cost is depth: a suite that also runs finance and clinical care usually runs operations and resident engagement less well than a specialist, and replacing finance and care at the same time as operations is the largest project an operator can take on. Choose this if your finance and care systems are also due for replacement and you have the project capacity to do all three at once.
A specialist operations layer connected to the systems you keep. Finance stays in finance, care stays in care, and the operations platform runs the daily work and the resident and family experience, connected two-way. The cost is that the integration has to be real and maintained, which is why question five above matters more than any feature. Choose this if your finance or care system is working and the pain is in requests, complaints, communication and the view across sites.
If you are a single village with one manager and no audit on the horizon, you may not need either yet. Buy when the second site, the accreditation date or the manager's resignation letter is in view, not after.
Where Conpago Fits
Conpago is the second shape: an operations and engagement platform with a resident and family App, a staff and leadership Dashboard, Workflow Studio underneath and Alloy connecting to the finance, care, CRM and property systems you keep. It runs the resident lifecycle operationally, from enquiry and waitlist to exit and refurbishment, with the finance system staying authoritative for the money. Eight years in Australian retirement living and care, 10,000+ people on the platform. Sector detail is on Retirement Living.
Yes, on the resident's terms. Consent-based family access, where the resident chooses what a family member can see, cuts the calls to the office asking for updates and keeps the resident in control of their own privacy. Test that the consent is granular and revocable, and that family users cannot see other residents' information.
Few vendors publish a rate card, because pricing depends on the number of units or residents, the number of sites, which modules are switched on and how much implementation is included. Conpago prices by proposal after a demo, shaped to sector and size, and charges only for the products you run. Ask every vendor to separate licence, implementation and integration costs.
Not necessarily, but you need the discipline of one: a written list of your processes, a scored demonstration against those processes, reference calls with operators of a similar size, and a pilot with measures agreed in advance. Operators who skip the process list end up scoring vendors on the demonstration the vendor chose to give.
That every record, attachment and audit history can be exported in a structured, readable format at any time and at exit, that data is held in Australia, and that it is deleted on your instruction after export. Ask where the data is hosted, who can access it, and how the vendor's ISO 27001 certification is evidenced.
Related reading
Bring your messiest process to a demo.
We will configure it in front of you, with your stages and your deadlines, and you can time us.
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.