Stop losing jobs in subcontractor gaps

Most service companies do not lose the subcontractor job because the sub is bad at the work. They lose it in the gap between your visit and theirs. The homeowner already told you the story. Then a second person shows up and asks for it again, quotes a different scope, or leaves without the photo you need to invoice.

A shared job file does not have to be fancy. It has to travel with the work. When the sub sees the same notes, photos, and next step you do, callbacks drop and the customer stops feeling like they hired two companies.

The gap is a missing file, not a bad personality

You can like the sub and still lose money on the job. The leak is information. Your tech wrote the gate code in a text. The office has the estimate in email. The sub has a verbal note that says to look at the unit on Oak Street. None of those are the job.

By the time someone calls you angry, the work may already be done wrong, skipped, or finished in a way you cannot bill cleanly.

Owners often treat this as a people issue. They switch subs, add a warning in the group chat, and hope the next one listens better. The same gap shows up with the new sub, because the handoff never had a home.

What the customer actually feels

They booked you. Your name is on the truck, the invoice, and the review. When the sub asks what is going on, the customer hears that nobody is in charge.

That is how a decent repair becomes a one-star story. Not always because the patch looks bad. Because the second visit felt like a cold start. They repeat the dog's name, the gate code, and the promise you made on Tuesday. Trust drops before the tool bag opens.

Referrals die the same way. A neighbor will not pass along a company that needed three phone calls to finish a hole in the wall. They remember the confusion, not the repair.

Where the money leaks out

The cost is rarely one dramatic failure. It is a stack of small leaks that show up on Friday.

A sub waits on site because access notes never left the first tech's phone.
Extra work gets promised in the driveway, then disputed on the invoice.
Completion photos never come back, so the office cannot close or get paid.
Warranty visits start from zero because the first scope is not attached.
Your crew burns an hour reconstructing a job that already happened.

One wasted wait in Tampa traffic can erase the margin on a small patch or a filter change. Two of those in a week is a scheduling problem, not a bad day.

A leak job in Brandon

Picture a plumbing company working around Brandon and Riverview. On Tuesday a tech finds a supply line leak under a kitchen sink. He shuts the water off, writes a quote for the repair, and tells the homeowner a drywall sub will close the access hole on Thursday.

The real details live in a group text. Kitchen, left sink, dog in the yard, HOA gate code, customer works until 4. Thursday morning the sub calls the office because the gate code is not on the work order. The office calls the tech, who is under a house in Riverview. The sub waits. The homeowner leaves a key with a neighbor and goes to work irritated.

The patch gets done. The photo of the closed wall never makes it back to the office. Friday the invoice covers the plumbing only. The customer emails asking why the wall still looks open in the picture she expected, and why nobody told her the sub would need a key. None of that was a skill problem. It was a file problem.

The same pattern shows up with HVAC companies that sub duct work, restoration crews that sub contents or mold, and landscapers that sub irrigation. The trade changes. The gap does not.

The file a sub should see before they roll

If a sub cannot open the job and answer these without calling you, the handoff is not ready. Use this as a release checklist, not a wish list.

Customer name, address, gate or lockbox, pets, and parking notes.
What you already did, and what is left.
Exact scope in plain language, including what is not included.
Photos from the first visit, with a short label on each.
Who approved the price, and how they expect to pay.
The arrival window the customer was actually promised.
Who to call if the scope changes, and what the sub must not promise.
The photo or note you need before they leave the driveway.

If any of those live only in someone's head, the job is already at risk. A text that says "same as last time" is not a scope.

Five rules before you release the work

You do not need a long policy manual. You need rules your office can apply on a busy morning without a meeting.

No roll without a written scope the customer has already seen.
One place for photos. A text can notify. It is not the archive.
The sub does not invent a new price on site. Changes come back to you first.
Promise one arrival window, and put that window in the file.
The job is not closed until their completion note and photo are attached.

Rule three protects margin. Rule five protects cash. Owners who skip the completion photo often discover the gap only when the customer disputes the bill.

Read the rules out loud once with the sub. Then put them on the work order so a fill-in dispatcher can follow them when you are on a roof.

Signs the handoff is already leaking

You do not need a report to see this. Look at the last ten jobs that used a sub.

The office called the tech for a detail the sub should have had.
The customer had to repeat access instructions.
An extra charge appeared that was not on the original quote.
The invoice waited because proof of completion was missing.
A review mentioned "they did not seem to know why they were there."

Two or more of those on a short list means the process is the problem. Hiring a sharper sub will not close it.

Fix the file before you add another sub

If you only send work out a few times a month, you do not need a large software project. You need one job record that the office, the tech, and the sub can open. A shared folder with a strict name can carry you for a while. It breaks when two people edit different copies, or when the link is buried in a thread from last month.

The sturdier version is simple. The booking or job tool is the file. Notes, photos, scope, arrival window, and the sub's status live there. A text can say the Thursday file is ready. It should not be the file.

Start with the next five sub jobs, not a company-wide rollout. Use the checklist. Hold the truck if the scope or the access note is missing. Track how many "where is the code?" calls you stop. That number is the business case.

Subcontractor gaps feel like people problems because the customer is upset and someone has to answer the phone. Most of the time the people were fine. The job details did not move with the work. A focused system, even a simple job file tied to the original booking, keeps the scope and the photos in one place so the second visit feels like the same company.