How Many Communities Can One HOA Director Oversee?

The layer nobody benchmarks: director span of control

Span of control is the number of direct reports and communities one supervisor can oversee before quality slips. In property management, the whole industry benchmarks the manager layer (doors per manager, communities per manager) and almost nobody benchmarks the layer above it: the portfolio or regional director overseeing those managers.

That gap matters because the director is where quality control is supposed to live. When a manager escalates a delinquency dispute, a vendor scope fight, or a board member going sideways, the director is the human judgment gate. Stretch that gate too thin and it stops being a gate. It becomes a rubber stamp.

The National Association of Residential Property Managers has long pushed the industry to think in terms of capacity per person rather than raw door counts. The same discipline needs to reach the supervisory layer, because a director rubber-stamping at scale is far more dangerous than an overloaded manager. One bad approval can cost a client relationship.

Three signals a director has silently hit the ceiling

Directors rarely announce they are drowning. The workload does not spike; it thickens. Here are the three signals that a director has quietly crossed from oversight into rubber-stamping.

The uncomfortable part: the faster-approvals signal usually reads as a good thing on a dashboard. Turnaround time drops. Throughput looks healthy. Meanwhile the actual review depth has collapsed, and nobody sees it until a wrong approval blows up in front of a board.

This is why turnaround-time metrics can lie to you. A director clearing 40 approvals in a day is either exceptional or not reading them. Usually the latter.

Calculate your director's real weekly oversight load

The math that matters is not communities per director. It is weekly oversight hours: communities times escalations per community times minutes of real review per escalation. Run your own numbers below.

Plug in a typical mid-portfolio director: 55 communities, 4 escalations each per week, 12 minutes of genuine review per escalation. That is 44 hours a week on escalation review alone, before a single board call, client check-in, or coaching session. That director is not overseeing. That director is triaging survival.

Now notice which lever moves the number most. It is not the community count. It is the escalation rate. Cut escalations per community from 4 to 2 and the same director drops to 22 hours a week and gets their judgment back.

Where the hours actually go (it is not the hard calls)

Here is the surprise when you audit a director's inbox: most escalations are not hard. They are the same routine questions re-answered because nobody wrote the answer down the first time. The director is not deploying judgment. The director is being a search engine with a salary.

A manager escalates "what is our late fee grace period for this community?" The director looks it up in the CC&Rs and replies. Next week a different manager asks the same thing about a different community. The judgment content of that exchange is zero. The time cost is real and it repeats forever.

Read that table honestly and roughly 70 percent of what reaches the director never should have. It is decided, documented, or draftable. The director's ceiling is not intelligence or hours. It is the plumbing feeding pre-decided problems upward.

This is also why hiring a second director is often the wrong first move. Adding a director doubles your judgment capacity and your cost, when 70 percent of the load was never judgment. You just bought two search engines instead of one.

How pre-triage raises the ceiling without a second director

An agent that pre-triages and pre-drafts changes the escalation math directly. It answers the answered-before lookups from a community knowledge base, drafts the routine notices for a manager to send, and flags the vendor COI gaps before they become escalations. What reaches the director is the 15 percent that actually needs a human.

Concretely, this is the pattern behind agents like CAMeron holding institutional memory per community, Victor tracking COI and license expirations, and Riley handling first-response resident questions before they climb the ladder. The point is not the names. The point is that pre-decided work stops traveling upward.

The director in the "after" column spends slightly more time per escalation, because the calls left are the real ones and they deserve it. That is the trade you want. Fewer decisions, better decisions, and a director who can actually catch a problem before a board does.

This is the core editorial line at One Home Agent: the agent absorbs the documented, repetitive, deadline-driven busywork so the human keeps the judgment and the relationships. It does not replace the director. It stops wasting the director.

When to add a director anyway (the honest limit)

Pre-triage raises the ceiling; it does not remove it. Add a director when the residual judgment load, the real gray-area calls, exceeds what one person can hold with attention, or when relationship coverage breaks down.

“The mistake I see most is promoting-and-stretching a director to save a headcount, then discovering six months later they have been approving things they never read. Automate the escalations that were never judgment first. Then you can tell whether you actually need a person or just needed to stop drowning one.”

Todd Paton, Partner, One Home Agent

Diagnose your bottleneck before you staff for it