How to Onboard a New Subcontractor Mid-Project Without Losing Track of Tasks

A subcontractor brought on at the start of a project absorbs context the same way everyone else does, gradually, as the job unfolds. A subcontractor brought in to replace someone mid-stream, or added to cover scope that was underestimated, doesn't get that runway. They're expected to pick up tasks that already have history: decisions made weeks ago, work that's partially done, dependencies that aren't obvious just from looking at the site. Skipping a deliberate onboarding step because "we need them starting tomorrow" is exactly how that history gets lost, and lost history on a job site usually resurfaces as rework or a dispute about what was actually agreed.

• The current scope of work specific to this project, not a generic version of what this trade usually does
• What's already been completed in their area of work, and what hasn't
• Any decisions or changes that affect their scope, especially ones made verbally that only exist in someone's memory
• Who they report to and who to contact for questions, by name
• Current schedule commitments and deadlines that are already in motion

A new subcontractor coming in under time pressure is exactly the situation where it's tempting to let them start work while paperwork catches up. That's backward. Confirm a current certificate of insurance and any required licensing before they're on site, not after, because the point of requiring it is to have coverage in place before there's any exposure, not to have a paper trail explaining why there wasn't.

The fastest way to lose track of a new subcontractor's work is to manage them through a side conversation, texts, a phone call, a quick chat on site, while everyone else's tasks live in the project's actual task list. Add their work as tasks in the same place the rest of the project is tracked, with clear ownership and due dates, from their very first day. This is also where assigning and tracking tasks matters most, because a new subcontractor is the person on the project least likely to already know what "normal" looks like, and most likely to need a task spelled out rather than assumed.

A new subcontractor often isn't going to be set up on your project software on day one, and may never be, especially a smaller outfit that prefers email or text. Make sure there's a working way to reach them and for them to reach you about the specific project and tasks at hand, including sending messages to people outside your core team by email when that's the practical option. The goal is that a question about their work gets tracked against the project it's actually about, not buried in a personal phone's message history that nobody else can see.

A new subcontractor is more likely than anyone else on the job to run into something unclear in the plans or scope, because they don't have the weeks of context everyone else has already absorbed. Treat each of those questions the way you'd treat any request for clarification on a project: as a specific, assigned item with an owner and a due date, not a verbal question that gets a verbal answer and then disappears. A task works fine for this. What matters is that the question and its answer end up somewhere everyone can find later, rather than only in the memory of whoever happened to answer it on site.

A new subcontractor is unlikely to flag that something seems off during their first few days, even if it genuinely is, because they don't yet have the standing or the context to know whether it's normal. A short, deliberate check-in partway through their first week, specifically asking whether anything about the scope or site conditions is unclear, catches misunderstandings while they're still cheap to fix rather than after a chunk of work has already gone the wrong direction.

When a new subcontractor is replacing one who left mid-job, whether over a schedule conflict, a performance issue, or something else, it's worth getting whatever documentation or walkthrough is realistically available from the outgoing sub before they're gone for good. Even a short conversation about what was done, what materials are on site, and what was still in progress can save the incoming subcontractor from redoing work or missing something that was already handled. This isn't always possible, especially if the departure was contentious, but it's worth attempting before assuming the new sub will have to figure everything out from scratch.

The project, subcontractor, and people below are fictional and for illustration only. They do not describe a real ConstruDo customer or project.

Three weeks into a restaurant buildout, the original plumbing subcontractor walked off the job over a payment dispute with the owner, leaving the rough-in half finished. The general contractor brought in a new subcontractor, Example Plumbing LLC, and needed them productive within two days.

Before the new crew arrived, the project manager documented exactly what had been completed, pulled the certificate of insurance, and created a task list specific to the remaining rough-in work, noting a change the owner had verbally requested for a relocated floor drain that the original sub never got around to.

On day two, the new foreman asked whether the drain relocation had actually been approved or just discussed. Because it was logged as a task with the owner's name attached rather than left as a verbal note, the project manager could confirm it in minutes instead of having to track down who said what to whom.