Project Management & Efficiency, Technology & Innovation

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

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.

Frank Kalman
August 6, 2026

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

Georgia Has a 10,000-Worker Problem. This Nonprofit Is Closing the Gap.

Construction & The Economy, People & Project Spotlights
Sarah Lindenfeld Hall

Construction Ready has trained and placed thousands of workers since 1998. Here's how the pipeline gets built.

The skilled labor shortage doesn’t just keep contractors up at night. It keeps the whole industry honest. Every tool built for the jobsite depends on one thing: people who know how to use them. When the industry can’t find those people, everyone loses — the GC, the sub, the software company, the owner waiting on a building that isn’t coming.

That’s the context for what Construction Ready is doing in Georgia. And it’s worth paying attention to.

Scott Shelar grew up tagging along behind his grandfather — a small residential developer in Florida who built houses with his hands. But this was the 1980s, and the message to young people was loud and clear: Go to college.

So Shelar did. He wasn’t unusual. A whole generation of potential tradespeople got pushed in the same direction. The construction workforce has been paying the tab ever since.

Now Shelar is president and CEO of Construction Ready, a Georgia-based nonprofit working to close that gap since 1998 — when he first joined the organization. In January, Associated Builders and Contractors estimated the industry would need 349,000 new workers in 2026 alone to meet demand and 456,000 new workers in 2027. In Georgia, the annual shortfall runs about 10,000 workers. In 2024, Construction Ready brought more than 2,500 of them in.

“We’re having a 25% impact on the shortage we have in the state,” Shelar said. “It’s very measurable, and it’s very significant.”

Knocking down the door

The shortage isn’t just a contractor’s problem. It’s a people problem — generations of workers who were never shown a clear path into the trades, never told it was a real option, never handed the gear and credentials to walk onto a jobsite and get started. Nobody pulled them aside and said: This is a career. A good one. And here’s how you get in.

“We’ve really done a disservice to generations of young people by not lifting up those opportunities and giving them a real clear pathway and direction to pursue those opportunities,” Shelar said.

Scott Shelar, president and CEO of Construction Ready, at a construction site. Under Shelar, the Georgia nonprofit brought in more than 2,500 workers in 2024 — about 25% of the state’s annual shortfall. “It’s very measurable,” he says, “and it’s very significant.”

Construction Ready’s adult program attacks that problem directly. No tuition or prerequisites. Four weeks, 160 hours. Participants learn how to use power tools, how to read blueprints — and the stuff that matters just as much on a real jobsite: showing up on time, staying drug-free, understanding what employers need from someone on day one. Graduates walk out with OSHA 10-Hour certification, first-aid credentials and the tools and safety gear to start work immediately. Then Construction Ready runs a hiring fair with a 96% placement rate.

“The whole idea of the training is to knock down as many barriers as we can for a person wanting to get into our industry,” Shelar said.

That’s not a mission statement. That’s a design principle. The program is engineered around every friction point that typically stops someone from getting a foot in the door — cost, credentials, connections, gear. Remove enough of them, and people walk through.

Building the pipeline from the ground up

The adult program is the fast lane. The longer game is happening in schools.

Construction Ready supports more than 200 high school construction programs across Georgia, reaching more than 20,000 students. Carpentry, electrical, masonry, plumbing, architectural drafting, heavy equipment operation. Shelar calls it what it is: a talent pipeline. Not a feel-good initiative. Not a PR play.

A pipeline.

Still, pipelines need pressure to work. Shelar figured out early that one of the biggest leaks in the system was teacher retention. A skilled trades instructor can make considerably more money going back to industry. The good ones know it — and eventually, a lot of them go. So Construction Ready built a counteroffer: bonus checks of up to $10,000 for teachers, based on workforce impact — how many seniors they placed in the industry, how connected they are with local construction companies. Last year, the organization paid out more than $300,000 in bonuses across Georgia.

Trainees during a session of Construction Ready’s adult program. The free, four-week course — 160 hours, no tuition or prerequisites — pairs power-tool and blueprint instruction with job-readiness basics, then feeds a hiring fair with a 96% placement rate.

“To keep these good teachers in the classroom and not go back to industry, we figured out one of the key things is just more cash,” Shelar said.

No sugarcoating. That’s what works.

