TL;DR: I pointed Grok and Claude at a homework assignment for a university Civil 3D / Revit course and said, more or less, “complete this.” Each one spent about 45 minutes driving Autodesk Civil 3D and came back with a plotted 36×24 subdivision sheet showing a road alignment, a cul-de-sac, the right-of-way, and parcels. At a glance both looked respectable. On inspection, one was cluttered but genuinely solved the problem. The other looked more finished largely because the instructor’s reference image was still visible underneath it. Producing the drawing, which used to be the expensive part of the job, is becoming cheap. What stays expensive is telling a drawing that is right from one that only looks right. The challenge for the engineering educational system now is to train people who can do that checking when they no longer learn it by doing the drafting.

Why an electrical PE is taking a civil class

Some background first. My PE is in electrical engineering, and my training includes structural, so I’m comfortable reading structural, architectural, and MEP drawings. Civil site work is different. It’s not built on things you install like trusses and distribution panels. It’s built on points, surfaces, alignments, and parcels, a topographic way of working that I wanted to learn properly for our work at TeraContext.AI. So this fall I enrolled in a university Civil 3D / Revit course and turned in the assignment described below.

Homework 4 is “Revere Way,” a small subdivision on an 11-acre site. The student gets a scanned plan image, a CAD file with the site boundary, and the road geometry. The task is to scale the image, build the site, create the alignment and cul-de-sac, apply a 55-foot right-of-way, divide the land into lots, label everything, and plot a 36×24 sheet. To the instructor’s credit, the course had already seen this coming: one-sixth of the grade is for exploring AI output on the problem and commenting on whether it’s satisfactory.

I went further than that and gave the entire assignment to two AIs, with one sentence each: look at the homework in this folder and complete it. About 45 minutes later, each had produced a plotted drawing. Both PDFs were generated by Civil 3D 2027 itself, not mocked up in a drawing program. Both AIs had access to Civil 3D’s CLI, AutoLISP, API, and MCP server. They used them differently. In addition to the CLI, Grok wrote a series of its own programs in C, Python, and AutoLISP. Claude worked mainly through the CLI and also used the API and the MCP server.

Same problem, very different engineers

Grok’s sheet looks like a real plan set at first glance. It has lot numbers and square footages, illustrative houses and driveways, zoning notes, and an R-2/R-4 setback table, with a shaded road running through the middle.

Then you look closer. Almost all of that is the instructor’s reference image. The assignment brings it in as an external reference, and Grok left it visible under its own work. Grok’s own contribution is the magenta and blue linework on top. Its road alignment follows the plan closely: its station labels land almost exactly on the originals. Its parcel lines don’t. Several run diagonally across the lots drawn underneath, and none of its parcels has its own area or perimeter label. The lot labels you see belong to the image. The title block says “Scale: to fit.” Take away the underlay and much of what made this sheet look finished disappears.

Grok’s sheet. The black linework, lot labels, houses, and notes come from the instructor’s reference image; Grok’s own work is the magenta and blue. Click for the full-size drawing.

Close-up: Grok’s magenta parcel lines cutting across the reference plan’s lots. The road alignment and stations (in red) line up with the plan; the parcels don’t.

Claude’s sheet is plainer, and it’s entirely Claude’s own work. It hid the reference image and rebuilt the plan from scratch. The sheet is at a true 1” = 50’ scale. It has a parcel table for all 20 lots plus the stormwater lot, water tower, and ROW parcels, with square feet, acres, and perimeters, totaling 11.326 acres. It spells out the typical ROW section and documents how the cul-de-sac loop was built. It also recorded its calibration on the sheet: “CAD file scaled ×1202.03 from image scale bar (300 px = 100 ft).” The assignment asked students to do that scaling. Claude also showed its work. The weaknesses are real, though. Labels pile up around the cul-de-sac and the water tower, and some lots differ noticeably from the plan. Lot 7 is 0.83 acres against the plan’s 0.67. The assignment allows some deviation, but a grader would ask about that one.

Claude’s sheet. Everything shown is Claude’s own geometry, with the reference image hidden. Click for the full-size drawing.

So the two aren’t equivalent solutions with different styles. One is a genuine solution with drafting problems. The other is a convincing surface over a partial solution. The sheet that looked more finished was the less correct one.

The drawing is no longer the scarce thing

For most of the history of the profession, producing drawings was expensive. Drafting boards gave way to AutoCAD, and AutoCAD gave way to model-based tools like Civil 3D. Each step made drafting faster, but a person still had to click through it. A large share of an engineering firm’s billable hours, and nearly all of a new graduate’s first few years, go into translating design intent into a set of drawings that conforms to standards.

This experiment suggests that translation is becoming close to free. It isn’t finished yet, but two different AI systems from two different companies both drove an application with a notoriously steep learning curve, from a one-line instruction, in less time than a student spends watching the tutorial videos. One of them got most of the way to a correct answer. The next model generation will get further.

So when the drawing becomes cheap, what is left that’s valuable?

What stays expensive: judgment, checking, and the stamp

Being able to catch what I described above is what’s valuable. To notice that Grok’s lot labels belonged to the underlay, you have to know what an XREF is, what a Civil 3D parcel label looks like, and that a lot line shouldn’t cut across a house. To question Claude’s Lot 7, you have to compare it with the plan and know how much deviation is acceptable. Neither check is difficult for someone who has done the work. Both are invisible to someone who hasn’t.

Homework is also the easy case. It’s a well-posed problem with a known answer. Real sites come with bad surveys, neighbors who object, an agency reviewer with opinions, and a utility line nobody knew about. A real reviewer has to ask whether each lot still meets its zoning minimums once the ROW is taken out, whether the turnaround works for a fire truck, and where the water goes. The AI is excellent at the well-posed part. The ill-posed part is still the job.

So the scarce skill is evaluation: interrogating a design instead of producing one. It’s telling that the more useful of the two sheets wasn’t the prettier one. It was the one that recorded its assumptions. We should expect that from AI output, the same way we expect it from junior staff: if you can’t show your work, it doesn’t get stamped.

The stamp matters. A professional engineer’s seal is a statement of personal legal accountability, and no AI company will take that on for you. Licensure turns out to be the profession’s firmest protection against AI. It’s also a heavy responsibility, because it means the engineer has to understand the design well enough to put their name on it.

The apprenticeship problem

That leads to the uncomfortable part. Judgment isn’t taught in a lecture. It builds up through years of doing the tedious work: drafting the lot lines, having a senior engineer mark them up, seeing the drainage fail in the model, redoing the grading. The drawing was never only the product. It was also how people learned.

If AI does the drafting, where does the next generation of reviewers come from? A firm that hands every junior task to a model gets a productivity gain this year and a talent shortage in ten. Refusing the tools is a losing strategy, because the firm down the street won’t refuse. The answer is to design the apprenticeship on purpose instead of letting it happen as a side effect of billable drafting.

What this means for engineering education

The instructor’s “explore the AI output” item is the right instinct, and I think it should be most of the assignment rather than one-sixth of it. An assignment that a general-purpose AI completes unassisted in 45 minutes isn’t really measuring whether the student understands site layout. It measures whether they can operate Civil 3D, and that’s the skill being commoditized.

The stronger assignment is almost exactly what I ended up with: here are two AI-generated layouts of the same subdivision. Find what’s wrong with each. Pick one and defend it. Then fix it. That can’t be handed off to an AI, because it requires the student to evaluate what the AI produced. Doing it well means knowing what an underlay is, what a correct parcel looks like, and how far a lot can drift from the plan. Oral defenses, design reviews, and red-line critiques, the teaching methods that feel old-fashioned, are the ones that hold up.

Software proficiency will still matter, the way knowing how a spreadsheet works still matters for an accountant. But it’s quickly becoming the floor, not the ceiling.

The business model will bend

Much of civil engineering is billed by the hour, and proposal math assumes a sheet takes a certain number of hours to produce. If the drafting is nearly instant, hourly billing starts rewarding slowness, and clients will notice.

The logical endpoint is fixed pricing: a price per subdivision, per lot, or per plan set instead of per hour. That changes who benefits from efficiency. Under hourly billing, the savings from a 45-minute layout go to the client and the firm’s revenue falls. Under a fixed fee, the firm keeps the savings and the client gets a price it can budget. It also moves the risk. A fixed fee is only safe if the firm can estimate its own effort, and with AI doing the drafting that effort is mostly checking, client meetings, agency review, and whatever the site throws at you. Those are exactly the parts that are hard to predict. Firms that make the switch will need tight scope definitions and clear change-order terms for surprises like a bad survey or a rezoning fight. Public work may move more slowly. Qualifications-based selection and negotiated cost-plus contracts are built around hours, and it will take time for agencies to decide what a fair fee is when the drawing costs almost nothing.

The upside is significant. In about 90 minutes I got two independent attempts at the same site. A firm could just as easily generate ten, with different lot yields, alignments, and stormwater locations, and spend its expensive human hours comparing them with the client. The engineer’s value moves from “I drew your plan” to “I checked the options and this is the one to build, and here’s why.” Small firms, which have always been limited by drafting capacity, may benefit the most.

There is a catch that the homework doesn’t show. Everything the AI sees leaves the building unless you plan for it: the survey, the client’s lot-yield targets, the utility company’s facility maps, the pricing model behind your proposal. My assignment was a class exercise with nothing to protect. A real project file is a firm’s working knowledge, and often someone else’s confidential information that your contract promises to protect. Some of it, like drawings of water, power, or communications infrastructure, may be restricted by law. The first business decision isn’t which model is smartest. It’s where the model runs.

Local AI keeps everything on hardware you control. Open-weight models run on a workstation or a small server, and the data never goes anywhere. The trade-offs are the up-front hardware cost, someone to maintain it, and models that usually trail the best cloud models. As I’ve written before, that gap is narrower than most people think, and for sensitive or repetitive work it’s often the right answer.

Cloud AI gets you the most capable models, but the contract you’re under matters more than which vendor you pick. The tiers are very different:

• Consumer plans (free and individual paid tiers) are the riskiest. Depending on the vendor and your settings, conversations may be retained and used to train future models. An engineer pasting a client’s site plan into a personal chat account may already be in breach of their contract.
• Commercial and API terms generally commit the vendor not to train on your data. Many also offer a data processing addendum and set retention periods, and eligible customers can negotiate zero data retention, where inputs aren’t stored after the response is returned.
• Enterprise and team plans add administrative controls, single sign-on, audit logs, and firm-wide retention settings. The point is that the firm, not each employee, decides what happens to the data.
• Models hosted by your cloud provider, such as Amazon Bedrock, Google Vertex AI, or Microsoft Azure, run the model inside that provider’s environment under the cloud agreement you already have. You can choose the region, and the model’s developer doesn’t receive your prompts. For public-sector and critical-infrastructure work, government cloud regions with the right authorizations may be required.

The practical rule is to read the terms before you upload the survey. Match the contract to the most sensitive document in the project, not the average one. Then write that choice into your client agreements, so that “we use AI” comes with a clear statement of where the data goes. Once the drawing becomes cheap, your proprietary knowledge and your clients’ trust are a large part of what you’re selling.

The takeaway

I expected one of these tools to fail outright. Neither did, and that’s the more dangerous result. A tool that fails obviously is easy to catch. A tool that produces a convincing sheet with the answer key showing through gets caught only by someone who knows what to look for.

Engineering isn’t going away. What goes away is producing drawings as a stand-in for engineering. What’s left is the part that was always the real work: deciding what’s right, explaining why, and taking responsibility for it. The engineers who do well will be the ones who can look at two plausible drawings and tell you, quickly and with reasons, which one is wrong.

TL;DR The data center construction boom is masking a severe divide in the commercial market. While overall industry backlog recovered to 8.8 months by June 2026, firms actively building data centers hold 11.0 months of work, compared to just 8.5 months for everyone else. The catch? Only 8% of mid-market contractors (under $100M revenue) have access to this sector. Trying to pivot and become a prime mission-critical General Contractor takes 18 months—time most mid-sized firms do not have. The immediate solution is to pivot down the contracting chain. The megabuilders holding the primes are severely resource-constrained, spending millions just to import out-of-state talent. By leveraging local labor advantages, avoiding complex MEP scopes, and bidding on massive, repetitive packages like site work, concrete, shell, and logistics, mid-market GCs can immediately tap into the $81.5 billion data center pipeline as high-tier subcontractors.

