Is 'I never got the update' usually true, or is it an excuse?

True more often than most GCs assume. PlanRadar's 2025 survey of 811 firms found crews without a consistent QA/QC process are 21% more likely to see avoidable rework, which only happens at scale if the gap is structural, not a pattern of subs lying. Treat the claim as probably true and fix the routing. You lose nothing if it turns out to be an excuse, because the fix catches that too.

Who's liable when a sub installs off a change he says he never received?

Usually you, unless there's a record showing the change reached him before he started. A text you sent proves you tried. It doesn't prove he read it. Without a timestamped log tied to that specific person and that specific change, a back-charge argument turns into two honest people disagreeing, and the GC absorbs the tear-out to keep the job moving.

Should I notify every sub about every change, or just the ones it affects?

Route it to the trade it touches, not the whole job. A reply-all thread trains every sub to skim, because most of what lands in it is never his problem. Send the electrician three relevant changes over a month instead of forty irrelevant ones and he actually reads the next one. Blast everyone and the one change that mattered to him drowns with the rest.

What's faster than a group text for getting a change to the right sub?

A push notification scoped to his trade and logged when he opens it. A group text feels fast to send and is slow to land, because it competes with every other thread on his phone and leaves no record of who actually read it. A routed, logged push does both jobs: it reaches only the people the change touches, and it proves whether it worked.

What do I do when a sub ignores a change notification and builds the old way anyway?

Escalate before he starts cutting, not after. Set a window, a few hours on an active job, and if nobody's opened the change by then, that's the trigger for a phone call, not a discovery you make at the walkthrough. The point of logging who opened what is to catch the silence while it's still cheap to fix.

September 15, 2026 · 5 min read · Patrick Keating, Founder

"I Never Got the Update": Ending the Sub Communication Gap

The short version: Subs don't ignore updates as often as GCs assume. Most of the time the update never reached them in a form that registered as one, a buried thread, a verbal note at a walkthrough someone else attended, a reissue nobody reread. PlanRadar's 2025 survey of 811 firms across 13 countries found crews without a consistent QA/QC process run 21% more avoidable rework. Closing the gap means three things: route the change to the trade it actually touches, push it instead of hoping someone checks, and log whether it landed.

An HVAC sub is on a ladder in a bonus room over the garage on a Thursday, flex duct looped over one shoulder, snips in hand, cutting register boots into a soffit framed two weeks earlier. The soffit dropped six inches on Tuesday, when the architect cleared a structural beam and emailed the revision to the GC's office. Nobody forwarded it to the sheet-metal sub. He's cutting boots for a ceiling line that no longer exists, and he'll find out when the boots don't line up with the grille locations on the finish set.

Nobody here is lazy or careless. The architect sent the change. The office received it. The sub never got it, because "got it" requires someone to hand it to him, and in the gap between those three true statements, the missed-update half does its work again.

Is "I never got it" usually true?

Ask that question on enough jobs and the honest answer is yes, more often than most GCs want to admit. A change that lives in an email thread the sub isn't copied on, a verbal mention at a walkthrough he wasn't at, a reissue that buried one moved line on page 23: none of those count as delivery, even though someone technically sent something. PlanRadar's 2025 survey, spanning 811 firms in 13 countries, found crews without a consistent QA/QC process run 21% more avoidable rework than crews with one. That gap doesn't show up at that scale from a handful of subs lying. It shows up because the system drops changes on the way to the field, and nobody's counting how often.

Why reply-all makes it worse, not better

A sub's scope agreement behaves like a contract once signed. The price and the schedule are fixed against that day's drawings, and every revision after that either gets reconciled into his copy or quietly drifts away from it. WorldCC's 2025 research, cross-industry but directly applicable here, found contracts lose roughly 11% of their value after signing purely to poor management of what's inside them, not to the deal itself. A sub's agreement is no different. The number was right on day one. It erodes a little every time something changes that never crosses back into his version of it.

Most small builders respond to that risk by over-notifying instead of routing correctly: every change goes to every sub, because it feels safer than leaving someone out. It does the opposite. A framer who gets copied on plumbing fixture swaps, electrical panel changes, and tile selections learns fast that most of what lands in that thread isn't his. He starts skimming. The one message that actually needed him gets the same half-attention as the other thirty.

