Subcontractor Job Handoff Checklist for Service Contractors
A roofing company hires a separate crew for a small gutter scope. The crew knows the address and start date, but not which elevation is included, where the materials will be staged, or who can approve an unexpected change. The work may begin on time and still produce avoidable rework. A subcontractor job handoff needs more than a calendar entry and a forwarded estimate.
Build the handoff around one question: could someone who missed the sales conversation perform and return the agreed work without guessing? This checklist focuses on coordination after a subcontractor has been selected through your normal business process. It does not replace your contracts or vendor qualification procedures. The goal is a usable scope package, a confirmed readiness decision, and a clear path back to the office.
Name one internal owner. Assign a person who is responsible for the subcontractor's operational questions from release through acceptance. The customer should also know whom to contact at your company. If sales, dispatch, and production can all issue different instructions, the subcontractor has no reliable source of truth. Identify a backup for absences and explain which decisions require the primary owner rather than letting every question become a group-message debate.
Package the specific scope. Include the job identifier, service address, work area, included tasks, exclusions, approved materials, and expected result. Reference the current document version and relevant photos. For a gutter scope, distinguish the front elevation from the entire property, identify downspout locations, and state whether removal and cleanup are included. Avoid sending the entire customer file when a smaller, accurate work package contains what the crew needs.
Describe the boundary with your own crew. List the work that must happen before the subcontractor arrives and what your team will do afterward. A separate finish crew cannot complete its work if the preceding installation is still changing. State who confirms readiness and what evidence is required. Treat this as an explicit dependency reviewed by a person; merely placing two visits in sequence does not prove the first scope is ready for the second.
Confirm materials and site readiness. Identify who supplies each major item, where it will be delivered, and who checks that the correct quantity and specification arrived. Add access arrangements, parking constraints, work-area restrictions, and the customer contact for arrival coordination. Keep sensitive access details in an appropriately restricted channel and share them only with the people who need them. A general note saying materials on site should not substitute for a specific readiness check.
Request acknowledgment of the package. Ask the subcontractor to confirm the scope version, planned work window, required materials, and any unresolved questions. A message marked delivered is not the same as an accepted assignment. Keep tentative scheduling separate from confirmed scheduling until the recipient has responded and your internal readiness checks are complete. If a crew cannot make the planned window, return that decision to the owner before communicating a replacement date to the customer.
Define the change approval path. Unexpected conditions should trigger a question to the designated owner, with a description and supporting evidence. State who can authorize a revised scope and who communicates any customer-facing price or timing change. Do not let a field conversation silently become an approved addition. Use the normal documented change process, and provide the subcontractor with the revised instruction before affected work continues. Preserve the earlier version so the sequence remains understandable.
Use a compact release note. A useful template is: job and address; scope version; included areas; exclusions; predecessor work accepted by; materials confirmed by; planned visit; internal owner and backup; change approval contact; required completion evidence; return-review deadline. Keep each entry factual. Replace ready with a statement such as front elevation cleared and specified materials counted by the production lead. That gives dispatch a reason to trust the release decision.
Keep Joby's record useful without assuming a vendor portal. Joby's lead page holds job details, visits, assignments, files, tasks, and history for your team. Keep the internal handoff summary and approved scope references with that job context. Share the necessary package through your established subcontractor communication channel. This process does not assume an external subcontractor portal, automatic vendor access, or a dedicated subcontractor approval engine. Confirm access permissions before inviting anyone into your workspace.
Agree on the return package before work begins. Specify the completion photos, scope confirmation, exceptions, remaining work, and material discrepancies your reviewer needs. Ask for photos that demonstrate the agreed result rather than a large undifferentiated image dump. For example, request an overview of each included elevation and a closer view of the agreed connection points. The reviewer should be able to compare the returned evidence with the released scope without recreating the original conversation.
Separate reported completion from acceptance. A crew saying finished should start the internal review, not automatically close every obligation. The owner checks the evidence, records any punch-list item, and assigns the next action. A missing photo and incomplete work are different exceptions and should be treated differently. Follow your agreed commercial process for subcontractor invoices; a scheduling status alone should not be interpreted as proof that every invoice line has been reviewed.
Walk through a simple handoff. Your crew finishes the prerequisite roof-edge work on Tuesday. The owner checks photos and material readiness, then releases the gutter scope for Thursday. On Thursday, the subcontractor reports a changed connection condition. The owner resolves the question through the approval process and issues the updated instruction. After completion, the reviewer compares photos with that version and records acceptance or a specific return item. Every transition has an owner and evidence.
Improve the recurring failure point. Review recent subcontractor jobs for missing scope, failed readiness, unapproved changes, and incomplete return evidence. Pick the most common cause and improve the relevant handoff field. More paperwork is rarely the objective. The useful improvement is fewer assumptions between companies and a job record that explains what was requested, what changed, and what your team actually accepted.
