Community & Operations Platform
Apworth forAged care and retirement villages
Rosters, events, messaging, money and compliance records for aged care homes and retirement villages, built in Australia and shaped to how your community 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
Workforce
Rosters, shifts, timesheets and award-aware pay. Training and credentials stay current, and coverage is visible while there is still time to act on it.
Community
Events, RSVPs, notice board, messaging, menus and games. The daily life of the community, organised and visible to everyone in it.
Wallet
Invoices, statements and payments for residents and families, clear at a glance, without the spreadsheet shuffle.
Governance
Incidents, hazards, maintenance, assets and policies, with the evidence trail an audit expects already in place.
Plus Notes for staff observations and a daily Digest so nothing slips.
Built For Your Sector
Two sectors that run differently
Apworth ILU
Community first. Events, notices, messaging and menus replace the printed pile, and residents stay close to family. The village calendar runs itself instead of running the office.
Underneath, maintenance, assets and incidents are tracked with the paperwork the village audit expects.
Apworth Aged Care
Workforce first. Roster against your care targets, keep training and credentials current, and log incidents the moment they happen. Governance evidence builds itself as the team works, so audit week is a report, not a scramble.
And residents get the same warm community experience: events, menus, games and family connection.
Where Apworth Stops
Apworth is not a clinical system
No care plans, no progress notes, no medication charts, no medical records. Ask hands anything clinical to a staff member rather than answering it. Apworth runs alongside the clinical software you already have.
What it does hold is the workforce evidence around care: whether a carer's medication competency is current, whether a police check has lapsed, whether the incident was logged and followed up.
Ask
The fastest way to get anything done
For Residents & Families
And your residents love using it
Games
Trivia, Name the Year, Word Grid, plus card games against the neighbours 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
Audit evidence you did not have to assemble
Compliance software asks your team to record the work twice: once because they did it, and again because someone will ask. In Apworth the record is the same action.
- A carer logs an incident on the floor
- An entry in the incident register, with a follow-up owner and a date
- Someone opens a policy and taps to acknowledge it
- A signed record against their name
- 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 community 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 home 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 community
Book a walkthrough and see your own workflows in it, not a canned tour.