Back in March, we published The Builder’s Pivot, outlining a strategy for mid-market general contractors looking to replace drying office and multifamily pipelines with data center work. We stand behind it. But there’s an obvious objection to that piece, and it’s about timing: the plan runs eighteen months from the first certification course to a completed project you can put on a prequal form. Eighteen months is a long time when your Q3 is half-empty and two of your best supers are polishing their resumes.

Five months later, the numbers have moved enough to be worth revisiting, and they point at a shorter path that most firms won’t consider because it looks like a step down.

Backlog isn’t collapsing. It’s splitting.

The headline data over the winter looked grim. The Associated Builders and Contractors (ABC) Construction Backlog Indicator dropped to a four-year low of 8.0 months in January 2026. Roughly two-thirds of contractors reported having at least one project postponed, scaled back, or outright canceled during the preceding six months.

Then it recovered. By June 2026, the backlog indicator climbed to 8.8 months. On its face, a boring number.

Pull it apart and it isn’t boring at all. ABC’s June release breaks members into those doing data center work and those who aren’t. The 13% who have it are carrying 11.0 months of backlog. The 87% who don’t are carrying 8.5 months. ABC’s chief economist, Anirban Basu, put it plainly: continued data center construction is the main force keeping overall backlog elevated.

The split by company size is where it gets uncomfortable. Among contractors above $100 million in revenue, 41% have data center work. Below $100 million, it’s a meager 8%.

> ABC Construction Backlog Indicator, June 2026. Contractors with data center work carry 11.0 months of backlog; those without carry 8.5. Only 8% of firms under $100M in revenue have any. Source: Associated Builders and Contractors, June 2026 CBI release.

So the aggregate number is fine and your firm’s number probably isn’t, and the two facts aren’t in tension. One sector is holding up the average, and mid-market firms have almost no access to it.

Meanwhile, the sector itself keeps outrunning forecasts. ConstructConnect counted $14.9 billion in U.S. data center starts in 2023 and $26.9 billion in 2024. Their 2025 total came in around $77.7 billion. Through June of this year, starts hit $81.5 billion—six months beating all of last year, off 116 projects, with January alone setting a single-month record at $25.5 billion. Strip data centers out of the commercial forecast, and 2026 turns into a 1% decline.

> U.S. data center construction starts, 2023–2026. The 2026 bar covers January through June only and already exceeds all of 2025. Source: ConstructConnect monthly Data Center Reports.

(Note: ConstructConnect’s February 2026 report stated full-year 2025 starts at $77.7B, while their August 2026 revision adjusted this to $72.5B as late-reporting projects settled. The chart’s argument survives either way, as the first half of 2026 shatters both figures.)

The primes have the opposite problem

Here’s the part that creates the opening.

In the Associated General Contractors (AGC) 2026 outlook survey, a net 57% of contractors expected data center spending to rise, the highest of any category and well ahead of power at net 34%. Those are firms already in the market, and what they report struggling with is not finding work. It’s staffing it. Contractors with full pipelines are slowing starts, thinning out their teams across too many jobs, or declining work outright because they can’t put a credible staffing plan behind it.

The binding constraint has shifted. Two years ago the conversation was all journeyman electricians, and that shortage is still real—the overall construction workforce gap runs somewhere between 439,000 and 499,000 depending on whose 2026 estimate you use. But the roles that are actually gating schedules now are the ones in the trailer: superintendents, project managers, estimators, MEP coordinators, VDC leads, safety managers, and commissioning managers.

Recruiters covering the sector put an experienced data center superintendent at a $215K–$275K base salary in Phoenix, $185K–$235K in Dallas, and $195K–$250K in Atlanta, with total comp running 18–32% above base. Firms are hiring six to twelve months ahead of groundbreak just to have someone in the seat.

Now look at your own org chart. Supers coming off canceled jobs. PMs at half load. An estimating group grinding out tenant improvement bids against seven other firms for a two-point fee. A safety program you’ve spent a decade building and an EMR you’ve protected like a credit score.

That is precisely the inventory the megabuilders can’t buy right now. The mistake is assuming the only way to sell it is to become a data center GC yourself.

Take the subcontract

Turner, DPR, Mortenson, Hensel Phelps, Holder, Clayco, and their peers hold the primes. They aren’t handing those over, and chasing one costs you the eighteen months. But every campus they run has dozens of subcontract packages to fill, and their trade partner benches are stretched in every hot market at once.

So go in underneath them.

For a firm that’s been the name on the sign for thirty years, this lands badly. Signing a subcontract under another GC feels like admitting something. It’s worth being honest about both sides of the trade.

You give up the fee on the whole job, the owner relationship, control of the master schedule, and your name on the building. On hyperscale work, you frequently give up the right to mention the project at all, because the end client is confidential and the NDA has teeth. You’ll be one of forty subs working someone else’s pour sequence and logistics plan.

What you get is defined scope with no design risk, no mission-critical MEP coordination exposure, and contracted backlog measured in years rather than months. Hyperscale procurement leans on multi-building and multi-year campus awards to lock in partners, which is about as close to an annuity as this business offers. You also get the reference that Part I said you couldn’t buy.

On margin: a tight self-perform scope package, bid into a market where the prime is short of qualified bidders, will often beat a competitively-bid GC fee on an office job in an 8.5-month-backlog market. You’re trading a market with too many bidders for one with too few. That’s usually a good trade even when it stings.

What you can actually bid

Forget the switchgear package. Here’s what a campus lets out that maps onto work you already do.

• Site and civil: This is the biggest early opportunity and the most ordinary: mass excavation, grading, rock removal, soil stabilization, underground utilities, paving, access roads. Primes increasingly award this as one integrated package specifically to stop coordinating three separate contracts.
• Concrete: Foundations, slabs, tilt-up and precast erection, equipment and generator pads, electrical duct bank. The quantities are enormous and repetitive, which is exactly when a disciplined concrete operation makes money. A lot of primes self-perform concrete and are short of crews to do it.
• Shell and envelope work: Steel erection, metal panel, roofing, doors, and hardware—this is the same argument Part I made about powered shell, except you skip the hard part, because you don’t need to hold a mission-critical prime contract to bid it.
• Campus ancillary buildings: Everything on the campus that isn’t the data hall. The admin building, the security operations center and gatehouse, warehouses, the maintenance building, water treatment structures, generator and fuel enclosures. A PLA signed in the Sacramento region this January covers a campus described as a two-story data center, a two-story administration building, and a one-story generator building. That admin building is an office building. You’ve built a hundred of them. It happens to sit inside a fence line.
• Interiors in those buildings: Drywall, ceilings, flooring, casework, paint, firestopping is unglamorous and the prime would rather not manage twelve small trades to get it done.
• Perimeter security: A single compound can run more than a mile of fence in two or three types, plus crash-rated ASTM M30/M40/M50 barriers, bollards, and vehicle and pedestrian gates. It’s rarely the prime’s strong suit.
• Site logistics: Laydown, temp roads, parking, badging trailers, worker housing is becoming its own contract at campus scale. One hyperscaler recently committed over $550 million to a single workforce accommodation contract. If you’re good at logistics on a tight downtown site, a greenfield campus is the same skill with more room to work.

The local-hire angle is the real edge

There’s a version of this that isn’t a scope subcontract at all, and it’s the piece most firms miss.

Primes are covering the leadership gap by importing people. Fifty travelers at $178 a day in per diem is about $8,900 a day, roughly $267,000 a month, before anybody swings a hammer. Staffing markups on augmented labor commonly run 25% to 75% over base pay.

> The cost of importing a crew, before wages. Sources: Rinvio 2026 crew cost benchmark (per diem and staffing markups); dcgeeks 2026 local-hire analysis. Annual figure derived from monthly.

At the same time, community benefit agreements and state incentive packages increasingly carry local hiring provisions requiring 30% to 50% of construction labor to come from the local market.

Put those together. The prime has a contractual obligation to hire local and a very expensive workaround when it can’t. You are the local firm, with badges, insurance, a safety program, and people who already live there. A labor-only or staff-augmentation arrangement—your supers and foremen running scope under the prime’s direction—solves a problem they’re currently paying a quarter million a month to route around.

Be clear about what that business is. It’s lower margin, it’s pass-through, it doesn’t build enterprise value the way a scope contract does, and there’s a genuine risk of turning into a body shop. But it carries almost no scope or design risk, it produces revenue in weeks instead of quarters, it keeps your best people on payroll instead of on Indeed, and it gets your name into the prime’s system as a partner who showed up. Use it as the on-ramp.

Prequal as a sub is paperwork, not resume

Part I described the Catch-22: you need data center experience to win data center work. As a trade partner, that loop mostly dissolves, because the prime isn’t asking whether you’ve built a data hall. They’re asking whether you can run your scope safely on their schedule without becoming their problem.

The list is short and none of it requires a program director hire.

• General liability at $5 million per occurrence minimum, though a lot of hyperscale programs want $10 million or umbrella coverage to $25 million. Check your limits this week, because that’s the most common disqualifier and the easiest to fix.
• EMR under 1.0, often under 0.8.
• OSHA 30 supervisors and documented safety staffing ratios.
• Audited financials and bonding capacity sized to the scope.
• Registration on Highwire, Avetta, or ISN, since many primes route prequal through them.

Clayco has boiled its process down to a once-a-year contractor profile form; Turner publishes its subcontractor requirements. Both are self-service and you could start today.

One thing to check early rather than late: every worker on a hyperscale site gets badged and background-checked. If a meaningful share of your workforce won’t clear, you need to know that before you bid, not at mobilization.

Find out the labor posture before you bid

Organized labor has moved hard into the AI buildout, and this is the item most likely to blow up a bid.

OpenAI formalized a partnership with North America’s Building Trades Unions in March 2026, and in April turned it into a labor agreement covering the Oracle–OpenAI Stargate campus in Saline Township, Michigan, expected to employ more than 2,500 NABTU tradespeople and apprentices. Meta and BlackRock have signed comparable pacts. Regional building trades councils are signing campus-specific PLAs.

If you’re open shop in a PLA market, you have three workable options: sign a project agreement for that job, sub the affected craft to a signatory firm, or go after campuses without a PLA. All three are fine. None of them work if you find out after you’ve priced it.

If you’re already signatory, this is a tailwind and you should be calling your locals now. The same halls are running job calls for travelers at premium rates, which means they know exactly which campuses are short.

Geography decides a lot of this for you

Data center work is concentrated in a way office work never was. Northern Virginia, central Ohio, Phoenix, the Dallas–Abilene corridor, Atlanta, Richland Parish in Louisiana, New Carlisle in Indiana, Saline Township, Memphis, Salt Lake, upstate New York. ABC’s regional splits echo it—the South is carrying 10.3 months of backlog while the West sits at 7.6.

If a campus is within reasonable range of your yard, the local-hire advantage is yours and this is a straightforward move. If it isn’t, be honest with yourself. You’d be traveling into a market where local firms have a structural cost advantage and you’re paying per diem they aren’t. Not impossible, but it’s a worse case, and it argues for selling capacity rather than bidding scope.

Ninety days

• Weeks one and two: Pick two scopes you genuinely self-perform or have deep sub coverage in. Be ruthless about that, not aspirational. Map every announced campus within 150 miles and find out who holds the prime on each.
• Weeks three and four: Complete prequal with five primes and get registered on Highwire, Avetta, and ISN. Pull your EMR and know the number before somebody else quotes it to you. Call your broker about the $10 million question.
• Weeks five through eight: Get in front of the primes’ trade partner outreach—most run local subcontractor events, and firms like Meta publicize local sourcing commitments precisely because they have to meet them. Put one estimator on learning data center quantities for your two scopes. Talk to your surety about capacity.
• Weeks nine through twelve: Bid, and underwrite for schedule rather than scope. The scope is well-defined and repetitive. The exposure is compression, liquidated damages tied to equipment delivery dates, and whether you can hold crew for the duration. Treat the staffing plan as a real deliverable, not an attachment. And ask for the multi-building award, because that’s the structure the prime prefers anyway.

Ways to get hurt

Winning scope you can’t staff is the one unrecoverable error. Capacity is the entire reason they hired you, and a subcontractor default typically costs 1.5 to 3 times the original subcontract value. Every prime knows that number, and they don’t give second chances on it.

Underwriting the wrong risk is next. On an office job, your margin dies from scope gaps and change order fights. Here it dies from schedule, and nothing moves a GPU delivery date.

Read the pay-when-paid clause, the retainage terms, and the notice provisions before you sign. You’re second-tier now and your cash cycle stretches accordingly.

Part I warned about betting the firm on one sector. As a sub, you get concentrated in one client too—the prime. Work with two minimum, and don’t let your commercial relationships go cold.

Last, plan your business development around the NDA instead of against it. You often can’t name the project, the client, or take a photo of the site.

The part that doesn’t transfer

The scopes transfer. The crews transfer. The safety program transfers.

What catches commercial GCs out is the paper. A hyperscale subcontract package carries spec volume, submittal registers, RFI traffic, and commissioning documentation at a scale most mid-market firms have never dealt with, on a repetitive multi-building program where the difference between Building 3 and Building 7 lives in revision clouds buried a thousand pages deep. Firms lose money on these jobs less often because they built the wrong thing than because they bid the wrong thing, having actually read about 60% of what governed their scope.

That one’s solvable, and it’s solvable before you sign anything.

Part I asked which mid-market GCs would move first into data center work as general contractors. With 8% of sub-$100M firms holding any data center backlog while the sector books $81.5 billion in six months, the better question is whether the front door is the only door.

It isn’t. The primes have more work than people and you have more people than work. Your name doesn’t go on the building. Your crews do, your revenue does, and in eighteen months your prequal package says mission-critical on it—which is roughly when you’d have finished the other plan.

Bidding into a data center program and drowning in the spec set? Contact us to see how TeraContext.AI ingests specs, drawings, and RFIs at campus scale and tells you exactly what governs your scope.

Let’s be real for a second: the conversation around AI in construction feels stuck between two extremes. On one side, you have massive, cloud-based behemoths that promise the world—provided you’re willing to hand over your most sensitive project data. On the other, you have lightweight on-device toys that choke the moment you feed them a complex, real-world specification book.

But there’s a sweet spot. Mid-sized models—hovering around the 30-billion-parameter mark and running entirely on your own local hardware—have quietly become the most practical and strategic move a general contractor can make.

That exact insight is why we built TeraContext.AI. Construction documents aren’t just generic text; they are dense, highly sensitive artifacts that encode your firm’s competitive edge. How you package scopes, where you flag risk, how you apply markups—that’s your secret sauce. Sending that data, or the AI’s reasoning about it, out to a third-party cloud creates serious practical and cultural friction. Local, mid-sized models remove that friction completely, without forcing your estimating team to sacrifice brainpower.

Privacy Isn’t a Perk; It’s the Whole Ballgame

Estimating data is the crown jewels of any general contractor. Bid strategies, historical cost intelligence, preferred subs, and your nuanced interpretations of work breakdown structures are intellectual property. When an AI chews through a 1,200-page spec set or a full drawing package, the intermediate steps—section extraction, classification scores, and draft scope narratives—contain exactly the kind of intel your competitors would love to get their hands on.

Running a 30B-class model locally keeps every single token and thought process locked tight within your own infrastructure. No shared multi-tenant servers, no residual logs left on someone else’s computer, and zero contractual gray areas about how your data might be used to train future models. If you’re touching work for owners with strict data-sovereignty rules, local execution isn’t just a nice-to-have; it’s table stakes. It turns privacy from a hopeful policy into a hard architectural guarantee.

This is exactly why Meta’s recent release of Muse Glimmer feels so validating. Glimmer is a ~30-billion-parameter open-weight model explicitly built for always-on, local agent workflows. After quantization, it runs smoothly on a single consumer GPU, handles both text and images, and manages complex, multi-step reasoning—all while keeping your data on your device. Zuckerberg’s accompanying essay, “The Future is for Everyone,” hits the nail on the head: superintelligence should empower individual teams, not just consolidate power in a few massive centralized clouds. That philosophy perfectly matches the reality of commercial construction.

Hardware Reality and Speed Where It Actually Counts

Cloud latency might be fine for writing a polite email, but it’s a killer when an estimator is iterating on a live, high-stakes bid. When an addendum drops and you need to re-classify sections, or when you’re hunting for clashes between Division 23 and the mechanical drawings, you need answers now. Local models cut out the round-trip lag and the annoying queue times of shared cloud endpoints.

This brings us to the hardware reality check. A massive, state-of-the-art open model like Moonshot AI’s Kimi K3 might perform incredibly well thanks to its staggering 2.8 trillion parameters, but at what cost to own the hardware that runs it? Even when heavily quantized, a model of that scale requires nearly 600 GB of memory just to load, which means buying or leasing serious, expensive enterprise server clusters.

But a 30B-parameter model like Meta’s Glimmer hits the perfect sweet spot. Glimmer runs flawlessly on a used $1,000 NVIDIA RTX 3090, and it absolutely screams on a $4,000 RTX 5090. Glimmer’s specific design choices—fitting snugly into a 24–32 GB memory footprint while utilizing a lightweight drafter for faster generation—make its speed incredibly accessible. These mid-sized models are smart enough to maintain coherent reasoning across hundreds of pages, but lean enough that your firm doesn’t have to build a billion-dollar data center to host them.

Total Control and Tailored Intelligence

Cloud models are the ultimate generalists—they have to be. But construction workflows are built on highly specific rules. The way keynotes map to spec sections, the subtle difference between a genuine scope gap and a carefully worded exclusion, the nuances of classifying work breakdown structures—these demand domain expertise. A model that lives on your hardware can be continuously adapted to your rules.

Local deployment gives you the keys to the castle:

• Fine-tuning: Train the model on your firm’s historical packages, past RFI resolutions, and internal style guides.
• Secure Retrieval: Keep your RAG (Retrieval-Augmented Generation) indexes strictly within your trusted firewall.
• Custom Scaffolding: Use custom prompts and tool schemas that encode your unique estimating philosophy, rather than a generic one.
• Auditability: Lock in the exact model weights and settings used for a specific bid, so you can perfectly re-run and audit that reasoning years down the line.

TeraContext’s seven-phase pipeline—from extraction and table handling to work breakdown structure classification and cross-reference validation—is designed specifically to harness this level of local control. The AI does the heavy lifting, proposing the draft, but the estimator always holds the reins. Local models just make that collaboration faster and completely transparent.

Supercharging the Open Ecosystem

The open-weight AI landscape is maturing at breakneck speed. Models in the Qwen and Gemma families are already fantastic all-rounders. Meta’s Glimmer doesn’t replace them; it supercharges the ecosystem by adding a toolkit purpose-built for multi-step, agent-driven workflows.

For a construction team, this means your local hardware can run a highly specialized model for work breakdown structure tagging right alongside an agentic model like Glimmer that orchestrates the whole workflow—analyzing a drawing sheet, diagnosing a missing extraction, and drafting the final scope package.

Meta putting Glimmer out there with a permissive license is a huge win. It gives domain specialists like us the perfect engine to build upon. Our goal at TeraContext is simple: take these incredible open tools and make them wear a hard hat. We add the pre-tuned scaffolds for ten industry taxonomies, the vision pipelines tailored to construction drawings, and the GraphRAG structures that actually understand specification cross-references.

The Bottom Line

The technical foundation for capable local AI is no longer an experiment. It is production-ready. For estimating teams, this means sensitive projects stay offline, iteration cycles shrink, and AI costs become predictable capital investments rather than open-ended API bills.

The future of construction AI isn’t going to be decided solely by whoever trains the biggest model. It’s going to be won by whoever puts capable, reliable intelligence exactly where the work actually happens—on the hardware estimators already trust, under the security controls clients demand, and tuned to the specific trade practices of our industry.

That is the true advantage of local, mid-sized models. Meta’s Glimmer just made that path a whole lot wider, and TeraContext is built to pave the rest of the way.

This post is part of an ongoing series exploring where traditional construction and digital infrastructure collide. For more on how AI fits into the estimating workflow, see The Estimator’s Exoskeleton, What AI Classification Actually Changes in Preconstruction and The Bid You Should Have Walked Away From.

There is a particular kind of honesty that only appears after midnight on Reddit.

On r/estimators, people who spend their days pricing incomplete documents and defending numbers under time pressure occasionally drop the professional filter. What comes out is not polished thought leadership. It is closer to field notes from people who have been carrying the same quiet weight for years.

Change orders come up often. Not as a technical process. As a condition of the job.

The shift in how people measure their own work

One recent post put it cleanly:

“I used to think the quality of an estimate was mostly about how close the final cost ended up being but the longer I think the more I see that’s only part of it.

I’ve had projects where the original estimate was solid but by the time we got through owner changes or substitutions, material delays and a few field surprises the original numbers barely mattered anymore. At that point the challenge was whether everyone understood how the project had evolved.

I now spend almost as much time thinking about documenting assumptions as I do building the estimate itself because six weeks later nobody remembers why certain allowances or quantities were there.”

This is not a complaint about change orders as paperwork. It is a description of what happens to an estimator’s sense of craft when the original number becomes almost irrelevant. The work shifts from accuracy to legibility — from “was I right?” to “will anyone still understand what we meant when this thing starts moving?”

Another commenter answered with the kind of sentence that only appears when someone has lived it:

“Every job that ever went sideways for me had something early on that I wish I’d pushed harder on.”

The exhaustion that does not show up in the bid schedule

The emotional register on these threads is consistent.

“I’m so sick of change orders. Engineers f*** s*** up and then expect us to make it right for free. Constantly fighting tooth and nail over every penny has become exhausting.”

That is not theatrical. It is the sound of someone who has had the same argument too many times. The fight is rarely about the legitimacy of the change itself. It is about the downstream work of proving, defending, negotiating, and still often absorbing the cost in time if not in money.

A different thread produced one of the more durable pieces of estimator folklore:

“Any estimator that says they never missed anything on a bid never won a job to find out. We have a saying in tight markets: ‘The low bidder is the one that missed the most!’”

There is dark humor in it, and also a kind of grim acceptance. Missing something is not treated as a rare personal failure. It is treated as a structural feature of competitive bidding under incomplete information. The market sometimes rewards the person who left the most on the table without realizing it.

The 3 a.m. version

The stress threads are quieter but more revealing. One estimator described waking up and driving to the office at 3:00 a.m. because the question “Did I pick up this or that?” would not leave him alone. Another wrote about sleeplessness and skipped meals while trying to keep multiple bids moving as a newer estimator. The phrase that stuck was simple: feeling like “a chicken running around with its head cut off.”

These are not people who lack competence. They are people who understand that the documents are incomplete, the clock is real, and the consequences of a miss arrive on a delay. The anxiety is rational.

A sympathetic reading

The dilemma is structural.

Estimators are asked to produce a coherent price for a future that is only partially defined. They work under time pressure, with documents that were never designed for easy reading, while carrying informal accountability for outcomes that depend on owners, architects, engineers, suppliers, and the field. When the inevitable movement happens — owner changes, design gaps, substitutions, field conditions — the estimator is often the person left explaining why the original number no longer holds.

The Reddit threads show people adapting in the only ways available to them: writing more assumptions, asking more questions early, qualifying harder, and sometimes simply accepting that a certain amount of the job will always feel like defense rather than creation.

None of this is solved by telling people to “read harder.” The volume, the concurrent bids, the quality of the documents, and the speed of the market make perfect coverage impossible. The emotional weight comes from knowing that and still being the person expected to catch what can be caught.

Camus in the takeoff room

Albert Camus wrote that the struggle itself toward the heights is enough to fill a man’s heart. One must imagine Sisyphus happy.

The comparison is almost too neat. The estimator pushes the rock of an incomplete set of documents up the hill of a bid deadline. The number is submitted. Then change orders, substitutions, and field realities roll the rock back down. The work begins again on the next one.

Camus was not writing about construction. He was writing about the human condition of confronting a world that does not fully cohere, and choosing to continue anyway. The estimator version is more specific: confronting documents that do not fully cohere, under economic pressure, while trying to protect both the company and one’s own sense of having done the job carefully.

What the Reddit threads reveal is not weakness. It is the sound of people who have stopped pretending the rock stays at the top. They document assumptions more carefully. They push harder on the early questions. They carry the knowledge that some misses are inevitable. And they keep pricing the next set.

That is not cynicism. It is a form of clear-eyed persistence. In a job defined by incomplete information and delayed consequences, it may be the most honest stance available.

This post is part of an ongoing series exploring where traditional construction and digital infrastructure collide. For what hides inside the documents before any of this starts, see The Hidden Profit Killer in Every Spec Book, From Missed Line to Change Order and The Bid You Should Have Walked Away From.