The pipeline now starts even earlier — middle school programs, elementary school visits, dedicated full-time construction teachers in some Georgia schools. The logic is dead simple: if you want someone choosing the trades at 18, you need them curious at 10. You need them to have touched a saw, read a plan, felt what it’s like to build something real — before anyone tells them it’s not for them.

“We have to start early,” Shelar said. “We have to start planting those seeds at a young age.”

The work ahead

Construction Ready runs on a mix of philanthropic funding, support from construction companies, and local, state and federal dollars. It has expanded into Florida. The challenges ahead are real — an aging skilled workforce, the constant pressure to scale, the grinding, daily work of convincing the next generation that a career built with your hands is worth choosing.

Young students try their hands at power tools at a Construction Ready event. The nonprofit’s pipeline now starts early — middle school programs, elementary school visits — on a simple logic: kids need to touch a saw and read a plan before anyone tells them the trades aren’t for them.

Shelar has been at this long enough to know what it means when it works — when someone finds a trade that clicks, gets placed, builds a life.

“Finding a career that you love is so important in life; we spend so much time working,” he said. “I love that we’re able to help people find a career that they love, a career where they can make a great living.”

That’s the whole point. Not just for Construction Ready, but for everyone who depends on a skilled, ready workforce to get the work done — the work that ultimately gets done, by actual people, on actual jobsites.

See why crews trust Bluebeam to keep the work moving.

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

AI Can Read Your Specs. But Can It Read Your Drawings?

Project Management & Efficiency, Technology & Innovation
Shir Abecasis

Why the next phase of construction AI may depend less on chatbots — and more on spatial intelligence.

Everyone in construction — and everywhere else, really — is talking about AI.

Copilots. Agents. Automated takeoffs. The demos are slick, and the headlines keep getting louder. What’s more, the promises are seductive: fewer people, faster bids, more precise procurement, smarter workflows.

Yet there’s a question almost no one is asking:

Can AI really read a drawing?

Most of today’s AI is built for language: It summarizes specs; drafts emails; answers questions about contracts. All useful … until you realize that some of the most expensive mistakes in construction don’t live in paragraphs, but in geometry.

A door listed in a schedule but missing from the floor plan, a subtle revision between drawing sets that shifts cost exposure, a mismatch between visual conventions and written labels — these are spatial problems, not language or grammar ones.

If AI cannot see what is happening on a page — not just read the words attached to it — then a significant share of construction risk stays invisible.

The next real shift in construction AI may not be conversational at all. It may be visual, spatial, domain-specific. Less about generating content and more about catching what humans are most likely to miss, while keeping humans firmly in charge of the final call.

Why Construction Risk Lives in Geometry, Not Text

If you want to know whether AI is useful in construction, stop asking what it can write and start asking what it can catch.

The industry’s biggest headaches rarely trace back to a poorly phrased sentence in a specification. They come from coordination gaps that hide in plain sight — buried in drawing sets that run hundreds, sometimes thousands, of pages. And as Bluebeam’s own work with AI-driven drawing review has shown, the costliest mistakes are often the ones nobody caught until crews were already on site:

• A door shows up in the schedule but never makes it onto the floor plan.

• A symbol appears in elevation but not in section.

• A revision shifts a wall a few inches and changes quantities downstream.

• A glass type is labeled one thing, drawn another.

Individually, these seem minor. Collectively, they become change orders, delays, rework, blown budgets and strained relationships. According to a SpecFinder analysis of industrywide data, rework consumes roughly 5% to 9% of total project value, and change orders account for 8% to 14% of total contract value, with distressed projects running as high as 25%.

These aren’t language failures. They’re geometry failures.

What’s more, they’re about spatial relationships, like how elements connect, overlap, align and sometimes contradict each other across views; about consistency between plan, elevation and detail; and, perhaps more crucially, about the delta between Rev. 3 and Rev. 4 that someone must manually scan before a bid is due.

For decades, the industry has relied on experienced professionals to spot these issues through repetition and instinct: highlighters, markups, side-by-side comparisons. In other words, careful, skilled work — but human work, nonetheless. However, humans get tired, and that dependence on institutional knowledge is growing more precarious: NCCER projects that roughly 41% of the construction workforce will retire by 2031, taking decades of earned pattern recognition with them.

