5 Communication Habits That Separate Great GCs from Good Ones

Rework caused by miscommunication and bad project data costs the US construction industry $31.3 billion a year, according to FMI and PlanGrid's Construction Disconnected study. Not weather. Not lumber prices. Not labor shortages. Communication.

Here's the uncomfortable part: at the level where you're bidding against three other outfits for the same job, everybody can build. The framing is plumb either way. What separates the GC that subs fight to work for from the GC that subs tolerate is almost never craft. It's how information moves through their jobs.

Watch any well-run outfit for a week and the same five habits show up, over and over. None of them require charisma, a big office, or expensive software. All of them require discipline. Here's each one — what it looks like in practice, and what it costs when it's missing.

Habit 1: They confirm everything in writing, the same day

Great GCs treat a verbal agreement as unfinished business until it exists in writing. Every parking-lot conversation, phone call, and walkthrough decision gets a short written echo before the day ends — usually within minutes, before the truck leaves the driveway.

In practice it's a two-line message, not a contract amendment. You agree on the phone with your plumber to push rough-in two days. Before you hang up the next call, you send: "Confirming today's call: rough-in moves to Thursday the 14th, same scope, no price change. Flag me if that's not your understanding." An owner asks for the island moved 18 inches during a walkthrough. The echo: "Per today's walkthrough, you want the island shifted 18 inches toward the pantry. That's a change order — written pricing to you by Friday."

This isn't legal paranoia. It's a memory system. Two honest people walk away from the same conversation with two different versions of it — memory decays, and it decays in whatever direction favors the person remembering. The written echo freezes the agreement while it's still fresh, and it does it without a lawyer in the room. Subs don't read it as distrust. They read it as a GC who won't burn them later.

What its absence costs: the classic he-said-she-said over scope. FMI's researchers traced 48% of all US construction rework back to poor project data and miscommunication — and a large share of that starts life as a verbal agreement nobody wrote down. Worst case, the missing paper trail is what turns a $400 disagreement into a back-charged invoice and a dead relationship.

Habit 2: They over-communicate schedule changes — push, never pull

When the schedule moves, great GCs tell every affected sub, supplier, and owner before anyone has to ask. That's the entire habit: information gets pushed out, never pulled in.

You know a pull job when you're on one. The electrician calls at 6:40 AM to ask whether the slab passed inspection, because if it didn't, he's burning a morning. The owner texts every Friday asking "where are we?" The lumber yard delivers to a site that isn't ready. On a push job, none of those calls happen — everyone already knew last night.

What it looks like in practice: the footing inspection fails Tuesday at 2 PM. By Tuesday evening, the framer knows his start date slid three days, the lumber drop is rescheduled, and the owner knows what failed and what the fix is. The GC ate ten minutes of messaging. Everyone else's week stayed intact. The bar isn't "did I tell people who asked" — it's "did anyone have to ask."

What its absence costs: your subs run crews across multiple GCs, and they quietly rank you. The GC who pushes schedule information gets the A-crew and a straight answer about availability. The GC whose jobs are "show up and find out" gets deprioritized the moment somebody else's job is more predictable. That cost is invisible — you never see the weeks your subs scheduled around you. The research backs the size of the stakes: PMI's Pulse of the Profession research found ineffective communication is the leading contributor to project failure, putting $75 million at risk for every $1 billion in project spend.

Habit 3: They run one channel per job

On a great GC's job, every decision that touches scope, schedule, or money lives in one place the whole team can see. Calls and side texts are fine for logistics — but decisions go in the job channel, every time.

The failure mode is familiar. The owner texts you directly about swapping the tile. You answer from the truck. Three weeks later the tile sub — who was never on that thread — installs off the old spec, and now you're paying for demo, material, and a second mobilization. The information existed. It just lived in one man's phone.

The habit in practice is a single rule the whole crew knows: if it changes scope, schedule, or money, it goes in the job channel. Take the call, have the side conversation — then repeat the decision into the channel within the hour. The bonus compounds: when a new sub or crew lead joins mid-job, onboarding is "scroll the channel," not three phone calls and a guess.

What its absence costs: the same FMI study found construction professionals spend over a third of their working hours on "non-optimal activities" — chasing project information, fixing mistakes, resolving conflicts — to the tune of $177.5 billion in labor cost per year. Digging through five text threads, two email chains, and a voicemail to reconstruct one decision is exactly that bucket. So is the rework when the reconstruction is wrong. We dug into the field side of this problem in the office-field communication gap.

This is the one habit where tooling honestly matters. A group text holds up fine at one or two jobs with a three-man crew. At five concurrent jobs with rotating subs, it falls apart — no job separation, no file storage, no way to add or remove people cleanly. Chat-native tools like ContractorsChat make every project its own channel by default, with the files, change orders, and decision trail attached to the job instead of scattered across personal phones. But the rule comes first. Software just lowers the friction of keeping it.

