For strata and resident-run villages
Building and facilities, for the people who live there
Your brief, item by item, with the screens that answer it. Every “Show me” opens the demo village, St. Default, as the person who would use that screen: an owner who chairs the strata committee, or the office.
- In use today at villages now
- Built switched on per village
- Preview on screen in the demo while it is built
Who uses it
Residents and owners
Report a job and follow it, book a room, read notices and by-laws, see the work on common property.
OwnerAn owner’s home screenThe office (reception)
Every job and request in one place, notices to owners, files, the units and owners register.
OfficeThe office’s homeTriage
New jobs land on the board by category, with the usual person for each suggested first.
OfficeThe office’s job boardMaintenance staff
Their own jobs, with photos, the unit, access permission and the asset’s history.
OfficeThe office’s job boardGardening committee
Gardening jobs on common property, the gardens’ part of the asset register, and the contractors who have done its jobs, in their own portal.
OwnerThe committee’s jobsBuilding committee
The asset register: what is coming up for replacement, and what it will cost. The demo’s owner does not sit on it, so this opens the strata committee’s, which reads the same register.
OwnerThe asset register, as a committee reads itStrata committee
Everything the other committees see, plus jobs inside units, contractors and committee papers.
OwnerThe committee portal
What the brief asks for
Easy to use, whoever is using it
In use todayLarge type, big buttons and one thing per screen. Built for residents first, and it works on a phone, a tablet or the computer at reception.
Task entry: building maintenance
In use todayAn owner reports a job, with a photo if they like. The office can log one for them from the phone or the desk.
Task entry: gardening
BuiltEvery job carries a category (Building, Gardening, Village management) and whether it is in a unit or on common property.
Booking facilities
BuiltOwners book the lounge, guest suite, barbecue, workshop or billiards room. Some rooms are booked straight away; the office confirms the rest.
Case management: status updates and comments
BuiltEach job moves from received to done on a board, and the office posts how it is going (“Greenleaf are quoting first”). The committees read every update in their portal, every owner reads it on Around the village for work on common property, and the person who asked reads it with their own request. Committee members leave notes the office reads, and can ask the office for an update.
Transparency: an owner portal
BuiltEvery owner who lives in the village sees their own jobs in full and the work on common property, never who asked. Committees see more, in a portal of their own. Owners who live elsewhere come with the owners register.
Different access for owners and committees
BuiltOwners, each committee, the office and maintenance each see what is theirs. The owners elect the strata committee, so its list follows the annual general meeting; a gardening or building committee’s chair adds and removes its members.
An asset register linked to the buildings
BuiltHot water systems, lifts, roofs: when each was installed, its warranty, every job done to it and what it cost. Its place is written in words today (“Block B plant room”), and is tied to its building and unit when the owners register is live.
A document library: newsletters and by-laws
BuiltFiles for every owner, in use at villages today. By-laws get a section of their own, and committee papers only that committee can open, with who has read each one.
Building and owner details
BuiltEvery unit by building and level: its owners (including those who live elsewhere, and estates), who lives there, its lot and entitlement, and the jobs and assets in it. The office adds and changes them, and only admins see owners’ details. “Email these owners” shows who an email by building would reach; sending to owners comes next.
Bulk email
BuiltA notice on the board can also go by email to every resident, or to one committee, with a one-click unsubscribe. Email to owners who live elsewhere, and by building, comes with the owners register.
Workflow: assignment to teams
BuiltEach category has its usual person (building maintenance, gardening, village management). You choose how automated it is: the office hands out every job, the usual person is suggested and the office confirms, or a new job goes straight to the usual person and they are told. The office can always give it to someone else.
Village management: WHS and compliance
BuiltA hazard and incident register, and a contractors register whose insurance and licences show beside their name whenever a job goes to them. The schedule, orders and invoices beside the register are a preview.
Induction and training
BuiltA one-page quick-start for committee members and a setup guide for the office.
Works for real, not in the demo
The demo reaches nobody, so these are switched off in it.
Emails to owners
Notices go from “your village via Apworth”, replies come to the office, and every email carries a one-click unsubscribe. The demo sends nothing.
Phone notifications
An owner hears on their phone when the office writes to them about their job. Committee members hear when a paper is filed.
Asking the office
A committee member’s question about a job reaches every office administrator in the app and on their phone.
Text messages
An urgent notice (water off, lift down) can go as a text to residents’ mobiles.
Coming next
Agreed, and being built after what is on the screens above.
Every asset tied to its building and unit
Where each item on the register is, as a block or a unit on the owners register rather than words.
Owners who live elsewhere
Their own sign-in to Around the village and to their own jobs, and notices by email wherever they live, from the owners register.
Contractors, the second half
Certificate expiry alerts, the schedule, work orders by email, and invoices.
Files kept in Australia
Your database is already held in Sydney; uploaded files move there before your go-live.