Residents get their own app. Your board and committees get a separate one built for the work they actually do: walk the community, log a finding with photos, send the notice, review an architectural request and decide it. Nothing waits for somebody to get back to a desk.
A purpose-built app for the people managing communities rather than living in them. Inspections, violations, notice letters and architectural review, with each user seeing only the sections their permission level covers.
Most platforms ship one app and hide half of it behind a role check. A homeowner checking a balance and an inspector walking a community want opposite things from the first screen.
Their violations, their applications, their balance, their messages. One property, no navigation to learn. See the resident app
What is open, what is overdue, what is waiting on a decision, and the map of where it all is. Built to be used standing up, outdoors, one-handed.
On a phone screen, reviewing a queue means tapping into a record, reading it, backing out and losing your place. Give the app a wider canvas — an unfolded iPhone Duo, or an iPad in landscape — and it lays the queue out beside the record, so you move down the list without ever leaving it.
It is width-driven rather than tied to one device, so the app simply takes whatever window the operating system hands it. Fold it and the single-column layout comes back, mid-task, without losing where you were.
Architectural applications show the list beside the one you are reading, so a committee can work through a backlog in one sitting.
One app, one codebase, one login. The layout responds to the screen instead of you installing something different.
The community as a map, worked street by street, with findings and photos logged where you are standing. How inspections work
Review, act on and resolve violations in the field, with the cure-by date and the full letter chain in front of you.
Every generated notice, so you can see exactly what a homeowner was sent before you knock on their door.
Read the plans, see the neighbor sign-offs, and approve or deny — the screen that gets the two-pane treatment on a wide canvas.
Pushed the moment a resident submits a request, uploads a file or replies — filtered by the sections each admin is permitted to see.
An architectural committee member can decide applications without seeing finances. Permission levels are per module, not all-or-nothing.
Yes, and that is the point — the audit trail records who did what. Each member gets a permission level that matches their role, so a committee member is not handed the whole association to get at one screen.
Access is granted and removed per person, and everything they did stays on the record. No shared password changing hands at the annual meeting, which is how most small associations lose their history.
No. The app is for the work that happens away from a desk. Setting up the association, configuring workflows, pricing, reporting and anything long-form is better in the browser, and both read the same data.
Architectural applications today — the queue where working through a backlog in one sitting makes the most difference. The layout is width-driven, so it is the same mechanism wherever it is applied next.
We will log a finding on the board app and show you what the homeowner sees on theirs, in the same call.
These features complement what you just read — most customers use them together.
We are happy to give you a virtual tour.
Schedule an appointment!