"How many maintenance techs do we need?" is one of the hardest questions in property management — and most answers start and end with a rule of thumb. The old standby, roughly one technician per 100 units, is a fine starting point and a poor stopping point. A 40-year-old garden community with a pool and constant turnover doesn't staff like a five-year-old building with no amenities, even at the same unit count. Real staffing comes from workload: how many work orders you actually get, how long they take, and how fast you've promised to close them. This 2026 guide walks the ratios, the factors that bend them, and how OXMAINT AI, the AI-powered CMMS, turns your real work-order history into a staffing number you can defend.
Property Maintenance Staffing 2026: Technicians Per Unit & Work Orders
Guessing at headcount and either burning out your techs or paying for idle hours? OXMAINT AI grounds staffing in real data: every request and inspection becomes a tracked work order, work orders reveal true volume and time-per-job, and that history turns "one tech per 100 units" into a number sized to your actual workload — plus the PM scheduling that keeps reactive load from spiraling.
The Rule of Thumb — and Why It's Only a Start
The industry shorthand is roughly one full-time maintenance technician per 100 occupied units. It's useful for a first-pass estimate and a sanity check, but it treats every unit as identical — which no portfolio ever is. Two properties at the same ratio can have wildly different actual workloads.
Start free and see your real workload per unit in OXMAINT AI.
- Treats a 40-year-old property like a brand-new one
- Ignores amenities — pools, elevators, gyms all add load
- Misses turnover spikes that flood techs with make-readies
- Assumes reactive-only; no credit for a working PM program
- Says nothing about the response times you've promised
- Actual work-order volume per property, per month
- Average time-to-complete by job type
- Turnover and make-ready cycles built into the plan
- PM load balanced against reactive demand
- Headcount sized to hit your response-time targets
Six Factors That Bend the Ratio
Start from the rule of thumb, then adjust for the realities of the property. These six factors are what separate a portfolio that needs more than one tech per 100 units from one that needs fewer.
Book a walkthrough to model these factors for your portfolio.
You Can't Right-Size Staffing on a Number You're Guessing.
The ratio is a guess until it's backed by your real work-order volume and time-per-job. OXMAINT AI turns that history into the staffing math — so you defend headcount with data, not a rule of thumb.
The Workload-Based Way to Size a Team
Instead of starting from units, start from work. The logic is simple, and every input comes straight from your CMMS. Walk it in four steps.
Sign up free and pull these inputs from your work orders in OXMAINT AI.
This is a planning framework, not a fixed formula — the right inputs depend on your properties, service standards and labor market. The point is that every number here can come from real work-order data instead of a guess.
Rule of Thumb vs. Data-Driven Staffing
| What matters | Rule-of-thumb ratio | Data-driven in OXMAINT AI |
|---|---|---|
| Basis | Unit count alone | Actual work-order volume & time |
| Property differences | Ignored | Age, amenities, turnover factored in |
| PM vs. reactive | Not distinguished | Balanced and scheduled |
| Response targets | Not considered | Sized to hit your SLAs |
| Defensibility | "Industry says so" | Your own numbers, on the record |
How the CMMS Right-Sizes Your Team
The reason work-order data beats a ratio is that it's specific to you. Here's what OXMAINT AI gives you to size — and keep sizing — a maintenance team.
Book a demo to see staffing analytics on your portfolio.
Signs You're Under- or Over-Staffed
- Work-order backlog climbing month over month
- Response and completion times slipping past targets
- PM tasks constantly deferred for emergencies
- Overtime creeping up and technician burnout rising
- Consistently low work-order volume per tech
- High idle time between jobs
- PM fully current with slack to spare
- Labor cost per unit well above comparable properties
Both states are visible in work-order data long before they show up in budgets or turnover — which is exactly why staffing decisions belong on your CMMS numbers, reviewed regularly, not set once and forgotten.
Frequently Asked Questions
Staff to the Work, Not the Rule of Thumb.
Turn real work-order volume, time-per-job and response targets into a defensible headcount — and keep it right as your portfolio changes — with OXMAINT AI, so you stop guessing between burnout and idle hours.