Habit 4: They close loops fast

Every question on a great GC's job gets one of two things the same day: an answer, or a date for the answer. Nothing just sits.

Closing a loop doesn't mean knowing everything. "I don't know yet — the engineer is reviewing it, you'll have an answer Thursday" closes the loop. Silence doesn't. The sub with an ETA plans around it. The sub with silence assumes the worst, and he's usually right to.

What it looks like in practice: a ten-minute end-of-day sweep. Every open question from subs, the owner, suppliers, and inspectors gets an answer or an ETA before the phone goes on the charger. And the ETAs get kept — or re-dated before they lapse, not after the sub calls asking. Same discipline on formal paper: an RFI that needs the architect gets forwarded the day it lands, with the asker told it's moving.

The same rule applies up the chain. An owner whose Tuesday question is still hanging on Friday doesn't conclude you're busy — he concludes you're hiding something, and the next conversation starts from suspicion instead of trust. Owners who get fast loop-closing forgive slipped dates; owners who get silence dispute invoices. The ten-minute sweep is the cheapest client-relations program you will ever run.

What its absence costs: a sub waiting on an answer doesn't actually wait. He does one of two things — guesses, or pulls his crew to a job where he isn't blocked. The guess becomes rework. The pulled crew becomes a two-week hole in your schedule, because you don't get him back on your timeline, you get him back on his. Unanswered questions are also how minor RFIs ferment into delay claims: every day a documented question sits open, it accrues someone else's version of events. More on running this discipline with subs in subcontractor communication best practices.

Habit 5: They talk about money before it's awkward

Great GCs put payment terms in writing before work starts and price change orders before the changed work gets done. The money conversation happens on day one, when it's easy — not at invoice time, when it's not.

What it looks like in practice: sub agreements name the pay-app date and the payment window, in numbers, before mobilization. The owner sees the draw schedule before demo starts, so the first big invoice is an expected event instead of a shock. Change orders follow one non-negotiable: no signed CO, no changed work — pricing goes out in writing within 48 hours of the request, and crews don't touch the change until it's signed. And invoices leave on schedule, every time, because a GC who bills erratically forfeits the right to complain about getting paid erratically. (If your paperwork is the bottleneck, a free invoice generator kills that excuse in five minutes.)

The numbers on what avoidance costs are ugly. Rabbet's 2025 Construction Payments Report put the cost of slow payments to the US construction market at $299 billion in 2025 — respondents pegged it as a hidden 14% tax on project costs. And reputation prices in: in the same report, 91% of GCs said they weigh an owner's payment reputation when deciding what to bid, and 88% declined to bid at least one job in the past year over a slow-pay reputation. Your subs run the exact same math on you. Pay slow and communicate about money worse, and every number you're quoted quietly carries a risk premium.

The awkwardness never shrinks by waiting. An unpriced change order discussed after the work is done isn't a pricing conversation anymore — it's a negotiation where you've already spent your leverage. The GCs who talk money early aren't braver. They've just learned that the early version of the conversation is the cheap one.

The five habits at a glance

How to install the habits without adding office hours

Pick one habit and run it for two weeks before adding the next. These are muscle memory, not policy memos — trying to adopt all five on Monday is how all five are gone by Friday.

1. 1Weeks 1–2: the same-day echo. Every verbal agreement gets the one-line written confirmation before the day ends. This one feeds all the others.
2. 2Weeks 3–4: push the schedule. The moment a date moves, message everyone it touches. Track one number: how many times someone had to call you to ask. Drive it to zero.
3. 3Weeks 5–6: the channel rule. Announce it once to the crew and the subs: if it changes scope, schedule, or money, it goes in the job channel. Then enforce it by repeating stray decisions into the channel yourself.
4. 4Weeks 7–8: the end-of-day sweep. Ten minutes, every evening. Every open question gets an answer or an ETA.
5. 5Weeks 9–10: money upfront. On the next contract you sign, put pay-app dates, payment windows, and the no-signed-CO-no-work rule in writing before mobilization.

Software won't hand you the habits, but it can lower the cost of keeping them. ContractorsChat is built around habit 3 — every project is its own channel — with the GPS timeclock, change orders, quotes, and invoicing attached to the same job thread, so the written echo, the pushed update, and the priced CO all land in the one place the crew already looks. Know the limits before you switch anything: it doesn't do takeoffs or estimating databases, and it's not accounting software — it exports to QuickBooks rather than replacing it. If estimating is your bottleneck, fix that first. If communication is, the current beta gives you 6 months of Pro free, no credit card — full tier details on the pricing page.

None of these five habits is complicated, and not one of them requires you to be a better builder than the GC across town. That's the point. The GCs everyone wants to work for aren't winning on craft. They're winning because they're easier to build with — and that's a skill you can install one habit at a time, starting tonight.