To your customer, the work is still yours
The customer signed with you. If a subcontractor services the chiller, it is still your service visit to them, with your deadline and your name on the service report.
That is why the problem with subcontracting is rarely technical quality. It is information: the job goes out by phone and comes back, if it comes back, a week later as a PDF.
In between, three questions stay open: did they accept it, when are they going, and what did they use? This article is about answering them without chasing anyone.
Every job is accepted or declined, with a reason
A job sent is not a job accepted. Until the subcontractor says yes, nobody has committed to anything, whatever your calendar says.
- Ask for an explicit answer on every job: accepted or declined.
- A decline comes with a reason. “No HVAC tech available that week” lets you reassign right away. Silence tells you nothing.
- Set a response deadline. For example, one business day for preventive work and two hours for an emergency. Past the deadline, treat it as declined.
It looks like red tape, and it is the opposite. Every timely decline with a reason is an emergency you do not discover on the day of the visit.
The person going proposes the date; the person accountable to the customer confirms it
The subcontractor knows its own schedule. You know the contract, the committed response time and the window of the preventive maintenance plan. Neither side should decide alone.
What works is splitting the roles: the subcontractor proposes a date and your dispatcher confirms it. If it falls inside the plan’s window, it is confirmed. If it does not, it is negotiated or reassigned.
Example
The plan says “quarterly inspection, with a 15-day window.” The inspection is due on the 5th and the subcontractor proposes the 12th: it fits the window and gets confirmed. If they proposed the 25th, it would not fit, and your dispatcher decides, not their calendar.
The key rule: the job date only changes when you confirm it. That way, what the customer sees and what your team sees always match.
Hours and parts, on the same job and kept apart from yours
What the subcontractor does and uses has to live on the same job as the rest of the equipment’s history. Not on their own form, in their email or on their invoice.
- Hours, in time blocks: when each block of work started and ended, or at least the time spent on each visit.
- Parts, with their reference, so your inventory adds up when the part is yours.
- No prices. The subcontractor records what was done and what was used. What it costs belongs in your agreement and their invoice, not on the service report.
- Kept separate from your team’s hours. If they get mixed, you will not know what each contract really costs or be able to compare one subcontractor with another.
With that in place, checking their invoice is no longer an act of faith. You compare what was billed with what was logged on each job, and the gaps stand out.
Close it on site, with the customer’s signature
A service report that arrives a week later is late for everything. Late for the customer, who asks whether the work was done; for billing; and for the next technician, who does not know what was replaced.
Subcontracted work should close the same way your own does: on site, signed by the person receiving it, with the report generated right then.
If you use checklists, use the same one for your team and for the subcontractor. An inspection cannot have two versions depending on who does it.
Who sees what at the subcontractor
A subcontractor is not one person. There is usually someone who accepts jobs, the technicians who go out, and someone in the office who handles purchase orders and invoices.
- The person who accepts sees the jobs sent to their company and assigns them to their people.
- The technician sees their own jobs, with what they need to do them: equipment, address, history and checklist.
- The back office sees purchase orders, delivery notes and invoices, not the jobs.
The practical way to do this is a subcontractor portal, where each person signs in with their own account. None of them sees your internal system, your other customers or your prices. A shared login “for the subcontractor” breaks all of this and erases who did what.
Common mistakes
- Sending the job over WhatsApp. Quick to send, impossible to track. Three days later, nobody knows whether it was accepted.
- The service report that arrives a week later, as a PDF someone retypes into the system.
- Subcontractor hours mixed with yours. The contract cost looks fine in the report and wrong in the P&L.
- Granting full access “to save time.” The subcontractor sees what it should not, and there is no trail of who did what.
- Not measuring each subcontractor. Without data, you renew the one you like best, not the one that performs best.
How to tell it is working
- Jobs answered on time, accepted or declined, per subcontractor.
- Jobs closed with a signed report the same day, versus those that arrive later.
- Response time met on subcontracted jobs, using the same rule as for your own team.
- Reopened jobs: jobs that come back after each subcontractor’s visit.
With three months of this data, the renewal talk with each subcontractor is about their response, their timeliness and their reopened jobs, not impressions. And if you work at sites with safety obligations, their documents belong in the same conversation: see contractor safety documents.
Last updated: