Everyone knows a project that went sideways. Everyone also has a story about why: the sub who didn’t show, the materials that arrived late, the rain that killed two weeks in October.
Those are the stories we tell. They’re not always the true ones.
The single most controllable cause of construction project failure isn’t weather, labor or supply chain volatility. It’s the way project teams communicate.
What’s more, at the center of that failure — on almost every project, at almost every firm — is a tool invented in 1971 that was never designed to manage a $40 million build.
It’s email. And it’s costing the industry $31.3 billion a year in rework alone.
The Coordination Tax
Before we talk about what email costs, it helps to understand why it won.
Every construction project is a temporary organization. A general contractor assembles a team — structural subs, MEP trades, the owner’s rep, the architect, the civil engineer — that has never worked together in exactly this configuration and probably never will again.
The project ends. The team dissolves. A new one forms on the next job.
In that environment, every firm brings its own systems, processes and preferred tools. The GC might run Bluebeam. The structural sub uses Procore. The owner’s rep opens Outlook in the morning and doesn’t close it until 7 p.m.
Bluebeam’s own research found that 72% of AEC firms still use paper in at least one project phase — and that the average firm operates across 11 separate data environments.
So, what’s the default communication layer? The one thing everyone already has. The one tool that requires zero onboarding, license negotiation or coordination to adopt. Email wins not because it’s good at construction; it wins because it costs nothing to start.
That’s not stupidity as much as it’s rational behavior under real constraints. Still, rational in the short term doesn’t mean cheap in the long run.
The average construction professional spends 14 hours a week on non-optimal activities. Five and a half of those hours are spent looking for project information — hunting through threads, forwarding attachments, trying to figure out which version of a drawing is current.
That’s an inbox problem.
What Happens When Information Lives in Someone’s Inbox
There’s a specific failure mode that every project manager reading this has lived: the drawing revision that went out on a Tuesday. It was in the email. Someone on the mechanical team didn’t see it — or saw it and didn’t flag it — and the crew spent three days installing ductwork based on the old design.
That’s not a hypothetical. According to the PlanGrid/FMI “Construction Disconnected” report, 48% of all construction rework in the United States is driven by poor data and miscommunication. Not design errors or bad workmanship. Miscommunication and the wrong information reaching the wrong people at the wrong time — or not reaching them at all.
Rework costs the U.S. construction industry $177 billion annually. Poor communication and bad data account for $31.3 billion of that. The median rework event costs $8,300 and delays the schedule by 3.4 days. Multiply that across a project with dozens of active work fronts and the math becomes a different kind of problem.
And then there are RFIs.
On a typical project, an RFI sits unanswered for an average of 9.7 days. Twenty-two percent of RFIs managed through traditional channels never receive a reply at all. Not late. Never. The question gets buried, the sub makes a judgment call and two months later someone is tearing out a wall.
Processing a single RFI costs approximately $1,080 in administrative time. A one-year commercial project generates hundreds of them. Run the math — then consider that construction disputes in North America now average $43 million in value and take more than 14 months to resolve. The audit trail that determines who wins those disputes lives, almost entirely, in inboxes no one can fully reconstruct.
We’ve Seen This Before
In 2019, 70% of healthcare providers still communicated via fax machine. Not because they didn’t know about better tools. They knew. They just couldn’t stop.
The structural reasons were identical to what’s happening in construction today: everyone had a fax line, the systems didn’t talk to each other, the format had legal standing and switching meant convincing thousands of independent providers to adopt a new standard simultaneously.
Healthcare’s fax problem didn’t get solved because a better technology appeared. Better technologies had existed for a decade. It got solved when the Centers for Medicare & Medicaid Services issued a mandate in 2025 requiring electronic exchange, with a hard deadline and financial stakes. The technology wasn’t the forcing function. Accountability was.
Construction’s email problem has the same architecture. Email persists not because nobody knows it’s a problem — construction professionals are among the most practically intelligent people in any industry. It persists because it’s the lowest common denominator in a fragmented, project-based ecosystem where switching costs fall on everyone simultaneously and the benefit of switching doesn’t fully materialize unless every firm on the project makes the move together.
That, folks, is a standardization problem.
What Standardization Actually Does
Firms that standardize project communication — a common document environment, structured RFI workflows, markup and review processes that every stakeholder on the project can touch — don’t just move faster. They manage differently.
When project information lives in a shared, structured system instead of 17 inboxes, decisions happen while there’s still time to act on them. RFIs get answered. Revisions reach the field before the work gets done wrong. Accountability is visible without anyone having to reconstruct a thread at 11 p.m. before a deposition.
Pinnacle Engineering put this into practice with Bluebeam Revu and Studio. Before the transition, emails piled up with conflicting versions of the same PDF, client updates were delayed and tracking changes across disciplines required constant back-and-forth. After standardizing on a shared platform, the firm cut document response times by 10% to 20% and reduced the design revision cycles that had been killing its schedules.
Firms with documented quality and communication standards keep rework below 5% of project budget. Firms without them run two to three times that rate. That’s not a marginal difference. On a $30 million project running 6% margins, the gap between 5% rework and 10% rework is the difference between a profitable job and a year of work that cost the company money.
The internal champion who brings this argument to leadership doesn’t need to sell software. What they need is to answer one question: What is our rework rate, and how much of it is a communication problem?
Because if the honest answer is “we don’t know,” that’s the first thing to fix.
The weather will delay a project for a day. A missed RFI will delay it for a week. An inbox that no one can search, audit or trust will delay it for the life of the project — and make the next dispute harder to defend.
The information was there. It was just in someone’s email.