That’s the blind spot for most text-first AI. It can read the spec and tell you what “Door Type A” means, but can it confirm that every instance of that door exists where it should? Can it recognize that a hatch pattern implies spandrel glass even if the label says “clear”? Can it compare two drawing sets and isolate only what changed visually?

Until AI can operate at that spatial layer — not just the textual one — it risks solving the easy part of the problem while leaving the expensive part untouched.

Document Intelligence vs. Drawing Intelligence: A Critical Distinction

Text-first AI isn’t useless in construction.

It helps summarize specifications, extract submittal requirements, answer compliance questions and surface clauses in long contracts. These are real efficiency gains. Yet, it’s still operating at the document layer, and construction projects operate at the drawing layer.

As Bluebeam’s own guide to reading and interpreting engineering drawings makes clear, a drawing isn’t a static image so much as a dense system of symbols, line weights, hatching patterns, dimensions and relationships. A wall isn’t just a line; it’s tied to doors, windows, hardware schedules, fire ratings and structural constraints. Change one element and you may affect five others.

That’s where a different kind of AI starts to matter.

Call it spatial intelligence. Call it drawing intelligence. The label matters less than the shift it represents.

Instead of asking, “What does this spec say?” the questions become:

• What changed between these two revisions visually?

• Does every door listed in this schedule exist in the plan?

• Are these callouts connected to valid details?

• Does this symbol appear consistently across views?

These aren’t natural language queries; they’re geometric validations.

Technically, that means moving beyond pure language models and into computer vision and structured relationship mapping — systems trained to recognize shapes, patterns and spatial conventions specific to construction documents. Research from AWS and TwinKnowledge demonstrates how combining large language models with computer vision can process thousands of architectural drawings while maintaining near-human accuracy on QA/QC, precisely the kind of scale that manual review cannot match.

In practice, the AI isn’t trying to replace the professional but acts more like a second set of eyes, scanning for inconsistencies at scale, highlighting potential risk and narrowing the field of what needs human attention.

Document intelligence makes information easier to consume; drawing intelligence, meanwhile, makes coordination risk harder to miss.

If AI is going to earn trust in construction, it probably won’t be because it chats fluently but because it catches what would otherwise become a change order.

Human-in-the-Loop AI: Why Full Autonomy Doesn’t Fit Construction

Construction companies don’t roll out new technology the way a startup deploys an app update.

In plenty of industries, a software mistake means a broken dashboard or a delayed report. In construction, it can mean a failed inspection, a safety incident or a six-figure change order. PlanRadar’s 2025 Construction QA/QC Impact Report found that firms without consistent QA/QC standards are 21% more likely to experience avoidable rework and 50% more likely to face warranty exposure.

That’s why fully autonomous AI — the “let the agent handle it” model — feels out of sync with how this industry operates.

Construction is built on accountability. Licensed professionals stamp drawings. Contracts define scope. Insurance policies hinge on who signed off on what. None of that can be outsourced to a black box.

The more realistic path is augmentation, not replacement.

The most promising systems don’t try to redesign the building. Instead, they narrow the review field; flag inconsistencies; highlight deltas; surface potential conflicts. Then step aside.

Human-in-the-loop isn’t a compromise. It’s the only model that makes sense in a liability-sensitive environment.

Construction teams need accuracy and explainability. They need to understand why something was flagged and how that conclusion was reached. MIT Technology Review’s reporting on AI and construction safety makes the limitation concrete: visual language models still struggle with spatial reasoning, and even very high accuracy rates may not be sufficient when the remaining errors involve missed clashes. A hallucinated paragraph in a chatbot is annoying; a hallucinated clash detection could be catastrophic.

The question, therefore, isn’t whether AI can outsmart a seasoned estimator or project manager.

It’s whether AI can reliably act as a force multiplier — scanning thousands of pages faster than any human could while leaving final judgment exactly where it belongs.

The 2D vs. 3D Reality: Where AI Can Close the Gap

The industry has long talked about BIM and digital twins as if they would eliminate ambiguity altogether.

In theory, the 3D model is the source of truth: It contains intelligence, quantities and relationships.

In practice, however, most projects still hinge on 2D documents.

As Bluebeam’s guide to engineering drawings notes, permits are reviewed in 2D; contracts reference 2D sheets; subcontractors build from 2D drawings in the field. Even in countries where BIM Level 2 is achieved, local legal regimes often require 2D drawings to be on hand, as the PDF remains the legal and practical record of the project. According to survey data in Bluebeam’s AEC Technology Outlook 2025, more than 70% of respondents still work primarily from blueprints in their original 2D form.

That creates tension.

The model may change. The drawing may lag. A schedule may update in one place but not another, and a detail may look correct in 3D but miscommunicate in 2D output.

This gap between the live model and the contractual snapshot is where coordination risk accumulates. Spatially aware AI has a meaningful role here — but it’s not as a replacement for BIM, but as a validation layer between worlds.

If AI can compare model-derived schedules to 2D plans, flag inconsistencies and detect visual mismatches before they hit the field, it becomes less of a novelty and more of a safeguard.

The industry doesn’t need another dashboard. What it needs, desperately, are fewer surprises between what was designed, what was documented and what gets built.

What Construction AI Must Prove in the Physical Economy

Construction isn’t the only industry wrestling with this. Manufacturing, energy and infrastructure also operate in the physical world. They deal in materials, tolerances and real-world consequences.

The question is whether the dominant, language-first wave of AI is enough.

If a model can write a clean memo but can’t detect a clash between systems, what problem is it solving? If it can summarize a contract but can’t flag that a critical element disappeared between revisions, how much risk is it really reducing?

The physical economy forces a harder standard.

It’s not enough for AI to be articulate. It has to be observant. ENR’s recent reporting on visual intelligence in construction frames the shift precisely: the next phase isn’t about AI that can chat about your project but about AI that can see it, understand spatial relationships and flag where reality is drifting from plan.

Construction is ultimately an unforgiving test case.

Projects are expensive. Timelines are tight. Margins are thin. Liability is real. That environment doesn’t reward flashy demos so much as tools that reduce rework, accelerate reviews and surface issues before they cascade. Industry experts are consistent on this point: the AI tools that will earn adoption aren’t the most impressive but the most useful — on the ground, on deadline.

If AI can prove itself there — not necessarily as a replacement for expertise, but as a reliable layer of spatial validation — it may earn its place across other capital-intensive industries.

If it can’t, much of the physical economy will remain resistant to automation that only understands words.

The Future of Drawing Intelligence: Predictive Risk and Real-Time Validation

If drawing intelligence becomes reliable — not perfect, but reliable — the implications go beyond faster review cycles. The first step is surfacing inconsistencies, highlighting deltas and flagging missing elements. The next layer then becomes possible.

Predictive risk scoring. Instead of simply pointing out what changed, AI could identify which changes historically correlate with change orders, RFIs or coordination delays. Not just “what changed,” but “what changed that matters.”

A 2026 roundup of AI-driven AEC solutions from BuiltWorlds profiles a growing class of tools built for exactly this: drawing analysis, code compliance auditing and automated RFI generation from drawing conflicts.

Automated compliance checks. Many building codes depend on spatial logic like clearances, egress distances and door swings. If AI can interpret geometry consistently, it can begin validating certain compliance conditions before plans leave the office.

Real-time model validation. As models evolve, AI could act as a constant validation layer between the live 3D environment and the 2D outputs contractors and regulators rely on. If a schedule updates but the drawing doesn’t reflect it, that discrepancy gets flagged immediately.

In that future, AI becomes less of a flashy overlay and more of an embedded safety net.

• It watches relationships between elements.

• It notices when something drifts out of alignment.

• It raises its hand before the field does.

This is already the direction Bluebeam is moving. The acquisition of my company, Firmus — an AI purpose-built to surface drawing errors before they turn into field rework — and tools like Auto Align and Automatic Title Block Recognition are early expressions of drawing-layer intelligence: not AI that generates content, but AI that validates it.

That’s also the foundation of Bluebeam Max, an AI layer built directly into Bluebeam that brings drawing intelligence to the workflows construction teams already rely on. Rather than asking teams to adopt an entirely new platform, Max adds spatial validation, insight and automation where the work already happens.

The real breakthrough may not be AI that can generate a building. It may be AI that helps ensure the one you’re already designing is internally consistent before it ever reaches the jobsite.

See how AI can catch drawing risks earlier.

Explore Bluebeam Max

What Bluebeam Max Really Means for Builders

Project Management & Efficiency, Technology & Innovation
Luke Prescott

Because the last thing your project needs is another markup nobody acts on.

