Community managers are the management company's product and its single largest cost, and their capacity is the lever that sets both margin and retention. Load a manager too heavily and service slips, the board notices, and at renewal the contract goes to RFP. Under-load them and the labor model never pencils out. This template shows the doors, communities, and revenue each manager actually carries, against the target, so portfolios get rebalanced before a manager burns out.
What this report answers
The capacity page answers the staffing question directly: how many doors does each manager carry, how does that compare to the target, and who is over the line? It pairs doors with communities, because a manager with 12 small associations can be busier than one with 4 large ones even at the same door count. The rebalancing page turns that into a plan — who to offload, who has headroom, and where a whole region is imbalanced — with tenure on the table so you can weigh moving a long-tenured manager against the board relationships that move with them.
The metrics that matter
Doors per manager is the industry's core capacity ratio; owners benchmark it against roughly 600–1,000 doors depending on portfolio mix and onsite-versus-remote model. Communities per manager captures the relationship load that pure door counts miss. Revenue managed per manager is the productivity benchmark that connects staffing to the P&L. Managers over capacity is the at-risk list — the people most likely to resign and take their boards with them.
Why the data is trapped across the systems
The assignment of communities to managers lives in Vantaca, CINC Systems, AppFolio, or Enumerate / CiraConnect, but door counts live per association, revenue lives in each association's books, and tenure lives in HR or a payroll system. No single CAM screen sums doors and revenue by manager across the whole portfolio, because the platform is organized by association, not by employee. So capacity gets tracked — when it gets tracked at all — on a spreadsheet a regional director updates by hand, which is always slightly out of date and never shows revenue alongside doors. This template rolls all three together by manager.
How to read it
Start with the doors-by-manager bar and the 900-door reference line — anyone well above it is a flight risk and a service risk. Cross-check against communities per manager, because a high relationship count is its own kind of overload. On the rebalancing page, the positive doors-vs-target bar is your offload list and the regional view shows whether the fix is moving doors between managers or hiring in a region that has simply outgrown its team.
The sample on this page uses entirely synthetic, anonymized manager data — no real employees or assignments.
Metrics it tracks
| Metric | What it means |
|---|---|
| Total Doors Managed | Total portfolio doors under active management, summed across all managers. |
| Active Community Managers | Count of community managers carrying a portfolio — one row per manager. |
| Doors per Manager | Total doors divided by manager count — the core capacity ratio owners benchmark, often against roughly 600–1,000 doors. |
| Communities per Manager | Total communities divided by manager count — the average number of board relationships each manager juggles. |
| Revenue Managed per Manager | Total revenue book divided by manager count — a per-manager productivity benchmark. |
| Managers Over Capacity | Count of managers whose doors or community count exceed the company's target threshold. |
Used by: Owners and regional directors managing staffing economics
Frequently asked questions
How many doors should one community manager handle?
It depends on portfolio type, but owners commonly benchmark portfolio (remote) managers against roughly 600–1,000 doors, with onsite managers far lower because a single large community absorbs them full-time. The template uses a 900-door target as the reference line; you'd set your own based on your service model and tier mix.
Why track communities per manager and not just doors?
Because relationship load doesn't scale with doors. A manager with a dozen small associations attends a dozen board meetings, fields a dozen sets of homeowner escalations, and manages a dozen vendor relationships — often more work than one large community at the same door count. The template shows both so you can spot relationship overload that a door count would hide.
Is this built on real staff data?
No. The sample is entirely synthetic and anonymized. To build your own, export each manager's assigned communities, doors, revenue, and tenure; we model it into a Power BI report you open in Power BI Desktop.
Build this report on your own data
Clone this HOA management template — describe it and we’ll generate sample data so you can try it free, or upload your own export. You get a fully modeled, branded Power BI project that opens in Power BI Desktop.
Use this as a template →