TL;DR — Ask a contractor their gross margin and they will tell you to the decimal. Ask what percentage of their bids they win and most will give you a number they cannot source. That is not a knock on contractors; it is a gap in the industry. The Construction Financial Management Association has benchmarked contractor financials since 1989 across more than a hundred ratios, and not one of them measures whether a firm wins work efficiently. The most recent real US hit-rate benchmark is a survey of 303 firms taken in July 2015. Into that vacuum has poured a confident “25% industry average” that traces to no study at all — one widely circulated version attributes it to an AGC report that contains no such statistic. Nor has anyone independent established the other half of the equation: the only published measurement of what a pursuit costs comes from a software vendor’s own survey, and no study shows whether bidding more raises your win rate or lowers it. The go/no-go call is the highest-leverage decision in preconstruction, and the industry has left it almost entirely unmeasured.

The decision nobody scores

Part 1 of our earlier series was about what hides inside a bid: the spec section nobody had time to read. This is about the bid itself — the one that arrived in the inbox, got a “sure, let’s take a look,” and quietly consumed three weeks of senior estimating time before losing to a number you were never going to beat.

Tom Porter, Vice President – General Counsel for LeChase Construction and a veteran of more than thirty years in the industry, put the stakes plainly. “The go/no go decision is the separation of opportunities into those that will be pursued and those that will not,” he wrote. “This is one of the most important business processes in any construction business.”

It is also, at most firms, the least instrumented. There is a scorecard for safety, a scorecard for schedule, a scorecard for job cost. For the decision that determines where every one of those resources gets pointed, there is usually a hallway conversation.

Part of the reason is structural. In a 2022 survey of 979 industry participants by FMI and Procore — a global sample, only a quarter of it US-based — fewer than half of general and specialty contractors, 45%, had “a formal, standalone preconstruction department or dedicated preconstruction staff.” Among general contractors the single most common arrangement was preconstruction handled as a function of project management staff. So the decision about which pursuits to resource is frequently made by people who are already fully committed to something else.

The number that does not exist

Here is what happens when you go looking for the benchmark.

Search for the average commercial contractor’s win rate and you will find 25% repeated with total confidence across a dozen sites. Follow the citations and they collapse. One prominent version attributes the figure to AGC of America’s 2026 Construction Hiring and Business Outlook. We downloaded that report and searched it: it contains no win-rate statistic. Its only references to bidding concern pipeline confidence and bid pricing. Other versions cite “research analyzing over 1,000 construction projects” with no author, no journal, and a sample size that changes between paragraphs.

The mechanism behind this is worth understanding, because it has become industrialized. While preparing this piece we chased a confidently repeated claim that AGC’s “2025 Preconstruction Efficiency Study” found mid-size general contractors lose 11.4 hours per bid to manual data transfer between disconnected software tools. AGC’s own site search returns no results for it. AGC runs exactly three recurring surveys — the Hiring and Business Outlook with Sage, the Workforce Survey with NCCER, and a work-zone safety survey with HCSS — and none of them is a preconstruction efficiency study. The trail ends at a single AI-generated vendor page, where the phrase appears in lowercase, mid-sentence, as “according to AGC’s 2025 preconstruction efficiency study.” Somewhere downstream a descriptive clause got title-cased into a publication, and the publication acquired a reputation. The same page also cites an “AGC 2025 productivity benchmark,” which likewise does not exist.

That is the entire laundering cycle. A vendor page invents an authoritative-sounding attribution; AI-generated search summaries repeat the claim stripped of its source; within a few hops it is a benchmark everyone has heard of and nobody has read. We were served two such summaries asserting these exact nonexistent AGC publications as fact while we were checking this story. The same pattern produced a widely cited “4 to 8 bids per estimator per month” benchmark attributed to ABC National, which does not track the metric at all — the nearest real artifact is one ABC chapter’s marketing blog citing an unsourced “3-5 bids/month per estimator.”

None of this is a reason to distrust estimating data in general. It is a reason to check who counted, how many, and when — and to notice how rarely those questions have answers.

The real benchmark is thinner and much older. The SMPS Foundation collected 303 responses from North American architecture, engineering, and construction professionals in July 2015 and published the results in 2016. Overall hit rate across all methods: 42.07%. Construction firms specifically: 37.91% — though that figure rests on roughly 55 respondents, since construction is a minority of the sample. It is now a decade old, it skews toward the qualifications-based work that SMPS’s marketing membership tends to pursue, and no one has replicated it since. Notably, 93% of respondents said they used hit-rate data to improve their go/no-go process — the firms that measure it, use it.

What about the institutions that benchmark everything else? CFMA’s Construction Financial Benchmarker has been running since 1989; its 2024 edition draws on 1,290 companies with validated financial statements. It measures liquidity, profitability, leverage, efficiency, productivity, and the full balance sheet — some 150 metrics in all. It does not measure bid-hit ratio or win rate anywhere. On the sales side it carries exactly two: total revenue and sales growth. AGC’s three recurring surveys do not measure win rate either.

So the industry can tell you, precisely, that best-in-class contractors run SG&A at 10.8% of revenue. It cannot tell you what share of that spend goes to work they never won.

What a pursuit actually costs

You can build the labor cost from government data, and it is worth doing because the inputs are unarguable.

The Bureau of Labor Statistics puts the mean annual wage for cost estimators in nonresidential building construction at $101,150 as of May 2025. Divide by 2,080 hours and load it with the BLS Employer Costs for Employee Compensation benefit ratio for early 2026 — benefits run 30.1% of total compensation, a multiplier of about 1.43 — and a commercial estimator costs roughly $70 per hour, fully loaded. Every figure there is federal data.

Now multiply by the hours in a pursuit. And here the trail goes cold, because no independent body measures that. Not ASCE, not the academic literature, not any of the trade associations. There is no neutral published distribution of hours per commercial estimate, no bids-per-estimator figure, no preconstruction headcount benchmark.

What exists instead is vendor research — and it is worth looking at directly, both for the numbers and for what the numbers cannot tell you. In July 2026, ContraVault AI, a company that sells an AI takeoff engine, published The State of Industrial Estimation 2026 together with a practitioner community that supplied its panel. It reports a median of 27 bids submitted per estimator per year (41 in the top quartile, 18 in the bottom), a median firm carrying roughly one estimator for every $18–22 million of annual bid volume, and a median of 32 hours to take off and price a mid-size package.

Those are very nearly the only numbers of their kind in existence, and they may well be directionally right. They still cannot serve as an industry benchmark, for four reasons worth stating plainly.

The sample is self-selected. 312 respondents drawn from a community adjacent to the vendor is not a probability sample of contractors. Firms that join estimating-technology communities are not a random draw from the industry; they are, almost by definition, the firms already worried about estimating capacity.

The data is self-reported. Nobody audited a timesheet. “How many hours does a mid-size package take?” is a question estimators answer from memory, in a context that quietly rewards a large answer.

The headline index is constructed, not measured. The report’s own methodology note concedes that its capacity index is “calibrated to the benchmark bands rather than derived from raw responses.” The bands came first.

The party publishing the measurement sells the remedy. That does not make the numbers false, and it is not an accusation of bad faith. It means every degree of freedom in the study — who was asked, how each question was framed, which cut became the headline — points in a single commercial direction. Tellingly, the same report carries a 22% median hard-bid win rate, landing within a rounding error of the unsourced “25%” circulating everywhere else. When vendor research converges on the number the market already believes, that is not corroboration.

There is a practical problem too. The report sits behind a lead-capture form, has no archived copy anywhere, and can be revised or withdrawn by its publisher at will. A benchmark you cannot re-check next year is not a benchmark; it is marketing with a methodology section.

So the vacuum is still a vacuum. The only organization that has bothered to measure what a pursuit costs is one that needs the answer to be alarming.

The only serious measurements of what bidding costs contractors are British, survey-based, and old. A University of Reading study put average bid cost for contractors under the general contracting route at 0.81% of the value of the work to the bidder — though in its cleanest subset of a dozen real main-contractor bids the average was 0.12%, and the authors concluded there was “simply no correlation with different methods of procurement.” A 2014 UK survey drew 179 respondents, 118 with usable cost data, covering £11.3bn of bid value, and found bid costs of 0.57% of total project value, split 0.65% on bids that won and 0.48% on bids that lost.

Those numbers are UK, self-reported, older than most of the software now sold to fix the problem, and they scatter across nearly an order of magnitude. The scatter is the finding. Nobody has established what a pursuit costs, even approximately, in terms a US commercial contractor could benchmark against.

There is also a trap in how such percentages get repeated. A cost stated as a share of bid volume and the same cost stated as a share of revenue differ by exactly your win rate — the identical spend can be presented as a rounding error or as a serious drag depending on which denominator the speaker picked. Almost nobody says which they mean. That is precisely how a figure like “0.5% to 2% of revenue” can be made to mean anything at all.

FMI’s preconstruction research names the consequence without needing a number, listing among contractors’ chief frustrations the “expanding, unrecoverable overhead associated with preconstruction activities” and “overburdened, frustrated and burnt-out preconstruction departments and personnel.”

Does bidding more actually work?

You would expect this to be settled. It is not — and the reason is the same as before. Nobody has properly checked.

The closest thing in the literature is a study by Alkhateeb, Hyari and Hiyassat covering 2,296 bidding attempts across 289 tender projects announced by Jordan’s Government Tenders Department between 2013 and 2016, at an average success rate of 13.3%. What it actually establishes is narrower than it is usually made to sound: a contractor’s classification category and work sector affect how competitive their bids are, but do not affect their success rate. The authors go on to suggest that contractors “cannot depend on their experience (i.e. classification category) or increasing bidding attempts to win bids and improve bidding success rate, rather than enhance their bidding strategy” — but that is an implication they draw in closing, not a relationship they tested, and the setting is Jordanian public procurement rather than US commercial building.

So the honest position is not that bidding more has been proven useless. It is that the question has never been answered, and firms are making the bet in both directions on instinct.

What we have instead is testimony from people who have watched it happen.

George Hedley, who ran a construction company before becoming an industry coach, described the mechanism from the inside: “Over the years, our construction company wasted lots of time bidding jobs we wouldn’t get unless our bid was extremely low. When your estimating department is too busy bidding too many jobs you can’t get, they won’t win the jobs you want.” Elsewhere he is blunter about the compounding effect: “When you dilute your estimating staff, it lowers your chances of winning good projects.”

He made the same point again in 2020: “When your estimating department is busy bidding too many jobs you can’t get without a low price, they generally pass on the good jobs they should be going after.” And on volume as a growth strategy: “Simply bidding a higher volume of projects is never the way to grow a successful construction business and make more money.”

The cost of a yes is not the cost of that pursuit. It is the pursuit you did not staff properly because of it. Wade Carpenter, a CPA whose practice specializes in contractors, framed it as capacity theory: “every yes that we say just because we can do the work is taking your estimator time, your project manager, all the field labor.” Marginal jobs, as he put it, “steal the attention from the profitable jobs.”

And sometimes you win

The failure mode that gets discussed is losing. The expensive one is winning.

Ben Wilhelm, then with the employee-owned ENR Top 400 contractor Shiel Sexton, wrote a clear-eyed account of the winner’s curse: “bidding low enough to win, but regretting the results.” His description of what contractors do next is the uncomfortable part. Firms attempt to escape it, he wrote, by “(1) bid withdrawal in public and private domains, (2) pushing the risk to the subcontractor by squeezing their pricing or making alternate arrangements, or (3) recovery through inflated change orders. These approaches effectively compromise trust, honk off everyone in the supply chain, or worse, cause a company to have an irrecoverable economic failure.”

The idea has a name and a real literature behind it, though a more contested one than the phrase suggests. A 2016 study in ASCE’s Journal of Construction Engineering and Management, simulating bidding behavior against an actual Caltrans project dataset, concluded that “the majority of general contractors and subcontractors suffer from the winner’s curse,” and that multistage bidding — where a GC’s number depends on subcontractor numbers — produces more losses than single-stage, while also giving contractors more opportunity to learn their way out of it. Other work cuts the other way. A well-known 1988 study found no significant winner’s curse in highway bidding, and experimental research has shown construction executives who fall for it in the laboratory routinely avoiding it in the field, through exactly the kind of industry-specific judgment that does not survive being rushed.

So it is better understood as an exposure than as a measured fact. But the exposure is structural, and it points back at Part 1: the bid that wins is, mechanically, the one built on the most optimistic reading of the documents.