If you’ve ever watched a stack of RFIs pile up like unpaid parking tickets, you know the feeling: a small miss turns into a big delay, and suddenly everyone’s pointing at drawings instead of pouring concrete.

That’s the pain Bluebeam Max is built to solve.

Bluebeam Max is now available. Here’s the straight talk: it’s Revu, supercharged with AI and smarter workflows designed to keep your projects moving instead of stalling.

Catching errors before they catch you

Rework is expensive. Like, millions expensive. According to industry studies, rework eats up 5–9% of total construction costs. And most of it starts with small drawing misses that multiply downstream.

Max introduces Smart Review and Smart Overlay — AI-powered features that look at your drawings and surface conflicts, scope gaps and discrepancies before they spiral into RFIs and delays. Think of it like a second set of eyes that never gets tired and never shrugs off a “we’ll deal with it later.”

Smart Review scans construction documents for design issues, scope gaps and discrepancies, surfacing insights as AI-generated markups, dashboards and trackable issues. Smart Overlay detects design changes across phases, disciplines and drawing scales — so instead of manually hunting page by page, you get visual overlays and trackable comparisons that tell you exactly what changed and where.

That’s hours saved and headaches avoided, long before anyone has to fire off a frustrated email.

Bridging the gap between PDF, BIM

Every builder has had that moment where a flat drawing hides a three-dimensional problem. Architects and engineers see one thing, the field sees another, and you end up discovering the misalignment after steel is already cut.

Bluebeam Max starts to close that gap. With Connected Studio Sessions with Revit®, Bluebeam markups automatically link to the correct spot in Revit — in the corresponding drawing sheet and 3D view. Instead of flipping between tools and translating between mental models, teams see everything connected. Less guesswork, fewer “I thought that was supposed to be …” conversations and more confidence before the first pour.

Yet Connected Sessions doesn’t just bridge documents and models — it bridges teams. A builder can start a Connected Session and invite anyone to mark up — consultants, owners, designers, subs — regardless of license tier. Collaborators join from web, iOS, Android or Revu and do what they’ve always done: mark up in 2D, drop in comments, share expertise. The difference is that every piece of feedback flows directly back to the model. No separate platform. No extra licensing hoops. No “can you export that and send it over?”

This is the part that’s easy to overlook and hard to overstate. Plenty of tools connect files. Connecting the people who actually need to weigh in — without making them jump through technology or procurement gates — is something only Bluebeam is positioned to do.

See the bigger picture

Combining long corridor drawings used to feel like folding a fitted sheet: technically possible, but never fun. Max uses AI for new Stitching functionality that automatically combines drawing sheets from different parts of your project into a single, continuous view — giving you one navigable sheet instead of a Frankenstein patchwork.

It sounds small, but if you’ve ever had to piece together a 1,000-foot trench across a dozen sheets — or tried to visualize 100,000 square feet in a single view — you know how much smoother life gets when it all flows as one.

‘Magic’ markups (because who has time to redo the same work twice?)

Another small-but-mighty set of upgrades: ‘Magic’ markups. Three tools — Duplicate as, Convert to and Offset — that eliminate a shocking amount of repetitive work. Measure a shape once and duplicate it across material types without redrawing. Convert an existing markup to a different measurement type without starting over.

Offset a line to create parallel markups at precise distances, CAD-style, without leaving Revu. These are the features estimators and engineers have been wishing for. You use one once and wonder how you tolerated the old way.

Talk to your drawings

Perhaps the most transformative piece of Max is also the hardest to explain until you try it:

Revu connected to AI via MCP. MCP stands for Model Context Protocol — an industry-standard way to connect software to AI models. With Max, Revu connects to Anthropic’s Claude, which means you can use natural-language prompts to do things that used to require either deep Bluebeam expertise or a lot of manual clicking.

Tell it to scan a PDF for submittal requirements and organize them by CSI division. Ask it to review change orders and update markup metadata. Have it update 400 markups in a single command instead of doing it click by click.

One beta user put it plainly: “I save between four to six hours a month just on bookmarking and page labeling with MCP.”

Max launches with Anthropic/Claude integration. It’s built on industry-standard MCP, so as other AI models add desktop MCP support — Copilot, ChatGPT, Perplexity, Gemini — you’ll be able to connect whichever fits your workflow best. Max also supports AnythingLLM, giving customers the flexibility to connect to the model of their choice.

