Tuesday, 8:14 a.m. A tenant emails the property manager: the conference room on four is hot again. The property manager forwards it to facilities at 9:40, after her standup. The facilities coordinator reads it at 11:00, between two vendor calls, and types it into the tracking sheet — priority “medium,” because the email didn’t say otherwise. It will sit there until Thursday, when he does his batch of vendor outreach. The vendor will quote Monday. Someone will approve the quote Wednesday, after one nudge. The tech arrives the following Tuesday.

Seven days from report to wrench — and notice what happened during those seven days: nothing. No diagnosis, no parts, no labor. The week was consumed entirely by the work order traveling — inbox to inbox, sheet to phone call, quote to approval queue. Every person in the chain did their job competently. The asset waited anyway.

When 95% of a work order’s life is waiting for the next handoff, adding people doesn’t compress it. The bottleneck isn’t anyone’s effort. It’s the architecture.

The pattern: latency lives between people, not in them

IFMA’s FM Pulse survey puts a number on the aggregate result: only 10% of FM organizations report all projects running on schedule. The reflex reading of that number is a staffing story — teams stretched thin, too much work, not enough hands. And teams are stretched. But walk the Tuesday timeline again and count where the seven days actually went: roughly thirty minutes of human work, and six-plus days of queue time between humans.

That ratio is the diagnosis. When 95% of a work order’s life is waiting for the next handoff, adding people doesn’t compress it — more hands means more inboxes, and more headcount applied to a coordination problem just adds synchronization overhead. The bottleneck isn’t anyone’s effort. It’s the architecture: a process where every step requires a person to notice, decide it’s their turn, and push the item to the next person who must also notice.

There’s a second cost hiding in the same architecture, quieter than the delay: information decay. The tenant’s email said “hot again” — again — and that word died in the forwarding chain. By the time the vendor was briefed, the job was “AC issue, floor four,” stripped of the history that would have told the tech this is the third call on the same VAV box this quarter, which changes both the fix and the conversation about replacing it. Manual chains don’t just move work slowly; they shed context at every hop, which is how a commercial building maintenance program ends up solving the same problem repeatedly at full price.

The same Tuesday, with the travel removed

Rerun the timeline with the work order system doing the traveling. The tenant’s report lands in a portal or is triggered by the zone sensor that’s been reading high since Monday. A work order creates itself at 8:14 — classified by asset, not by email tone, and carrying the asset’s full history, including the two prior calls. Dispatch routes to the contracted HVAC vendor within the pre-authorized threshold; no quote cycle, because the rate card already exists. The vendor’s confirmation, ETA, and completion photos flow back into the same record. Escalation rules watch the clock: no vendor confirmation in four hours, it escalates; SLA at risk, a human is alerted — the one genuinely useful role for human attention in the chain, exception handling rather than parcel carrying.

Wrench time: Wednesday morning. The week of travel became a day, and nobody worked harder — the work order just stopped commuting.

STAGE 1 Automated Intake

Work orders self-create with full asset history and context intact, eliminating the information decay of manual forwarding.

STAGE 2 Direct Dispatch

Pre-authorized rate cards and routing rules bypass the quote-and-approval queue, instantly dispatching to the right vendor.

STAGE 3 Targeted Escalation

Humans intervene only when escalation rules flag an SLA risk, reallocating human effort from parcel-carrying to problem-solving.

The deeper change isn’t speed, though. It’s that schedule performance becomes visible and attributable. In the manual chain, “why was this late” has no answer because the latency lived in five inboxes. In the automated chain, every interval is on the record: created 8:14, dispatched 8:16, confirmed 9:02, on-site 7:40 next day. The 10% statistic exists in large part because most operations can’t even see where their time goes — measurement is the prerequisite the manual model structurally lacks. Closing that visibility gap is the core of what Sweven FM’s work order layer does; the speed is a side effect.

The Latency Audit

The audit for your own operation takes one work order and a highlighter: pick last month’s slowest job, lay out its timeline, and color the hours a human was actually working on it versus the hours it spent traveling between humans. The ratio you find is your real bottleneck — and it has never once been the people.

Sources: