Project Management & Efficiency, Technology & Innovation

A Takeoff That Adds Up Can Still Be Wrong

The checks estimators run between measurement and pricing to catch scale errors, missed scope and double counts before a bid goes out

Frank Kalman
October 28, 2026

How to Walk into Your CFO’s Office and Make the Case for Changing How Your Team Handles Drawings

Construction & The Economy, Project Management & Efficiency
Frank Kalman

You already know the problem. Here’s how to explain it to the person who controls the budget.

The super finds the drawing eventually — version 7, when he needed version 9, buried somewhere in a shared drive that nobody has organized since the last PM left. Forty minutes gone, plus the calls that followed, plus the rework that came after. None of it shows up on the job cost report.

That’s the thing about document management failures: they don’t announce themselves as failures. They show up, instead, as a bad morning, a slow week, a job that just never quite found its rhythm, and by the time anyone connects the dots back to a folder full of outdated PDFs, the money is already spent and the schedule is already gone.

You know this, and so does your PM, but the question is whether the person who controls the budget knows it — and whether you can walk into that office and make them see it the way you do. Most people can’t, not because they’re wrong about the problem, but because they bring the wrong argument. They bring the frustration instead of the math, describe the workflow instead of the cost, and hand a CFO a complaint when what they needed was a business case.

This piece is the business case. It’s for the PM, VDC lead or superintendent who is done getting the sympathetic nod and needs to close the room.

If you want the full cost picture first, read The Hidden Cost of Document Chaos. What follows is what you do with it.

Lead with a Number, Not a Complaint

A CFO who hasn’t stood in a trailer hunting for a drawing revision isn’t going to feel the cost of that problem intuitively, which means describing it won’t get you very far. You have to quantify it, and you have to make the number specific to your firm.

Start with the industry baseline. Construction professionals spend more than 14 hours a week on what one major study calls “non-optimal activities” — hunting for project data, resolving conflicts, dealing with rework rather than building or managing — and across the US workforce, that wasted time runs an estimated $177.5 billion a year in labor cost.

Here’s how to translate that into something that lands in your office. According to BLS May 2025 wage data, construction managers earn a mean $59.79 per hour, while first-line supervisors — the closest SOC match to superintendents — earn $41.56. Add benefits, which BLS benefits data puts at about 31% of total compensation, and the fully burdened rate runs roughly $86 an hour for a construction manager and $60 for a super.

Fourteen hours a week at those rates is $1,200 a week, per manager, in labor cost that isn’t producing anything. Multiply that by the number of PMs and supers on your active jobs, and the number stops being an industry statistic — it becomes a line on your income statement that nobody has labeled yet.

“$1,200 a week, per construction manager, in labor cost that isn’t producing anything.”

Rework compounds it further. The Construction Industry Institute puts direct rework at about 5% of total project cost, and nearly half of that traces back to poor communication and bad project data rather than bad workmanship. On a $30 million job that’s $1.5 million, and on a portfolio of $30 million jobs, the compounding is the kind of number that tends to get a CFO’s attention.

RFIs stack on top of that. A Navigant Construction Forum analysis of more than 1.1 million RFIs across 1,362 projects found the average large project generates 796 of them, each costing about $1,080 to process — roughly $860,000 per project in RFI overhead before anyone swings a hammer. The median response time was 9.7 days, and about 22% of RFIs never got a response at all, a rate Navigant flagged as a leading predictor of disputes and claims.

What the current workflow costs, by the numbers

Cost driver	Benchmark	Source
Time lost to non-optimal activities	More than 14 hours per person, per week	FMI and PlanGrid
Labor cost of that lost time, U.S. workforce	$177.5 billion a year	FMI and PlanGrid
Fully burdened hourly rate, construction manager	About $86	BLS wage and benefits data
Fully burdened hourly rate, first-line supervisor	About $60	BLS wage and benefits data
Weekly cost of 14 lost hours, per construction manager	About $1,200	Calculated from the rates above
Direct rework	About 5% of total project cost	Construction Industry Institute
RFIs on an average large project	796	Navigant Construction Forum
Cost to process one RFI	About $1,080	Navigant Construction Forum
RFI overhead per project	About $860,000	Navigant Construction Forum
Median RFI response time	9.7 days	Navigant Construction Forum
RFIs that never get a response	About 22%	Navigant Construction Forum

You don’t need all of those numbers. You need one that maps to something your CFO is already accountable for, with a firm-specific dollar figure attached to it. That specificity is what separates a business case from a grievance.

How do you translate a document management problem into language a CFO responds to?

CFOs don’t evaluate technology — they evaluate exposure. The field and the finance office are looking at the same failure through different instruments: one sees a lost morning, the other sees nothing, because no report captures it. A request earns budget when it makes that invisible cost show up where finance already looks.

CFOs think in three categories — margin, risk and labor cost — and the document management problem has a real story in all three. Your job is to tell it in their language rather than yours.

On margin, the numbers are more uncomfortable than most people realize. The CFMA 2025 Financial Benchmarker, which analyzes data from more than 1,500 construction companies, puts pretax net income for commercial GCs and CMs at 4.4% — not the 5–6% that gets thrown around in general industry discussions. At 4.4%, a rework event running 5% of contract value doesn’t just eat into profit; it erases the job’s margin entirely and then keeps going. That’s the reframe worth landing with a CFO: document-driven rework isn’t an operational nuisance; it’s a margin event that can flip a job from profitable to a loss.

On risk, the exposure is quieter but just as real. Every unanswered RFI and every version conflict is a potential claim waiting for a trigger, and the audit trail that doesn’t exist today is the one you’ll need in six months when a sub says they built off what they were given. Courts and arbitrators don’t care that the right drawing existed somewhere in a shared drive; they care whether you can prove who had what version and when. The cost of not being able to prove it often dwarfs the cost of the original mistake.

On labor, the math is straightforward and uncomfortable in equal measure. Construction wages rose 4.2% year over year as of August 2025, the most recent year for which data are available, and the industry needed to attract 349,000 net new workers in 2026 on top of normal turnover, per ABC. Meanwhile, 92% of construction hiring firms report difficulty filling positions, and 45% name worker shortages as the leading cause of project delays, according to AGC’s 2025 Workforce Survey. Firms are paying more for experienced people than they ever have at exactly the moment those people are hardest to find, which makes sending them into the week with 14 hours of information-hunting baked into their schedule not just inefficient, but the most expensive possible use of the industry’s scarcest resource.

What’s the most effective way to structure a construction technology business case?

A business case gets funded in order: the problem, its price, proof that a peer solved it, then the ask. The order is the argument. A CFO who hears the solution before feeling the cost has nothing to weigh it against, and a request with nothing to weigh against it gets deferred.

Every CFO in this industry has the same four questions before they approve anything, and the goal isn’t to surprise them with the problem — it’s to make it impossible for them to set it aside.

Start with something specific rather than a category. Not “our document management isn’t working,” but the version conflict on the Riverside Avenue project that cost two weeks of rebar schedule, or the RFI that sat 11 days and triggered a change order nobody budgeted for, or the closeout package that took six weeks to assemble because nothing had been documented in one place throughout the job. A real thing that happened, with a real cost attached to it. Specificity does what statistics can’t — it makes the problem real to someone who wasn’t there.

Then put a number on it. Use the industry benchmarks as a floor — 5% rework, $860,000 in RFI overhead per project — and build toward your own. Firm-specific data always leads, but if you don’t have it, the benchmarks still establish what the category typically costs, and your firm’s experience is unlikely to be better than average.

Then show them a firm that fixed it, because this is where the room usually turns.

DPR Construction was staring down a 31-day schedule delay on the Alta Bates Summit Medical Center project in Oakland — a $500 million hospital expansion where every day of delay carries a very specific dollar figure. Rather than continuing to pass PDFs back and forth between the engineer of record and the rebar detailer, the team ran real-time collaborative reviews using Bluebeam Studio Sessions, which cut the submittal review cycle by more than 33% and compressed a 25- to 30-workday process into 10 to 12 days. Up to 10 days of schedule recovery, per review cycle.
Balfour Beatty put a dollar figure on the same principle at its DFW Airport renovation: $5 million in project savings from centralizing documents and giving field teams real-time access to current information. The savings didn’t come from better technology in any abstract sense; they came from fixing the moment where the wrong information reached the wrong person.
Premier Mechanical saved $70,000 digitizing project delivery, and Turner Construction cut paper costs 73% making the same shift. Rudolph and Sletten, a commercial GC running projects north of $500 million, cut preconstruction review times 30% by standardizing on Bluebeam Studio.

Different firm types, different project sizes, same pattern: the savings don’t come from the tool itself; rather, they come from the workflow the tool makes possible.

Close with a specific ask rather than a category. Not “better document management,” but a defined scope: standardized drawing workflows across active projects, with version control and a single shared set accessible to field teams in real time. That’s something that can get a line item. A category cannot.

What objections should you expect when making the case for construction document management software?

The four objections that stall most construction technology proposals — cost, adoption, integration and rollout complexity — all have the same underlying structure: risk aversion. Each one is most effectively answered by reframing the risk. The status quo isn’t the safe option; it’s just the one whose costs don’t get tracked.

If you’ve walked in without answers to all four, you haven’t finished preparing.

“What does it cost?” Less than one rework event on a mid-size job, and that’s before you count the schedule impact or the claim exposure. The more useful frame is total cost of ownership vs. total cost of the status quo, and the Bluebeam ROI calculator can help you build that comparison before you walk in. Come with the math already done.

“Will the field actually use it?” This is the right question, and it deserves a real answer rather than a reassurance. AGC’s 2025 Workforce Survey found 43% of construction firms name lack of time to implement and train as a primary obstacle to tech adoption, because the most powerful platform in the category is worthless if the foreman won’t open it on his phone in a trailer with bad signal. Bluebeam earns 4.7 out of 5 on Capterra across nearly 1,000 verified reviews, and on G2’s head-to-head with Procore, it leads on “Meets Requirements” (9.2 vs. 8.8) and “Ease of Setup” (8.5 vs. 8.2). It was built around the drawing rather than added to a broader platform as a module, and that focus shows up in how quickly field crews ultimately adopt it. The document management software evaluation guide is direct about the principle: ease of use for field crews is the criterion that determines whether any of this pays off.

“How does it fit with what we already have?” Bluebeam integrates with the PM platforms and design tools most construction firms already run, and many teams use it for drawing and markup work inside a Procore or Autodesk Construction Cloud-managed project — the two are complementary rather than competing. The more productive question isn’t whether Bluebeam fits in the stack; it’s whether the tools you already have are talking to each other the way they should.

“What does rollout look like?” Shorter than the question implies. A focused document and markup tool isn’t an enterprise ERP implementation — run a two-week pilot on a live project with a small crew, and you’ll know more than any demo or feature matrix could tell you. The risk of a two-week pilot that doesn’t work out is two weeks. The risk of another year of the current workflow is whatever you calculated it to be in step one.

What to Bring Into the Room

You don’t need a slide deck for this conversation. You need three things, and they should ideally fit on a single page you can hand across the table.

One number that represents your firm’s own estimate of what the current workflow is costing — in rework percentage, RFI overhead, or PM hours spent on non-building work. Use the industry benchmarks to anchor it, round it to something defensible, and don’t get too precious about the precision. The point is that you did the math and the number isn’t small.

One story from a firm that already fixed it. DPR, Balfour Beatty, Premier Mechanical, Turner and Rudolph and Sletten are all in the public record, so pick the one that maps most closely to your firm’s project type and scale. A story from a contractor doing the same kind of work you do lands differently than a case study from a world the CFO doesn’t recognize.

One specific ask with a defined scope — not a category like “better document management,” but a workflow: standardized drawing sets across active projects, version control, field access in real time, markups tracked from issue through closeout. That’s something that can get funded. The category cannot.

“The firms winning in this market haven’t found ways to absorb the cost of document chaos. They’ve found ways to stop incurring it.”

The Conversation You’re Having

Here’s what’s worth remembering before you walk into that room: you’re not there to explain technology. You’re there to explain money, and specifically the money the current workflow is costing the firm every time a project runs.

The document management problem is a margin problem, a risk problem and a problem about what your most expensive and hardest-to-replace people are doing with their time. CFOs have those conversations every day — they’re fluent in all of it — and the only thing separating the people who win those conversations from the people who get the sympathetic nod and a deferral is whether they showed up in the CFO’s language or their own.

The firms that have already won this argument aren’t running better technology in any abstract sense. They’re running better information: one set of drawings that everyone trusts, markups that are tracked and auditable, RFIs that move in hours rather than days, and closeout packages that get built throughout a project rather than assembled in a panic at the end. The technology is almost beside the point — what changed was who had access to what and when.

You know your firm’s version of the problem, you have the numbers to show what it’s costing and you have proof from firms that already fixed it. Now you have the structure for the conversation. Walk in and close it.

Bluebeam’s Document Management for Construction 2026 Guide lays out the full framework, and the document management software evaluation guide walks through how to evaluate the options and match a platform to your team’s actual workflow. Both are worth having open before the meeting.

Frequently Asked Questions

How much does poor document management cost a construction firm?

Construction professionals lose more than 14 hours a week to non-optimal activities such as hunting for project data, according to FMI and PlanGrid. At fully burdened BLS wage rates, that is about $1,200 a week per construction manager. Direct rework adds about 5% of total project cost, per the Construction Industry Institute, and RFI processing adds roughly $860,000 on an average large project, per Navigant.

What is a typical profit margin for a commercial general contractor?

The CFMA 2025 Financial Benchmarker, drawn from more than 1,500 construction companies, puts pretax net income for commercial general contractors and construction managers at 4.4%. At that margin, a rework event equal to 5% of contract value erases the profit on the job.

How long does it take to pilot construction document management software?

A focused document and markup tool can be tested in a two-week pilot on a live project with a small crew. That is long enough to see whether field teams will use it, and the downside of a pilot that doesn’t work out is two weeks.

Does Bluebeam work with Procore and Autodesk Construction Cloud?

Yes. Bluebeam integrates with the project management platforms and design tools most construction firms already run, and many teams use it for drawing and markup work inside a project managed in Procore or Autodesk Construction Cloud. The tools are complementary rather than competing.

Put one live project on a single trusted drawing set.

Start Free Trial

185 Yards on Paper. 195 in the Truck. Both Numbers Are Right.

Project Management & Efficiency
Frank Kalman

Quantity takeoff, material takeoff and cost estimate are three different jobs. When they collapse into one, you lose the ability to answer the only question that matters in review.

The slab measured 185 cubic yards. The truck delivered 195.

Somewhere between those two numbers, someone made a decision. Maybe it was a 5% waste factor. Maybe it was pump priming and a subgrade that came in uneven. Maybe it was a purchasing manager who has been burned before and rounds up on principle. Any of those is defensible. What is not defensible is not knowing which one it was.

That gap, the 10 yards nobody can account for, is what happens when quantity takeoff, material takeoff and cost estimate get treated as the same activity. They are three distinct steps with three different owners doing three different jobs. Blurring them does not just muddy the paperwork. It costs you the ability to defend a number six months later, when the person asking is a project manager and the answer had better be good.

Why do three different jobs share one name?

The vocabulary drifted because the work compressed. When one person measures, adjusts for waste and prices in a single sitting, the language stops distinguishing steps that used to belong to separate desks. The terms did not become interchangeable. The workflow simply stopped making the seams visible.

There was a time when these three documents were produced by three different people, often in three different rooms. A takeoff clerk measured. A purchasing agent turned those measurements into orders. A chief estimator applied pricing and decided what the number would be. The handoffs were physical, so the distinctions were obvious.

Digital workflows collapsed that sequence onto one screen, and, in most firms, onto one person. That is a real productivity gain. It is also how the language got sloppy. Add the fact that “takeoff” works as both a verb and a noun, and that most software in this category is marketed as “takeoff and estimating,” and you end up with an industry using one word for three jobs.

The confusion is a language problem. The consequences are not.

What does a quantity takeoff establish?

The quantity takeoff is the only layer of an estimate that does not belong to anyone’s judgment. It belongs to the drawings. That is the source of its authority, and the reason it has to stay unnegotiated. The moment an estimator’s opinion enters the measurement, the number stops being evidence and starts being an argument.

A quantity takeoff (QTO) measures the net in-place quantities required to build the project as designed. Lengths, areas, volumes and counts, captured directly from the construction documents, with no adjustment for waste, packaging or field inefficiency.

Square footage of flooring shown on the plan. Cubic yards of concrete defined by slab thickness and footprint. Fixture counts pulled off the reflected ceiling plan. The QTO is the project’s geometric truth, and it answers exactly one question: What exists on paper?

A clean QTO leaves four things out on purpose:

Waste factors for cuts, spillage and breakage
Packaging logic, standard sizes and order minimums
Labor productivity assumptions
Any form of pricing

The test is not whether the total feels right. It is whether a second estimator, handed the same sheet set, would land on the same number and be able to see how you got there.

The QTO defines scope, not strategy. Nothing about how you plan to buy the material, sequence the work or price the job belongs anywhere near it.

How is a material takeoff different?

A material takeoff is the first place construction reality gets a vote. Waste, breakage, standard sheet sizes and the uneven subgrade nobody drew are all legitimate inputs, and they all reflect somebody’s experience rather than the drawing set. That is precisely why they need their own container instead of being folded into the measurement.

The material takeoff (MTO) builds on the QTO but answers a different question: What do we need to buy?

This is where net quantities become gross quantities. Waste factors for cuts, spillage and breakage. Packaging and standard sizes, because drywall comes in sheets and rebar comes in lengths. Overlap allowances for roofing and siding. Overage for constructability, including the pump priming and the subgrade variability that turned 185 yards into 195.

The MTO is a procurement tool. It supports purchasing, logistics and delivery planning. It is not a bid comparison document, and it is not a scope validation document. Treating it like one is how contractors end up bidding their own waste factors, paying markup on the same material twice: once in the volume and again in the unit price.

A clarifying way to think about it: Two contractors bidding the same job should produce nearly identical quantity takeoffs and meaningfully different material takeoffs. The QTO reflects the design. The MTO reflects the builder. If two QTOs disagree, somebody misread the drawings. If two MTOs disagree, that is just two companies with different suppliers, different crews and different tolerances for running short.

Where does the cost estimate fit?

Pricing is the layer everyone watches and the layer with the least power to fix anything. A sharp unit cost applied to a wrong quantity produces a confident, well-formatted mistake. The estimate inherits whatever the takeoff got wrong, and no amount of discipline downstream can reach back upstream and repair it.

The cost estimate is where quantities meet money. Unit prices, labor productivity rates, equipment costs, indirect costs, general conditions, contingency and profit. This is the step that produces the number you submit and then live with for the next 18 months.

No amount of pricing accuracy can fix bad quantities. If the takeoff is wrong, the estimate will be wrong, whether it comes in high or low. The quantity takeoff is the independent variable. Every other number in the file depends on it.

The three layers

Layer	Question it answers	Primary owner	What it must never contain	It changes when
Quantity takeoff	What do the drawings show?	Estimating	Waste, allowances, pricing logic	The drawings change
Material takeoff	What do we need to buy?	Procurement	Labor rates, margin, contingency	Suppliers, site conditions or means and methods change
Cost estimate	What will it cost to build?	Estimating and leadership	Unverified quantities	Markets, labor rates or risk appetite change

Why does keeping the layers separate matter in practice?

Separation is not bookkeeping hygiene. It is what makes an estimate survivable under interrogation. Estimating is a discipline that gets judged retroactively, months after the fact, by people who were not in the room. The layers exist so that any number can be walked backward to the decision that produced it.

Three moments make the case, and every estimator has lived through all of them.

The addendum lands three days before bid

The architect moves a wall. With clean layers, you update the affected quantities in the QTO, let the change flow into the MTO where it affects procurement, and reprice only what moved. With collapsed layers, you cannot isolate the change, because you cannot tell which part of the number was the drawing and which part was the waste factor. Now the revision is a full rebuild, and you are doing it on a Tuesday night.

The PM questions a number in month six

You want to open the sheet, point at the markup and say: Here is what we measured, here is what we ordered and here is why those are different. Three sentences, and the conversation is over. If waste and pricing were baked into the measurement, you cannot produce those three sentences. You produce a shrug, and shrugs are expensive.

A new estimator joins the team

Consistency across a team is impossible when every estimator has a private convention for where decisions live. One buries a 7% waste factor in the takeoff. Another applies it downstream. Their numbers will never be comparable, and no amount of peer review will fix a problem that starts with structure.

How do you know your layers have already collapsed?

The failure is quiet. Nobody announces that scope and procurement logic have fused. It shows up as friction that gets rationalized as normal, which is why the symptoms are worth naming out loud rather than waiting for a bad job to name them for you.

A few reliable tells:

You cannot say what your waste factor is without opening a file, because it lives inside the measurements rather than beside them.
Procurement calls to confirm quantities before every order, because they do not trust that the number they received is the number they should buy.
A drawing revision triggers a full remeasure instead of a targeted update.
Two estimators measure the same scope and produce totals that do not reconcile, and nobody can explain the delta.
Someone asks where a number came from and the honest answer is that it came from the last estimate on a similar job.

None of these is a software problem. They are structural ones, and they get solved before the first m e asurement is placed, by deciding where each kind of decision belongs and then holding that line.

Three steps, one workflow

Quantity takeoffs, material takeoffs and cost estimates are not competing methods. They are sequential layers, and each one inherits whatever the layer before it got wrong.

The QTO defines what the drawings show. The MTO determines what gets purchased. The cost estimate calculates what it costs to build. Keep those three jobs in three separate containers, and the estimate stays reviewable, revisable and defensible under pressure.

So the next time someone on your team asks for “the takeoff,” ask them which one they mean. If nobody in the room can answer cleanly, that is the actual problem, and it is not going to fix itself at bid time.

Frequently asked questions

What is the difference between a quantity takeoff and a material takeoff?

A quantity takeoff measures the net in-place quantities shown on the drawings, with no adjustment for waste or packaging. A material takeoff converts those net quantities into gross purchase quantities by adding waste factors, standard sizes, laps and overage. The QTO defines scope. The MTO supports procurement.

Should waste factors be included in a quantity takeoff?

No. Waste belongs in the material takeoff, not the quantity takeoff. Baking waste into the measurement makes quantities impossible to audit against the drawings and makes drawing revisions far harder to isolate, because you can no longer separate what the plan showed from what you decided to order.

Can an accurate cost estimate compensate for an inaccurate takeoff?

No. Pricing is applied to quantities, so the estimate inherits every quantity error. Sharper unit costs and better labor rates cannot correct scope that was never measured. The quantity takeoff is the independent variable; everything downstream depends on it.

Is a material takeoff the same as a bill of materials?

They overlap but are not interchangeable. A material takeoff is derived by the estimator from the drawings and adjusted for waste, packaging and constructability. A bill of materials is typically a specified list of components tied to a design, an assembly or a manufacturer. The MTO answers what to order for this job under these conditions. A bill of materials answers what the design specifies.

Who owns the material takeoff?

Procurement typically owns it, though estimating often produces the first version. What matters more than the org chart is that the MTO exists as its own artifact rather than living inside the quantity takeoff, so that purchasing decisions can be reviewed and revised without disturbing the measured scope.

See what a defensible takeoff looks like.

Start Free Trial

Nobody Budgets for the 40-Minute Drawing Hunt

Construction & The Economy, Project Management & Efficiency
Frank Kalman

The hidden price tag on familiar workflows — and why the math is getting harder to ignore.

Picture a superintendent on a commercial job, 10 weeks from substantial completion. They’re not behind on approvals or missing a deadline. They’re looking for a drawing.

Not a drawing that doesn’t exist. A drawing that does exist, somewhere, in one of four shared drives their team has accumulated across three years of project turnover. They find it 40 minutes later. It’s version 7, and they needed version 9.

Nobody budgeted for that 40 minutes. Nobody budgeted for the calls that followed, or the rework that came after. That’s the thing about document management failures: they don’t present as failures. They look like Tuesday.

The construction industry has built an entire operating culture around workflows that feel good enough — until you calculate what good enough is costing you. Bluebeam works with more than 4 million construction professionals worldwide, and this pattern shows up everywhere: in the data, on the jobsite, and in the stories crews tell about the moment they finally changed how their teams work.

Those patterns are confirmed by Bluebeam’s own research. The AEC Technology Outlook 2026, a global survey of more than 1,000 construction professionals published in October 2025, found that only 11% of AEC firms are fully digital across all project phases. The other 89% are still relying on paper, spreadsheets and legacy tools — especially in the field and during closeout, where document integrity matters most.

This piece makes the case for why that gap matters — in dollars.

Bluebeam’s Document Management for Construction 2026 Guide goes deep on what a modern document workflow looks like. What follows is the business case for why it matters.

The Gap Between ‘Digital’ and Actually Digital

Every firm in construction will tell you they’ve gone digital. In a narrow sense, most of them have. PDFs replaced paper; email replaced fax; shared drives replaced filing cabinets. That counts.

Still, digital tools and digital workflows are not the same thing. Nearly half of AEC professionals still rely on paper during design or handover, according to the AEC Technology Outlook 2026. Nearly 40% report challenges managing collaboration across the full project lifecycle, especially when crews are siloed between design, construction and operations. Meanwhile, 23% cite integration complexity as their top barrier to adoption — higher than cost, higher than time, higher than lack of leadership buy-in.

That partial digitization is exactly where the cost hides. The filing cabinet is gone, but the chaos it represented hasn’t been. It’s been distributed across inboxes, cloud folders, and markup files with names like “final_FINAL_v3_revised.pdf.” Field teams are hunting for information across systems that don’t talk to each other, and that hunt shows up on the job as wasted time, cost overruns and risk.

The tools are there. The connection between them often isn’t.

What 14 Hours a Week Costs

The most detailed look at where construction crews spend their time comes from the FMI and PlanGrid “Construction Disconnected” study, a 2018 survey of nearly 600 construction leaders. The finding that should stop any PM cold: construction professionals spend 35% of their time — more than 14 hours a week — on what the study called “non-optimal” activities. Hunting for project data; resolving conflicts; dealing with rework. In other words, not building or managing. Looking.

The breakdown is worth sitting with. Of those 14-plus hours, 5.5 go to chasing down project information. Another 4.7 go to conflict resolution. The remaining 3.9 go to mistakes and rework. Across the US construction workforce, that wasted time carries an estimated annual labor cost of $177.5 billion.

That figure is specific, to be sure, to 2018 dollars and one methodology. Yet the directional argument holds regardless: when your most experienced people are spending a third of their week chasing information rather than making decisions, you’re paying a tax on every hour you’ve hired them. That tax doesn’t show up on any job cost report.

Rework, RFIs and the Paper Trail Nobody Wanted

The time loss is real. Yet it’s the downstream consequences that turn an efficiency problem into a business problem.

Start with rework. The Construction Industry Institute’s field rework research, drawn from a database of 144 industrial projects, established the benchmark the industry still cites: direct rework costs run about 5% of total construction cost. That figure understates the actual hit because rework is systematically underreported — roughly a third of the project teams CII surveyed believed their recorded rework captured only 50% to 75% of what occurred.

What’s more, the 2018 FMI and PlanGrid study put a dollar figure on it: $65 billion of US construction spending goes to rework annually, and $31.3 billion of that — 48% — traces back to poor communication and bad project data. Not bad workmanship. Bad information.

The broader picture is starker. A 2021 Autodesk and FMI study estimated that inaccurate, incomplete or inaccessible project data cost the global construction industry $1.85 trillion in 2020, driving $88.69 billion in rework alone. Thirty percent of respondents said more than half of their project data was “bad” in some way — inaccurate, outdated, inaccessible or entered twice.

Then there are RFIs. A Navigant Construction Forum analysis of roughly 1.1 million RFIs across 1,362 projects found that the average project in the sample generated 796 RFIs, each costing an estimated $1,080 to review and respond to. That works out to about $860,000 per project in RFI processing alone.

The median response time in the analysis, meanwhile, was 9.7 days. And roughly 22% of RFIs never got a response at all — a rate Navigant called a leading indicator of deeper trouble, from an overwhelmed response system to no real controls over how RFIs get processed in the first place.

Change orders add another layer. An AIA analysis of nearly 900,000 change orders across more than 18,000 completed US building projects found that change orders average 4% to 5% of contract value, with the top of the typical range running about 15%.

More useful than the average, though, is the timing: most change orders land in the back half of a project, and AIA found that the later one arrives, the fewer options an owner has and the more it tends to cost.

This is another way of saying the expensive changes are the ones nobody saw coming — because the information that would have surfaced them was sitting somewhere no one could reach.

None of these, to be clear, are acts of God. They’re what happens when crews on the same job are working from different versions of the same information.

The Productivity Gap That Makes It Worse

The document management problem doesn’t exist in isolation, either. It sits inside a broader productivity problem that construction has been living with for decades.

McKinsey Global Institute’s 2017 analysis found that global construction labor productivity had grown only 1% per year over two decades, compared to 2.8% for the total world economy and 3.6% for manufacturing. In the US, construction labor productivity is lower today than it was in 1968.

A 2023 McKinsey update found that construction productivity improved only 10% between 2000 and 2022 — while the broader economy improved 50% and manufacturing improved 90% over the same period.

That stagnation has many causes, and document management is one of them. When nearly a third of a crew’s week goes to finding and reconciling information, no technology investment fully compensates for it. The workflow has to change.

Bluebeam’s Document Management for Construction 2026 Guide lays out what that change looks like in practice — from version control protocols to real-time collaboration workflows to closeout documentation that doesn’t require a four-month archaeological dig.

Why the Math Is More Urgent Now

The inefficiency was always there. What’s changed is the margin available to absorb it.

GC net margins sit around 5%-6% in a good year, and about one in six contractors say they’ve absorbed recent cost increases themselves rather than pass them through — a strategy that works until it doesn’t.

Meanwhile, construction wages rose 4.2% year over year as of August 2025, and Associated Builders and Contractors estimated the industry needed to attract 439,000 workers in 2025 alone — a number it raised to 499,000 for 2026.

Effective tariff rates, moreover, on construction goods hit a 40-year high of 25% to 30% in 2025, according to Deloitte’s 2026 Engineering and Construction Industry Outlook. AGC’s producer price data shows what that did downstream: aluminum mill shapes up 30.5% across 2025 and steel mill products up 17%, the steepest increases since 2022. Total US construction spending, meanwhile, was down almost 3% year over year by July.

When every cost input is moving the wrong way at once, self-inflicted costs start to matter in ways they didn’t when margins were thicker. Rework that was a nuisance at 12% margin can be existential at 5%. RFI delays that were an annoyance on a fully staffed project become critical path issues when you’re already shorthanded.

There’s a workforce dimension, too.

The AEC Technology Outlook 2026 found that 44% of firms say advanced technology plays a key role in attracting and retaining workers, alongside culture and pay. In an industry already facing a serious labor shortage, document chaos isn’t just an efficiency problem; it’s a recruiting problem. Younger workers notice when they’re handed outdated systems on day one.

The firms absorbing these costs without fixing the underlying workflow aren’t just losing money on individual jobs. They’re building structural disadvantages into how they operate.

What Good Looks Like

The answer isn’t another tool, but a different way of working. The firms that have made the change are producing results that show up on the bottom line.

Consider DPR Construction’s experience on the Alta Bates Summit Medical Center project in Oakland. Facing a 31-day schedule delay and an accelerated rebar fabrication timeline, DPR turned to Bluebeam Studio Sessions to run simultaneous, real-time collaborative reviews with the engineer of record and rebar detailer.

By reviewing and resolving shop drawing issues in a live session rather than passing PDFs back and forth, the team cut the submittal review cycle by more than 33% — compressing a 25-to-30-workday process into a 10-to-12-day window. That’s up to 10 days of schedule recovery per review cycle, on a project where every day had a dollar figure attached to it.

The results at Balfour Beatty’s DFW Airport renovation tell a similar story: $5 million in project savings attributed to centralizing documents and giving field teams real-time access to the information they needed, when they needed it. The savings didn’t come from a technology initiative; they came from fixing how information moved through the project.

Those aren’t outliers. They’re what Bluebeam sees when firms close the gap between having digital tools and ultimately running digital workflows. Among the 27% of construction firms currently using AI tools, 68% report saving at least $50,000 on recent projects, and 46% have saved 500-1,000 hours by applying AI to scheduling, planning and document analysis, according to the AEC Technology Outlook 2026.

What the firms getting these results have in common isn’t a particular software stack. It’s a single source of truth for project documents, accessible to every stakeholder in real time. It’s markups that are tracked, versioned and auditable — not living in email attachments. It’s RFI and submittal workflows that move in hours, not days. It’s a closeout process that doesn’t require assembling a package from five different places at the end of a job.

Bluebeam is built specifically for this kind of work — document-based collaboration that spans disciplines, formats and project phases without requiring firms to overhaul their entire tech stack. Bluebeam Max brings together markup, collaboration and project management in a single platform built for AEC workflows from design through closeout. Bluebeam’s customer stories offer a closer look at what these workflows produce in practice across firms of every size and type.

The Question Worth Asking

There’s no line item on a job cost report for “time spent looking for the right drawing.” There’s no budget category for “rework caused by working off the wrong version.” These costs are real, recurring and largely invisible — which is exactly why most firms haven’t done the math.

The math, when you do it, is uncomfortable. Hundreds of thousands of dollars per project in RFI management alone. Five percent of project value in rework, half of it caused by bad data. More than 14 hours a week per worker spent on things that aren’t building anything. Across a firm’s project portfolio, those numbers stop looking like friction and start looking like a structural problem.

The firms winning in this market — on thinner margins, with tighter crews — haven’t found ways to absorb those costs. They’ve found ways to stop incurring them.

If your team is working harder than the project warrants, the answer might be in how your documents are — or aren’t — moving. Bluebeam’s Document Management for Construction 2026 Guide is a good place to start that conversation.

See what a clean document workflow does on a live job.

Start Free Trial

Construction Isn’t Slow. It’s Out of Room.

Project Management & Efficiency, Technology & Innovation
Frank Kalman

The most-repeated line about the construction industry is that it resists change. The people doing the work are telling a different story, if anyone will listen.

The foreman gets promoted on a Friday.

On Monday, someone from the office hands him a laptop. There’s software on it he’s heard of but never opened. A project manager mentions, in passing, that the drawings for the next data center job are already loaded. Somebody (he’s not sure who) will show him how to use it. Eventually. Right now everyone’s running two jobs behind schedule and there’s a design change that just came through on a fourth-floor mechanical room.

He nods, takes the laptop home, and by Wednesday he’s watching YouTube tutorials at 10 p.m., trying to figure out how a takeoff works before the shop starts fabricating on Monday.

This isn’t a story about a contractor who won’t adopt technology.

It’s a story about an industry that keeps insisting the problem is willingness while the people doing the work are just trying to find enough oxygen to breathe.

The most-repeated line in the industry

Every conference opens with it. Every consulting deck features it. Every LinkedIn think piece leans on it.

Construction is slow to adopt technology.

The line has data behind it. McKinsey’s 2024 update to its landmark construction productivity research found that global construction productivity grew just 0.4% annually from 2000 to 2022, compared to 2 percent for the total economy and 3% for manufacturing. Construction firms historically spent less than 1 percent of revenues on IT, less than a third of what automotive and aerospace spent. The gap is real. It isn’t going away on its own.

How the gap gets explained is where the industry has gotten lazy. Contractors are traditional. Culturally resistant. Slow to change. Get them to see the light and adoption will follow. Buy the software. Attend the demo. Read the case study.

That story doesn’t survive contact with what contractors say the moment nobody hands them a multiple-choice answer.

Read what they wrote

In January, 303 MEP contractors sat in a conference room in Austin and answered questions in real time on their phones. Alongside the multiple-choice items were open-ended prompts, space for contractors to say in their own words what was really breaking their business. Their answers became the MEP Innovation Report 2026.

Across 532 open-ended responses, zero contractors said the industry should slow down on technology. Not one argued the old way was better. Not one pushed back against innovation on principle.

What they wrote instead sounded like this:

“Rate of change. Too fast for users to adopt effectively.”
“Adoption is a pain point.”
“Success implementing Stratus in the shop. Obstacle: implementation in the field.”
“Acceleration in schedules while design is lagging behind.”

These aren’t the words of an industry that wants the world to stand still. They’re the words of an industry, rather, sprinting and being asked to sprint faster, with fewer experienced people, against tighter deadlines, on drawings that aren’t done yet.

Nobody in these responses is asking for less technology. They’re asking for enough air to use the technology they already bought.

This isn’t just a construction problem

BCG’s research on AI adoption offers what might be the cleanest formulation. Seventy percent of the value in any digital initiative comes from people and process. Twenty percent comes from technology and data. Ten percent comes from the algorithm itself, the thing everyone spends most of their time talking about. Seventy-four percent of the companies BCG surveyed had yet to show tangible value from their use of AI. The technology worked fine.

The most vivid proof came from an operating room. In 2009, a study in the New England Journal of Medicine introduced a 19-item surgical safety checklist into eight hospitals around the world. Major complications fell from 11% to 7%. Inpatient deaths fell from 1.5% to 0.8%, a drop of more than 40%. No new technology. No new equipment. Just a documented process that everyone in the room followed.

Construction hasn’t figured this out yet. MEP contracting is where the gap shows up the sharpest.

The number that should change the MEP conversation

Back to the 303 contractors in Austin.

Fifty-one percent said their documented business processes were not sufficient. Only 5% said they were fully documented.

Hold onto that 5% for a second.

Nineteen out of every 20 MEP contractors in the room, firms with full order books, sophisticated tools, leadership teams thinking seriously about VDC, BIM and AI, don’t have the documented workflows that would let a new hire, a new crew or a new tool plug into how the company ultimately works.

Before anyone dismisses this as a small-shop problem, look at the cross-tab. Among the smallest firms surveyed, those with fewer than 20 employees, 60% reported inadequate process documentation. Among the largest, firms with more than 1,000 employees, 46% said the same. A 15-person shop and a 1,500-person shop, dealing with the same problem. That shows up whether you’re doing takeoffs on a strip mall or a hyperscale data center.

Why the resistance story keeps getting told

Because it’s easy.

If contractors are the problem, the solution is more pitching; more demos; better case studies; and sharper ROI calculators. That playbook has been running for a decade. It hasn’t worked because it was solving the wrong problem.

There’s a name for what’s really happening. Change management research firm Prosci calls it “change saturation,” the point at which the volume of change an organization is being asked to absorb exceeds its capacity to absorb any of it. More than 73% of respondents in Prosci’s most recent research said their organizations were near, at or beyond that point.

A 2023 Harvard Business Review article put numbers on the collapse. Employee willingness to support enterprise change fell from 74% in 2016 to 43% in 2022. The average employee faced 10 planned enterprise changes in 2022. In 2016, it was two.

Contractors aren’t different from workers in any other industry. They’re just further along the same curve, dealing with all the same fatigue, plus a labor shortage, plus incomplete designs, plus schedules that were locked in before they walked in the door.

You can’t persuade your way past a calendar that’s already full. A great pitch to a contractor with no bandwidth to absorb it isn’t a missed sale. It’s a missed signal.

MEP is at the epicenter

Labor is thinning out. Designs land half-finished. Field teams adapt to information that isn’t ready, then absorb the rework when it changes. Supervisors stop planning because they’re too busy correcting. Every marked-up drawing that must be re-issued in the field, every clash resolved in real time, every RFI that sits open for another week — that’s a contractor spending capacity they don’t have on friction that shouldn’t exist.

The pressure is worse because the demand is enormous. Dodge Construction Network reported that commercial construction planning was up 37.2% year-over-year in April. Strip data centers out and the number drops to 5.8%. Meanwhile, AGC of America’s 2026 outlook found that 82% of firms are struggling to fill hourly craft positions, a higher share than at any point in the past three years.

Enormous demand. Compressed schedules. No bench to draw from. That’s the capacity trap.

What building capacity looks like

This is where the story turns.

In Santa Clara County, California, the largest electrical apprenticeship program in Northern California is doing something transformative. The Electrical Training Alliance of Silicon Valley (ETASV), jointly managed by IBEW Local 332 and the NECA Santa Clara Valley chapter, trains an average of 600 students and has built two Bluebeam courses into its curriculum. One assumes zero prior software knowledge. The other hands students a working tool set built over years of real jobsite use and teaches them to design real projects with it.

Chris Paup, who built the fundamentals course and now serves as a business representative for IBEW Local 332, wrote most of it while deployed overseas with the California Air National Guard. Free hours between duty shifts, testing early lessons on the service members around him. When he got back and put 20 students in front of the material, he says the first thing he learned was how much he’d have to change.

The result: union electricians who show up on data center jobsites already digitally fluent. Not learning on the fly. Not being handed a laptop at 10 p.m. on a Wednesday. Ready.

“That’s when you see them showing up 45 minutes early, an hour early,” Paup says, describing the moment students stop learning the software and start bending it to their own problems. “Because they’ve been thinking all day about how they can do this and they can’t wait to get to the classroom to try it.”

The full story of what ETASV is doing is coming to BUILT soon. It’s worth reading in full, not just as an example of the capacity building this report keeps pointing to, but because it suggests where the industry’s answers might ultimately come from: the training centers, union halls and apprenticeship programs doing the work while everyone else argues about resistance.

The real work ahead

One more thing worth noting. The MEP Innovation Report found that only 17% of contractors describe AI as active in any workflow beyond pilots. The most common description of the industry’s relationship with AI, chosen by 20% of respondents, was “it’s complicated.” That’s not skepticism, just honesty. But the tools don’t care. AI-powered design review, automated markup, drawing comparison, natural-language workflow prompts are already shipping. Every one of the pressures above is now on a shorter clock than it was last year.

The MEP industry that shows up in this data isn’t stuck in the past. It’s ambitious, capable and increasingly well-equipped. What it doesn’t have is room — room to plan, to train, to implement the tools that could make the next 24 months easier instead of harder.

The firms that move fastest over the next two years won’t be the ones that buy the most software. Instead, they’ll be the ones that figure out how to create enough organizational stability, in enough parts of the business, for long enough, to let new ways of working take root.

That’s harder than buying tools. There’s no purchase order for protected planning time. There’s no vendor selling a Tuesday afternoon where nobody is firefighting. Those are the things that separate the firms that pull ahead from the firms that never quite catch up. At Bluebeam, we’re publishing this series because we think the industry is ready to have the harder conversation. The one about conditions, not tools.

The real work ahead is building the room to do it.

This is the first in a four-part BUILT series on the MEP Innovation Report 2026, produced in partnership with MCAA, NECA and SMACNA. Upcoming posts examine the growth paradox, the technology-to-process gap and what MEP contractors are saying about AI.

Your crew already has the tools. Give them the room.

Start Free Trial

The Permitting Crisis Isn’t What You Think It Is

Construction & The Economy, Project Management & Efficiency
Parth Tikiwala

The New York Times says America's infrastructure is stuck in permitting hell — and they're right. Yet they're missing half the story.

In January, a corroded section of the Potomac Interceptor sewer line burst in the Maryland suburbs of Washington, sending more than 240 million gallons of raw sewage toward the river — one of the largest such spills in U.S. history.

D.C. Water had wanted to reinforce that stretch of pipe for years, but the federal environmental review it needed dragged on well past a one-year deadline set in 2020, as a Washington Post investigation later documented. The pipe burst before the review was finished.

This spring, the New York Times Editorial Board used that story to make a case for permitting reform. The editors called for centralized oversight of transmission lines, binding timelines for environmental reviews and a congressional deal that speeds up infrastructure approvals without gutting environmental protections.

All good ideas. All politically hard.

All likely to take years.

Still, here’s what the Times missed: even if Congress passed permitting reform tomorrow, most public agencies would still be drowning.

Because the bottleneck is an operational problem that extends beyond what any regulation can accomplish.

I spent four years at the Office of Management and Budget watching federal agencies struggle with permitting timelines. Before that, I spent six years as an economist at the Bureau of Labor Statistics, building the data systems that agencies rely on to track what’s happening. I know what operational data looks like when it’s working and what it looks like when it isn’t.

At OMB, the delay was rarely the environmental analysis. Instead, it was version confusion, siloed reviews and comment reconciliation that nobody had ever properly resourced. That’s operational debt, and it accumulates quietly for years until a sewage line bursts. The good news is it doesn’t require an act of Congress to fix, just someone with the authority to look at the workflow honestly and decide that the status quo is no longer acceptable.

Federal environmental impact statements take an average of 3.8 years from start to finish. The Council on Environmental Quality’s own data shows that the gap between completing a final environmental review and issuing a decision averages 5.3 months — more than five times the 30-day regulatory minimum.

CEQ attributes that gap to “factors other than regulatory requirements.” In other words: administrative drag, not the environmental analysis itself.

We at Bluebeam work with hundreds of public agencies, and we’ve seen what happens when they stop doing the stupidest parts of their job. The results aren’t incremental.

Detroit went from issuing 3,000 permits a year to 7,500 — a 150% jump. Pleasanton, Calif., quadrupled per-reviewer capacity. Chicago’s Department of Transportation saved $24 million in 2022 by fixing utility coordination workflow.

What permitting looks like

Start in Las Vegas, 2018. The city handles more than 15,000 plan reviews a year. Before digital transformation, a customer walked in with two or three rolls of plans. A technician created a project number, manually stamped it on the plans and added a physical tag for tracking. Plans got checked into the system and stored in an “active” repository.

When a plans examiner was ready to review, they emailed the administrative staff with the plan number. The examiner physically walked to the repository. Staff retrieved the plans and logged them out. The examiner took the plans back to their desk, marked them up and returned them. Staff checked the plans back in, stored them again and waited for the next reviewer.

“Typically, we would have at least three to four different departments reviewing the plan and following this process,” Yolanda Palomo, process review coordinator for the city of Las Vegas, told Bluebeam.

That’s not 1985. That’s 2018.

Now zoom out. Seattle, same year. The city’s 430-person building department permits about $4 billion in construction annually.

Their review process didn’t use paper plans — but it wasn’t much better. Reviewers opened a submitted plan, then opened a separate text file to write corrections. Every comment went into that text file. When finished, an automated email sent the text file as an attachment. The applicant had to cross-reference the two documents to figure out what needed fixing.

It was siloed. Two digital documents that had to be manually reconciled. Version confusion was constant.

South Carolina, 2014. The state Department of Transportation launched a design-build team to accelerate infrastructure delivery. Yet their review workflow was killing that speed advantage. Reviewers submitted individual comments on separate forms sent via email. No centralized markup. No way to see what other reviewers had said.

“It was essentially like a relay race, where the baton is passed from the designer to the contractor,” Brooks Bickley, assistant program manager with the South Carolina Department of Transportation, told Bluebeam.

Where the time goes

When the Council on Environmental Quality publishes data showing environmental reviews averaging 4.5 years between 2010 and 2018, what does that time consist of?

A lot of it isn’t analysis, so much as coordination. CEQ’s own E-NEPA Report to Congress lays this out: agencies maintain “isolated, non-interoperable software systems.” Applicants submit the same data to multiple agencies. There are no common data standards; the public uses multiple platforms to track a single project.

Translation: agencies are spending months reconciling comments from different reviewers, chasing down the person who has the one marked-up copy, restarting review cycles because someone was working off version 2.3 when version 2.5 was current.

An Oregon Department of Transportation study of 12 highway projects found the strongest statistical correlation wasn’t between project complexity and timeline, but between the number of comment letters from state and federal agencies and the time to get from draft to final review.

More agencies commenting meant more time reconciling conflicting feedback, not necessarily more time analyzing environmental impacts.

A Federal Highway Administration survey of 89 long environmental reviews found the top delay drivers were lack of funding (18%), local controversy (16%), low priority (15%) and complex projects (13%).

Staffing and communication problems showed up in 42% of projects. These are workflow problems.

North Carolina saw this firsthand. Before implementing electronic plan review, the state’s multi-discipline reviews took weeks. After digitizing, North Carolina measured a 39% increase in productivity, not because they hired more staff or cut corners on compliance, but because they stopped losing time to coordination friction.

Las Vegas saw the same thing. Under the old paper system, plans could only be reviewed one discipline at a time — a week or more per discipline, across at least five departments. Printed mylars then had to be routed to five utility companies for final signatures, a process that took up to six weeks.

Then COVID hit.

The fix nobody’s talking about

March 2020. Every public agency in the country goes remote overnight. In most places, that would have been a disaster. Las Vegas, however, like the culture of the city itself, didn’t miss a beat.

“From my perspective, I don’t think we had any downtime due to COVID-19, other than the time that we waited to get laptops,” one city official told Bluebeam at the time.

Zero downtime, during a pandemic, for a department handling more than 15,000 plan reviews a year.

The city had replaced paper plans with digital files. Sequential review with concurrent review — multiple disciplines marking up the same plan at the same time. Physical repositories with cloud storage. Email attachments with real-time collaboration.

The regulatory requirements didn’t change. Las Vegas was still doing plan review, still checking compliance, still coordinating across departments. They just stopped doing it stupidly.

The results: eight-step paper process cut to four steps; $600,000 saved annually; reviews that used to take weeks now take days.

South Carolina cut design review time by 50%.

Detroit’s Buildings, Safety Engineering and Environmental Department went from issuing 3,000 permits a year to 7,500, supporting roughly $5 billion in development in 2023. Chief Building Official James Foster told Government Technology: “I can’t imagine how we would have been able to handle all of this if plan review were still on paper.”

Pleasanton’s Building Division saw per-reviewer plan checks go from 25 to 30 per month to roughly 100, nearly quadrupling capacity. Chief Building Official Robert Queirolo: “A plan check that might have taken six hours the old-fashioned way now takes a few hours.”

Chicago’s Department of Transportation implemented better utility coordination workflow and saved $24 million in 2022. They cut underground utility hits from the national average of 1.67 per 1,000 to 0.49.

Seattle ditched the separate text-file approach and moved to inline markup. In the first six months of 2022, the city approved 20% more complex construction permits than the previous six months. “The quality of communications was so high in our new system that we’re doing more volume — we are getting to ‘approved’ faster,” one city official told Bluebeam at the time.

What this means for infrastructure

The TransWest Express transmission line took 18 years to win final approval — not because anybody opposed clean energy, but because coordinating across jurisdictions, agencies and landowners is a nightmare.

That’s the same workflow problem Las Vegas had. The same coordination friction South Carolina faced. The same version confusion Seattle dealt with.

Policy reform matters. The SPEED Act, which passed the House in December 2025 and now sits before the Senate Environment and Public Works Committee, would streamline NEPA timelines and limit litigation windows. That would help.

But if your review process is still running on email attachments and paper round-trips, all the policy reform in the world won’t save you. You’ll just be doing bad workflow faster.

The emergency repair on the Potomac line is done and the water has cleared, but the cleanup has already run past its $20 million estimate — and the permanent fix still has to clear another round of environmental review, the same process that was too slow the first time.

Maybe Congress passes the SPEED Act. Maybe lawmakers broker a bipartisan deal. Maybe they don’t.

Yet while we wait, there are cities approving permits twice as fast because they stopped mailing PDFs and started marking them up in real time.

There are state departments of transportation cutting review cycles in half because reviewers can finally see each other’s comments.

There are public agencies that didn’t lose a single day during COVID because their workflow wasn’t dependent on paper.

It’s not sexy, and it won’t make the editorial page of the New York Times. But it’s the kind of infrastructure fix that doesn’t require a bill — just a willingness to look at how you’re really spending your time and admit that some of it is waste.

The permitting crisis is real. The Times is right about that.

But the fix isn’t just in Washington. Some of it is sitting in your own workflow, waiting for someone to finally admit it’s broken.

Parth Tikiwala is head of government affairs at Bluebeam and head of global public sector for the Nemetschek Group. He previously served as acting director of technology modernization and data at the U.S. Office of Management and Budget, Executive Office of the President.

Your agency’s biggest delay might be fixable right now.

Start Your Trial

Your Estimate Is Only as Honest as Your Takeoff: Seven Steps to a Number You Can Defend

Project Management & Efficiency, Technology & Innovation
Frank Kalman

Fast and defensible aren’t opposites. The takeoff is where you prove it — seven steps to a number that holds up when someone’s trying to tear it apart.

Every estimator has a number that still bothers them. The job you won, then watched bleed. The miss didn’t show up in the takeoff, where it would’ve been cheap to fix. It showed up in the field, three weeks in, when the slab pour came up short and somebody had to make a phone call nobody wanted to make.

That’s the whole game. A takeoff isn’t busywork you grind through before the real estimating starts. It is the estimate’s foundation. Your estimate is only as honest as the takeoff under it, and no amount of good pricing fixes a shaky one. The estimators who don’t get burned aren’t faster because they’re geniuses. They’re faster because they run the same play every time.

A digital takeoff measures and counts quantities straight off the PDF — areas, lengths, volumes, counts — instead of dragging a scale ruler across paper and praying your highlighter didn’t skip a room. Done right, it spits out two things at once: a picture of what you measured and a clean set of numbers the estimate stands on. What follows is the seven-step version of that play. It’s the hands-on layer under the full estimation process, and the working companion to the complete guide to construction takeoffs.

What does a digital takeoff workflow look like?

A takeoff workflow is less a software feature list than a discipline. What separates the estimators who get burned from the ones who don’t isn’t talent or speed; it’s whether the process is repeatable enough that the resulting number means the same thing no matter who on the team produced it.

The tools change. The order doesn’t. Counting devices on an electrical plan or pulling concrete volumes off a foundation drawing — same seven steps move you from a raw set to numbers you’d put your name on.

Step 1: Review the drawings and scope

Before you measure a single thing, read the set. Drawings, specs, addenda, general conditions. All of it. And not the way you read a text at a stoplight. You’re building a mental model of how this thing goes together, and the quality of that model is a ceiling on everything downstream.

The veterans read for what’s missing. The structural section that fights the architectural plan. The finish schedule pointing at a spec that doesn’t exist. The retention pond on the site plan that the civil drawings forgot to grade. Measure a set you don’t really understand and all you’ve done is put precise numbers on the wrong thing — which is exactly how takeoffs go wrong before a single quantity gets recorded.

AI is starting to earn its spot here. Smart Review in Bluebeam Max scans a set for design issues, scope gaps and discrepancies, then hands them back as trackable issues. It won’t tell you what a gap means — that’s still your call, and it always will be — but it cuts the hours you’d otherwise spend hunting for the contradiction that wrecks the bid.

Step 2: Calibrate the drawing scale

A digital measurement is only as honest as the scale behind it. Set a known dimension — a dimension line, a door width, a column grid — so the software turns pixels into real feet and inches.

Calibrate every sheet. Not the first one and a prayer for the rest. Scales drift between disciplines and even between sheets in the same package, and a plan that says “to scale” in the title block is not under oath about it. Verify against a dimension you trust. Skip this and every length, area and volume after it inherits the lie.

Step 3: Configure tools and layers

Set up before you measure, not while you measure. Load the tool sets for the trade, decide how quantities get organized — by system, floor, phase, cost code — and color-code so the drawing stays readable once it fills up with markups.

This is where standardization saves a firm. Custom tool sets let a whole team capture the same scope the same way, so a bid doesn’t hinge on who happened to run it that week. Splitting scopes onto separate layers keeps electrical off plumbing and demo off new work — which makes the takeoff easier to check and a lot easier to fix when the drawings change. And they will change.

Musselman & Hall streamlined its takeoffs alongside project management — and that pairing is the tell. When the takeoff is set up the same way every time, it doesn’t just spit out cleaner numbers, it plugs into everything else the team is running. Consistency at the setup stage is what makes the takeoff portable.

Step 4: Measure the quantities

Now the real work. Right measurement type for each item: length for conduit and wall runs, area for flooring and drywall, volume for concrete, count for fixtures and devices. Every measurement lands twice — as a markup on the drawing and a value in a data table — at the same time.

This is also where the machines pull their weight. AI symbol detection — VisualSearch in Revu — scans a sheet and finds every instance of a fixture or device in seconds, turning an afternoon of counting into a few minutes of review. Quantity Link pushes measurements straight into a spreadsheet so totals move in real time as you work. Your job stops being the human tally counter and becomes the person who decides what to capture and confirms what came back.

The AI layer goes further in Bluebeam Max. Magic Markups duplicate, offset and convert markups with CAD-level precision, so you’re not redrawing the same detail 40 times. Stitching pulls sheets from different parts of a project into one continuous view, which keeps a scope that spans pages from getting missed or double-counted. And because Max wires Revu to Anthropic’s Claude, you can talk to the drawings — search the set, update markups, pull markup data into something useful — instead of digging for it by hand.

This isn’t a theoretical gain. Quantity surveyor Angus Cockburn runs takeoffs 70% faster in Revu — and the speed doesn’t come from skipping the check. It comes from not doing by hand what the software can do in seconds. Fast and defensible aren’t opposites. They live in the same workflow, which is exactly why the next step matters.

Step 5: Visually verify coverage

Because every measurement is also a markup sitting on the drawing, you can see what got counted and — the part that matters — what didn’t.

Turn the markups on and pan the set. The empty room that should’ve been measured lights up by being blank. The wing nobody touched. The two markups stacked on the same fixture. A number that lives only in a table can’t be caught this way. A number tied to the drawing can. This eyeball pass is the fastest way there is to catch the missed scope and the double-count before they catch you.

Step 6: Validate the quantities

Coverage confirmed, now pressure-test the numbers. Cross-check against the specs, not just the drawings — the two don’t always agree, and the spec usually wins. Sanity-check unit totals against jobs that looked like this one: square feet per floor, devices per room, cubic yards per footing. Anything that smells off gets chased down before it goes anywhere near a price.

Make it reviewable while you’re in there. A second estimator should be able to open the file, see how every quantity got measured and trace it back to the markup. Fresh eyes catch what familiarity walks right past, and a takeoff nobody can review is a takeoff nobody should trust.

Validation gets ugly when drawings get revised mid-bid, which is to say always. Smart Overlay in Bluebeam Max flags design changes across disciplines and drawing scales, then reports them as trackable comparisons — so a revised sheet doesn’t leave a dead quantity sitting in your estimate. That’s the difference between re-measuring everything and re-measuring only what moved, which is also why most takeoffs fall apart when the drawings change.

Step 7: Export the data for estimating

The takeoff isn’t done until the numbers reach the estimate. Export to your estimating platform, push to Excel or feed assemblies that turn one measurement into a full materials-and-labor line. A live link like Quantity Link keeps the estimate in step as quantities shift, so a revision updates the math instead of forcing you to re-key it.

The takeoff isn’t the finish line — it’s the first link in a chain. CCI Mechanical runs Revu bid to closeout, which is the whole point: the numbers you capture here don’t just feed the bid; they feed everything that comes after it. A takeoff that exports clean is a takeoff that keeps paying off long after the job is won.

Manual re-entry is where good takeoffs go to die. Every hand-typed transfer is a fresh chance to drop a digit or flip a total, and you won’t see the error until the field hands it back to you. Move the data straight from takeoff to estimate and you close that gap — and you start building the feedback loop that makes the next bid sharper than this one.

AI accelerates the takeoff, but the estimator still drives

Automation hasn’t shrunk the estimator’s role so much as relocated it. The hours reclaimed from counting and redrawing don’t leave the job; they shift toward the parts no model can own: reading design intent, deciding what counts as scope and standing behind a number once it leaves the building.

Almost every step up there has a machine assist now, and the gains are real, not brochure-real. Counting that ate an afternoon takes minutes. Scope gaps surface early instead of in the field. Repetitive markups stop getting hand-drawn. Revisions get caught instead of slipping through.

Inside Bluebeam it shows up in two layers. Revu’s VisualSearch automates the symbol counting while you measure. Bluebeam Max, the premium AI plan, adds the connective tissue around the takeoff: Smart Review for early scope-gap detection, Stitching for one continuous view across sheets, Magic Markups to skip the redraw, Smart Overlay to track changes between versions, and a straight line to Anthropic’s Claude so you can ask the drawings questions instead of excavating them.

What none of it does is decide. AI counts, flags and compares. You read the set, set the scope, confirm the counts and stand behind the number when it goes out the door. That’s the through-line in how the sharp teams use these tools — a faster way to do the work, not a stand-in for the judgment the work demands. The estimator who can read a drawing and knows the difference between a number that looks right and one that is right is still the most important variable on the job.

What makes a construction takeoff defensible?

Defensible doesn’t mean cautious. It means the number arrives with its own evidence — anyone can open the file and trace each quantity back to the mark that produced it. That built-in auditability is what turns an estimate from a private judgment call into something a firm can stand behind under questioning.

A takeoff isn’t a pile of numbers so much as it’s a financial commitment your firm has to live with, and the workflow is what makes that commitment something you can defend out loud in a bid review.

Run the same sequence every time — review, calibrate, configure, measure, verify, validate, export — and three things follow. It’s repeatable, so it doesn’t depend on who ran it. It’s reviewable, so a second set of eyes can back it up. And it survives a revision instead of getting blown up by one. That’s the line between a number you hope is right and a number you can point to.

Then there’s the part the word “defensible” undersells. A takeoff you can defend isn’t just protection — it’s leverage. ClearTech won 50% more jobs by making estimation more efficient. That’s not staying out of trouble, but a competitive weapon. The number you can stand behind is also the number you can move fast on, bid confidently on and win with.

The estimators who win work at margins they can deliver aren’t cutting steps to go faster. The steps are just second nature. Build the habit, and the speed is the byproduct.

Want to run the play on your own drawings? Start a free 14-day trial, dig into Bluebeam’s takeoff and estimation tools or see what the AI adds with Bluebeam Max.

Frequently asked questions

What is a digital takeoff in construction?

A digital takeoff is the process of measuring and counting quantities — lengths, areas, volumes and counts — directly off PDF drawings on screen. Each measurement is recorded as both a visual markup on the drawing and a value in a data table, which is what makes the quantities reviewable and auditable.

How is a digital takeoff different from a manual takeoff?

A manual takeoff uses printed sheets, a scale ruler and a highlighter, with quantities tallied by hand. A digital takeoff measures on screen, ties every quantity to a visible markup, automates the repetitive counts and exports totals straight to the estimate — faster, more accurate and far easier to revise.

	Manual takeoff	Digital takeoff
Medium	Printed sheets, scale ruler, highlighter	On-screen measurement straight off PDF drawings
Counting	Tallied by hand	Automated symbol detection, confirmed by the estimator
Audit trail	A number sitting in a column	Every quantity tied to a visible markup on the drawing
Revisions	Re-measure by hand when sheets change	Re-measure only what moved; a live link updates totals
Hand-off to estimate	Manual re-entry, with the re-key risk that brings	Direct export or live link into the estimating platform

What is the first step in a digital takeoff?

Reviewing the drawings and scope. Before any measuring, the estimator reads the full set — drawings, specs and addenda — to understand what’s in, what’s out and where the risk sits. Calibrating the drawing scale comes next.

Can AI do construction takeoffs?

AI handles the most repetitive part — symbol detection and counting — by scanning a set and finding every instance of a fixture or device in seconds. It doesn’t replace the estimator, who still defines what to capture, verifies coverage and validates the totals. Tools like Bluebeam’s VisualSearch are built on this review-and-confirm model.

Does Bluebeam Max help with construction takeoffs?

Yes, indirectly. Bluebeam Max is the premium AI plan layered on Revu, and several features speed the work around a takeoff: Smart Review flags scope gaps and discrepancies, Stitching combines sheets into one continuous view, Magic Markups duplicate and offset markups without redrawing, and Smart Overlay tracks design changes between revisions. The quantity measurement itself still runs through Revu’s takeoff tools, with the estimator confirming what gets counted.

What software do estimators use for digital takeoffs?

Estimators commonly run a takeoff-first tool such as Bluebeam to measure quantities off PDFs, often paired with a dedicated cost-estimating platform for pricing. For a full breakdown of platform types and how to choose, see Construction Estimating Software: The Complete Guide.

Run the same play on your own drawings.

Start Free Trial

The Architect Who Never Left the Table

Project Management & Efficiency, Technology & Innovation
Frank Kalman

Jean-Pierre Trou spent 20 years designing buildings in Austin. Then he built the AI that reviews them, without ever putting down his red pen.

On a late night sometime around 2018 or 2019, Jean-Pierre Trou sat at his dining room table in Austin with 250 pages of construction drawings spread in front of him. A 90,000-square-foot Class A office building, three stories, represented across dozens of sheets: architectural plans, structural details, MEP routes.

Red pen in hand, he was checking for the kinds of errors that cost hundreds of thousands of dollars if they’re not caught before construction starts: an uncoordinated curtain wall detail, missing vertical penetrations over structural elements, a conflicting mechanical route; the kind of mistakes that compound through every floor.

“This is me on the dining room table, redlining drawings,” Trou said in a 2024 podcast, describing his nightly quality-control routine. The review took him a full week. This, he was careful to point out, wasn’t just his problem.

“It’s the whole industry.”

In 2026, this is still what quality control largely looks like in architecture. It’s still manual and tedious. It’s still expensive. And it’s still happening at dining room tables across the country.

Most architects would stop at complaining. Trou built software to fix it. Yet the twist in his story, the thing that makes it different from the usual founder-exit narrative, is that for a time, he never actually left that table.

Trou at an industry trade show with a member of the mbue team. The company’s AI-Powered Overlays and Submittals platform was built to help commercial electrical contractors reduce risk and avoid costly construction mistakes.

For 20 years, he ran Runa Workshop, an award-winning architecture firm. For the past four, he also built mbue, an AI startup that uses computer vision to review drawings and generate trade submittals. He did both simultaneously. Not architect-turned-founder. Just architect who happened to build the AI.

In May of this year, mbue joined Bluebeam. The dining room table problem — missed changes, wasted time, billions in preventable construction errors — is about to scale to millions of users. To understand why that matters, though, you have to understand why Trou kept practicing while he built the software. Because the credibility is the point.

Still Practicing

Runa Workshop, which Trou founded in 2009 with Aaron Vollmer, isn’t a boutique firm that sketches concepts and hands them off. Instead, it builds real, award-winning projects, from some of Austin’s most recognizable office buildings, including WeWork at 801 Barton Springs, Waterloo Central downtown, and the recently completed Victory Plaza in Central Austin, to Caffé Medici on South Lamar, the Austin Visitor Center, ViaSat’s Austin office, and YMCAs across the city.

Sixteen years of built work, and the firm is still operating.

The name comes from Quechua: “runa:” means “people,” and “workshop” signals exchange. Trou is Peruvian American, born in Lima, trained at Universidad Peruana de Ciencias Aplicadas before earning a master’s in architecture from the University of Texas at Austin. He’s been in Texas for two decades.

Trou is also a founding partner at Vaast, a real estate development company, which means he doesn’t just design buildings; he owns them, finances them, lives with the consequences when construction errors show up on the balance sheet. He’s licensed: NCARB, TBAE, AIA, ASID. He taught at UT Austin’s School of Architecture from 2019 to 2021. All of this while founding and scaling mbue.

Trou’s wife, who’s a director of marketing at an AI company and a former public relations lead at Edelman and Ketchum, says he overcommits. In the 2024 podcast, Trou joked about the problem: “I need an AI to tell me, ‘Jean-Pierre, you’re overcommitted.'”

*Trou at the OA A-List Awards at SXSW 2025 in Austin, Texas, where mbue was recognized among standout startups in the city’s technology ecosystem.*

Yet the overcommitment was structural, not accidental. For years, Trou worked both jobs in parallel. “I did work on both Runa and mbue in the very beginning,” he said in a recent conversation, “but I quickly realized that leading mbue was more than a full-time job and needed my complete attention.” He executed a transition plan over more than six months. By the time mbue scaled, he was fully focused on it as founder and CEO.

But the practitioner instinct, the architect’s eye, never left. “I am an architect, and I always will be,” Trou said. “I am just not working on projects in the traditional sense anymore.”

The $100 Billion Problem

The U.S. construction industry wastes more than $100 billion annually on errors, changes and omissions, according to industry estimates that Trou has cited in press releases and investor pitches. It’s not an abstract figure for him, as he’s watched it happen on his own projects.

“As a founding principal of an architecture firm in Austin, I found myself spending countless late nights reviewing thousands of drawings,” Trou said when mbue announced its pre-seed funding. “It’s astonishing that in 2024, we’re still relying on PDF tools to manually redline drawings.”

Take that 90,000-square-foot office building: three stories, 250 pages. A full week of work. Checking architectural plans against structural and MEP coordination, verifying code compliance, catching graphic errors and text discrepancies. One character change in a slope designation can break gravity lines throughout a building; one wall-thickness error compounds through every floor. Miss it at the table and it costs six figures in the field.

Architects, by industry estimates, spend 30% to 40% of their time on quality control, and they’re not particularly good at it. Human eyes miss things, and those mistakes cascade into 5% to 10% of total construction costs — the very waste he set out to eliminate.

So why couldn’t software solve this decades ago? Because it’s fundamentally a visual and perceptual challenge. A square on a drawing could represent a wall. It could also represent a table. Context tells you which. “Easy for humans to solve,” Trou explained in the podcast, “is very complex for a computer to do it.”

BIM, building information modeling, promised to eliminate coordination errors. It didn’t. The legal and practical reality of construction hasn’t changed: drawings, PDFs specifically, remain the contract documents. The dining room table is still where quality control happens.

The founding moment for mbue wasn’t a sudden insight, but a thousand accumulated frustrations, each one a late night with a red pen, each one an opportunity to ask: What if AI could see drawings the way an architect does?

Building mbue

Trou founded mbue in May 2022 with Ron Green — chief innovation officer and co-founder of KUNGFU.AI — Stephen Straus, Aaron Vollmer and Dave DeCaprio, who joined as CTO in late 2023. The company graduated from Techstars Austin that spring and was spotlighted at the L’ATTITUDE Match-Up, a platform for Latino founders. In September 2024, mbue raised $1.8 million in pre-seed funding led by Techstars. The company joined NVIDIA Inception and Google for Startups Accelerator.

The company started with Smart Overlays, AI-powered drawing comparison and change detection. Character-level text parsing, visual change detection, context-aware object recognition. The technology could identify changes across complex drawing revisions with precision that manual review couldn’t match. Hoar Construction, an early customer, reported saving $100,000 on a single project after mbue caught changes that human eyes had missed.

The move from Smart Overlays to Submittals wasn’t a single insight so much as a natural progression. “Smart Overlays helped us understand changes in drawings with a high degree of precision,” Trou said. “As our models became more accurate at segmenting drawings, parsing text and analyzing specifications, it became clear that we could apply that same foundation to one of the most painful and document-heavy workflows in construction: submittals.”

The logic, as Trou framed it, was simple. If mbue could accurately understand what was in the drawings and interpret what was required in the specifications, the company could connect the two and generate fully compliant product data submittal packages. Choosing Division 26 was deliberate. “Electrical is one of the most complex areas to test this capability,” Trou said. “The information often lives in many different places and formats, including schedules, floor plans, tables, diagrams and specification sections.”

Take a lighting submittal. It requires gathering fixture information from architectural and electrical schedules, then connecting that back to the specifications. A conduit submittal demands identifying conduit schedules, finding locations in electrical plans or diagrams, understanding the environment and materials, and then checking the applicable specification requirements. Each step has its own complexity. If mbue could handle Division 26 consistently and accurately, the thinking went, the same technology could eventually apply to the remaining divisions.

As a result, in September 2025, mbue launched Submittals. Instead of just flagging changes, the platform could now generate the submittal packages required to address them. It uses a proprietary AI model and computer vision to analyze drawings, specifications and electrical schedules, then automatically extracts product requirements and generates submittal packages.

The pilot customer was Weifield Group, a major electrical contractor. Early results: 70% reduction in manual effort, 90% fewer rejections, 50% faster submission cycles. “mbue Submittals removes a long-standing bottleneck for subcontractors,” Trou said when the product launched. “By compressing weeks of paperwork into minutes and improving the accuracy of what gets submitted, we’re giving contractors a faster, more reliable path to approval so they can focus on building, not busywork.”

Trou’s guiding philosophy has remained consistent: augmentation, not replacement. “I would not replace myself,” he says frequently. His reference point in the 2024 podcast interview was characters from the Marvel film Iron Man, Tony Stark and Jarvis: architect as director, AI as assistant. “Show me all deviations between architecture and structural.” “Are there any mechanical conflicts with this proposed solution?” “Give me two rerouting options.” Data-driven design decisions at the architect’s fingertips, not black-box automation.

“We are building a technology that will be able to read and understand technical drawings to a level far superior than a human being,” he said. “It will not only be able to detect changes and potential big, big impactful mistakes, but also understands how to make them right, how to correct them, to provide you real-time design solutions.”

The Bluebeam Chapter

In May 2026, mbue joined Bluebeam. For Trou, the appeal was specific. “We were excited to partner with a company that has spent decades working deeply with PDFs and understands the complexity of construction documents better than almost anyone,” he said. “Bluebeam is already used by so many people in our industry, so bringing mbue’s technology into that ecosystem creates an opportunity for much greater impact.”

The firm’s customers are being transitioned to Bluebeam over 60 to 90 days. The technology mbue built will fold into what Bluebeam is building. The scale shift is dramatic: from a handful of customers to a platform used by millions.

Jean-Pierre Trou, founder and CEO of mbue and principal of Runa Workshop, the Austin-based architecture firm he co-founded in 2009. After more than 20 years of practice, Trou is now 100% focused on mbue’s work within Bluebeam.

As for Trou himself, the transition is complete. “Today, I am 100% focused on mbue’s work within Bluebeam,” he said. Runa Workshop, the firm he founded in 2009, continues operating under Aaron’s leadership. After more than 20 years of practice, he is no longer actively designing buildings.

Yet the throughline of his story — the architect who never left the table — hasn’t broken. It has shifted. “I don’t think I ever left the table,” Trou said. “In many ways, I am closer to the table now because I am closer to our customers and their challenges, not only understanding the problems but helping solve them at scale.”

What Comes Next

“Imagine value engineering of the future won’t exist,” Trou said in the 2024 podcast, “because you already made all the smart decisions until the point of construction.” That was the vision then: not just detecting errors but understanding how to correct them, surfacing real-time design solutions at the architect’s command.

Two years later, the vision has expanded. “My vision of a world built better, effortlessly and with fewer errors, feels more real than ever,” Trou said. “With Bluebeam, I believe we have the opportunity to dramatically reduce errors in construction over the next few years.” Beyond traditional value engineering, he sees workflows like RFIs, change orders and submittals becoming increasingly automated.

What that frees up matters more than what it eliminates. Less time on tedious, manual coordination. More time on the built side of the work. More time for craft, mentorship, apprenticeships and training the next generation of builders.

The constant in Trou’s messaging, however, has been what doesn’t change. Architects still design. Engineers still engineer. Project managers still manage. AI doesn’t replace judgment; instead, it eliminates tedium. “I would not replace myself” remains the north star.

Trou misses design. He admits as much: “But the opportunity to eliminate errors in construction keeps me excited and energized.” The architect’s identity, he insists, doesn’t depend on the projects. “I am building software that can bring value to every project. The potential impact of that contribution is greater now, and that is both humbling and extremely rewarding.”

If the technology works as intended, the manual review that once took a week might take an hour. The $100 billion in annual waste might drop to $50 billion, then $25 billion. Not so much because AI replaced architects but because an architect who never stopped practicing built the AI that could finally understand what architects see.

The table is still there. He’s just sitting at a different one now.

See how AI can reduce project rework.

Start free trial

Your Project Isn’t Behind Schedule Because of Weather. It’s Behind Schedule Because of Email.

Project Management & Efficiency
Frank Kalman

Communication failure is costing your firm millions. The fix isn't more software, but stopping the one thing everyone already agreed to hate.

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.

Fix communication before it costs you more.

Start free trial