Why it matters

At the end of the day, Bluebeam Max isn’t about shiny new features. It’s about fewer headaches, fewer missed deadlines and fewer “how did this slip through?” conversations.

It’s about letting design and build teams work smarter together, not spend half their time patching over gaps in process or communication.

Perhaps most importantly, it’s about making sure the next time someone says, “We’ll deal with it later,” there’s a system in place that makes sure “later” doesn’t turn into “too late.”

Start building smarter with Bluebeam Max today.

Start free trial

From Pitch to Progress: Qflow’s CEO Brittany Harris on What It Actually Takes to Scale in Construction Tech

Project Management & Efficiency, Technology & Innovation
Frank Kalman

Qflow won Bluebeam's Startup Spotlight at Unbound 2025. What happened next was the more interesting story.

Winning a pitch competition is one thing. Knowing what to do with it is another.

When Qflow walked off the stage at Bluebeam’s Unbound Conference in October 2025 in Washington, D.C., the materials and waste data startup had a trophy, momentum and, more importantly, a seat at the table. The Startup Spotlight win unlocked a series of working sessions with leaders from Bluebeam and Nemetschek Group — not more pitching, but the harder, more useful work of pressure testing a business in real growth mode.

Qflow captures and structures data around materials and waste on construction sites — turning delivery notes and waste records into clean, usable information that project teams can ultimately act on. With sophisticated auditing Qflow flags risks to the project teams, helping them to avoid risks such as re-work, better manage their supply chain and accurately account for their impact. It is a problem every project team feels. Few have solved it.

For co-founder and CEO Brittany Harris, the sessions came at exactly the right moment. The product was working. Customers were enthusiastic. But the company was bumping up against the question that trips up most startups at this stage.

Built spoke with Harris about Qflow’s journey, what she took away from the experience and what it really means to scale in construction tech.

Built Blog: For anyone who hasn’t heard of Qflow, what are you building and what problem does it solve?

Harris: At its core, we are bringing clarity to one of the messiest and opaque parts of construction — materials and waste. It accounts for over 40% of a project’s budget and 90% of its embodied carbon, but still, its management is ad hoc and largely paper based. Every project has enormous amounts of information moving through the supply chain, but almost none of it gets captured in a way that is structured or actionable.

Harris on stage at Unbound 2025 in Washington, D.C.

We use AI and human verification to turn things like delivery notes and waste records into clean, usable data, and then we audit the hell out of it. Project teams can finally see what is happening on site — what is being delivered, what is being wasted and where the risks are.

What we’ve learned is that this isn’t just a sustainability problem, even though that’s where we started. It is also about quality, cost and accountability. If you do not know what is really being built, you cannot manage any of it effectively.

Built Blog: What did winning the Startup Spotlight mean for you and the team?

Harris: It was a big moment — not just for the visibility, but for what came after. Winning meant real time with leaders across Bluebeam and Nemetschek. That is very different from pitching on stage. You are not telling your story anymore. You are having your assumptions challenged by global industry leaders in our space.

For a team at our stage, going from startup to scale up, that kind of access is genuinely valuable.

Built Blog: What were you trying to figure out going into those sessions?

Harris: We are at that classic inflection point — from UK founder-led startup to global scaling company. The challenges are completely different.

Three things were top of mind: how we think about pricing and packaging as we grow, how we improve product marketing and drive adoption, and how we build a customer success function that scales with the business. We’ve built something customers really value. The next challenge is making that repeatable.

Built Blog: What surprised you most about the conversations?

Harris: How practical they were. It wasn’t theoretical advice — it was grounded in real experience. People shared what had worked, what hadn’t and where they had made mistakes at similar stages.

I was also impressed by the humility of the team — every company has a different journey, and we have different target customers, so what works in one place may not work in another. They focused on discussing core principles and experiences over hard solutions, giving us the space to figure out what will work for Qflow and our clients.

Built Blog: Did anything challenge your assumptions?

Harris: We’ve not really done any focused product marketing to date and have let the product and our clients speak for themselves, which is fine at the early stages, but as Qflow evolves to include more capabilities and service more user types, we need to get more strategic about how we talk about the product.

