Subcontractor management and trade coordination field guide

Managing the subs is the job

Subcontractor management is the work of picking the trades, putting them under contract, sequencing them so the work flows, and paying them in a way that keeps risk where it belongs. On a data center or a large MEP job the general contractor pours almost no concrete, bends almost no pipe, and pulls almost no wire. The subs do. So managing the subs is not a side task next to building the project. It is the project.

That surprises people who picture a GC as the company that builds the building. The GC builds the schedule, the contracts, the coordination, and the paper that keeps everyone paid and covered. The electrician builds the gear room. The mechanical contractor builds the chilled-water plant. The GC's job is to make sure the electrician and the mechanical contractor are not standing in the same six feet of ceiling on the same Tuesday, that both carried the insurance the contract required, and that neither one is owed money they can lien the owner over.

The work runs in a rough order: prequalify a trade before you award, write a scope clean enough that nobody can claim the gap was someone else's, sign a subcontract that flows the right terms down, hold the insurance and lien paper current, sequence and coordinate the trades in the field, then pay against work that was actually built and inspected. Two of those steps lean on their own disciplines. An open question that changes the work becomes an RFI or a submittal, covered in the RFI and submittal guide. A change that adds scope becomes a change order, covered in the field change order guide. This guide is about the trades themselves and the relationship that decides whether they finish on time.

Why it decides whether the job finishes

Subcontractor management decides four things, and they are the four things a job lives or dies on: schedule, quality, risk, and margin.

Schedule is the obvious one. The trades have to sequence or they collide. Overhead is where it shows up first, because duct, pipe, conduit, and cable tray all want the same plenum and somebody has to be in there before somebody else. Get the order wrong and the second trade tears out the first trade's work to get its run in, and now you are paying twice for the same six feet of ceiling and falling behind while you do it.

Quality is next. A sub installs to its own habits unless the scope, the submittals, and the inspections hold it to the spec. Catch a defect at rough-in and it is a fix. Catch it at commissioning and it is a tear-out behind finished work, on the critical path, with the owner watching.

Risk is the one that bites long after the trade has left. A sub without current insurance is the owner's exposure, not the sub's, the day there is a claim. A sub that did not sign a lien waiver can put a lien on the owner's building for money its own supplier never got paid. The GC carries that risk on paper until the paper is closed out.

Margin is where it all lands. Scope gaps, collisions, undocumented back charges, and money paid against work that was not done all come out of the same pool. The job that finishes on time and on budget is almost never the job with the best crews. It is the job where the subs were managed.

How do you prequalify a subcontractor?

You prequalify a subcontractor by checking that it can actually carry the work before you award it, not after it fails mid-job. The vetting covers five things: financial strength, bonding capacity, safety record, references, and real capacity for your scope and schedule. A sub that looks cheap on bid day and cannot make payroll in month four is the most expensive sub on the project.

Financials tell you whether the company survives the job. Ask for financial statements, working capital, average monthly billing, and current backlog. A sub whose backlog already exceeds what it can staff is a sub that will rob your job to feed another one. Bonding capacity is a second read on the same question, because a surety has already underwritten the company. Find the surety, the single-job and aggregate bond limits, and the rate, even if the project never asks for a bond. A sub that bonds for far less than your scope cannot carry it.

Safety shows up in the experience modification rate, the EMR, which the workers' comp system calculates from a contractor's injury history against its peers. A 1.0 is average. Below 1.0 is better than average. Many large jobs will not let a sub on site above 1.0, and the strictest owners set the bar near 0.85. The EMR is not just a safety number. A sub that gets people hurt also stops your job every time it does. References and capacity close it out. Call three or four recent GCs, not the ones the sub hands you, and ask whether they would hire the sub again. Confirm the sub has the crews, the foremen, and the financial room to run your scope at the same time as its other work.

What is a scope gap?

A scope gap is a piece of work that no subcontract clearly assigns, so every trade assumes someone else owns it and nobody prices or builds it. Scope gaps are where the trade fights come from, and they almost always surface in the field at the worst time, when the work the gap blocks is on the critical path.

