One property manager has 12 communities and a clean inbox. Another has 9 and is buried in escalations. Portfolio owners rarely see the gap until someone quits. LotWize's staff workload dashboard scores every property manager's caseload and lets owners rebalance it in a few clicks.
A portfolio owner running a property management company rarely finds out a property manager is overloaded from the property manager. They find out when that manager gives two weeks' notice, or when a community's board calls corporate directly because their usual contact hasn't returned a message in four days, or when an escalation that should have taken a day to resolve is still open after three weeks because the person responsible for it is also responsible for eleven other communities and something had to give.
By the time any of those things happen, the imbalance has usually existed for months. Caseloads at most PMCs get built the same way: a new HOA joins the portfolio, and it gets assigned to whichever property manager has bandwidth — or, more often, whichever property manager was in the room when the deal closed. Nobody revisits that assignment later. Communities that were quiet when they joined can turn difficult — a new board, a special assessment fight, a wave of violation appeals — and the manager who inherited that community six months ago is now carrying a caseload nobody planned for, while a colleague two desks over has six easy communities and capacity to spare.
This is the gap LotWize's PMC staff workload dashboard is built to close: a portfolio-wide view of who's carrying what, scored consistently across every property manager, with a one-click way to fix it once you see it.
The obvious first instinct for a portfolio owner checking on staff capacity is to count communities per manager. It's also the wrong number to trust on its own. A property manager with six small, well-run 20-unit communities that rarely generate escalations is not carrying the same load as a manager with four 150-unit communities in the middle of a reserve-fund dispute and a contested board election. Raw community count treats both caseloads as roughly equal. They aren't.
LotWize's staff dashboard, at /pmc/staff, replaces that guess with a workload score built from three signals pulled live from the same data the platform already tracks for every community:
Those three numbers sum into a single workload score, and the score sorts a manager into one of three bands: light at or below 4, moderate above 4 through 8, and heavy above 8. The dashboard also surfaces upcoming compliance deadlines — anything due within the next 30 days across a manager's communities — as a fourth data point shown alongside the score, since a manager heading into a stretch with five annual-meeting notice deadlines due in the same month is facing a real crunch even if their baseline score looks moderate.
None of these numbers require a portfolio owner to ask anyone how things are going. They're computed from live data — assignment records, unit counts, open escalation status, deadline dates — every time the dashboard loads.
Opening the staff view surfaces a portfolio-level summary first: total number of property managers, the average number of communities per manager, and a count of managers currently flagged heavy. That top line alone answers the question a portfolio owner usually can't answer without going manager by manager: is my staffing balanced right now, or is it not?
Below that, each property manager gets a card showing their workload badge (light, moderate, or heavy, color-coded so heavy reads red and light reads green), their total assigned communities, total units under management, open escalation count, and upcoming deadline count. Every assigned community appears as a chip on that card, each one showing the community's unit count and, if the owner wants to act on what they're seeing, a reassign link right there on the chip.
This matters because it collapses two steps most portfolio owners currently do separately — first noticing an imbalance exists (usually informally, in a hallway conversation or a manager's frustrated email), then figuring out what to actually move to fix it — into one screen. The imbalance and the fix live in the same place.
Fixing an imbalanced caseload used to mean an email thread: telling one manager they're picking up a new community, telling the outgoing manager to hand off files, and hoping the community's board finds out from someone rather than nobody. LotWize turns that into a single action from the dashboard — a portfolio owner or admin clicks reassign on a community chip, picks the receiving property manager from the list (filtered to exclude the manager the community is currently leaving), and confirms.
Under the hood, the reassignment isn't a silent update to a field. The system deletes the existing assignment record and creates a new one — both as audited operations, meaning who made the change and when is permanently attached to the community's history. If a board later asks "who was our property manager in March, and when did that change," that's a lookup, not a guess based on someone's memory of the org chart six months ago.
The system also enforces that reassignment only happens within a portfolio — a property manager can't accidentally (or maliciously) reassign a community to someone outside their own portfolio, and only a pmc_owner or pmc_admin role can trigger the reassignment in the first place. A staff-level property manager can see their own dashboard card, but rebalancing the portfolio is an owner/admin decision, which matches how the actual authority to reshuffle caseloads works inside most PMCs.
Portfolio management companies grow the way most service businesses grow: unevenly, deal by deal, with staffing decisions made under time pressure. A PMC that starts with three property managers and eight communities can end up, two years and forty communities later, with staffing that still reflects decisions made when the portfolio was a third its current size — because nobody built a system that made the imbalance visible enough to justify the awkward conversation of moving a community away from a manager who's had it for years.
The cost of that inertia isn't abstract. Property manager turnover is one of the most expensive, disruptive events a PMC can absorb — every community that manager touched needs a handoff, every board relationship gets reset, and the departing manager's institutional knowledge about which homeowner is litigious or which vendor is unreliable walks out the door with them. Burnout from an unevenly loaded caseload is a preventable cause of that turnover, and it's preventable specifically because it's measurable — if a portfolio owner can see the imbalance before it costs someone their weekend for the sixth month running, there's a real chance to fix it before the resignation letter.
There's a second, quieter cost: communities that end up on the heavy side of an imbalance get worse service, not because the manager assigned to them is worse at the job, but because they're stretched across more open escalations than any one person can meaningfully carry. A board that experiences slow response times has no way of knowing their property manager is also covering nine other communities single-handedly — they just experience a management company that seems less responsive than it used to be, and that perception is exactly what drives boards to put management out for bid.
Staff workload balancing sits inside LotWize's PMC portfolio tier, alongside the same infrastructure that tracks community-level escalations and compliance deadlines — it's not a bolted-on staffing tool that lives disconnected from the operational data. The workload score is only meaningful because it's built from the same live escalation and deadline data the rest of the platform already surfaces to individual property managers, which means the number a portfolio owner sees on the dashboard is the same reality the property manager is living day to day, not a separate, lagging metric someone has to reconcile by hand.
It's worth being clear about what this does and doesn't solve. The dashboard doesn't decide which manager should get a difficult community, and it doesn't replace a portfolio owner's judgment about who's ready for more responsibility versus who needs relief. What it removes is the blind spot — the months where an imbalance exists and compounds simply because nobody had a reason to go looking for it. A portfolio owner checking the dashboard once a week catches a caseload drifting toward heavy long before it shows up as a resignation or a board complaint.
For a PMC managing five communities, this is a nice-to-have. For a PMC managing thirty-five, it's closer to a staffing requirement hiding in plain sight — the same way a general contractor wouldn't run six job sites without knowing which crew is overbooked, a portfolio owner shouldn't be running dozens of HOA relationships without a live read on who's actually carrying the load.
Nobody builds a PMC by intending to run their best property managers into the ground. It happens by accretion — one more community here, one more here, until the person who said yes the most times ends up carrying the most weight. LotWize's staff workload dashboard doesn't make the staffing decisions for a portfolio owner. It makes sure those decisions get made on purpose, with real numbers, before the imbalance costs a manager, a community, or a management contract.
Start your free LotWize trial and see how the PMC portfolio tier turns staff workload from a hallway conversation into a dashboard you can act on in a few clicks — before your best property manager burns out on a caseload nobody was watching.
LotWize handles violations, resident questions, dues reminders, and meeting packets automatically — so your board gets its time back.
More guides for HOA boards
Changing who manages an HOA — self-managed to professional, or one management company to another — is usually a manual, records-losing scramble. LotWize's Community Transfer feature turns it into a governed, board-approved, automatically-billed workflow.
Property management companies acquiring a competitor's HOA portfolio usually get a CSV manifest, a data room, and two weeks. AI due diligence reads that data the way an analyst would — scoring financial health, maintenance backlog, document quality, and compliance risk before the deal closes.
Angry communities rarely call before the annual meeting. AI sentiment tracking reads portal messages, appeals, and maintenance requests to surface a rolling mood score per community — so property managers catch trouble before it becomes a board recall.