Retirement Village Platform
Apworth forRetirement villages
Events, notices, maintenance requests, rosters and resident accounts for Australian retirement villages, in one place and shaped to how your village already runs.
Use Ask. Any question. Any action. Just Ask.
Worth it for your staff, your residents, and your families' peace of mind.
The Platform
What your team stops chasing
Community
Events, RSVPs, the notice board, messaging, menus and games. Village life organised once and visible to every resident, instead of printed, pinned up and phoned through to the office.
Governance
Maintenance requests from the unit to done, plus assets, incidents, hazards and policies, with the paper trail the village needs already in place.
Wallet
Invoices, statements and payments for residents and their families, clear at a glance, without the spreadsheet shuffle.
Workforce
Rosters, timesheets and award-aware costing for the village team. First aid and police checks stay current, and gaps show while there is still time to fill them.
Plus Notes for staff observations and a daily Digest so nothing slips.
Built For Villages
Made for how a village actually runs
Residents who run their own lives
Village residents are independent, and the software should treat them that way. Apworth puts the calendar, the notice board, the menu and the office in their pocket, and leaves the choices with them.
Family get their own login too, so a daughter interstate knows what Mum has on this week without ringing the office.
A small team doing everything
The village manager is also reception, the maintenance coordinator and the events planner. Apworth puts service requests, notices, rosters and resident accounts on one screen, so the office stops being the only place anything happens.
When a request comes in at the front desk, it lands with the right person and stays visible until it is done, without the manager chasing it.
Working With You
We build it with you
We work alongside your team from the first week, build what your village needs, and keep developing Apworth with you long after it goes live.
Your rosters, menus and forms come first. When the office asks for something, it shapes what we build next, so Apworth fits around how your village already runs.
Ask
The fastest way to get anything done
For Residents & Families
And your residents love using it
Games
Trivia, Name the Year, Word Grid and plenty more. Keeps minds sharp and days full.
Guides
What's on this week, the notice board, the menu, photos and the handbooks. Everything a resident would otherwise walk to the office to ask about.
Contacts
Family and carers get their own login, so they can follow along and help manage things. You set how much each of them can see and do.
Governance
The paper trail, without the paperwork
Villages answer to residents, the committee, the board and the regulator. Most of what they ask for is already in Apworth, because the record is the same action as the work.
- A resident reports a leaking tap from their unit
- A service request with an owner, a status and the date it was fixed
- A staff member logs a fall in the gardens on their phone
- An entry in the incident register, with a follow-up owner and a date
- A police check or first aid certificate is uploaded
- An expiry that raises itself before their next shift
- A maintenance job is closed off
- Service history and spend recorded against that asset
None of it is a separate compliance exercise. It is the same work, written down once.
Getting Started
Rolled out with you, not handed over
Any platform takes a while to bed in. What matters is who does the work, and how much of it lands on your team.
We do the setup
Residents, staff, rosters and the calendar loaded before anyone logs in. Your team never starts at an empty screen.
Staff pick it up on shift
No training programme to schedule. The things they do most sit on the first screen, and Ask covers the rest.
Turn features on as you go
Start with what your village needs now. Everything else waits until you want it, and switches on without a new project.
Trust
The paperwork your procurement team will ask for
- Every village is isolated as its own tenant, enforced in the database rules and again server side.
- Passwords, staff codes and resident PINs are stored as salted hashes.
- Operator access to production consoles requires MFA.
- Security incidents follow a Notifiable Data Breach runbook with a named owner.
See Apworth run your village
Book a walkthrough and see your own village in it, not a canned tour.