The classic gap is support steel. Who hangs the unistrut and the trapeze that carries the conduit and the cable tray? The electrician assumes the GC or the structural sub provides it. The structural sub priced building steel, not miscellaneous supports. The GC assumed the electrician carried its own supports. Nobody priced it, and now three parties are arguing in the ceiling while the schedule burns. Firestopping is another reliable gap. The trade that makes the penetration and the trade that seals it are often not the same trade, and the spec rarely says which one owns the sleeve, the seal, and the inspection.

You close gaps by writing scope that says what is in and, just as hard, what is not in. A good scope names the work, the drawings and spec sections it covers, what the sub furnishes versus installs, and the interfaces where its work meets the next trade's. Write the exclusions explicitly. A sub that excludes support steel in writing has handed you the gap to assign on purpose, which beats finding it by accident in month five. The buyout meeting, where you walk the scope line by line with the sub before signing, is where the gaps get caught while they are still cheap to fix.

What the subcontract has to nail down

The subcontract is the document that turns a bid into an enforceable deal, and the terms that matter are scope, price, schedule, retainage, payment terms, and flow-down. Most of the standard forms, the AIA A401 between contractor and subcontractor and the ConsensusDocs 750, are built around exactly these. Use a real form or your own reviewed form, not a purchase order, for any scope worth managing.

Scope and price reference the buyout you already did, the drawings, and the spec sections, with the exclusions spelled out so the gap argument is settled before it starts. Schedule binds the sub to the project milestones and the look-ahead, not just a final date, so you can hold it to the sequence, not just to substantial completion. Retainage is the percentage the owner holds back from each payment, commonly 5 to 10 percent, that flows down to the sub, and the contract should say how and when it gets released. The A401 ties the sub's retainage release to the prime contract, so a sub does not get full release ahead of the GC unless the prime allows it.

Flow-down is the term people skip and regret. A flow-down clause makes the sub responsible to the GC for the same obligations the GC owes the owner under the prime contract and the general conditions, commonly the AIA A201. Without it, the owner can hold the GC to a standard the GC never passed down to the trade that actually did the work, and the GC eats the difference. Read what flows down. Schedule, indemnity, insurance, warranty, dispute resolution, and notice deadlines should all reach the sub that controls them.

Why do you need a certificate of insurance from a subcontractor?

You need a certificate of insurance, a COI, from a subcontractor because a sub without current coverage is the owner's and the GC's exposure the moment there is a claim, not the sub's. No current COI means no work. That rule is not bureaucracy. It is the difference between the sub's insurer paying for the sub's accident and you paying for it.

The certificate, usually the ACORD 25 form, summarizes the sub's policies: general liability, auto, workers' comp, and umbrella, with the limits, the policy numbers, and the expiration dates. Check three things hard. The named insured has to match the legal entity on the subcontract and the W-9, or the coverage belongs to a different company. The limits have to meet what the contract required, often 1 million per occurrence and 2 million aggregate for general liability as a baseline, higher on a data center. And the GC and the owner have to be named as additional insured by endorsement, commonly the ISO CG 20 10 for ongoing operations and the CG 20 37 for completed operations, confirmed by the edition the contract requires.

The trap on the certificate holder line is worth saying plainly. Being listed as the certificate holder does not make you an additional insured. The certificate itself says the statements on it do not amend the policy. You need the endorsement, the actual policy document that adds you as an insured, not just your name in a box. Ask for the endorsement, not just the COI.

Then there is the part everyone knows and nobody does well: the expiration date. A COI is a snapshot, and policies renew. A sub that was covered at award can be bare three months later when the policy lapses, and you will not know unless you are tracking the date. Track every COI's expiration and chase the renewal 30 to 60 days out, before the gap opens, not after the claim. Collect the W-9 at the same time you collect the COI, because you cannot pay the sub at year end without it.

What is a lien waiver?

A lien waiver is a signed document in which a subcontractor, or its supplier, gives up the right to file a mechanic's lien against the owner's property for the amount it is being paid. You collect one with every payment, because the lien is the sub's strongest card and the waiver is how you retire it. Pay without the waiver and you can pay twice: once to the sub, and again to the sub's unpaid supplier who liens the building you already paid for.

There are two kinds that matter, and the difference is timing. A conditional waiver takes effect only when the payment actually clears, so it is the one you collect with the pay application, before the check is cut. An unconditional waiver takes effect the moment it is signed, paid or not, so it is the one you collect after the payment has cleared the sub's account. Sign or accept an unconditional waiver before the money moves and the sub has waived its lien rights for a payment it may never receive, which is the most common and costly mistake in the whole process. Match the waiver to the moment: conditional before payment, unconditional after.

Each kind comes in a progress version and a final version. Progress waivers cover the work through the date of that pay period. The final waiver, collected at closeout with the last payment and the retainage, releases the rest. The GC's job is to chase the sub's waiver and its lower-tier waivers too, from the second-tier subs and the major suppliers, because any one of them can lien the owner over the GC's head. Lien rules and deadlines vary by state, so the specific form, the timing, and who has lien rights are set by the lien law where the project sits and by the contract. Confirm both before you build the process around a template.

Sequencing the trades so they do not collide

Coordination starts at the schedule. The trades have to be sequenced so each one has its predecessor complete and its work area clear before it shows up, and the tool for that is not the master schedule. It is the look-ahead. A three-week or six-week look-ahead, pulled from the master schedule and worked weekly with the foremen, is where the real sequence gets built and the constraints get cleared.

The strongest version of this is pull planning, where the trades sit at the wall with sticky notes and build the sequence backward from a milestone, each foreman saying what he needs from the trade before him and when. It comes out of the Last Planner System, and the reason it works is that the people who do the work commit to the handoffs, instead of a scheduler guessing at them from an office. A pull plan surfaces the collisions and the missing predecessors while they are still notes on a wall, not crews standing in the same room.

The constraint log is the other half. Every task in the look-ahead that cannot start has a reason: a missing submittal, an open RFI, gear not delivered, an inspection not scheduled, a predecessor not done. List the constraint, assign an owner, set a need-by date, and work it down before the week it blocks. A task with an open constraint is not ready, and putting a crew on it anyway is how you get the collision you were trying to avoid. The submittals and RFIs that show up as constraints are tracked in the RFI and submittal guide.

Coordinating the overhead before the field builds it

The overhead is where MEP trades collide, and the fix is to resolve the collisions in the model before anyone hangs steel. Duct, pipe, conduit, cable tray, sprinkler main, and structure all compete for the same plenum, and on a data center that plenum is dense. Coordinate it in the field by trial and tear-out and you lose weeks. Coordinate it in the model and the field installs to a drawing that already works.

That is what BIM coordination does. Each trade models its work to an agreed level of development, the models get combined, and clash detection software finds where the duct runs through the cable tray and where the pipe hits a beam. The trades work the clashes down in coordination sessions until the combined model is clean, then sign off on the coordinated drawings that the field builds from. The discipline is set up front in a BIM execution plan that says who models what, to what level, and on what schedule, so the coordination keeps pace with procurement and not behind it.

The thing to hedge here is that a clean model is not a built building. The model is only as good as the as-designed information in it, and the field still finds the beam that was an inch off or the gear that landed where it landed. BIM coordination cuts the field collisions hard. It does not erase them. Treat the coordinated model as the plan and the field verification as the check, and keep the priority of trades in the ceiling written into the coordination, so when there is a genuine conflict everyone already knows who moves.

The weekly coordination meeting

The weekly subcontractor coordination meeting is where the sequence stays honest. It runs against the look-ahead, not the master schedule, and every trade foreman is in the room or it does not work, because the whole point is the handoffs between trades and the trades have to be there to commit to them.

A working meeting covers three things. The look-ahead for the next few weeks, walked task by task, with each foreman confirming what he will finish and what he needs from the trade ahead of him. The constraints, walked down the log, with owners and need-by dates, so an open RFI or a late delivery gets surfaced and chased instead of discovered the morning the crew is blocked. And the conflicts, the places two trades want the same area or the same week, resolved in the room while it is a conversation and not yet a collision.

Keep it short and keep notes. The notes are the record of who committed to what, and they are what you hold a trade to next week when the handoff did not happen. A coordination meeting with no minutes is a meeting that everyone remembers differently. Tie the open RFIs and submittals into the same review, because they are the constraints that block the most work, and they are covered in the RFI and submittal guide.

The sub's submittals and RFIs flow through the GC

A subcontractor does not talk directly to the design team. Its submittals and its RFIs flow up through the GC, get logged, and come back down through the GC, and the GC's job is to track them so neither one stalls the trade that is waiting on it. A submittal sitting in review and an RFI sitting unanswered are the two most common reasons a sub cannot build, and both are the GC's to manage.

On the submittal side, the GC keeps the register: every product, shop drawing, and sample the sub owes, what is in review, what came back approved or rejected, and when the long-lead gear has to be released to make the schedule. A rejected submittal that nobody re-submits becomes gear that never gets ordered, which becomes a milestone that slips. On the RFI side, the GC keeps the log and the aging, because an RFI that ages out is a crew guessing or stopped. The mechanics of writing a good RFI, running the register, and tracking the aging are the subject of the RFI and submittal guide. The point here is that they are the GC's coordination duty on the sub's behalf, not the sub's problem to chase alone.

The reason it runs through the GC is accountability. When the GC owns the flow, the GC can sequence the reviews against the schedule, push the long-lead items, and hold one log instead of every trade chasing the architect on its own. Let the trades freelance their own RFIs and you lose the thread on what is open and what it is blocking.

Sub change orders, priced before the work

When a subcontractor's scope changes, the change gets priced and authorized before the work is built, not after. A sub that builds added scope on a handshake and bills it later usually eats it, the same way the GC eats a change it built for the owner without a signed ticket. The rule runs all the way down the chain: notice first, price second, build third.

The GC sits in the middle of two change conversations at once. The sub's change to the GC and the GC's change to the owner are usually the same change, and they have to move together. If the owner changes the gear room layout, the electrician's added conduit is a sub change order to the GC and the GC's change order to the owner, and the GC cannot let the sub build it before the owner has authorized the GC to spend the money. Price the sub change with its own takeoff and markup, fold it into the GC's change to the owner, and keep the two in step. The full discipline of documenting and pricing a field change from a takeoff is the subject of the field change order guide.

Back charges are the other side of the change ledger, and they have to be fair and documented. If one sub damages another sub's work, or leaves a mess another trade has to clean, the GC charges the cost back to the responsible sub. Done with photos, a notice, and a real cost, a back charge holds up. Done as a number that appears on a pay app with no record behind it, it becomes a dispute that costs more to fight than it recovers. Back charges live or die on documentation, the same as everything else in this guide.

The sub pay application and what controls it

A subcontractor gets paid on a pay application that bills against a schedule of values by percent complete, and the GC reviews it before it rolls up into the GC's own application to the owner. The schedule of values, the same structure as the AIA G702 and G703, breaks the sub's contract into line items with a value each, and each pay period the sub claims a percent complete on each line. The GC's job is to verify that the percent claimed matches the work actually in place, because a sub that bills ahead of the work is a sub you have overpaid if it walks.

Two terms shape when the money moves. Retainage, commonly 5 to 10 percent, is held back from each payment and released at the end, which keeps the sub motivated to finish the punch and the closeout. Pay-when-paid and pay-if-paid clauses tie the sub's payment to the owner paying the GC, and they are not the same thing. Pay-when-paid generally sets a reasonable timing window and the GC still owes the sub eventually. Pay-if-paid tries to make the owner's payment a true condition of the sub ever getting paid, which shifts the owner's credit risk onto the sub. Their enforceability varies by state, so the lien law and the contract control which one actually holds.

The discipline that protects the owner and the GC is simple and it is the one people break: do not pay against work that is not done, and do not pay without the lien waiver in hand. Verify the percent complete in the field, collect the conditional waiver with the application, and release the unconditional waiver only after the money has cleared. The pay app, the percent complete, the retainage, and the waiver move as one package or the protection falls apart.

Inspecting and punching the sub's work

The GC inspects the sub's work as it goes and holds retainage against the punch until the defects are fixed. Quality is not something you verify once at the end. You verify it at rough-in, before the work gets covered, because a defect found behind finished drywall or under a poured slab is a tear-out instead of a touch-up.

Inspect at the points where the work disappears. Underground before backfill, in-wall before cover, overhead before the ceiling closes, terminations before energizing. Those are the moments where a cheap fix turns into an expensive one if you miss it. A sub that knows the GC checks at rough-in builds to the spec at rough-in. A sub that knows nobody checks until commissioning builds to its own habits and you find out late.

Retainage is the lever that gets the punch done. The punch list is the running record of defects and incomplete work, and the rule is plain: the work is not complete until the punch is closed, and the retainage does not release until it is. A sub chasing its retainage finishes the punch fast. A sub that already has its money finishes it whenever it gets around to it, which on a busy trade is never. Hold the retainage, close the punch, then release.

Sub safety orientation and program

Every sub's crew goes through site safety orientation before it sets foot on the work, and the sub runs to its own written safety program under the project's overall plan. The EMR you checked at prequalification told you the sub's history. The orientation and the program are how you manage the present.

Orientation is short and non-negotiable: the site rules, the hazards specific to this project, the muster points, the PPE, and who the competent person is for the trade. A worker who has not been oriented does not work. On a data center with energized gear, confined spaces, and overhead work stacked tight, the orientation is also where you reinforce the lockout and the permit systems that the trade fights share. A sub that gets people hurt stops your job every time it happens, so safety is schedule protection as much as it is the right thing.

Scoring the subs and rehiring the good ones

Score the subs on the work and keep the score, so the next buyout uses what this job taught you. The three measures that matter are on-time performance against the schedule, quality measured by rework and punch, and safety measured by incidents and near misses. A sub that hits all three is worth more than a sub that bid lower and missed them, and the only way you know is to have written it down while it was happening.

The scorecard does two jobs. During the project, a sub trending the wrong way on schedule or quality is a problem you can catch and correct before it becomes a crisis, instead of discovering at closeout that the same trade was behind all along. After the project, the score is what feeds the next prequalification. The best subcontractor pool a GC has is the list of trades it has already run, scored, and would rehire. Rehire the good ones and your prequalification is half done before the next job starts. Drop the ones that cost you more than they saved, no matter how low they bid.

One place for the documents, not scattered email

Every document that manages a sub, the subcontract, the COI and its expiration, the lien waivers, the submittals, the RFIs, the schedule, the pay apps, the back charges, lives in one place the whole team can see, or it lives nowhere. The single worst way to run subcontractor management is across scattered email threads and a folder on one PM's laptop, because the day that PM is out is the day nobody can find whether the sub's COI is current or whether the last waiver was collected.

The risk is concrete. An expired COI that nobody noticed because the renewal sat in someone's inbox. A lien waiver that was never collected because the pay app and the waiver lived in different systems. A sub change built off an email that the office never saw. Every one of those is a document that existed but could not be found by the person who needed it, which on the risk that matters is the same as not having it.

A field-service platform that keeps the sub records, the COI expirations, the coordination notes, and the document trail in one shared place is how a GC keeps this from becoming forty inboxes. FieldOS is built for exactly this kind of field operation: the COI expiration tracking that warns before the gap opens, the coordination and meeting notes tied to the job, the pay and waiver records in one log, and the document history the next person can actually find. Its tradeos workflow keeps the sub paperwork and the field coordination in the same record instead of scattered across email, so the question of whether a sub is covered, sequenced, and paid has one answer the whole team can see.

What to self-perform versus sub out

A GC self-performs the work where control is worth more than the risk it carries, and subs out the rest. Most large GCs self-perform little and sub almost everything, because the trades own the licensed labor, the specialty tools, and the trade insurance, and trying to self-perform a specialty trade means carrying all of that risk in-house for work the market does better.

The case for self-performing is control of the critical path. Concrete, layout, and general conditions work are common self-perform scopes because they set the pace for everyone behind them and a GC would rather not hand its schedule to a sub. The case against is risk and overhead: self-performed work puts the labor, the safety, the warranty, and the means and methods on the GC's own books, and a trade you do not run well is more expensive in-house than bought. The honest answer is run by scope, not by policy. Self-perform what controls the schedule and you can run better than the market. Sub the specialized, risk-heavy work to the trades built to carry it.

Where subcontractor management fails

The failures repeat from job to job, and they are predictable enough to design against. No prequalification, so a weak sub gets the award on price and then cannot make payroll or staff the work, and it fails in the middle of the job where it is most expensive to replace. Scope gaps, so a piece of work like support steel or firestopping sits unassigned and three trades fight over it in the ceiling while the schedule burns.

An expired COI or a missing lien waiver, so a coverage gap or a supplier's lien lands on the owner that the GC was supposed to have closed out. No coordination, so the trades collide overhead and the second one tears out the first one's work. Paying without the waiver, so the GC pays the sub and then pays the sub's supplier again over a lien on a building it already paid for. And back charges with no documentation, so a real cost the GC tried to recover turns into a dispute it loses for lack of a photo, a notice, and a number. None of these is exotic. All of them are the basics skipped under schedule pressure.

What to document

Subcontractor management runs on records, and the record is what answers the question months later when a sub disputes a back charge, a supplier files a lien, or an owner asks whether a trade was ever covered. Capture it as it happens, because reconstructing it after the fact is how disputes get lost.

Common mistakes

• Awarding on price with no prequalification, so a weak sub fails in the middle of the job.
• Leaving scope gaps between trades that no subcontract assigns, so nobody owns the support steel or the firestopping.
• Letting a COI expire or skipping the additional-insured endorsement, so a coverage gap lands on the owner.
• Paying a sub without collecting the lien waiver, so a supplier liens the building you already paid for.
• Accepting an unconditional waiver before the payment has cleared the sub's account.
• Running no field coordination, so the trades collide overhead and tear out each other's work.
• Billing or accepting percent complete ahead of the work actually in place.
• Issuing a back charge with no photos, no notice, and no itemized cost behind it.

Field checklist

Standards and references

The subcontract terms come from the standard forms and the project's general conditions. The AIA A401 between contractor and subcontractor and the ConsensusDocs 750 are the common subcontract forms, and both are written to flow down the obligations of the prime contract, commonly the AIA A201 general conditions, to the sub. Read what the form actually flows down on your job, because the parties amend these forms, and the amended version controls.

Insurance runs on the certificate and the endorsement, not the certificate alone. The COI is usually the ACORD 25 form, and additional-insured status comes from a policy endorsement, commonly the ISO CG 20 10 for ongoing operations and the CG 20 37 for completed operations, in the edition the contract specifies. The certificate holder line does not grant coverage. Lien rights, lien waiver forms, and the deadlines that go with them are set by the mechanic's lien statute of the state where the project sits, and they vary enough that a form that works in one state can be wrong in another. Confirm the lien law and the contract before you build a waiver process.

Coordination practice leans on pull planning from the Last Planner System, published by the Lean Construction Institute, and on BIM coordination governed by the project's BIM execution plan and an agreed level of development. Payment applications follow the schedule-of-values structure of the AIA G702 and G703. None of these substitutes for the contract documents and the lien law, which govern. Stress the three that decide the job: prequalify and write a clean scope, keep the COI and the lien waiver current, and coordinate the trades before they collide.

Units, terms, and conversions

Subcontractor management carries its own vocabulary, and the same idea can read differently across a contract, a certificate, and a pay app. The terms below are the ones that decide money and risk.

Retainage is also called retention. A COI is a certificate of insurance, the ACORD form. Additional insured is the endorsement status, distinct from certificate holder. EMR is the experience modification rate, sometimes the experience modification factor or mod. The schedule of values, the SOV, is the line-item breakdown a pay app bills against. Flow-down is sometimes written as conduit or pass-through clause. A back charge is sometimes called a chargeback. Get the term right on the document, because the document is what gets enforced.

Prequalification

Vetting a sub's financials, bonding, EMR, references, and capacity before award

EMR

Experience modification rate, the workers' comp factor that scores a sub's injury history against its peers, 1.0 being average

Scope gap

Work no subcontract clearly assigns, so every trade assumes another owns it and nobody prices or builds it

Flow-down

A clause making the sub responsible to the GC for the same obligations the GC owes the owner under the prime contract

COI

Certificate of insurance summarizing the sub's coverage, limits, and expiration; coverage runs through the policy and endorsement, not the certificate

Lien waiver

Signed release of mechanic's lien rights for an amount paid; conditional takes effect on payment, unconditional on signing

Retainage

A percentage, commonly 5 to 10, held back from each payment and released at closeout, also called retention

Schedule of values

The line-item breakdown of a subcontract that a pay application bills against by percent complete

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is an RFI in construction?
• What is a field change order?
• What is a blanking panel in a server rack?
• What is a data center PM program?
• Why is cable management important in a data center?