The conversation with the Bluebeam team was useful to provide a different perspective; while you can carry out agile development and do lots of small feature releases to gather lots of customer feedback, the marketing of key features can be held back and grouped to form overarching narratives that engage key user groups specifically. We are still figuring this out for Qflow, but it is a great start on the journey.

Built Blog: You came to market through a sustainability lens. Has that changed?

Harris: Sustainability is still core to what we do and how we operate, but it is no longer the only focus. We have found that the same data solves multiple problems. A sustainability team cares about carbon reporting. A quality team cares about whether the right materials were used and what that means for re-work and the quality of the end asset. A commercial team cares about cost and risk; are they paying for what they have and how vulnerable their supply chain is.

So, we have broadened Qflow’s capabilities to reflect that. It is still one platform; now it delivers value to multiple stakeholders across a project. That has been an important shift as we think about how we deliver sustainable, scalable impact across this amazing industry.

Built Blog: What would you tell other startups at a similar stage?

Harris: Don’t underestimate how different the next phase is. What gets you to your first few million in revenue is not what gets you to the next level. You have to rethink how you operate; how you price, how you communicate, how you support customers.

Also, stay open to outside perspective. Access to people who have been through it before can cut years off your learning curve. We have learned [from] all kinds of mentors and advisors at each stage, and although we may not implement everything they say, we have learned a huge amount in the process that has made us a more robust company.

Built Blog: What’s next for Qflow?

Harris: Scaling what we have already proven. That means expanding our enterprise footprint, continuing to evolve the product to deepen our value to cost and quality teams across every customer we work with. Only by linking sustainability to these core functions can we ensure that we continue to progress along this important journey in the face of economic and political turmoil.

We have already established a team and beachhead clients in North America and are really excited by the traction and rate of growth across the Atlantic. We are also looking at new markets, particularly in Europe, which brings its own challenges and opportunities. But fundamentally, the focus hasn’t changed: helping construction teams make better decisions with better data to build a more sustainable future.

See how better data drives better project outcomes.

Start free trial

What permitting looks like

Where the time goes

The fix nobody’s talking about

What this means for infrastructure

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

What does a digital takeoff workflow look like?

Step 1: Review the drawings and scope

Step 2: Calibrate the drawing scale

Step 3: Configure tools and layers

Step 4: Measure the quantities

Step 5: Visually verify coverage

Step 6: Validate the quantities

Step 7: Export the data for estimating

AI accelerates the takeoff, but the estimator still drives

What makes a construction takeoff defensible?

Frequently asked questions

What is a digital takeoff in construction?

How is a digital takeoff different from a manual takeoff?

What is the first step in a digital takeoff?

Can AI do construction takeoffs?

Does Bluebeam Max help with construction takeoffs?

What software do estimators use for digital takeoffs?

Run the same play on your own drawings.

Knocking down the door

Building the pipeline from the ground up

The work ahead

See why crews trust Bluebeam to keep the work moving.

Still Practicing

The $100 Billion Problem

Building mbue

The Bluebeam Chapter

What Comes Next

See how AI can reduce project rework.

The Coordination Tax

What Happens When Information Lives in Someone’s Inbox

We’ve Seen This Before

What Standardization Actually Does

Fix communication before it costs you more.

Why Construction Risk Lives in Geometry, Not Text

Document Intelligence vs. Drawing Intelligence: A Critical Distinction

Human-in-the-Loop AI: Why Full Autonomy Doesn’t Fit Construction

The 2D vs. 3D Reality: Where AI Can Close the Gap

What Construction AI Must Prove in the Physical Economy

The Future of Drawing Intelligence: Predictive Risk and Real-Time Validation

See how AI can catch drawing risks earlier.

Catching errors before they catch you

Bridging the gap between PDF, BIM

See the bigger picture

Talk to your drawings

Why it matters

Start building smarter with Bluebeam Max today.

Built Blog: For anyone who hasn’t heard of Qflow, what are you building and what problem does it solve?

Built Blog: What did winning the Startup Spotlight mean for you and the team?

Built Blog: What were you trying to figure out going into those sessions?

Built Blog: What surprised you most about the conversations?

Built Blog: Did anything challenge your assumptions?

Built Blog: You came to market through a sustainability lens. Has that changed?

Built Blog: What would you tell other startups at a similar stage?

Built Blog: What’s next for Qflow?

See how better data drives better project outcomes.

Select Region