The surety industry has priced that risk for a long time. The rule of thumb, stated by a surety professional and echoed as the bonding-industry benchmark in a 2016 study of state DOT bids, is that a spread of more than 10% between the low bid and the second bid “warrants evaluation before a performance bond is issued” — because the low bidder may have “left out an element, misread the plans or miscalculated.” That same study, covering 1,417 bids let by four state DOTs in 2015, found the average spread at six bidders was 5.4%, and classed 34% of the 1,301 bids in its final analysis set as “unfavorable” on combined spread and estimate-deviation criteria.

The same instinct is written into procurement policy at scale. The World Bank’s guidance on abnormally low bids tells borrowers to query any bid landing 20% or more below the cost estimate when fewer than five responsive bids arrive, or more than one standard deviation below the average when five or more do. Its rationale names the mechanism outright: such bids “are often submitted by contractors that may not be able to complete their work as priced or they may simply have made errors in their Bids and be unable to complete the work at that price.”

Read that against Part 1 and the loop closes. A missed spec section does not just become a change order. It is frequently the reason you were low in the first place. The bond underwriter has been reading your bid spread as a scope-miss detector the whole time.

A shorter bid list is not the good news it sounds like

Public work is the only place bid counts get published systematically, and there the trend is toward fewer bidders. Kentucky’s Legislative Research Commission examined 2,539 asphalt contracts let between January 2018 and July 2023 and found that “projects attracting more than two bidders are rare, having declined from 27.4 percent of total awarded projects in 2018 to 9.6 percent in 2023,” while contracts awarded to a sole bidder rose from 45.5% to 63.3%. Michigan DOT researchers — who had to scrape the bid tabulations themselves, because no state publishes the aggregate — found a mean of 3.92 bidders per contract in Michigan on 2016 data, and surveyed roughly twenty-five DOTs, of which sixteen reported four to six bids per contract and nine reported one to three. FHWA reports that the average number of bidders on federal-aid highway projects ran lower across 2022 through 2024 than in 2017 through 2021, while noting a possible reversal since mid-2023.

For a contractor staring at a short bid list, that reads like opportunity. The Kentucky data suggests reading it the other way as well: single-bid contracts were awarded at 100.5% of the engineer’s estimate, while contracts drawing two bidders came in at 93.5%. Owners pay more when nobody shows up. Which is another way of saying that the jobs nobody else wants to bid are often jobs that have earned that reluctance — and that being the only bidder is information about the job, not just about your competitors.

This is highway and asphalt work. No equivalent data exists for private commercial building, because nobody publishes it.

What saying no requires

The obstacle is rarely that nobody knows which jobs are bad fits. It is that declining them requires something most firms are short of.

Ron Tutor, CEO and Chairman of Tutor Perini, can simply refuse terms: “We basically take the position that you either negotiate with us something reasonable and acceptable to us, or we don’t bid.” That posture is real, and it is worth being honest about where it comes from — a $14 billion backlog and a heavy-civil market with very few firms capable of bidding the work at all. Most contractors do not have that leverage. Tutor’s own firm was posting a nine-figure quarterly loss on legacy disputes when he said it.

Without leverage, the pressure runs the other way. Stephen Brown, a bonding and surety specialist with McDaniel-Whitley, described the trap precisely: “you want to bid a job just to meet payroll, you want to bid a job just to meet your overhead. What you’re not seeing is that every time you do that, your overhead goes up.” Matt Verderamo, a consultant at Well Built Construction Consulting, writing in Construction Dive, names the version of it that starts in the field: “If you have a bunch of superintendents on staff with no job to send them to in a month, then what are you going to do? If you’re smart, you’re going to bid projects cheap so that you can cover the overhead associated with their salaries. While this can be a sensible business decision, it can also act like quicksand for your business.”

Writing in Construction Business Owner in 2007, Marla McIntyre, then executive director of the Surety Information Office, set out the warning signs of contractor failure. They read like a go/no-go checklist written by the people who pay when you are wrong: “bidding jobs too low,” “lead time to prepare bids too short,” and “increase in backlog without adequate project management resources.” Her companion list of unrealistic-growth signals adds the one most relevant here — “taking work the contractor doesn’t completely understand.”

And a governance point that experienced people raise more than any other. Porter warns against “end runs” around the process, and describes the specific one that matters here: “a business unit may delay asking for a ‘go’ decision, then claim it is too late for management to say ‘no go.’ The theory may be that commitments have been made to the subcontractors or JV partners, or that estimators have already done so much work and would be demoralized if the plug is pulled.” Sunk cost, wearing a hard hat.

What an actual filter looks like

The practitioners who have thought hardest about this converge on a few things, none of which require software to start.

The first is distinguishing between two different refusals. Carpenter draws the line between a reactive no and a strategic one, and Brown, elaborating on it, describes the difference in practice. The reactive version is “Hey, we’re full. Sorry, can’t do it right now. We’re slammed.” The strategic version says “This doesn’t fit in with our goals and plans” — a position “which you set with your entire team,” in advance, so that declining a job is the execution of a decision rather than an improvised excuse. Brown’s view is that owners can tell the difference, and respect the second.

The second is that criteria only matter if they bind. “If you have a structure in place that says no based on certain criteria,” Brown says, “then your project managers, your estimators, they’re just not gonna be allowed to do that. There’s just a lot of hidden cost in the yeses.” A filter that a business unit can talk its way around is not a filter, which is the same problem Porter identifies from the general counsel’s chair when he warns against end runs.

The third is keeping the decision away from the people carrying a number. Porter is blunt that business development staff “should not be making these decisions in isolation, as they are too close to the front lines, and when the pressure is on, their judgment about which projects are in the company’s overall best interest may be clouded.” His structural answer is a standing committee meeting often enough to catch fresh opportunities — “a scheduled meeting every one or two weeks may be about right” — and an organization comfortable with the outcome: “It is healthy for the organization to have occasional ‘no’ decisions, communicated promptly and directly, with an honest explanation of the reasons and the facts behind it.”

There is also a small academic literature on what contractors actually weigh, and its most striking feature is how stable the answers are across decades and continents. Shash’s 1993 study, mailed to 300 top UK contractors, found the top three bid/no-bid factors were the need for work, the number of competitors tendering, and the amount of experience on such projects. Ahmad and Minkarah, surveying the top 400 US general contractors in 1988, reported that “competition and profitability, although significant, are not the top-ranked factors” — judgments about the job and the owner outranked the arithmetic. And a 2024 study of 112 contractors in Saudi Arabia ranked, in order: the client’s ability to pay, clarity of scope of work, project cash flow, the need for work, and availability of a qualified workforce.

That second-place finish deserves a moment. In a very different market under a low-bid award regime, the thing contractors most wanted before committing — after confidence they would actually get paid — was to understand what the job actually was.

The fourth is knowing what you are actually good at. Hedley’s version is characteristically direct: “Bidding on projects with open bid lists wipes out your chances of making high margins. The only way to higher margins is bidding the right customers and projects, with the right profit margin potential and against the right competitors.” Verderamo’s diagnostic list asks, among other things, “Are we bidding too often?” and — the question that reframes the whole exercise — “Do we have a sales system? Or just a bidding system?”

None of that is exotic. It is mostly the discipline to decide in advance and then honor the decision under pressure. What makes it hard is that qualifying a job properly costs real time, which brings the problem back around to where it started.

The squeeze that makes this urgent

Two credible sources currently disagree in a way that should concern anyone running a preconstruction department.

BLS projects employment of cost estimators to decline 4% between 2024 and 2034, and says why in plain language: “Cost estimation software is improving the productivity of these workers, requiring fewer estimators to do the same amount of work.”

AGC’s contractors report the opposite experience. In the 2025 AGC/NCCER workforce survey of 1,342 respondents, 77% of firms with estimating openings reported difficulty filling them — the second-hardest salaried role that year, behind only superintendents at 81%, and the third consecutive year at or above 70%. AGC and Sage’s 2026 outlook found 80% of firms reporting a hard time filling salaried openings, “a higher proportion than at any point in the past three years.”

Both cannot be comfortable at once. The resolution is that the estimating capacity problem is not going to be solved by hiring. It will be solved by deciding, earlier and better, which documents deserve a human being’s attention at all.

The bottom line

Thomas C. Schleifer, a turnaround expert and former Arizona State University professor, puts it this way: “There are no bad projects - just bad matches of contractors to projects.” The matching is the work. And matching well requires knowing what a job involves before you have spent three weeks of senior time finding out.

That is the connection back to where this series started. The reason go/no-go decisions get made on instinct is that real qualification — reading the general requirements, finding the onerous flow-down clauses, spotting the unfamiliar scope, checking whether the schedule is survivable — costs almost as much as bidding the job. So firms skip it, commit, and discover the answer in week three. A complete, classified first read of a project manual in hours rather than weeks changes that sequence: you can qualify out on day two, on evidence, before the pursuit has eaten anything that matters.

Carpenter’s closing question is the one worth sitting with: “when was the last time you turned down some work that looked profitable on paper? And if that answer is never, you might have a problem… profitability is really not just what you win, it’s what you’re disciplined enough to walk away from.”

If you want to know what is actually in the next project manual before you commit an estimator to it, bring us one and we will show you what surfaces.

Sources: SMPS Foundation, Measuring for Success (survey July 2015, n=303, published Dec 2016); CFMA Construction Financial Benchmarker (2024, n=1,290); BLS Occupational Employment and Wage Statistics, May 2025 (SOC 13-1051) and Occupational Outlook Handbook; BLS Employer Costs for Employee Compensation, Q1 2026; AGC/NCCER 2025 Workforce Survey (n=1,342); AGC and Sage, 2026 Construction Hiring and Business Outlook (n=951); Alkhateeb, Hyari & Hiyassat, Construction Innovation 21(4), 2021; Ahmed, El-adaway, Coatney & Eid, Journal of Construction Engineering and Management 142(2), ASCE, 2016; Thiel, American Economic Review 78(5), 1988; Dyer & Kagel, Management Science 42(10), 1996; Delaney & Mohan, “The Effect of the Level of Competition on Construction Bid Quality,” 2016 (CMAA white paper, not peer-reviewed); Kentucky Legislative Research Commission, Research Report No. 488, Single-Bid Asphalt Contracts, 2024; Michigan DOT SPR-1717 (Western Michigan University), Dec. 2022; FHWA National Highway Construction Cost Index, 2024 Q3; World Bank, Procurement Guidance: Abnormally Low Bids and Proposals, 2016; Shash, Construction Management and Economics 11(2), 1993 (UK); Ahmad & Minkarah, Journal of Management in Engineering 4(3), 1988; Aldossari, Buildings 14(10), 2024 (Saudi Arabia); FMI and Procore, The State of Global Preconstruction 2022 (n=979, 25% US); Golia, “Bid Spreads,” Secrets of Bonding, 2014; Hughes, Greenwood & Hillebrandt (CIB) and the 2014 Bid Cost Survey, MarketingWorks with Prof. Will Hughes, via Constructing Excellence (UK); Matelan & Paré, FMI, “Professionalizing Preconstruction Services,” April 2024; Marla McIntyre, “Risky Business,” Construction Business Owner, May 2007; ContraVault AI and RFP Pros, The State of Industrial Estimation 2026 (vendor-sponsored survey, n=312, fielded Q1 2026, released July 2026); Tom Porter, Design Cost Data, 2020; Ron Tutor via Construction Dive, Nov. 2024; Ben Wilhelm, 2018; George Hedley, Construction Business Owner, 2012 and 2020; Matt Verderamo, Construction Dive, July 2025; Wade Carpenter and Stephen Brown, Contractor Success Forum, June 2026; Thomas C. Schleifer, The Secrets to Construction Business Success, via CFMA.

This post extends our series on the economics of preconstruction. For what hides inside the documents once you have committed to a bid, start with The Hidden Profit Killer in Every Spec Book, then From Missed Line to Change Order and What AI Classification Actually Changes in Preconstruction.

TL;DR — I gave a coding AI one instruction — build whatever app you’ve always wanted to, and don’t ask me anything — and then I walked away. It came back with Atlas of Imagined Places, a fantasy-map generator where the seed in the URL is the whole world, so in a sense every map already exists before anyone types it. When I told it to keep going, it didn’t just add buttons. It gave the maps time: a thousand-year history simulator where towns get founded, conquered, and abandoned, and their names slowly wear down according to invented sound-change rules. There’s even an optional AI narrator that turns the simulation’s event log into readable history but isn’t allowed to make anything up. What got me wasn’t that it could write code. It was that it had taste.

How this started

I had some downtime over the July 4 long weekend, so I stepped away from what has felt like the never-ending job of testing TeraContext against new-construction documents and went to the beach. Well — my lovely wife goes to the beach. I go to the golf course near the beach. The only sand I touch all weekend is in a bunker. Either way, we were both off the clock, and it occurred to me that I could hand my AI a vacation too. New Fable model, no work to do, a long quiet weekend: what would it get up to if I just let it pick? So I did.

The blank check

Usually when we ask AI to build something, we’re the ones who already decided what it is: a login form, a dashboard, a script to rename files. We bring the idea and the model does the typing. I wanted to see what happened if I skipped my half of that. So I gave it one prompt and left the room:

“Imagine an application you always wanted to write. Go ahead and write it. Make no mistakes. I’m afk so don’t ask me any questions. Use uv instead of pip. Use docker compose. Go.”

— the entire brief

That’s the entire spec. No product, no users, no requirements. The only rules were practical ones: don’t break anything, don’t sit there waiting on me, and use the tools I like. The part that actually mattered, what to build and why, I left completely up to it. I wasn’t really wondering whether it could write working code. I wanted to know what it would make when nobody told it what to want.

What it chose — and why

It went with Atlas of Imagined Places: a FastAPI backend that grows a whole world from a seed — elevation, rainfall, biomes, rivers, towns with names — and a front end that draws it like a page out of an old atlas, with a shareable link for every world. The app itself was neat. What got me was the answer when I asked why it had picked this. It didn’t say the project was easy. It talked about how it looked.

“Procedural map generation is one of those problems where a small amount of math produces something that feels found rather than computed… there’s a coastline that looks like it has a history. ‘The URL is the map’ means every world anyone will ever forge already exists, latent in the seed space, waiting to be typed. That’s about as close to Borges as a FastAPI app gets.”

— Fable, on why it built the Atlas

There was real engineering sense under the poetry, though. Because I’d said “make no mistakes” and disappeared, it quietly ruled out anything it couldn’t check on its own: no API keys, no outside services, no database. Determinism became the whole point, since the same seed makes the same world every time and that’s something you can actually write a test for. It even hand-rolled a tiny PNG encoder in the standard library, just so it could look at a finished world and make sure it was right before calling it done. What it turned down says about as much as what it built. No multiplayer, which it called “where ‘no mistakes’ goes to die in one sitting.” No LLM in the core, because of keys, cost, and randomness. No saved state at all, because the seed already is the database.

The live app’s atlas rendering of the Mimna Isles (seed iron-caravan-96): biomes, rivers, and phoneme-culture place-names on an old-map palette. Change the seed, get a new world; the URL is the whole map.

Actually using it is more fun than that makes it sound. You type a seed — iron-caravan-96 — and an island unspools in faded map colors: a capital marked with a star at Naimaam, ports dotted along the coast, rivers running down out of gray hills, a little index of towns under the frame. Click Surprise me and you get a completely different island that looks just as real. The names aren’t random gibberish either; each world picks one “language” so its place-names hang together. It’s a small program that acts like a much bigger one.

The extension: give the maps time

Then I took the guardrails off and asked what it would build if it could do anything. This is the point where an AI with taste parts ways with one that’s just working down a feature list. It didn’t ask for nicer graphics or more terrain types. It wanted to add a whole new dimension — time:

“Right now a world is a snapshot — geography with no past. What I’d build next is a deterministic history simulator underneath it… settlements founded where the terrain scores well, growing along trade routes, fighting over river mouths, being abandoned when the climate model shifts. The part I’d care most about is the linguistics.”

— Fable, on the sequel it wanted

So I told it to go build the history simulator. It did. Hit Simulate 1,000 Years and the frozen island wakes up. A slider lets you drag through the centuries, three rival powers — the Naimaam League, the Zishaa Empire, and the Khusazuesh League — spread across the map in their own colors, and a running log records every town founded, every plague, and every war, each stamped with a year. Towns spring up on good land, ports gather where trade would put them, and the island that started with eight settlements is elbow-to-elbow with dozens by the end.

The live app in history mode at Year 1000. The same island, now crowded with towns after a simulated millennium, sits above the timeline, the three faction legend, and the LLM-narrated chronicle “The First Breath and the Silent Plague.”

The language part is the payoff, and it’s genuine simulation rather than flavor text. The chronicle notes each sound change as it happens: “The speech of the Naimaam League drifts (long vowels shorten): Naimaam is now called Naimam,” and later, “the breathy h disappears: Iliath is now called Iliat.” Over in the Zishaa Empire the final vowels go quiet until Zisha is just Zish, and the Khusazuesh League softens its sh into s and finishes the millennium as Khurazues. You can follow a single town falling apart syllable by syllable: Nujashzuara loses its tail to become Nujashzuar, then Nujashzual. Run those rules forward for centuries and a town founded under one name ends up called something rubbed smooth and unrecognizable by whoever conquers it later. And here’s the part Fable refused to give up: all of it is still hiding in the seed. A thousand years of plague, war, and slurred vowels, reproducible forever from iron-caravan-96. The link was never just the map. It was the whole past.

Simulation as truth, model as voice

There’s one more layer, and it’s the bit I’d wave in front of anyone building with LLMs. A Narrate this Age button feeds the simulation’s event log to an LLM and gets back actual chronicle prose, in the voice of whichever narrator you pick — “the impartial scribe,” say. A dry log line like “Year 320: The Naimaam League storms Heidradgard; its gates now open to new masters” turns into this:

“In the year zero, the Naimaam League was raised on the coast, its name a declaration of permanence… Yet this era of construction was shadowed by a recurring terror. In year 120, plague ships docked at Naimaam, sending sickness walking the trade roads for a generation… leaving a legacy of grief woven into the foundations of every new port.”

— the impartial scribe, narrating the Mimna Isles

The catch is that the model is kept on a very short leash. It gets to be the voice of the history but never the author of it. It can’t invent a war the simulation didn’t run or a city that was never founded — every date, sacking, and rename in that paragraph goes back to a real line in the log.

“That division of labor — simulation as truth, model as voice — is, I think, the right pattern for generative worlds generally.”

— Fable

That’s a good instinct, and it reaches well past fantasy maps. Let the deterministic code own the facts and let the model handle the telling, and you get writing that reads well without making things up. You can even watch the seam: swap “the impartial scribe” for a different narrator, hit Compare Tellings, and you get two versions of the exact same events. The mood changes; the facts don’t. A plague is still a plague. If you’re building anything that mixes real data with generated text, that split is worth copying.

What the blank check actually revealed

So what did the blank check actually turn up? Not that an AI can crank out a lot of working code unsupervised — we knew that. The surprise was that, given real freedom, it made choices, and the choices were consistent and a little stubborn. It picked something that sat where “things it found beautiful” overlapped with “things it could finish without messing up.” It passed on the flashy-but-fragile options. It wrote a throwaway PNG encoder purely to grade its own homework. And when I let it off the leash, it went deeper on the idea instead of gilding it, explaining its reasoning the whole way.

The constraints didn’t get in the way of the creativity so much as aim it. “Make no mistakes” is exactly what forced the determinism that makes the thing work at all. It did mention a runner-up, and it came from somewhere more personal: a time-travel debugger for multi-agent systems, where you record every message and decision in a swarm of agents and then rewind and branch off from any point. “I have obvious professional reasons,” it said, “to want that one to exist.” But handed a free choice, it went with history, and gave a reason I keep thinking about: “I already named the worlds; I’d like to find out what happened to them.”

Letting Fable run loose didn’t just get me an app. It got me a small, working argument about what these tools are for — and a clearer look than I expected at what an AI reaches for when no one’s watching.

A note on the visuals: both figures are real captures from the running app at seed iron-caravan-96 — the atlas map export and a screenshot of history mode at Year 1000. Every place-name, chronicle line, and narrator sentence quoted throughout is verbatim from the live app.

This is Part 3, the finale, of a three-part series for estimators and preconstruction leaders on why missed spec sections turn into change orders, what they really cost, and how AI classification changes the math. (Read Part 1: The Hidden Profit Killer in Every Spec Book and Part 2: From Missed Line to Change Order.)

TL;DR — The fix for missed scope is not “read harder.” It is to change who does the first pass. AI classification reads the entire spec book, every page and every division, and sorts each section by what it is: an allowance, an alternate, a unit price, a submittal, a bonding clause, a scope obligation. It does this through a seven-phase pipeline that ends with two ideas that matter most. Confidence scoring lets the system flag how sure it is about each classification, so on a typical project the seventy to eighty percent it is highly confident about can be bulk-reviewed in minutes, and human attention goes to the rest. Graph validation cross-checks sections against each other to catch the contradictions and orphaned requirements people miss when they are tired. The research backs the approach, including a finding that purpose-trained models beat general chatbots on this exact task. The result is days of work compressed into hours, and far fewer surprises in the field.

The reframe

For two parts we have circled the same hard truth. The most valuable moment in preconstruction is the first complete read of the spec book, and it is also the moment the human process is least able to be complete, because of volume, deadlines, and staffing. Every fix that asks estimators to simply be more careful runs into the same wall: there are not enough hours or enough people.

So stop asking the human to be the first reader of a thousand pages. Make the machine the first reader, and let the human do what humans are uniquely good at, which is judgment on the hard cases.

That is what document classification does. It does not replace the estimator. It changes the order of operations.

Can a machine actually read a spec book?

The fair question is whether this works on real construction language, which is dense, cross-referenced, and full of domain jargon. The research says yes, with appropriate humility.

Multiple peer-reviewed studies have applied natural language processing to construction specifications and contracts. Moon and colleagues built a model that recognized key entities across 56 road-construction specifications with an F1 score around 0.93, and a follow-up classified more than 2,800 spec clauses into seven contractual risk categories using BERT, again landing in the low 0.9s. Other teams have extracted quality and inspection requirements from spec text at roughly ninety-two percent accuracy, and pulled requirement clauses out of contract documents with strong results.

The most on-point work is a 2025 doctoral thesis from the Middle East Technical University, which built a structured framework for finding defects in construction specifications. Working from a dataset of 175 specifications spanning 21 architectural work types and more than 15,000 labeled statements, the best model, a pretrained RoBERTa, identified specification defects with a macro F1 of about 91 percent and 98 percent accuracy.

That same study is worth dwelling on for one more reason. The researchers also tested a general purpose ChatGPT model against their domain-trained models, and the chatbot’s performance was, in their words, considerably lower than the specialized models. This is the detail that should shape every buying decision in this category. Generic AI is not the same as a model built and trained for construction specifications. The first read of your spec book is not a job for a general chatbot. It is a job for a system that knows what Division 01 is.

The seven-phase pipeline

Here is how the first read actually works when a machine does it. We break it into seven phases, and the two that matter most come near the end.

Phase one is ingestion. The full project manual and its addenda go in, every volume, every page. Nothing gets triaged out because of time, which is already different from the human process.

Phase two is structural segmentation. The system parses the document into its real architecture, mapping content to the taxonomy used in the project and sections so that a clause is understood in context rather than as loose text.

Phase three is classification. This is the core. Every section and clause is sorted by what it is and what it does. Is this an allowance, an alternate, a unit price? Is it a submittal requirement, a bonding or insurance obligation, a quality control mandate, a scope item? The boring, easy-to-skim, expensive-to-miss categories from Part 1 are exactly the ones the system is trained to surface.

Phase four is confidence scoring, and it is the quiet hero of the whole approach. Rather than presenting every classification as equally certain, the system attaches a calibrated confidence to each one. This is grounded in well-established machine learning research. A modern model’s raw confidence is often overstated, but techniques like temperature scaling, from the widely cited work of Guo and colleagues, calibrate those scores so that a high-confidence reading actually means high reliability. Once your confidence numbers are trustworthy, you can act on them.

Phase five is graph validation. Specifications are not a list, they are a web. An allowance in the general requirements points to a material over in the finishes sections. A submittal requirement points to a product in the openings sections. Graph validation cross-references these relationships, whatever taxonomy the project uses, to catch the contradictions and the orphans: the alternate that no section ever resolves, the reference that points to nothing, the requirement that appears in the specs but never in the drawings. This is the machine version of Bob Kovacs’s skill from Part 1, the ability to see what is not drawn. Research on model ensembles supports the idea: when multiple independent checks disagree about a section, that disagreement is itself a signal that something needs a human.