What a routed, logged change looks like against the alternatives

Channel	Creates a record?	What happens when he says "I never got it"
Group text to the whole sub list	No log of who opened it, buried under every other thread	Everyone claims they missed it, and nobody's wrong
Email attachment, no flag on what changed	Sent, not confirmed opened	"Check your inbox" isn't an answer standing at rough-in
Verbal note at a walkthrough	Lives in one person's memory	Whoever wasn't there never heard it, and can't be blamed for that
Routed push, scoped to the affected trade, logged on open	Timestamped, tied to one person and one change	The log either shows the open or it doesn't. The argument is over in one line

The same proof-of-receipt gap sits at the center of plan revision control's fourth habit: a sent message and an opened one are different events, and only the second protects anybody. Routing just narrows who the message goes to before you measure whether it landed.

What happens when nobody acknowledges

Set a window. On an active job, a few hours is enough: long enough for a sub to see a push between tasks, short enough that a missed change doesn't sit quiet until someone's holding a saw. If the window closes and the log still shows nothing opened, that's the trigger for a phone call, not a surprise at the walkthrough.

That's a different job than scanning a code taped at the room to see the current set, which proves a sub can see the current version whenever he shows up. Escalation is the other half: catching the sub who hasn't shown up to check at all, before his scope gets built against a version that's already gone.

None of this needs a document-control hire or a new app for the crew to resist. It needs the change routed to the right person, pushed instead of parked, and logged whether it landed, with a human follow-up the moment the log goes quiet. SpecAlign runs exactly that loop on every revision: changes route to the trades they touch, push instead of wait, and log the open, so a GC spends the follow-up call on the sub who's actually behind, not the nine who already saw it.

Stop asking whether a sub read the text. Build the system that tells you, and make the silence itself the alarm.

Sources

PlanRadar, "QA/QC Report" (2025): survey of 811 firms across 13 countries; crews without a consistent QA/QC process run 21% more avoidable rework than crews with one
WorldCC (2025): contracts lose roughly 11% of value after signing to poor management of the obligations inside them, not the underlying deal
SpecAlign product capability: trade-scoped change routing, push delivery, and open-logging on revisions

The HVAC example illustrates a common pattern, not a specific job. The PlanRadar and WorldCC figures are industry-wide, not residential- or SpecAlign-specific.

Frequently asked questions

Is 'I never got the update' usually true, or is it an excuse?: True more often than most GCs assume. PlanRadar's 2025 survey of 811 firms found crews without a consistent QA/QC process are 21% more likely to see avoidable rework, which only happens at scale if the gap is structural, not a pattern of subs lying. Treat the claim as probably true and fix the routing. You lose nothing if it turns out to be an excuse, because the fix catches that too.
Who's liable when a sub installs off a change he says he never received?: Usually you, unless there's a record showing the change reached him before he started. A text you sent proves you tried. It doesn't prove he read it. Without a timestamped log tied to that specific person and that specific change, a back-charge argument turns into two honest people disagreeing, and the GC absorbs the tear-out to keep the job moving.
Should I notify every sub about every change, or just the ones it affects?: Route it to the trade it touches, not the whole job. A reply-all thread trains every sub to skim, because most of what lands in it is never his problem. Send the electrician three relevant changes over a month instead of forty irrelevant ones and he actually reads the next one. Blast everyone and the one change that mattered to him drowns with the rest.
What's faster than a group text for getting a change to the right sub?: A push notification scoped to his trade and logged when he opens it. A group text feels fast to send and is slow to land, because it competes with every other thread on his phone and leaves no record of who actually read it. A routed, logged push does both jobs: it reaches only the people the change touches, and it proves whether it worked.
What do I do when a sub ignores a change notification and builds the old way anyway?: Escalate before he starts cutting, not after. Set a window, a few hours on an active job, and if nobody's opened the change by then, that's the trigger for a phone call, not a discovery you make at the walkthrough. The point of logging who opened what is to catch the silence while it's still cheap to fix.

Patrick Keating, Founder

Patrick Keating is the founder of SpecAlign, building AI construction intelligence for custom home builders.