Subcontractor Communication: The Complete Guide for General Contractors

Poor project data and miscommunication caused an estimated $31.3 billion in construction rework in the US in a single year, according to the FMI and PlanGrid Construction Disconnected study. The same research found construction pros burn about 35% of their working hours — more than 14 hours a week — chasing project information, resolving conflicts, and fixing mistakes.

A big share of that waste lives in one relationship: the GC and the sub. The framer who built to the old drawing rev. The electrician who never got the schedule update and showed up to a slab that wasn't poured. The plumber who did the extra rough-in on a verbal yes and is now fighting you over $1,400 nobody wrote down.

This guide covers the whole loop: why sub communication breaks, what it costs, and the specific rituals — contract language, kickoff packets, schedule confirms, change-order discipline, payment communication — that keep your jobs moving and your bench of subs answering on the first ring.

Why GC-sub communication breaks down

Sub communication breaks for structural reasons, not because subs are flaky or GCs are disorganized. Three forces work against you on every job, and until you design around them, no amount of "communicate better" talk fixes anything.

Your sub is juggling four other GCs

A working trade crew is rarely on one job for one builder. Your drywall sub has your job, two other GCs' jobs, and a side job for his cousin, all live at once. Your schedule update is competing with four other text threads for the same crew. When a conflict hits, the GC who confirmed clearly and pays fastest wins the crew that week — and the GC who went quiet gets the no-show.

There is no shared system

You run the job from email and a spreadsheet. Your super runs it from his truck. The sub runs it from a group text with his two guys. Nothing lands in one place, so every piece of information has to be relayed person-to-person, and every relay loses detail. The drawing revision that died in your sent folder is a rework invoice waiting to print.

Scope lives in text threads

The most expensive sentence on a jobsite is "yeah, go ahead and do it." Field directives get made verbally, photographed scope lives on one person's phone, and the agreement that mattered exists only in a text thread between two people — one of whom will remember it differently when the invoice shows up. When scope has no home, every change becomes a memory contest.

What a communication breakdown actually costs

The cost shows up in three places: rework, schedule slip, and inflated bids. FMI and PlanGrid put a number on the first one — poor data and miscommunication were responsible for 48% of all US construction rework, worth an estimated $31.3 billion in 2018 alone.

Schedule slip compounds. One trade that mobilizes two days late doesn't cost you two days — it bumps the trade behind them, who is now committed elsewhere, who bumps the trade behind them. A single missed confirm can cascade into two weeks on a tight residential schedule.

Then there are disputes. Arcadis's 2024 Global Construction Disputes Report points at contract documents that are unclear, incorrect, or missing pieces entirely as a recurring driver of formal disputes — which is what a text-thread scope argument becomes when the dollars get big enough. The third cost, inflated bids from subs pricing in your reputation, is covered in the payment section below, and it may be the biggest one.

Set the communication SLA at contract signing

The time to fix communication is before the job starts, in the subcontract itself — not mid-job, when you're already mad. Treat communication terms the way you treat payment terms: written, specific, and signed. A short exhibit attached to the subcontract does it. Spell out:

• Response window. Messages about schedule or scope get answered within one business day. Both directions — this binds you too.
• Channel of record. Name the one place where official communication lives (a project channel, a shared thread, even a dedicated email address). Anything said elsewhere is a courtesy, not a record.
• Who can authorize changes. Named people, not job titles. If your super can't approve extra work, say so here, in writing, before someone tests it.
• Schedule confirm rule. The sub confirms mobilization at 72 and 24 hours (more on this below). Silence at 72 hours is treated as a no.
• Notice requirements. Delays, RFIs, and differing conditions get written notice within a set number of days, per the subcontract's notice clause.
• Pay-app cycle. When pay apps are due, what a complete one includes, when payment goes out, and the retainage percentage and release terms.

The kickoff packet every sub should get

Every sub gets one page — or one pinned post in the project channel — with everything they need before they load the truck. Most GC-sub friction in the first week traces to information the GC had and the sub didn't. The packet kills that. Include:

• Scope summary and exclusions. What's in their contract, and just as important, what isn't. Exclusions in writing prevent the "I assumed you had that" fight.
• Current drawing revision and the one place the latest set always lives. The packet names the source; nobody builds from an attachment in a three-week-old email.
• Site logistics. Parking, laydown area, work hours, gate or lockbox code, dumpster rules, where the porta-john is.
• Contact tree. Super's name and number, PM's name and number, and the named people who can authorize changes (matching the subcontract exhibit).
• Schedule window and the 72/24 confirm rule, stated plainly so the first confirm text isn't a surprise.
• Pay-app schedule, retainage percentage, and the lien-waiver requirement, so the first pay app comes in clean.
• Insurance and safety requirements. COI on file before mobilization, plus any site-specific safety rules.
• The change-order rule in one line: no written CO, no extra work, no exceptions.

Scope changes: no written change order, no work

Every scope change gets a written change order before the work happens — that's the whole rule, and it has no asterisk. The verbal field directive is how a $400 favor becomes a $4,000 dispute. Arcadis's disputes research keeps landing on the same culprit: contract documentation that's unclear, incorrect, or missing. A scope change that lives only in a conversation is missing documentation by definition.

The reason GCs skip written COs is friction, so remove the friction. A change order doesn't need to be a formal AIA document for a $600 add. Three lines from your phone does it: what changed, what it costs, who approved it. Sent in the channel of record, acknowledged by the sub, done in ninety seconds. Apps like ContractorsChat build change orders into the project chat for exactly this reason — the CO happens where the conversation is already happening, so it actually gets written.

Train your supers on the difference between a scheduling courtesy and an authorization. "Yeah, we can work around that" is a courtesy. Money only moves on paper. Subs who push back on this are telling you something useful about how the end of the job will go.

Schedule confirmation: the 72/24 rule

Confirm every sub twice before mobilization: once at 72 hours out, once at 24 hours out. This is the single highest-return communication habit a GC can build, because it attacks the structural problem head-on — your sub is juggling multiple GCs, and the job that confirmed is the job that gets the crew.

The 72-hour confirm is the important one. It's your early-warning system. A clean "we're good for Thursday" costs you nothing. A wobble — "should be fine, finishing up another job" — gives you three days to lean in, re-sequence, or line up a backup. Finding out Thursday at 7 AM gives you nothing but an empty site and a framing crew standing behind a trade that isn't there.

The 24-hour confirm closes the loop and carries the logistics: start time, access, what needs to be ready for them, what they need to bring. Two texts. Maybe forty seconds of your day per sub.

Payment communication: pay fast, talk straight

How and when subs get paid is communication — the loudest kind. Rabbet's 2024 Construction Payments Report put the cost of slow payments to the US construction industry at $280 billion in a single year, and found that 100% of subcontractors factor a GC's payment reputation into their bids, with over 75% saying they raise their bids to GCs who pay slow. Your payment speed is priced into every number that hits your inbox.

Flip that around and fast payment becomes your cheapest retention and procurement strategy. The GC known for paying in days gets first pick of crews, tighter bids, and the benefit of the doubt when a job gets hard. That reputation is built with boring clarity:

• Pay apps: state the cycle and the checklist up front — what a complete pay app includes (schedule of values, lien waivers, backup) — so the first one comes in clean instead of bouncing twice on paperwork.
• Retainage: name the percentage and the release terms in the subcontract and the kickoff packet. Retainage subs agreed to stings less than retainage they discovered on the first short check.
• Prompt-pay obligations: most states have prompt-payment laws covering private construction work, with interest penalties for late payment. Know yours; the good subs already do.
• Bad news early: if the owner's draw is late and your payment to the sub will slip, say so the day you know, with a date. Subs forgive a late check with a straight story far faster than a quiet one.

Sloppy invoicing on your side feeds the same fire — if your numbers to the owner are slow or wrong, everything downstream slows with them. We covered that failure chain in construction invoicing mistakes that cost you money.

When a sub goes dark

When a sub stops responding, escalate on a clock and document as you go — don't stew for a week and then explode. Most dark subs aren't ducking you out of malice; they're overcommitted and avoiding an awkward conversation. Your job is to force the conversation early, while there's still schedule left to save.

1. 1Day 1: switch channels. If the text went quiet, call. If the call goes to voicemail, try the foreman or the office. You're diagnosing — overbooked, short-handed, or done with you — not punishing yet.
2. 2Day 2: send written notice in the channel of record, referencing the subcontract's notice clause and stating the date you need a response by. Calm, factual, dated. This starts the paper trail you'll want either way.
3. 3Same day: start lining up a backup quietly. You're not pulling the trigger — you're buying yourself the option so the dark sub isn't negotiating against an empty bench.
4. 4Day 3-5: document impacts daily — crews standing, trades resequenced, days lost. If back-charges or supplementation come later, this log is what makes them stick.
5. 5Decision point: when they resurface, offer the honest off-ramp: "Tell me the real date you can be here and I'll work with it once. Go quiet on me again and I'm supplementing the work." Most overcommitted subs grab the off-ramp and hit the real date.

If you do replace them, part clean: written termination per the subcontract, final accounting of work in place, and no trash talk around town. Trades talk to each other more than GCs think, and how you fire a sub gets repeated to every sub you'll want to hire next year.

Build a bench: reputation runs both ways

Reliable subs aren't found, they're made — by being a GC worth being reliable for. Everything above compounds into a reputation: confirm schedules, write the COs, pay fast, give bad news straight, and word moves through the trades. Remember the Rabbet finding — every sub is already scoring you. The only question is whether you're scoring them back.

So keep an actual scorecard, even a simple one. After each job, note three things per sub: responsiveness (did they answer the 72/24 confirms?), schedule performance (did they hit their windows?), and quality (callbacks and punch-list density). Three jobs of notes sorts your contact list into an A-bench and everyone else.

Then treat the A-bench like the asset it is: they get the first call on new work, the fastest payment, and a steady pipeline so they can plan their year around you. A great sub who trusts your paper and your checks will hold dates for you that they'd drop for anyone else. That's the whole game.

This is also why two-sided reputation is built into ContractorsChat's trades directory: GCs rate trades and trades rate GCs. The plumber deciding between two invitations to bid can see which GC pays on time and runs a clean job — which is exactly the pressure that makes the whole market work better for people who do it right.

Failure modes and the rituals that prevent them

Every breakdown in this guide maps to one cheap, boring ritual. Pin this table somewhere your PMs will see it.

Tools: what you actually need

You don't need software to run any of this. A GC with two jobs can do the whole playbook with a phone, a disciplined text habit, and a folder of paper. The rituals are the system; software just makes them survive scale.

Scale is where the phone-and-paper version breaks: five jobs, fifteen subs, three text threads per sub, and the change order from March is somewhere in 4,000 messages. The full PM suites — Procore, Buildertrend — solve it, but they're built and priced for bigger operations, and your subs have to live in them too, which is exactly where adoption dies. A trade crew won't learn a desktop platform for one GC's jobs.

ContractorsChat takes the other route: it's chat, because chat is what subs already use. Every project is a channel, so the channel of record from your subcontract exhibit is just... the app. Change orders, schedule, document storage, invite-to-bid, and two-sided ratings live inside the conversation, and it runs as a PWA on any phone — no app store, nothing for the sub to be trained on. Honest limits: it doesn't do takeoffs, estimating databases, or accounting (it exports to QuickBooks on Small Business plans and up). If you need those, pair it with a dedicated estimating tool. Pro runs $79/mo, and during the current beta it's free for 6 months with no card.

Whatever tool you pick — including none — the test is the same: does every sub on every job know the scope, the schedule, the changes, and the payment terms, in writing, in one place? If yes, you've already beaten the $31.3 billion problem on your jobs. The rest is just picking how much of it your thumbs do manually.