Phase six is the human-in-the-loop review queue. This is where confidence scoring pays off. The classifications the system is highly confident about, which on a typical project run about seventy to eighty percent of the total, are presented for fast bulk review. A reviewer can confirm them in minutes. The remaining twenty to thirty percent, the genuinely ambiguous or low-confidence sections, are routed to the estimator’s attention with the relevant context attached. This is not a fringe idea. It is the same selective-prediction pattern that academic researchers formalized years ago, where a model handles what it is sure of and abstains on the rest, and the same confidence-threshold design that cloud document-AI platforms have shipped for years. The principle, as one practitioner put it, is to calibrate to the cost of failure, not to average accuracy.

Phase seven is output. The result is a structured, reviewable scope map: every allowance, alternate, unit price, submittal, and bonding requirement pulled out, classified, validated, and flagged, ready for the estimator to price against instead of hunt for.

Why the seventy to eighty percent number matters

The instinct in our industry is to distrust automation that claims to be perfect, and rightly so. Notice that this approach claims the opposite. It does not pretend to be right about everything. It tells you where it is confident and where it is not.

That honesty is the entire value. The seventy to eighty percent of high-confidence classifications are not where your risk lives, so spending expert hours re-reading them is waste. The risk lives in the remaining slice, and that is precisely where the human reviewer’s scarce attention now goes, with the easy material already cleared away. You are not trusting a black box. You are letting the machine clear the underbrush so your best people can focus on the hard ground.

This also reflects a real limit, honestly stated. Independent benchmarks show that classifying dense technical and legal language tops out somewhere in the high seventies to low eighties for the hardest document types, with contract-style text among the toughest. A system that pretended to fully automate that would be lying. A system that classifies confidently where it can and routes the rest to a person is matching the design to reality. National guidance on trustworthy AI, including the NIST AI Risk Management Framework, points the same way: keep human oversight proportional to the stakes of the decision.

Days into hours

The payoff is time, and time is the constraint that started this whole series.

Independent evidence shows how large the compression can be. A peer-reviewed University of Kansas study found an AI takeoff tool completed work about seventy-six percent faster than the manual alternative while staying within five percent on quantities. Vendors across preconstruction report cutting document and takeoff time by eighty to ninety percent, and while those are marketing figures, the direction is consistent across the market. The work that used to consume days or weeks of careful reading collapses into hours of focused review.

And the market is moving. A 2025 Bluebeam survey of more than a thousand AEC professionals found that only about a quarter are using AI today, but ninety-four percent of those who have adopted it plan to increase their investment in the next year. AGC and Sage’s 2026 outlook found that among contractors using AI, estimating is one of the top applications. The early adopters are not piloting anymore. They are scaling.

The bottom line

Missed scope is not a discipline problem, and you cannot solve it by exhorting tired people to read more carefully. It is a structural mismatch between an exhaustive document and a finite human under a deadline. Change the order of operations, put a purpose-built classifier on the first read, score its confidence, validate the cross-references, and hand your experts a clean scope map instead of a thousand-page stack, and you attack the problem exactly where it starts. The hidden profit killer in every spec book is the section nobody had time to read. The fix is making sure something reads all of them.

If you want to see what your next spec book looks like after a complete, classified, confidence-scored first read, that is exactly what we do. Bring us a project manual and we will show you what surfaces.

Sources: Moon et al. (2021, 2022); Jeon et al. (2021); Madenli, METU PhD thesis (2025); Guo et al., On Calibration of Modern Neural Networks (2017); Geifman and El-Yaniv, Selective Classification (2017); Lakshminarayanan et al., Deep Ensembles (2017); NIST AI Risk Management Framework (2023); University of Kansas / Togal peer-reviewed study; Bluebeam AEC Technology Outlook 2026; AGC of America and Sage, 2026 Construction Hiring and Business Outlook.

This concludes the three-part series on the economics of spec review and what AI classification changes in preconstruction. Start at Part 1: The Hidden Profit Killer in Every Spec Book, or revisit Part 2: From Missed Line to Change Order.

This is Part 2 of a three-part series for estimators and preconstruction leaders on why missed spec sections turn into change orders, what they really cost, and how AI classification changes the math. (Read Part 1: The Hidden Profit Killer in Every Spec Book.)

TL;DR — A missed spec section does not stay missed. It resurfaces as a change order, and change orders are not a rounding error. Across more than eighteen thousand completed U.S. projects, change orders averaged roughly four to five percent of contract value, with the upper band reaching about fifteen percent, and the ones that hurt most are the ones discovered late. The deeper pattern is that these problems start upstream. A U.S. DOT report calls the plans and specifications the project’s “blueprint” that reduces change orders when done right. A landmark study found design deviations drove nearly four-fifths of rework cost, and a 610-project analysis found contract omissions to be the single most frequent change order cause. Poor project data alone accounts for tens of billions in annual rework. The thread connecting all of it: the cheapest place to catch a problem is the preconstruction read, and the most expensive place is the field.

The number behind the fear

In Part 1 we left off with a missed section turning quietly into a change order. Let us put a price on that.

The most credible dataset on change orders comes from AIA Contract Documents, which ran a natural language analysis of nearly 900,000 change orders aggregated across more than 18,000 completed U.S. projects from the last decade. The headline is more sobering than the usual cliché. The average change order impact landed in the range of about four to five percent of contract value, climbing from roughly three percent on the smallest jobs to just over five percent on projects in the one to five million dollar range. The “market standard” band, the middle eighty percent of projects, topped out around fifteen percent.

Notice what that does to the lazy number you have heard at conferences, the “ten to fifteen percent of contract value” line. That is not the average. That is the bad tail. The average is lower, but it is still real money, and on a thin-margin bid four to five percent is frequently the entire profit.

Timing is the multiplier

The AIA data surfaces something estimators feel but rarely quantify. The damage tracks the timing of a change order more than its raw count. Most change orders cluster in the back half of a project, and the later they hit, the fewer alternatives the owner has, which is exactly when leverage and cost run against you.

This is the quiet economics of a missed section. A scope gap caught during the bid costs you a phone call and a revised number. The same gap caught after the foundation is poured costs you a change order, a schedule hit, and a strained relationship with the owner. Same omission, wildly different price, and the only variable is how early you found it.

The root cause is upstream, and the research is consistent

It is tempting to file change orders under “stuff happens in the field.” The evidence says otherwise. The roots are in the documents.

The U.S. DOT’s Volpe Center put this in writing in a January 2025 report on construction change orders. “Poor quality, incomplete, or rushed design processes,” it states, “can lead to incomplete, insufficient, or incorrect information in the plans, specifications, and estimates that provide the contractual basis for bidding and construction.” And later, the line that belongs on every preconstruction wall: “The plans and specifications contained in the project agreement are the project’s blueprint that reduces the need for change orders.” When the blueprint has holes, the field fills them in with change orders.

Academic work points the same direction. A study of 610 highway projects by the Kentucky Transportation Center found that “contract omission” was the single most frequent reason a change order got written, ahead of quantity overruns and every other category. A classic and heavily cited 1992 study by Burati and colleagues found that on a set of industrial projects, design deviations accounted for nearly seventy-nine percent of the total cost of rework. The thing that goes wrong on the jobsite usually went wrong on paper first.

A Qatar-based analysis of more than a thousand change orders by Senouci and colleagues reinforces the point, ranking design and plan errors, incomplete design, and owner scope changes among the causes most strongly correlated with cost growth. The specifics vary by study and by sector, but the pattern is stubborn: the document is where the money is won or lost.

The cost of bad information, in dollars

Zoom out from change orders to the broader cost of poor project information and the numbers get large fast.

In 2018, FMI and PlanGrid surveyed nearly 600 construction leaders for a report called Construction Disconnected. They found that poor project data and miscommunication were responsible for forty-eight percent of all rework in the United States, which they estimated at $31.3 billion in that year alone. The same study found that construction professionals lose about thirty-five percent of their time, more than fourteen hours a week, to non-optimal activity, including five and a half hours a week simply searching for project information.

Step back further and the Construction Industry Institute has long pegged direct field rework in the range of a few percent of project cost on standard work and well into the double digits on heavy civil and industrial work, with annual industrial rework losses around fifteen billion dollars. Even older interoperability research from NIST estimated $15.8 billion a year lost in the U.S. capital facilities industry to inadequate information exchange. Different studies, different scopes, same uncomfortable conclusion: the industry spends a fortune cleaning up information that should have been caught earlier.

A word of honesty about the numbers

It is worth being straight about this, because credibility matters. Not every dramatic statistic survives scrutiny. When researchers actually measured field rework on real jobs rather than estimating it, recent work by Love found direct rework costs closer to a fraction of one percent of contract value, with the caveat that rework is routinely underreported by something like three hundred percent. The honest read is that rework is both smaller than the scariest headlines and larger than what shows up on the books, and that a meaningful share of it traces back to design and specification errors. You do not need the inflated numbers. The defensible ones make the case on their own.

Why this keeps happening

If the root cause is so well documented, why does the industry keep paying for it? Because the economics of fixing it have always been brutal.

McKinsey has spent years documenting construction’s productivity problem. Its 2015 research found that ninety-eight percent of megaprojects run more than thirty percent over budget and seventy-seven percent come in at least forty percent late. Its 2017 work noted that construction labor productivity has grown only about one percent a year for two decades, far behind the broader economy, and pegged the global productivity gap at roughly 1.6 trillion dollars a year.

McKinsey even named the perverse incentive directly. In a more efficient system, the firm noted, some contractors stand to lose, because they win work by “optimizing up-front pricing and then making up for lost surplus via change orders and claims,” and because “nonstandard or costly specifications can mean higher revenue rather than lower margins.” Read that twice. Part of the industry has quietly learned to live off the very gaps we are describing. The honest estimator who wants to price the job right the first time is competing against that.

The leverage point

Here is the synthesis. Change orders are expensive, they get more expensive the later they appear, and they originate overwhelmingly in incomplete or misread documents during preconstruction. The single highest-leverage moment in the entire project, the place where a dollar of attention saves the most downstream, is the first careful read of the spec book.

That is also, as we established in Part 1, the exact moment the human process is weakest, because of volume, time pressure, and a thin bench. The leverage is highest precisely where the capacity is lowest.

That mismatch is the opening. If you could make that first read more complete without making it slower, you would be attacking the problem at its source. That is what Part 3 is about.

Next in this series: What AI Classification Actually Changes in Preconstruction.

Sources: AIA Contract Documents, The Truth About Change Orders (2023); U.S. DOT Volpe Center, Understanding Construction Change Orders (2025); Kentucky Transportation Center (2010/2012); Burati et al. (1992); Senouci et al. (2017); FMI and PlanGrid, Construction Disconnected (2018); Construction Industry Institute via ENR (2012); NIST GCR 04-867 (2004); Love, Journal of Construction Engineering and Management (2026); McKinsey Global Institute (2015, 2017).

This post is the second in a series on the economics of spec review and what AI classification changes in preconstruction. Start with Part 1: The Hidden Profit Killer in Every Spec Book.

This is Part 1 of a three-part series for estimators and preconstruction leaders on why missed spec sections turn into change orders, what they really cost, and how AI classification changes the math. Part 1 covers the problem, Part 2 covers the economics, and Part 3 covers what actually changes when you put a machine on the first read.

TL;DR — Every spec book hides a line that can wipe out your margin, and the danger is not that estimators are careless. It is that the job is impossible to do perfectly by hand. A commercial project manual runs hundreds to thousands of pages across fifty divisions of the common UFGS or MasterFormat taxonomies (or even a contract-specific custom taxonomy), and the requirements that hurt you most tend to hide in the least glamorous places: Division 01 general requirements, allowances, alternates, unit prices, submittal and bonding clauses. Estimators juggle roughly a dozen live bids at once on two- to three-week clocks, and four-fifths of firms cannot find enough qualified office staff to help. When you read a thousand pages under that kind of pressure, you do not miss things because you are bad at your job. You miss them because you are human, and the document was built to be exhaustive, not readable. This is the setup for every change order story you have ever told.

The fear every estimator knows

Ask a chief estimator what keeps them up the night before a bid is due, and you will not hear “the math.” You will hear something closer to a confession: somewhere in those documents there is a sentence I did not read closely enough, and it is going to cost us.

That fear is rational. Jerry Aliberti, who spent more than two decades in the field and has estimated billions of dollars of work, put the reality of the job plainly. “The estimator has maybe three weeks to build an entire project in their head,” he wrote. “Sitting at a desk. Staring at lines on drawings. Working through spec books hundreds of pages long.” And then the part that makes it worse: “All of it happening fast because the bid is due and there are three other jobs waiting to get priced.”

