Datacat

Insights

2026-10-13 · 6 min

Preferred contractors who go quiet — response clocks that keep jobs moving

Your usual contractor goes quiet and sites start ringing around. Put a response clock and a named owner on every work order, and escalate inside your own list.

A site manager logs a tripped circuit in the kitchen on Monday morning. The work order goes to your usual electrician, the one everyone likes. By Wednesday nobody has heard anything. The site manager rings the facilities coordinator, who rings the electrician's office, who says the job is "in the system" and someone will be out this week. Thursday comes and goes. On Friday the site manager calls a local electrician off a fridge magnet, pays on a credit card, and stops trusting the process.

Nothing dramatic happened. The electrician was busy, not careless. The coordinator was juggling forty other open jobs. The problem is that the work order had no clock on it, no promised window anyone could see, and no single person whose job it was to notice the silence.

Multi-site teams rarely lose control of maintenance in one big failure. They lose it one quiet job at a time, until the open list is full of work orders nobody can explain.

Where response and attendance break down

The same pattern shows up across retail portfolios, offices, hospitality groups, schools, and care campuses.

  • Sent is treated as handled. Once a work order leaves the inbox, it drops off everyone's radar. Nobody checks whether the contractor accepted it, let alone booked it.
  • Promised windows live in phone calls. "Tuesday afternoon" or "first thing next week" gets agreed verbally and written down nowhere, so nobody can tell when it has been missed.
  • Nobody owns the nudge. The site assumes facilities is on it. Facilities assumes the contractor is on it. The contractor assumes the job can wait because nobody has asked.
  • Escalation means starting again. When a contractor goes quiet, the only move is to ring around or put the job out to quote, which costs days and throws away the relationship with your usual trades.
  • Stale jobs pile up silently. Open work orders from three weeks ago sit next to yesterday's, with no way to tell which are waiting on parts and which have simply been forgotten.

The result is the outcome nobody wants: sites stop logging jobs properly and start ringing around themselves, which breaks the record you rely on for spend, compliance, and work-order proof leadership can trust.

What good looks like

Holding contractors to a response standard does not mean more phone calls or a tougher contract clause. It means every job carries its own clock, and the system does the noticing so your team only steps in when it matters.

Every work order has a response clock. Urgency sets the expectation: an urgent job might need confirmation within the hour, a routine one within a business day. The clock starts when the job is sent, not when someone remembers to check.

Confirmation and attendance are separate steps. The contractor confirms they have the job, then commits to an attendance window. Both are recorded against the work order, so "they said they'd come" becomes a date and time anyone can see.

Follow-up is automatic before it is personal. When a contractor has not accepted in time, they get a reminder. When a window is about to pass, they get another. Your coordinator only hears about it when the reminders have not worked, so their day goes on the jobs that genuinely need a human.

Every job has a named owner. One person in ops owns each open work order until it is closed out. If they are on leave, ownership moves with the queue, not with someone's memory.

Escalation stays inside your usual contractors first. If the first contractor does not respond in time, the job offers to the next one on your ranked list for that trade and site, then the next. Going to quote is the last step, not the first, as in RFQ overflow when the preferred book is full.

The site sees where its job is. The person who logged the request can see that it has been accepted, when the contractor is due, and when it has been closed out with photos and sign-off. They stop ringing because they no longer need to.

Signals your contractors are setting the pace, not you

  • Nobody can say, without phoning around, which open jobs have not been accepted yet.
  • Attendance windows are agreed by phone and never recorded.
  • Work orders older than two weeks have no note explaining why they are still open.
  • Site managers regularly book their own trades because "the system is too slow".
  • When a contractor goes quiet, the next step is a fresh round of quotes.

One of those is a busy week. Three or more means your contractors are deciding your response times, and your sites are quietly working around you.

What good looks like after the first quarter

  • Every open work order shows whether it has been accepted, when attendance is due, and who in ops owns it.
  • Reminders reach the contractor before a window is missed, not after a site complains.
  • Jobs that stall move to the next contractor on your list automatically, with quotes reserved for real gaps.
  • Stale jobs surface on their own, so the open list only holds work that is genuinely in progress.
  • Response and attendance records give you a fair, factual basis for the next conversation with each contractor, across every site in one queue.

This is the problem we built OpsChase to solve: facilities repair software for multi-site teams that sends work to your usual contractors first, follows up until they accept and attend, moves stalled jobs down your ranked list before anything goes to quote, and closes every job with photos and sign-off. Sites see progress without picking up the phone. See how it fits on the OpsChase product page.

Running response standards across a larger contractor base or a custom service model? We build CRM and ops platforms and ops workflow automation around the clocks and escalation rules your operation actually runs on, and contractor and partner portals so confirmation and attendance land in one place. Browse selected work, book paid strategy and discovery if you are still scoping, or talk to Datacat.