2026-10-21 · 6 min
Repair requests that get fixed on the first visit
Vague repair requests send the wrong trade with no parts and no access. How multi-site operators capture the details that get a job fixed on the first visit.
"Leaking tap, kitchen." That is the whole job. The plumber drives out, finds the loading dock locked, waits twenty minutes for someone with a key, then discovers the leak is the inlet valve on a commercial dishwasher. Photos, a quote, and back to the yard to order the part. Two callout fees, several days, and the kitchen running on a bucket in the meantime.
On paper nobody did anything wrong. The site manager reported the problem, ops passed it on and the contractor attended. The job simply started with too little information, and every step after that paid for it.
Across a portfolio of sites this is one of the quietest costs in repairs and maintenance. It never appears as its own line in a report. It shows up as second visits, wrong trades, after-hours rates on work that could have waited, and site staff answering the same questions over the phone.
The look-and-quote visit nobody budgeted for
- The wrong trade turns up. "No power in the back room" might need an electrician, a staff member resetting a tripped circuit, or the landlord's switchboard contractor.
- The van has no parts. Without a model number or a photo of the unit plate, the first visit becomes a survey.
- Access fails. Keys, dock times, induction, a named contact on shift. Miss one and an attendance turns into a wasted trip.
- Urgency is guessed. Mark everything urgent and you pay after-hours rates on cosmetic jobs. Mark nothing urgent and the cool room fails overnight.
- The same fault is raised three times. Three staff report one broken door and two contractors arrive.
Five details that turn a complaint into a job
- Exactly what and where. The asset or area, not just the site: "walk-in freezer, back of house", not "fridge".
- A photo of the fault and the label. The fault itself, plus the plate showing make, model and serial. One label photo can save a whole survey visit.
- What it is stopping. Can the site trade? Is anyone at risk? Is stock at risk? That sets priority, not the tone of the email.
- How to get in. When the site can take a contractor, any access steps, and who to ask for on the day.
- What has already been tried. Reset, breaker checked, water isolated. It stops the contractor repeating what staff already did, and it catches the jobs that never needed a contractor at all.
Sort it out before anyone gets in the van
Triage is the step between "a site reported something" and "a contractor holds a work order". When the request already carries the facts, it takes seconds.
Set trade and priority from facts, not adjectives. A short set of priority rules, such as safety risk, cannot trade, running degraded and cosmetic, beats reading the mood of a message.
Look for an open job on the same asset first. That catches duplicates, and it flags the repeat faults we covered in the same fault, the third callout.
Send everything with the job. The usual contractor for that site and trade gets the photos, the label and the access notes on the work order, so they can bring the likely part on the first trip.
Send incomplete requests back quickly, with one question. "Can you send a photo of the label?" costs the site a minute. Sending someone to find out costs a callout.
Make the right request the easy one
Site managers are serving customers, running a shift or covering for someone who called in sick. If logging a job takes longer than texting the regional manager, the text wins and the details disappear.
- Raise it from the phone, at the fault. Camera open, standing in front of the problem, in under a minute.
- Tap, don't type. Areas and assets listed per site, so "which fridge" is one tap.
- Ask only what changes the decision. The plumbing questions are not the electrical questions, so the form should change with the trade.
- Show the site what happens next. When site staff can see the job was confirmed and when the contractor will attend, they stop phoning to check, and they trust the process enough to use it properly next time. One shared queue makes that possible, as we set out in multi-site maintenance without forty inboxes.
- Let AI tidy the rushed ones. A short message can become a structured request with a suggested trade and priority, with ops confirming before it goes out. That is the kind of ops workflow automation that saves real hours without taking the decision away from people.
A ten-job audit you can run today
Pull ten recently closed repair jobs and answer five questions:
- How many took more than one visit?
- For each extra visit, was the cause parts, access, the wrong trade or missing information?
- How many original requests included a photo?
- How many were raised as urgent, and how many really were?
- How many times did someone phone the site to ask something the request should have said?
Every extra visit caused by a missing photo or access note is money spent on finding things out, not on fixing them. Count those visits across your sites and you have the business case.
From the site manager's phone to the right trade
We built OpsChase around this exact hand-off. Site managers log the issue on site, and ops turn it into a work order with the trade, priority and right assignee, so the details travel with the job instead of living in a text thread. Work goes to the site's usual contractor first, attend-by times stay visible, reminders escalate when a contractor goes quiet, and the job can only be marked complete once the photos, checklist and sign-off match your template. Datacat's OpsChase overview covers implementation and rollout across your sites.
When requests also need to reach a CRM, asset register or finance system, we build that link as part of a preferred contractor and work order system, or as a field mobile app your site teams will actually open. Look through work we have delivered, or send us the repair request that cost you two callouts and we will show you where the missing details went.