Every property manager knows the feeling: the work-order queue at 9am, longer than yesterday, with three residents already calling about tickets from two weeks ago. The instinct says we need another tech. Often the math says otherwise — a backlog is usually a queueing problem wearing an effort problem’s clothes.
Why do backlogs grow with good teams?
Three structural reasons. Intake is steady; capacity is spiky — turns, storms, and emergencies raid the same techs who work the queue. Tickets get processed in emotional order — loudest resident, newest complaint, whatever the walkie says — which maximizes drive time and context-switching. And re-visits multiply silently: arrive without the part, without access, or without the full picture, and one ticket becomes three trips. None of this is fixed by hiring; it’s fixed by structure.
The four moves that bend the curve
- Triage classes, enforced. Emergency (now), urgent (48h), routine (batched), cosmetic (scheduled). Every ticket gets a class at intake — and routine means batched, not “someday.”
- Batch by geography and trade. One tech, one building, eight routine tickets, one trip. Then all the door-and-hardware tickets portfolio-wide as a run. Batching is where the hidden capacity lives — drive time is the backlog’s best friend.
- The weekly aging ritual. Fifteen minutes, oldest tickets first, one question each: what does this need to close this week — part, access, vendor, or decision? Backlogs are made of tickets nobody has looked at lately.
- First-visit completeness. Photos at intake (residents will send them), parts staged before dispatch, access confirmed the day before. Every re-visit you prevent is a free tech-hour.
When is overflow the right answer?
When the backlog is capacity-shaped: turn season, storm weeks, a vacancy on the team. Overtime burns out the crew you have; a hire takes months and becomes fixed cost. A per-ticket overflow partner — insured, photo-documenting, working your priority list on documented standards, one consolidated invoice — converts the spike into a variable cost and keeps the queue from compounding. That’s precisely the shape of our multifamily program: responsive dispatch across a portfolio, measured however you measure.
The bottom line
Class the tickets, batch the trips, age-review weekly, arrive complete — and rent capacity for the spikes instead of staffing for them. Backlogs don’t yield to heroics; they yield to queues run like queues.