Short answer: a property-management capacity model should translate portfolio demand into work by role. Estimate recurring volume, event-driven volume, average handling time, service target, complexity, productive capacity, coverage, automation effect, and exception load. Compare required hours with available reviewed capacity, then set an explicit hiring, vendor, process, or automation decision.
AppFolio's performance maturity model treats team capacity as a progression from headcount growing with units to visible workload, defined system responsibilities, and more staff time devoted to judgment and relationships. Buildium's metrics guidance connects portfolio measures with operational decisions. This independent model is a planning aid, not a promise that one staffing ratio fits every portfolio, team, jurisdiction, property class, or service agreement.
Do not begin with units per employee
Unit count is a useful denominator but a weak workload explanation. Fifty scattered homes, fifty units in one building, and fifty short-term rentals can generate very different leasing, travel, cleaning, maintenance, accounting, and communication demand. Keep unit count, property type, geography, service scope, condition, resident profile, lease activity, and owner complexity visible.
Model work by demand driver
Examples include inquiries, applications, renewals, move-ins, move-outs, work orders, inspections, invoices, owner decisions, report packages, delinquencies, bookings, turns, documents, and escalations. Use actual historical volumes where available. Separate predictable recurring work from volatile events and seasonal peaks.
Measure handling time without punishing good work
Sample the complete workflow, including review, communication, documentation, follow-up, and exceptions. A fast close that omits evidence is not productive capacity. Use ranges and confidence levels instead of pretending every task takes the same number of minutes.
Calculate productive capacity honestly
Start with scheduled hours, then account for leave, training, meetings, administration, quality review, unavoidable interruption, and coverage duties. Do not plan every paid hour as task capacity. Preserve minimum coverage for emergencies, resident access, payment controls, and other duties that cannot wait for a spreadsheet average.
Apply complexity as an explanation
Complexity factors may include distance, building age, deferred maintenance, owner approval structure, regulated housing, commercial terms, short-term turns, language needs, manual integrations, and incomplete source data. Define each factor and periodically test whether it predicts workload. Do not use an unexplained multiplier to justify a preferred staffing answer.
Separate automation from eliminated responsibility
Automation may reduce data entry, reminders, routing, summaries, or scheduling. It does not eliminate source verification, exception handling, approvals, accountability, or service recovery. Use the AI workflow governance guide to assign human monitoring, boundaries, and failure handling.
Download the capacity-planning model
Download the editable portfolio capacity and staffing model (CSV). It includes demand drivers, periods, volumes, handling-time assumptions, required hours, complexity, automation, coverage, available capacity, gap, decision trigger, owner, and review evidence.
Plan field and office capacity together
A leasing promise can create inspection work. A maintenance service target can create dispatch and owner-approval demand. A monthly report depends on operating records and close review. Connect the model to the maintenance service-level matrix and reporting calendar so one department does not promise capacity another must supply.
Use explicit decision thresholds
Possible actions include rebalance portfolios, remove duplicate work, improve data quality, change service scope, train, automate a controlled step, add vendor coverage, hire, or decline growth temporarily. Define when the action is considered, who approves it, and what evidence confirms the result. Avoid waiting until missed service becomes the hiring signal.
Review scenarios before accepting growth
Model a normal month, peak leasing or turnover month, staff absence, major property onboarding, and service interruption. Connect projected owner growth to the CRM and onboarding workflow. A signed management agreement should not arrive before the operating team sees the demand it creates.
Frequently asked questions
What is a good property-manager-to-unit ratio?
There is no reliable universal ratio. Service scope, property type, geography, support roles, condition, technology, risk, and resident and owner demand can change capacity substantially. Use a transparent workload model and compare it with actual outcomes.
How often should the model be reviewed?
Review it on a regular operating cadence and whenever service scope, portfolio mix, staffing, technology, or performance changes materially. Keep prior assumptions so changes can be explained.
Official references
- AppFolio: team capacity, operating maturity, and system responsibility
- AppFolio: scheduled analysis and actionable operating data
- Buildium: portfolio metrics and operating decisions