Most businesses do not plan for that.

A customer complaint is hard enough to manage when your own engineer attended the job. It is much harder when the person on site was a subcontractor and your job record tells you almost nothing.

The customer says the visit was vague. The follow-up work was not confirmed. Nothing has arrived in writing. You open the job and realise the photos are missing, the notes are thin and the evidence you need was never captured properly.

Now you are trying to manage a customer conversation about work you effectively handed off and hoped would go well.

The gap nobody talks about honestly

Subcontractors are a practical reality in the industries I work with. They cover specialist skills you don't carry in-house, they solve for geography, and they flex your capacity at peak periods, all without you carrying the overhead of employing for it.

The problem isn't using them. It's how most businesses manage them once they do.

The relationship tends to be transactional. A job gets passed over. The expectation is that the subcontractor knows what they're doing and will handle it professionally. You send the job details. They attend. You wait to hear back. The invoice arrives and life moves on.

That works. Until it doesn't.

What the customer actually experiences

The customer isn't looking at your org chart when someone knocks on their door. They're not thinking about whether this person is directly employed or brought in for the job. They see a visit connected to your company, your contract, and your name on the original paperwork.

What happens on that visit becomes part of what they think of you: how it was communicated, how professionally it was handled, and whether the evidence they needed for compliance or insurance purposes actually arrived. All of that reflects on your business, not the subcontractor's.

The customer does not separate their experience into employed engineer, subcontractor and back-office process. They just remember whether your business felt organised.

This is where a lot of businesses are carrying more reputational risk than they realise.

The reputational risk is only part of it. A weak job record also means slower invoicing, more disputes, and compliance gaps you can't always close after the fact.

Where this usually falls apart

The issue isn't poor workmanship, most experienced tradespeople are more than capable. It's that the operational standards they're working to aren't clearly defined, and nobody has checked whether they've been met.

Job notes come back thin or missing entirely. Photos aren't taken, or aren't linked to the right job. Compliance certificates arrive days later in a separate email rather than as part of a properly closed job record. The customer hasn't been told what was found, what was done, or what comes next.

The scope was vague going in, the job record was weak coming out, and everything in between was assumed rather than confirmed.

What better businesses do differently

The businesses that handle subcontractors well don't necessarily spend more time on it. They just set the expectations earlier and hold to them consistently.

Before a job goes out, the scope is clearly documented. Not a rough brief. An actual record of what's required, what evidence needs to come back, and what the customer has been told to expect. The subcontractor knows what a properly completed job looks like, not just where they need to attend and what they need to fix.

During and after the visit, the job is managed the same way as every other job. The subcontractor captures what they've done, uploads what's needed, and closes the job in a way that means the office has everything without having to chase. The customer gets what they expected. The compliance record is clean. There are no gaps to fill in later and no conversations to manage from a position of not knowing.

This is where a system like Joblogic's Subcontractor Portal earns its place: subcontractors connect through the same Mobile Engineer App your own team uses, so the evidence comes back the same way it always does, not as an afterthought.

That's not about micromanaging people who know their trade. It's about making the standard clear and giving everyone the means and system to meet it.

The onboarding problem nobody fixes

A lot of this friction starts before the job itself. Most businesses don't onboard subcontractors properly. There might be a brief conversation at the start of the relationship, maybe a terms of business document, but the standards that actually matter, how jobs should be captured, what evidence is expected, how communication should work, rarely get more than a five-minute phone call, if that.

Then when the standards aren't met, it gets treated as a failing of the individual rather than a gap in the setup.

If you want subcontractors to work to your standards, you have to share them clearly. In a way that's accessible and practical, not buried in a document that nobody reads a second time.

One final thought

Your reputation is built in the moments you're not there to supervise. When your subcontractor pulls up to a site, they're carrying your name with them. The customer experience they deliver is the one your business gets judged on.

If your current approach to subcontractor management is to assign the job and hope, that's not a strategy. That's luck.

The good news is that this is one of the more fixable problems in field service. It doesn't require a wholesale change to how you work. It requires clearer expectations going in, a consistent standard for what comes back, and a system that makes the right workflow easy to follow rather than easy to skip.

Get that right and subcontractors stop feeling like work you have handed away. They become a controlled, visible and trusted extension of what your business delivers.