Portfolio status board
Every open job across every community appears on one screen, sorted by age and by how far it sits from the board's approved response window.
SIZ Group builds a manager oversight app for HOA management companies that puts every open work order, staff assignment and overdue task for every community on one screen. The general manager sees what is stuck, moves it in a tap and reports on the portfolio without rebuilding a spreadsheet every Monday.
The general manager signing off on this app needs one answer: the company should know, before any board does, which communities have a problem. The answer has to be yes, and it has to come from the same records the field team uses. A dashboard that rebuilds numbers by hand each week will not earn trust.
We would start by agreeing on the operating questions the app must answer every morning. Which associations have work orders older than the response window the board approved? Which community managers are carrying more open files than their peers? Which violation letters are waiting on a signature or a board review? Each answer should take one screen, not an export.
The general manager opens the app at 7:30 and sees three flagged items across the portfolio: a pool pump failure at a large community, a gate repair waiting two days for a vendor, and a board packet due Thursday with two sections still unassigned. Tapping the pool item opens the job record with photos from the field lead, the vendor quote and the spending limit the board approved.
The gate repair needs action. The assigned vendor has not confirmed, so the general manager moves the job to a backup firm already on the approved list and adds a note that the board president should be told. The change is logged with the time and the person who made it, so the decision can be explained later without reconstructing an email thread.
Before leaving the screen, the general manager checks the board packet. Two sections show owner names and assignments, and the packet status changes to ready for review. Nothing has gone to directors yet, so the manager can check the wording first and release the packet once it is correct.
Most HOA management companies run an association management platform for accounting, owner records and ledgers, plus a separate tool for email and document storage. Where the platform offers an export or an integration, the oversight app reads from it. Where it does not, the app starts from a clean job list that the team keeps current, and we say so during the scoping call.
Accounting packages such as QuickBooks can hold vendor bills and check runs, but the oversight app should not duplicate them. Its job is operational status: who owns a job, how old it is and whether it breaks a board-approved limit. Keeping that split clear avoids two systems disagreeing about the same invoice.
Every open job across every community appears on one screen, sorted by age and by how far it sits from the board's approved response window.
A stuck job moves to another vendor or staff member with the reason and the time recorded in the job log.
Packet sections show who owns each item and whether it is ready for review, so gaps are visible before the packet is due.
Weekly summaries by community, manager and vendor category export to PDF or spreadsheet for owner and board presentations.
Several rules genuinely apply here. State property code provisions set how and when associations must give notice before fines, hearings or collection steps, and the app must record those dates rather than estimate them. Owner records are personal information, so access should follow the staff role. An assigned landscaper has no business seeing a homeowner's ledger.
If the company handles collections, the Fair Debt Collection Practices Act may apply to third-party collection activity, so the app should log contact attempts without placing calls itself. Card payments belong with a PCI compliant processor, and the app should hold only payment tokens, never full card numbers. Notices must also follow Fair Housing principles, which means the same standard for every owner.
Bring the community list with each association's management agreement terms, the approved vendor list with spending limits and the work order categories the team already uses. We also need the board calendar, the packet template and the standard for what counts as overdue for each type of job.
Access is the next gap. We need a named administrator on your side, read access to the management platform or an export, and sample records that show how a real job moves from request to close. Where quotes and photos live in email today, we need to know which folders hold them so the move does not lose anything.
The most common mistake is building a dashboard for the general manager alone. Field leads and community managers keep working from their own lists, and the dashboard then shows stale status. The oversight app should be where assignments are made, so the report becomes a by-product of daily work.
Another is trying to show every field from the management platform. A portfolio view with thirty columns is unreadable on a phone, and boards never see it anyway. We would limit the first screen to status, age, owner and the spending limit, and let the manager open a record for detail.
No. The oversight app works beside the platform that holds your ledgers and owner records. We read the data we need through an export or an integration, and job status and assignments live in the oversight app, where the team already works.
Each job carries a due date set by the board's approved response window or by the vendor agreement. When a job passes that date, it moves to the top of the queue, and the general manager receives a daily summary. Late items are grouped by community, so the same problem is not discovered three times.
Access follows the role. Community managers see their assigned associations, while the general manager sees the full portfolio. Every change is logged with the user and the time, which makes it easier to answer a board question about who handled a job.
Spending limits and approved vendor lists are loaded as rules in the app. When a job exceeds a limit, the app asks for the required approval before a vendor is booked, so the rule applies at the moment of assignment instead of in a later review.
It is a custom build, scoped to the operating rules of your company. A mobile app starts at $4,500, and we confirm the final figure in writing once scope is agreed.
Book a free scoping call, and we will map your operating rules before confirming scope and price in writing.