△
Coordination Cue
Task-specific guidance for ordinary trade-interface and handoff issues.
Project 08
Coordinate Subcontractors and Trade Hand-Offs
Create and execute one trade-coordination and handoff plan that defines responsibilities, readiness conditions, access, interfaces, acceptance, deficiencies, and protection for sequential residential work, using approved subcontracts, purchase scopes, the WBS, drawings, specifications, and the current schedule as the controlling information.
Field Cue System
These cues appear at the point of work. They identify trade-interface, access, and readiness issues before they become unsafe stacking, damaged work, or unclear responsibility.
✋
Critical Coordination Cue
Unsafe trade stacking, damaged work, or an unclear responsibility gap is possible.
⛑
Field Coordination Cue
Practical access, staging, and communication guidance between trades.
▤
Authority Alert
License, insurance, permit, or competent-person conditions vary by trade. Verify before mobilization.
▧
Contract Instruction Cue
Follow the executed subcontract's specific terms for scope, notice, and acceptance.
▱
Documentation Cue
Recordkeeping and traceability guidance for handoff and interface records.
Job Overview
This project qualifies you to create and operate a trade-coordination and handoff system for a residential project — the controlling process that defines which trade is responsible for which task, what condition an area must be in before the next trade takes over, and how that handoff is inspected, accepted, and documented. The finished work product is one approved trade-responsibility matrix, a set of measurable handoff conditions by area or system, an area-release and handoff form in active use, and a closed set of handoff records showing predecessor deficiencies, successor acceptance, and required documentation.
You will collect the approved subcontracts, purchase scopes, WBS, drawings, specifications, and schedule; build a trade-responsibility matrix and resolve scope gaps and overlaps in writing; identify every physical interface between trades and the dependencies at that interface; define measurable handoff conditions for each area or system; confirm each trade's mobilization readiness; coordinate work zones, penetrations, and routing to prevent damage and unsafe stacking; inspect predecessor work, record deficiencies, and accept or reject the handoff; protect accepted work; and close each handoff record only when documentation is complete.
This project depends on the scope baseline from Project 01, the WBS from Project 03, the sequence logic from Project 04, the baseline schedule from Project 05, the lookahead from Project 06, and the procurement plan from Project 07. It supplies the accepted, documented trade conditions that the coordination meetings in Project 09, the RFI process in Project 10, and the quality-control plan in Project 13 all depend on.
Skills You Will Demonstrate
- PM-043 — Identify trade responsibilities.
- PM-044 — Schedule trade access.
- PM-045 — Define handoff conditions.
- PM-046 — Communicate readiness requirements.
- PM-047 — Prevent trade conflicts.
- PM-048 — Document trade handoffs.
Where This Skill Fits
The trade-responsibility matrix built here is the direct successor to the responsibility matrix first created in Project 01 and refined in the Project 03 WBS dictionary — it takes those role assignments down to the level of individual physical interfaces between trades. The measurable handoff conditions defined here give the two-week lookahead from Project 06 a concrete readiness test, and they give the coordination meetings in Project 09 a specific agenda item: unresolved interface deficiencies.
The discipline of defining acceptance by measurable condition rather than an informal statement that an area is "ready enough" is the same discipline used later in the Project 13 quality-control plan and the Project 14 punch-list process. A handoff accepted without measurable conditions produces exactly the kind of disputed responsibility this project is built to prevent.
Scope and Intended Use
This project covers:
- collecting approved subcontracts, purchase scopes, WBS packages, drawings, specifications, schedule, and quality requirements
- building a trade-responsibility matrix and resolving scope gaps and overlaps in writing before mobilization
- identifying every physical, information, material, access, utility, equipment, and inspection interface between trades
- defining measurable handoff conditions by area or system, and defining who inspects and who accepts each handoff
- confirming subcontractor licenses, insurance, permits, safety documentation, staffing, and understanding of scope before mobilization
- coordinating work zones, penetrations, routing, and finish-trade sequencing to prevent unsafe stacking and rework
- inspecting predecessor work, recording deficiencies, and recording acceptance, conditional acceptance, or rejection
- protecting accepted work, tracking trade-caused damage, and closing the handoff record with complete documentation
This project does not authorize the learner to:
- direct a subcontractor to perform work outside its license, permit, insurance, training, or contractual scope
- transfer employer safety responsibility from the subcontractor, competent person, or permit holder to project coordination
- accept a handoff on behalf of a party whose approval the subcontract or quality plan specifically requires
- waive a required inspection, test, or authority approval merely to keep the schedule moving
Any conflict between a subcontract scope, the WBS package it is tied to, and the current approved drawings must be resolved in writing before that trade mobilizes.
Reference Conventions
Establish these references before the trade-responsibility matrix is built, and do not change them mid-project without a recorded revision.
| Term | Definition |
|---|---|
| Trade interface | A physical, information, material, access, utility, equipment, or inspection point where one trade's work depends on or affects another trade's work |
| Handoff condition | A measurable dimension, substrate, dryness, cleanliness, temperature, access, backing, rough-in, testing, approval, or protection requirement that must be met before an area is released to the next trade |
| Predecessor | The trade whose completed work must be inspected and accepted before a successor trade may begin in that area |
| Successor | The trade that receives the released area and inspects the predecessor's work before beginning |
| Conditional acceptance | Acceptance of an area with recorded exceptions that do not release the predecessor from correction responsibility |
| Trade stacking | Multiple trades working in the same area at the same time in a way that creates unsafe congestion, damaged work, lost productivity, or unclear responsibility |
Handoff Record Identification
Before releasing an area to the next trade, record the handoff identification directly on the area-release and handoff form:
Project name: ______ Area or system: ______ Predecessor trade: ______ Successor trade: ______
Date inspected: ____________ Inspected by: ____________ Result (accepted / conditional / rejected): ____________
Prerequisites
- Approved subcontracts, purchase scopes, and WBS packages for the trades being coordinated
- Access to current approved drawings, specifications, master schedule, and two-week lookahead
- Access to the Project 13 quality-control plan for acceptance criteria that intersect trade handoffs
- A trade-responsibility matrix template, area-release and handoff form, interface deficiency log, and trade-damage log ready for use
- Confirmation of subcontractor licenses, insurance, and safety documentation on file before mobilization
Common Field Fundamentals
Every trade handoff in this book, from a rough framing-to-MEP handoff to the final punch-list closure in Project 14, follows the same sequence: assign responsibility, identify the interface, define the measurable condition, confirm readiness, inspect, accept or reject, protect, and document. Learning that sequence here, across the full residential trade sequence, means every later coordination task starts from a method you already trust.
Responsibility matrixOne primary trade assigned to labor, material, layout, backing, penetrations, protection, testing, cleanup
InterfacesEvery physical, information, material, access, utility, equipment, and inspection dependency identified
Handoff conditionsMeasurable criteria for dimension, substrate, dryness, cleanliness, access, backing, and approval
Mobilization readinessLicense, insurance, documents, crew, access, and safety confirmed before a trade starts
Zone coordinationWork zones, penetrations, and routing coordinated to prevent stacking and damage
InspectionPredecessor work inspected before an area is released to the successor
AcceptanceAccepted, conditionally accepted, or rejected, with deficiencies recorded
ClosureHandoff record closed only after correction, successor acceptance, and documentation are complete
Interfaces, Handoff Conditions, and Acceptance
Every trade-coordination plan must identify the exact point at which one trade's work ends and the next trade's dependency begins, and must state the measurable condition that area must meet before release. Write the handoff condition immediately next to the interface it governs so a reader cannot mistake a general description of readiness for a specific, checkable requirement. An interface left ambiguous between predecessor and successor responsibility becomes a disputed deficiency, a damaged work claim, or an unsafe trade-stacking condition once construction proceeds.
PM-043 – PM-048
Trade Coordination / Handoff Qualification
Residential Trade-Coordination and Handoff Plan
A. Finished-Project Specification
Deliverable: one documented trade-coordination system for the residential project, containing a trade-responsibility matrix with resolved scope boundaries, an identified set of physical and information interfaces between trades, measurable handoff conditions by area or system, confirmed mobilization readiness for each trade, coordinated work zones and penetration sequencing, and a closed set of area-release and handoff records showing inspection, deficiencies, acceptance, protection, and correction.
B. Trade-Coordination Document Schedule
| Section | Content | Source | Purpose |
|---|---|---|---|
| Trade-responsibility matrix | Labor, material, equipment, layout, backing, penetrations, protection, testing, cleanup, permits, closeout by trade | Subcontracts, purchase scopes, WBS | Assigns one primary responsible party to each category of work |
| Interface list | Every physical, information, material, access, utility, equipment, inspection dependency | Drawings, specifications, WBS | Identifies every point where trades depend on each other |
| Handoff conditions | Dimension, substrate, dryness, cleanliness, temperature, access, backing, rough-in, testing, approval, protection criteria | Drawings, specifications, quality plan | Defines a measurable, checkable release condition per area or system |
| Area-release and handoff form | Predecessor, successor, inspection date, result, deficiencies, acceptance status | Field inspection | Records each handoff as an auditable event |
| Mobilization readiness | License, insurance, permits, safety documentation, staffing, supervision, documents distributed | Subcontract, safety plan, document register | Confirms a trade is authorized and prepared to mobilize |
| Zone coordination | Work zones, penetrations, sleeves, blocking, embeds, routing, shared equipment | Drawings, schedule, safety plan | Prevents unsafe stacking, damage, and rework |
| Deficiency and damage logs | Location, requirement, responsible party, due date; trade-caused damage and correction responsibility | Field inspection | Tracks unresolved items to verified closure |
C. Information and Document Takeoff
- Source records: approved subcontracts, purchase scopes, WBS packages, drawings, specifications, schedule, and quality requirements, sufficient to complete every section of the document schedule above without inventing missing scope information.
- Comparison records: the master schedule and two-week lookahead, used in Steps 12–13 to link handoffs to the current field sequence.
- Verification records: subcontractor licenses, insurance certificates, permits, and safety documentation, confirmed in Step 13 before mobilization.
- Closure records: the area-release and handoff form, interface deficiency log, and trade-damage log, maintained from first mobilization through Project 14 punch-list closure.
D. Acceptance Standards
| Check | Standard |
|---|---|
| Responsibility matrix | Exactly one primary responsible party assigned to each category of work; no category left to "trades" generally |
| Interfaces | Every physical, information, material, access, utility, equipment, and inspection dependency between trades is identified |
| Handoff conditions | Stated as a measurable, checkable requirement, not a general impression of readiness |
| Mobilization readiness | License, insurance, permits, safety documentation, staffing, and current documents confirmed before the trade begins |
| Zone coordination | Work zones, penetrations, and shared equipment scheduled to avoid unsafe trade stacking |
| Handoff records | Every area or system handoff recorded with inspection date, result, deficiencies, and acceptance status |
| Closure | Handoff record closed only after predecessor deficiencies, successor acceptance, and required documentation are complete |
E. Preparation — Build the Responsibility Matrix and Identify Interfaces
- Collect approved subcontracts, purchase scopes, WBS packages, drawings, specifications, schedule, and quality requirements. Assemble every available document before building the matrix.
- Create a trade-responsibility matrix for labor, material, equipment, layout, backing, penetrations, protection, testing, cleanup, permits, and closeout. Assign one primary responsible party to each category.
- Identify gaps and overlaps among trade scopes. Compare each subcontract scope against the WBS package it is tied to.
- Resolve scope boundaries in writing before mobilization. Issue a written clarification for every gap or overlap found in Step 3.
- Identify every physical interface between trades. Walk the drawings and specifications by area and system to find each point of dependency.
- Identify information, material, access, utility, equipment, and inspection dependencies for each interface. Record what each successor trade needs from its predecessor at that interface.
F. Define Measurable Handoff Conditions
- Define measurable handoff conditions for each area or system. State the condition as a dimension, test result, or documented approval, not a general impression.
- Include dimensions, substrate, dryness, cleanliness, temperature, access, backing, rough-in, testing, approval, and protection where applicable. Cite the controlling drawing, specification, or quality-plan reference for each.
- Define which party inspects the predecessor work and who accepts the handoff. Name the inspecting party and the accepting party separately when they differ.
- Define exceptions that may be accepted without releasing the predecessor from correction responsibility. State the conditional-acceptance rule and its limits.
- Create an area-release and handoff form. Include area, predecessor, successor, inspection date, result, deficiencies, and acceptance status fields.
- Link handoffs to the master schedule and two-week lookahead. Confirm the planned handoff date supports the successor trade's scheduled start.
G. Confirm Mobilization Readiness
- Confirm subcontractor licenses, insurance, permits, safety documentation, staffing, and supervision as required. Verify each item against the current file before mobilization.
- Confirm current drawings, submittals, RFIs, selections, and approved changes have been distributed. Confirm the trade has the current version, not a superseded draft.
- Confirm the trade understands scope, exclusions, allowances, quality criteria, schedule, and closeout requirements. Review the subcontract scope and the responsibility matrix with the trade lead directly.
- Confirm mobilization date, working hours, crew size, delivery, parking, storage, waste, power, water, lighting, and sanitation. Record commitments in writing.
- Confirm ladders, scaffolds, lifts, cranes, temporary protection, and shared equipment responsibility. Identify which party provides and maintains shared equipment.
- Confirm required competent persons, inspections, tests, and trade permits. Verify these are assigned and scheduled before mobilization.
H. Coordinate Zones and Interfaces
- Coordinate work zones to avoid unsafe trade stacking. Assign exclusive or scheduled work zones where multiple trades would otherwise occupy the same area.
- Coordinate penetrations, sleeves, blocking, embeds, equipment pads, clearances, and access panels before closure. Confirm every required opening or embed is installed before the area is closed.
- Coordinate MEP routing with framing, cabinets, ceilings, structure, and finishes. Resolve routing conflicts before rough-in proceeds.
- Coordinate finish-trade sequencing to prevent damage and rework. Sequence finish trades to protect completed work from subsequent trade traffic.
- Hold a preinstallation meeting for high-risk or multi-trade work. Confirm attendance from every affected trade for complex interfaces.
I. Inspect, Accept, Protect, and Close the Handoff
- Inspect predecessor work before releasing the area. Check the completed work against the measurable handoff condition defined in Step 7.
- Record deficiencies with location, requirement, owner, and due date. Enter every deficiency in the interface deficiency log individually.
- Do not declare an area ready while material defects or required approvals remain unresolved. Withhold acceptance until the condition is met or a documented exception is recorded.
- Record handoff acceptance, conditional acceptance, or rejection. Complete the area-release and handoff form with the result and signature.
- Photograph concealed or high-risk interface conditions. Capture the condition before it is covered by successor work.
- Provide successor-trade protection requirements and limits on modifying accepted work. State what the successor trade may and may not alter without notice.
- Require notice before a trade cuts, drills, relocates, removes, or damages another trade's work. Route the notice through the responsible supervisor before the modification occurs.
- Track trade-caused damage and correction responsibility. Enter each incident in the trade-damage log with responsible party and correction status.
- Reinspect completed successor work before the next handoff. Confirm the successor's own work meets its handoff condition before it becomes the next predecessor.
- Update schedule, quality, cost, and change logs for handoff impacts. Reflect any delay, deficiency, or damage cost in the relevant project-control log.
- Review handoff performance in coordination meetings. Report unresolved interface deficiencies at the next Project 09 coordination meeting.
- Close the handoff record only when predecessor deficiencies, successor acceptance, and required documentation are complete. Do not close a record with an open deficiency or missing signature.
- Archive the trade matrix, meeting records, handoff forms, photographs, and unresolved responsibility decisions. File the complete record in the project job file established in Project 02.
Common Trade-Coordination Inspection
Inspect every trade handoff using the same checks regardless of the trades or interface involved.
- Responsibility check: confirm exactly one primary responsible party is assigned to the task in dispute or under review.
- Interface check: confirm every physical, information, material, access, utility, equipment, and inspection dependency at the interface is identified.
- Handoff-condition check: confirm the release condition is measurable and checkable, not a general impression of readiness.
- Mobilization check: confirm license, insurance, permits, safety documentation, staffing, and current documents were confirmed before the trade began.
- Zone-conflict check: confirm no unsafe trade stacking, undocumented penetration, or unresolved routing conflict remains in the affected area.
- Closure check: confirm the handoff record shows inspection, deficiencies, acceptance status, and required signatures before it is closed.
Complete the Trade-Coordination Inspection Checklist in the Inspection Checklist section below before beginning Project 09.
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Failure Points and Troubleshooting
Cleanup
This project ends with an operating trade-coordination system, not a matrix filed once and forgotten.
- Confirm the trade-responsibility matrix reflects the current subcontract scopes and any approved changes
- Confirm every completed handoff has a signed area-release and handoff form on file
- Confirm the interface deficiency log and trade-damage log show every item resolved or explicitly carried forward with an owner and due date
- Archive completed handoff forms, photographs, and meeting records in the project job file
- Provide the current trade-responsibility matrix and open interface items to Project 09 for the next coordination meeting
Field Terms
- Trade Interface
- A physical, information, material, access, utility, equipment, or inspection point where one trade's work depends on or affects another trade's work.
- Handoff Condition
- A measurable requirement that must be met before an area is released to the next trade.
- Predecessor
- The trade whose completed work must be inspected and accepted before a successor trade may begin in that area.
- Successor
- The trade that receives the released area and inspects the predecessor's work before beginning.
- Conditional Acceptance
- Acceptance of an area with recorded exceptions that do not release the predecessor from correction responsibility.
- Trade Stacking
- Multiple trades working in the same area at the same time in a way that creates unsafe congestion, damaged work, lost productivity, or unclear responsibility.
- Area-Release and Handoff Form
- The controlled record of predecessor inspection, deficiencies, and acceptance for a given area or system.
- Interface Deficiency Log
- The log tracking each deficiency found at a trade interface to verified closure.
- Trade-Responsibility Matrix
- A control assigning one primary responsible party to each category of trade work.
- Mobilization Readiness
- Confirmed license, insurance, permits, safety documentation, staffing, and current documents before a trade begins work.
Skill Check
- Why must the trade-responsibility matrix assign exactly one primary responsible party to each category of work?
- What is the difference between a handoff condition and a general statement that an area is "ready enough," and why does this chapter require the former?
- What must be confirmed about a subcontractor before it mobilizes, and why must this happen before Step 16 rather than after?
- What is the difference between acceptance, conditional acceptance, and rejection of a handoff, and what does conditional acceptance not release the predecessor from?
- Why must penetrations, sleeves, blocking, and embeds be coordinated before an area is closed rather than after?
- What must exist before a trade may cut, drill, relocate, or damage another trade's completed work?
- What two conditions must be true before a handoff record may be closed, according to Step 35?
- What are three possible causes of a successor trade finding an area not ready after acceptance, and how does the learner confirm which one occurred?
- Why does this chapter require photographs of concealed or high-risk interface conditions before they are covered?
- Why must unresolved interface deficiencies be reviewed at coordination meetings rather than tracked only in the deficiency log?
Competency Rubric
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-043 | Builds a trade-responsibility matrix assigning one primary party to each category of work, with gaps and overlaps resolved in writing | |||
| PM-044 | Confirms and records mobilization date, crew, access, utilities, and required documentation before each trade begins | |||
| PM-045 | Defines measurable, document-referenced handoff conditions for each area or system requiring a trade interface | |||
| PM-046 | Communicates readiness requirements, scope, quality criteria, and closeout requirements to each trade before mobilization | |||
| PM-047 | Coordinates work zones, penetrations, and finish-trade sequencing to prevent unsafe stacking, damage, and rework | |||
| PM-048 | Documents each handoff on the area-release form with inspection, deficiencies, and acceptance status, and closes the record only after verified correction |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
Inspection Checklist — Trade-Coordination Inspection Checklist
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Responsibility matrix | One primary responsible party assigned per category of work | ||
| Interfaces | Every physical, information, material, access, utility, equipment, inspection dependency identified | ||
| Handoff conditions | Measurable, document-referenced, not a general impression | ||
| Mobilization readiness | License, insurance, permits, safety documentation, staffing confirmed before start | ||
| Zone coordination | Work zones, penetrations, and routing scheduled to prevent stacking and conflict | ||
| Inspection and acceptance | Predecessor work inspected against stated condition before release | ||
| Deficiency log | Every deficiency recorded with location, requirement, owner, due date | ||
| Protection | Protection requirements and modification limits recorded at handoff | ||
| Damage tracking | Trade-caused damage recorded with responsible party and correction status | ||
| Closure | Handoff record closed only after deficiencies corrected and acceptance documented |
Interface deficiency log status: ____________ Open items carried forward: ____________
Trade-coordination plan declared operating: ______ (Pass/Fail) Date: ____________ Project manager name: ____________
Performance Check
With the trade-responsibility matrix built and the handoff process in operation, review it against the Acceptance Standards table and confirm exactly one primary responsible party is assigned to each category of work, every trade interface is identified, every handoff condition is measurable and document-referenced, mobilization readiness is confirmed before each trade begins, work zones and penetrations are coordinated to prevent stacking and conflict, every completed handoff is recorded on the area-release form with inspection and deficiency information, and every closed handoff record shows verified correction and acceptance. Complete the Trade-Coordination Inspection Checklist and correct any failed item before beginning Project 09. If an item fails, identify whether the error occurred in responsibility assignment, interface identification, handoff-condition definition, mobilization confirmation, zone coordination, inspection, or closure before revising.
Project Closeout
You have completed the eighth project in the construction project management sequence: coordinating subcontractors and trade hand-offs. This project required you to identify trade responsibilities (PM-043), schedule trade access (PM-044), define handoff conditions (PM-045), communicate readiness requirements (PM-046), prevent trade conflicts (PM-047), and document trade handoffs (PM-048).
You now have an operating trade-responsibility matrix, a set of measurable handoff conditions, an area-release and handoff form in active use, and a growing record of closed handoff events. That system carries directly into the next project: running the jobsite coordination meeting that reviews these handoffs, along with schedule, safety, quality, and procurement status, and produces accountable action items.
File your trade-responsibility matrix, handoff forms, and deficiency logs where Project 09 can incorporate open interface items into the coordination-meeting agenda. Every later trade sequence in this book depends on the handoff discipline established here.