Ask ten boards what their community association manager actually does, and you’ll get ten answers. That ambiguity is part of the problem — and the reason most boards under-utilize the role they’re paying for.
This guide outlines what a competent community association manager handles day-to-day, what they shouldn’t be doing (but often get pulled into), and how boards can structure the relationship to get the strategic value out of it.
The core responsibilities
- Board liaison. Primary contact for the board, prepares agendas, attends meetings, follows up on action items.
- Vendor coordination. Manages bid processes, oversees contractor performance, schedules routine and emergency work.
- Owner communication. First-line response to owner inquiries, complaint resolution, covenant questions.
- Financial oversight. Reviews and approves AP, monitors AR aging, presents monthly financials to the board.
- Property inspections. Routine site visits documenting condition, safety, and covenant compliance.
- Compliance and risk management. Insurance renewal coordination, regulatory deadlines, legal coordination.
What separates a good manager from an average one
Many managers can handle the operational checklist. Fewer bring the strategic disciplines that protect a community’s long-term value:
- Financial literacy. A good manager can present a balance sheet and income statement fluently — and answer board questions without deflecting to the accountant.
- Governance coaching. Helps boards run better meetings, understand their fiduciary obligations, and avoid common procedural mistakes.
- Honest advisory. Tells the board the right answer, not the easy one. This is the single biggest separator.
- Vendor scope discipline. Builds standardized scopes-of-work so bids are genuinely comparable. Most bid comparisons aren’t.
- Reserve and capital planning. Connects monthly financials to the reserve study and capital schedule — so funding decisions are grounded.
We’re not property managers — we’re community managers. The difference is the people, and the difference shows up in every decision the board makes.
— Doug Newman, CPE
What managers shouldn’t be doing (but often are)
- Acting as legal counsel. Managers should refer legal questions to association counsel, not opine.
- Performing reserve studies. Independence matters — the firm performing the study shouldn’t also be managing the funding.
- Selling insurance. Managers can coordinate with brokers and recommend strategy, but shouldn’t be earning commissions.
- Acting as the board. Managers advise; boards decide. Managers who routinely substitute their judgment for the board’s create governance risk.
How to structure the relationship for maximum value
- Set expectations early. Define response times, meeting cadence, and escalation paths in writing.
- Use the manager strategically, not transactionally. Bring the manager into budget conversations early, not as a presenter at the final meeting.
- Push for honest advisory. Tell the manager you want the best-practice answer, not validation.
- Audit the work through structured feedback. Post-meeting surveys are a low-cost way to track manager effectiveness over time.
The boards that get the most out of their management relationships are the ones that treat the manager as a governance partner — not a service provider taking requests.
Frequently asked
How many communities should one manager handle?
Best practice is 8–12 communities per manager, depending on community size and complexity. Managers running 15+ communities are stretched in ways that show up as missed details, delayed responses, and burnout. Our two-person model (manager + dedicated assistant) is built around this.
What credentials should a community manager have?
In Connecticut, a CAM license is required by state law. Beyond that, the CMCA designation (Certified Manager of Community Associations) is the entry-level professional credential. Leadership tiers include PCAM (the highest individual credential) and the AAMC accreditation for firms.
How accessible should our manager be?
Same-business-day acknowledgment is reasonable to expect. Resolution windows depend on the issue, but every message should be acknowledged. Communities that don't get this consistently usually have a staffing model that doesn't support it.