Turning A Maintenance Call Into A Work Order

Maintenance cost is usually discussed as a price per repair. A large share of it is actually created before any repair happens, in how the request is captured and routed.

The report is the weakest link

A tenant reports a symptom, not a diagnosis. Water on a floor could be a supply line, a drain, an appliance, a roof or condensation, and each requires a different trade.

A vague report produces the wrong technician, which means a visit that diagnoses rather than fixes, followed by a second visit with the right skills and parts.

Structured intake reduces this. Asking where, when it started, whether it is continuing and what was tried already turns a symptom into something dispatchable.

Triage determines cost more than pricing does

Requests fall into categories with different urgency. A loss of heat, water or security is an emergency; a dripping tap is routine; a scuffed wall is a turnover item.

Treating everything as urgent generates after-hours callouts at premium rates for problems that could have waited until a scheduled visit the following week.

Treating everything as routine produces the opposite failure, where a small leak becomes a floor replacement and a tenant relationship deteriorates in the meantime.

Batching and route efficiency

Travel time is a real cost whether it is billed by a contractor or absorbed by staff. Two visits to the same building on separate days cost more than one visit handling both.

Non-urgent items can be held briefly and grouped, which is standard practice for portfolios with several properties in the same area and workable even for a small holding.

The trade is response time against efficiency, and it should be an explicit policy rather than an accident of whoever answers the phone.

The record is what makes patterns visible

Individual repairs look random. A log of requests by unit and by system reveals which components are failing repeatedly and which are simply old.

Three service calls on the same heating unit within a year usually cost more in aggregate than replacement would have, but nobody sees that without a record.

The log also supports the capital plan, because it converts anecdote into a list of components approaching the end of their useful life.

Communication is part of the repair

Tenants tolerate delay far better when they know it exists. An acknowledgement with a realistic timeframe prevents the repeat calls that consume administrative time.

Unrealistic promises create the opposite effect, generating follow-up contacts, frustration and a sense that the problem is being ignored even when work is scheduled.

Closing the loop after completion also matters, because an unconfirmed repair is one that may not have worked and will resurface as a new request later.