How to onboard a new sub in one day

You booked a new sub for Monday. He is good, he came recommended, and you are already behind on the job he is walking into. So onboarding becomes whatever you can say to him in the two minutes between the tailgate and the front door: park over there, watch the finished floor, text me if you have a question. Then you walk off and hope.

By Wednesday you find out what you skipped. He does not have a certificate of insurance on file, so accounting cannot cut his check. He put a ladder against the freshly painted wall because nobody told him it was done. He has been texting your cell at 6am about things the foreman could have answered, because he does not have the foreman’s number. None of that is him being a bad sub. That is a sub who was never actually onboarded, and it costs you a full day of cleanup you did not plan for.

The fix is not a longer process. It is a one-day version you can run start to finish before he does any real work, so the whole relationship starts on solid ground instead of guesswork. Everything below fits on one page. This is a subcontractors problem every small shop hits the first time they bring outside help onto a job.

Paperwork before he parks

Two documents decide whether you can legally and financially work with this sub, and both have to exist before his truck is on your site: a current certificate of insurance naming you as additional insured, and a signed W-9. Chase these the day you book him, not the morning he shows up. A COI can take a day or two to come back from his agent, and if you wait until Monday you are either working with an uninsured sub or sending him home.

The reason this goes first is that it is the one part of onboarding you cannot fix later. Site rules you can repeat. A phone number you can text him. But if his ladder goes through a skylight on day one and his COI was never on file, that claim lands on your policy, and no amount of good work afterward undoes it. Get the paperwork in hand, then everything else is just a conversation.

Site rules in five minutes

Walk him the site once, and keep it to the things that will cost money if he does not know them. Not a safety lecture. The five things that are specific to this job:

• Where he parks and stages material, so he is not blocking the driveway the homeowner needs at 3pm.
• What is already finished and off limits, the painted wall, the set tile, the floor that got sealed yesterday.
• The customer’s one rule, the dog that cannot get out, the side gate that stays locked, the hours he is not allowed to run loud tools.
• Where the bathroom, water, and dumpster are, the small stuff that turns into interruptions if he has to ask.
• What finished looks like on this job, so his idea of done and yours are the same idea before he starts, not after.

That last one is where most sub relationships go sideways later, and it belongs in the walkthrough because it is cheapest to settle now. If done means the fixtures are set and the area is swept and photographed, say so on day one. When the scope is fuzzy, the argument comes at pay time, and by then you are both already angry. Our piece on scope fights with subs covers how to get that in writing without a contract addendum.

Who he calls, and how you reach him

A sub who does not know who to call defaults to calling you, about everything, at whatever hour the question occurs to him. So name it plainly before he starts: the foreman on this job is the person he texts for anything on site, here is the number, and here is what actually needs to reach you directly instead. Give him one clear line and he will use it. Leave it blank and your phone becomes the line by default.

Do the reverse too. Get his cell, confirm it is the number he actually reads, and find out how he prefers to get the next day’s plan. This is the difference between a sub who shows Tuesday because you confirmed the night before and a sub who forgot because the ask was buried in a voicemail. Our guide on getting subs to confirm they are coming tomorrow walks that day-before ritual. Setting the channel on day one is what makes it possible.

Where the job talks happen

Here is the part most onboarding skips, and it is the part that decides whether the next three weeks run clean. Tell him where the conversation about this job lives. If it is your cell, then every question, every photo, every change lands in a thread that also has your kid’s soccer schedule and forty other jobs in it, and by Thursday nobody can find the message that mattered.

Put the job talk somewhere the job owns. One place where the scope is written, the address and gate code sit at the top, the schedule changes update instead of scrolling away, and the photos of finished work land on the task they prove. When a sub knows that is where the job lives, he stops texting you at 6am and starts posting where the foreman and the office can both see it. That is also how you keep him accountable without driving over, which our piece on keeping subs accountable without babysitting gets into.

The one-day onboarding sheet

Run these in order and a new sub is fully onboarded before he touches a tool. Print it, keep it in the truck, and use the same one every time.

1. COI on file, current, naming you as additional insured.
2. W-9 signed, so accounting can pay him without chasing it later.
3. Site walkthrough, parking, off-limits areas, customer’s rule, the basics.
4. Definition of done, what finished looks like on this specific job.
5. Points of contact, who he texts for what, both numbers confirmed.
6. Send the invite to the job thread, so day one starts with him already inside the record.

That last line matters more than its length suggests. Every step above is something you tell him once and hope he remembers. The invite to the job thread is the step that makes the other five stick, because now the site rules, the scope, the contacts, and the address are not in his memory. They are in a place he can scroll to at 6am instead of texting you.

The math on a botched first day

Say you skip all of this and just point him at the job. He shows up without a COI, so his first day is paperwork instead of work, half a day gone before he lifts a finger. He does not know the floor was sealed, so you eat a re-seal, another half day and material. And for the first week he calls you six times a day with questions the foreman should have fielded, an hour of your time bled out in interruptions. Call it a lost day of production plus a week of noise, easily a thousand dollars once you count the re-work and your own time, on a sub who would have been dialed in by lunch if you had run the sheet.

None of that is the sub’s fault. He did the work he was hired for. He just never got the fifteen minutes of setup that would have let him do it without stepping on a landmine you forgot to mention.

That is what a job thread is built to hold: one place per job where the sub joins as a free guest, sees the same tasks and the same scope your crew sees, posts a photo when the work calls for it, and marks his part done so the foreman can approve it. The onboarding sheet gets him to the door. The thread is what keeps day two through day twenty from turning back into a pile of 6am texts. We are new, so put your next sub on it for one job and see whether the questions stop landing on your cell.