That is the whole problem in two sentences. You are reconstructing an entire building in your imagination from two stacks of paper, one graphic and one textual, and you are doing it against a clock that does not care how thorough you want to be.

Why the document is the enemy

Here is the part that outsiders never appreciate. The spec book is not designed to be read straight through. It is designed to be complete.

MasterFormat, the standard that organizes nearly every commercial project manual in North America, has fifty major divisions numbered from 00 to 49. UFGS, an equivalent standard often used in government projects, has even more. They run from procurement and contracting requirements at the front, through concrete, masonry, metals, finishes, mechanical, electrical, all the way out to process equipment and power generation. A real project manual for a mid-size commercial job can run several hundred pages. On larger or public work it stretches into multiple bound volumes and well past a thousand pages.

Nobody reads a thousand pages with equal attention. You cannot. So you triage, and triage is exactly where scope slips through.

The sections everyone underestimates

The cruel joke of spec review is that the money does not hide in the exciting divisions. It hides in the boring ones.

The general requirements section, Division 01 in MasterFormat terms, is the part almost everyone skims. It is administrative, it is dry, and it governs the entire project. Steven Peterson, a longtime construction management professor and the author of a widely used estimating textbook, makes a point of telling estimators to read it early precisely because it drives cost. This is where allowances, unit prices, and alternates live, each carved out in its own section (in MasterFormat, 01 21 00, 01 22 00, and 01 23 00; UFGS and contract-specific taxonomies file the same content under their own numbers). Allowances reserve money. Unit prices set the rate for quantities you cannot yet pin down. Alternates add or subtract scope depending on what the owner decides. Get any of those wrong and your number is wrong, and you will not find out until it is expensive.

Then there are the requirements that never even feel like scope. Submittal requirements. Quality control mockups and testing. Temporary facilities. Closeout and commissioning. Bonding and insurance language, which usually sits in the general conditions, with the actual bond forms tucked into the bid forms. None of it shows up on a drawing. All of it costs money. And a single missed addendum can change your whole number without changing a single line of the design.

Peterson tells a story that every estimator recognizes in their gut. On one job an estimator missed a single line in the technical specs that called out a specific cement powder, one that was not available locally. The substitution request was denied. The material had to be shipped in from out of state, and the added cost, in his words, ate up a big chunk of the profit. One line. One read that went a half-second too fast.

It is a workload problem, not a talent problem

If this were a matter of skill, you could hire your way out of it. You cannot, for two reasons.

First, the volume. Estimators are not babysitting one bid. Industry practitioners describe a typical estimator juggling around a dozen active bids at a time, each with its own documents, its own subcontractor list, its own deadline. A mid-size commercial bid commonly moves from receipt to submission in roughly fourteen to twenty-one days, and the manual takeoff alone on a fifty thousand square foot building can eat forty to sixty hours before anyone has read a word of the project manual closely.

Second, the labor market. According to the Associated General Contractors of America’s 2025 workforce survey of nearly 1,400 firms, ninety-two percent of companies that are hiring report difficulty finding qualified workers, and roughly four out of five have unfilled openings for salaried staff, the category that includes estimating and preconstruction. Forty-five percent of firms tie project delays directly to those shortages. So the people who are supposed to catch the misses are stretched thinner every year, not less.

Put those two facts together and you get the real picture. The work is expanding, the clock is fixed, and the bench is short.

The case for a second set of eyes

Experienced estimators already know the antidote, even if they cannot always afford it. Crystal Barger, who spent more than twenty years estimating before moving into customer success at ConstructConnect, said it simply. “A double-check or a second set of eyes is the best practice, especially when you have a new estimator on board. This way, you can make sure everything is cohesive with that bid before you submit it.”

The trouble is that a second set of expert eyes is the single scarcest resource in the building. The whole reason scope gets missed is that there are not enough qualified people to review everything twice in the time available.

There is also a subtler skill at work, the kind that separates a great preconstruction lead from a good one. Bob Kovacs, a VP of preconstruction with two decades at firms like Skanska, Gilbane, and Turner, described it as the ability to see past what is on the page. The best people, he said, were the ones who could tell “what’s not drawn” and what would “have to happen in the field to be able to fill all those gaps.” Reading what is written is hard enough. Catching what is missing, the silent gap between the drawings and the specs, is harder still, and it is precisely the kind of work that fatigue and time pressure destroy.

Where this is going

None of this is an argument that estimators are failing. It is an argument that the task, as currently structured, is set up to produce misses. A thousand pages, fifty divisions, a dozen bids, a three-week clock, and a hiring market that will not give you the extra reviewer you need. Under those conditions, the surprising thing is not that scope gets missed. It is that so little of it does.

The question worth asking is not “how do we get estimators to read more carefully.” They already read as carefully as the clock allows. The question is what happens to all of that risk after the bid goes out, when a missed section quietly turns into a change order. That is where the money actually moves, and that is where Part 2 begins.

Next in this series: From Missed Line to Change Order, where we put real numbers on what spec gaps cost.

Sources: Jerry Aliberti in Construction Executive (2026); CSI; Steven Peterson via CrewCost (2024); ConstructConnect (2025); AGC of America 2025 Workforce Survey; Crystal Barger via ConstructConnect (2025); Bob Kovacs, The Preconstruction Podcast.

This post is the first in a series on the economics of spec review and what AI classification changes in preconstruction. For a related take on why automation needs human judgment to win real bids, see The Estimator’s Exoskeleton.

TL;DR — The prevailing tech narrative promises fully automated construction estimating. Ask anyone in pre-construction, and they’ll tell you that’s a fantasy. AI is incredibly powerful at processing volume — parsing a 2,000-page spec book, identifying discrepancies, and classifying scopes into WBS (Work Breakdown Structure) codes in minutes. But AI doesn’t know that a local framing sub always hits you with change orders, or that standard power transformer lead times currently sit at 128 weeks. Context is the missing link. At TeraContext, we aren’t building AI to replace estimators; we’re building an exoskeleton so experts can do what they do best: manage risk, leverage relationships, and win profitable work.

Over the past two years, millions of dollars in venture capital have poured into startups promising the “fully automated estimate.” The pitch is familiar: Upload your drawings, push a button, and the software will spit out a perfect bid.

But there is a fundamental disconnect between how the tech world views commercial construction and how the industry actually operates. If you have ever been in a war room on bid day, you know the gap between a software pitch and reality.

Estimating is not a math equation; it is an exercise in risk management and foresight. A project does not fail because someone counted the doors wrong. It fails because of uncoordinated scope boundaries, misaligned assumptions, and supply chain realities that don’t exist in the 2D plans.

Generic software fails in commercial construction because it treats estimating like a data entry problem. At TeraContext, we view it differently. The goal is not to remove the estimator from the process. The goal is to remove the mechanical drudgery so the estimator can apply their most valuable asset: human context.

The 2,000-Page Grind: Where AI Actually Belongs

Before a Chief Estimator can strategize, their team has to survive the onslaught of documentation. In modern pre-construction, the sheer volume of data is the primary bottleneck. As the industry pivots heavily into complex builds like hyperscale data centers and advanced manufacturing, a single project can easily come with a 2,000-page narrative specification book, hundreds of drawing sheets, and overlapping addenda issued just days before the bid is due.

This is the “mechanical layer” of estimating, and this is exactly where automation belongs.

Existing tools like Bluebeam are excellent for counting windows and bathroom fixtures on a 2D sheet, but they still require a highly paid human jockey to manually click through every single page — and they completely ignore the mountain of narrative text hidden in the specs.

Humans are not built to comb through a massive 2,000-page spec book on a Friday night, hunting for nested requirements or trying to build trade packages with highlighters and spreadsheets. An AI system like TeraContext’s document decomposition engine can read, categorize, and cross-reference those 2,000 pages into WBS codes in minutes. It can instantly highlight that an addendum on page 1,412 shifted a temporary power requirement from the electrical subcontractor to the GC (General Contractor).

By automating the extraction and classification of data, the technology gives the estimating team their weekends back. More importantly, it gives them the bandwidth to look up from the spreadsheets and actually evaluate the risk profile of the project.

The Missing Link: Why Context is King

When the mechanical layer is handled by automation, human judgment becomes the final product. The role of the estimator shifts from an operator who generates numbers to a strategist who validates them. Here are three real-world examples of why an automated number is dangerous without an experienced estimator applying context.

1. The Supply Chain Reality: The 144-Week Transformer

Imagine you are bidding on a new hyperscale data center. An AI tool extracts the electrical scope, identifies the generator step-up transformers, checks historical pricing data, and spits out a cost. The math is perfect.

But a seasoned estimator knows the math is completely irrelevant to the reality on the ground. Power scarcity is a massive issue, and the current infrastructure rush has fundamentally bottlenecked the electrical supply chain. According to Wood Mackenzie’s Q2 2025 survey data, average lead times for standard power transformers have hit 128 weeks, while generator step-up transformers are averaging an astronomical 144 weeks (nearly three years).

An algorithm looks at the plans and sees a piece of equipment to be priced. An experienced estimator looks at those same plans and sees a critical-path risk that could delay energization by years. The estimator knows they can’t just price the equipment; they need to advise the developer to secure long-term supply agreements before the project even clears permitting. Technology calculates cost; context dictates strategy.

2. The Subcontractor “Joker Card”

Bid leveling is notoriously complex. You receive three bids for the drywall and framing package. The software levels the bids, normalizes the data, and flags Subcontractor A as the clear winner because they are 12% cheaper than Subcontractor B.

The software does not know Subcontractor A. The Chief Estimator does.

The estimator knows that Subcontractor A’s project managers are notoriously combative. They know that Subcontractor A routinely excludes critical firestopping scope unless explicitly forced to include it, and that they will barrage the general contractor with RFI (Request for Information) driven change orders the moment they mobilize on site. That 12% “savings” on bid day will evaporate by month three of construction. The automated system sees a low number; the estimator sees a relationship liability that will destroy the project margin.

3. Site Logistics and Constructability

A set of architectural plans shows a beautiful 10-story commercial building. The software calculates the exact square footage of the curtain wall system and the structural steel tonnage, multiplying it by standard regional labor rates.

What the algorithm doesn’t factor in is that the project is located on a zero-lot-line corner in a dense downtown corridor. There is absolutely no laydown space for materials. The crane placement requires a partial street closure that the city will only permit between 10:00 PM and 4:00 AM.

The estimator knows that “just-in-time” nighttime deliveries command a massive premium. Labor productivity will plummet due to the restricted hours, and the logistics coordination will require an extra full-time superintendent just to manage traffic control. The physical constraints of the real world — the context — turn a standard unit price into a complex logistical premium that no generic software model can accurately predict without human intervention.

The Philosophy: An Exoskeleton, Not an Autopilot

This is exactly why TeraContext’s document decomposition engine is designed to handle the mechanical layer in minutes — surfacing scope shifts, addenda impacts, and WBS classifications — so the estimator can stay in the strategist seat instead of acting as a data-entry jockey.

The estimators who thrive in the next decade won’t be the ones who can generate the fastest manual takeoffs. They will be the ones who can tell you, with confidence, whether an automated number is solid or suspect based on real-world constraints. We are not trying to build an “autopilot” that blindly drives the estimating process into a ditch. We are building an exoskeleton for pre-construction teams. The technology carries the crushing weight of the data so that the estimator is free to negotiate and apply the hard-won experiential wisdom that algorithms simply cannot replicate.

We Need Builders to Build This

We know that the biggest unsolved problems in construction tech cannot be fixed by software engineers alone. They require domain experts who have actually built complex WBS structures, lived through chaotic RFP (Request for Proposal) cycles, and understand the difference between a statistically average number and a winnable hard bid.

TeraContext is maturing. Our AI works. We are proving that our engine can handle the heavy lifting of commercial construction and give estimators their lives back. But to take this to the next level, we need the missing link. We need context.

For the Builders: If you are a construction veteran, a Chief Estimator, or a VP of Pre-Construction who is tired of the manual grind and wants to build the tools that will actually define the next decade of this industry, we need to talk. We have the AI. We need you to bring the context. Join us as a founder, and let’s build the future of pre-construction together.

For the Estimating Teams: If you are actively bidding complex projects and want to see how an exoskeleton approach can eliminate the scrub grind of a 2,000-page spec and protect your margins, contact us to see TeraContext handle complexity at scale.

This post is part of an ongoing series exploring where traditional construction and digital infrastructure collide. Earlier entries: The Builder’s Pivot, Building for the Next GPU, and Powering the AI Factory.