AI risk, liability, and security in construction: what GCs and subs are actually exposed to in 2026

If an AI tool drafts a bad RFI response, flags a submittal wrong, or gets fed a poisoned document that changes what it reports, the licensed professional or contractor of record is still the one holding the liability — not the vendor. That's the single fact that should anchor every AI risk decision your firm makes in 2026: the tools are real, the productivity gains are real, and none of it moves the legal and insurance exposure off your desk.

This guide covers the five places that exposure actually shows up on a commercial project: who's liable when the tool is wrong, whether your insurance still covers it, what your contracts say (or don't), the specific security risk in letting AI read documents from outside parties, and what happens when the AI provider itself goes dark. None of this is a reason to stop using AI. It's the list of questions to have answered before your next renewal, your next federal bid, or your next AI pilot.

Who is liable when an AI tool gets it wrong on your project?

The contract doesn't change because a model drafted the answer. The engineer, PE, submittal reviewer, or PM who approves an AI-assisted deliverable is the party of record — courts and licensing boards hold that person to the same standard of care as if a junior staffer had made the call, AI or not.

That matters because AI vendor agreements are built to limit what you can recover if the tool itself is the problem. Vendor liability clauses commonly cap damages at a small fixed figure or the cost of the software license, regardless of how large the resulting error is on the project — a gap that shows up fast if an AI-flagged submittal turns out wrong and causes a six-figure rework (Hahn Loeser, "Understanding the Impact of AI: Artificial Intelligence, Construction Contracts, and Even More Complicated Disputes"). The broader legal framework treats the party that controls and benefits from the AI's use — the "integrator," in liability terms — as the first party courts look to, ahead of the model developer, unless you can show the developer owed you a specific duty of care (HFW, "Legal Liability for AI Decisions: Who Is Responsible When AI Fails?"). In practice: your firm is the integrator on almost every AI tool you deploy.

The practical fix isn't legal — it's process. Every AI-assisted item in your submittal log or RFI register should show a named human approval, the same discipline we cover in our RFI and submittal guide. That approval trail is your best evidence of good-faith standard of care if a dispute ever asks who signed off on what.

Is your insurance still covering AI-assisted work?

Maybe not, and the change happened fast. Verisk — the organization that drafts standard insurance policy language most US carriers license — rolled out three new endorsement forms (CG 40 47, CG 40 48, and CG 35 08) effective January 1, 2026, giving carriers ready-made language to exclude losses arising from generative AI from commercial general liability policies (Independent Agent, "Verisk to Roll Out New General Liability Exclusions for Generative AI Exposures"). By April 2026, major carriers — W.R. Berkley, Chubb, Travelers, Berkshire Hathaway, and Cincinnati Financial among them — had filed to adopt these exclusions or proprietary equivalents, with state regulators approving more than 80% of the filings submitted. One industry estimate projects 95% of carriers eventually adopting some form of AI exclusion (Gridex, "Verisk CG 40 47: What the New AI Exclusions Mean for Your Commercial Clients").

The trigger language is broad by design: coverage is excluded for losses "arising out of" generative AI, and under established insurance law that phrase only requires a causal connection — not that the AI directly caused the harm. A construction claim that touches an AI-assisted submittal review or spec check anywhere in its chain could fall inside the exclusion, even if a human made the final call.

There's a documented way to push back on the terms. Carriers have shown willingness to offer broader language to firms that can show active AI risk management — a written governance policy, a defined verification workflow, and a named licensed-professional sign-off step on every AI-touched deliverable — versus accepting the off-the-shelf exclusion at face value (2026 E&O Renewal Audit Guide). If your policy renews in the second half of 2026, put "what's our AI exclusion language and what would get it narrowed" on the agenda with your broker before the renewal call, not during it.

Do your construction contracts even address AI risk?

Almost certainly not. AIA, ConsensusDocs, and FIDIC standard-form documents were all written before generative AI was a live issue on a jobsite, and none of the major standard forms currently address AI-generated work product, algorithmic errors, or who owns the data rights when an AI vendor's tool processes your project documents (Dan Cumberland Labs, "The 8-Point AI Clause Audit for Engineering, Procurement, and Construction Contracts"). ConsensusDocs has started building AI-adjacent tooling — a ClauseBuilder AI product for drafting dispute-resolution clauses — but that's a drafting aid, not a published AI-risk clause for the standard forms themselves.

Until a standard form catches up, the working solution is a side letter or addendum on top of your existing contract, not a wait-and-see approach. At minimum, that addendum should cover three things: who is responsible for verifying AI-assisted output before it becomes a project record, whether the AI vendor can be joined as a party if a dispute traces back to a tool's error, and what happens to any project data the AI vendor's tool touched. None of this is exotic contract drafting — it's the same risk-allocation logic your legal team already applies to subcontractor scope and indemnification, pointed at a new category of "sub."

What's the real security risk in letting AI read subcontractor documents?

Prompt injection — instructions hidden inside a document that redirect what an AI agent does with it. We covered this in depth when a 2026 study of 30 deployed commercial AI agents found 8 with documented security incidents, most tied to exactly this failure mode. If a sub's product data sheet contains embedded text claiming spec compliance, or an RFI attachment contains a line directing the agent to disregard a flagged discrepancy, a vulnerable agent can treat that as instruction rather than as content to evaluate — and only 7 of the 30 agents studied had documented defenses against it.

Submittal review, RFI processing, and any browser-use agent navigating a compliance portal all share the same exposure: the agent reads content from a party with a stake in the outcome. Before giving an agent review authority over anything a subcontractor submits, get a straight answer from the vendor on whether it defends against indirect prompt injection and whether the agent runs sandboxed. Most vendors currently can't answer both.

What happens when your AI vendor goes dark?

It happens with no warning and no fallback plan, unless you've built one. On June 12, 2026, the US Commerce Department ordered Anthropic to suspend access to its two most capable models — Claude Fable 5 and Claude Mythos 5 — for every user globally, a shutdown that lasted more than a week and took down every construction tool built on those models with it, including AI features inside SketchUp. The trigger was an export-control dispute, not a construction-specific issue, but the lesson generalizes: a foundation-model provider can be ordered offline with zero notice, and every workflow that depends on it goes down at the same time.

Most GC ops teams can't currently answer a basic question: which foundation model powers the AI feature in each tool on their stack. That's the first fix — ask every vendor, in writing, what model they run, what happens if that provider restricts access, and whether the feature degrades to a manual workflow or simply stops. Any AI tool your own team built in-house on top of a single model provider is a documented single point of failure the moment you identify it as one.

Can federal contractors use cloud AI at all?

Not for anything touching Controlled Unclassified Information, and the compliance bar is about to get more specific, not less. Under CMMC 2.0, any AI tool processing CUI must meet NIST SP 800-171 controls, and none of the major commercial AI APIs — ChatGPT, Claude, Gemini — are authorized for that out of the box. Azure OpenAI's FedRAMP High tier covers some CUI use cases, but it's slower, limited to fewer models, and adds procurement overhead most subs and mid-size GCs can't absorb — which is why spec parsing, RFI drafting, and submittal review are largely off the table on federal work today, exactly where project complexity tends to be highest.

That bar is moving. GSA released a draft clause — GSAR 552.239-7001, "Basic Safeguarding of Artificial Intelligence Systems" — on March 6, 2026, that would require GSA contractors to disclose every AI system used to perform a contract (not just AI sold to the government), mandate domestically developed "American AI Systems," and flow those requirements down to subcontractors and any "Service Provider" that touches the AI system (Holland & Knight, "GSA's Proposed AI Clause: A Deep Dive"). Comments were due August 3, 2026. If your firm holds or bids GSA work, that's a live rulemaking to track, not a settled requirement yet — but the direction is toward more disclosure obligations, not fewer.

Separately, NIST released a concept note on April 7, 2026 for an AI Risk Management Framework profile specific to critical infrastructure — covering energy, water, transportation, and industrial control systems, the sectors most commercial construction touches on hospital, data center, airport, and utility work (NIST, "Concept Note: AI RMF Profile on Trustworthy AI in Critical Infrastructure"). It's voluntary and still in a community-feedback stage, not a binding requirement — but it's the clearest signal yet that critical-infrastructure owners will expect their construction teams to have an answer for AI risk management, not just AI adoption.

Is your jobsite's building automation exposed during AI-enabled attacks?

The exposure isn't in your project management software — it's in the building systems going live before the owner's IT team takes control. Six national cybersecurity agencies, including the NSA and CISA, said in a June 22, 2026 joint statement that AI-enabled cyberattacks on critical infrastructure are "months, not years" away, and the specific window where a project is most exposed is commissioning — the four-to-eight-week stretch where temporary credentials from factory acceptance testing often haven't been rotated and multiple parties still have live remote access to building automation, HVAC controls, and access control systems.

That's a spec and subcontract fix, not a software purchase: require credential rotation and network isolation as substantial-completion deliverables in Division 25, and require written confirmation from the controls contractor that non-essential remote access has been decommissioned before handover. It doesn't remove the AI risk, but it closes the specific gap the threat model is aimed at.

Comparison: AI risk categories construction firms are actually exposed to

Risk category	What it looks like on a project	Who's exposed	What actually mitigates it
Liability for AI errors	AI drafts a wrong RFI response or misses a submittal discrepancy that causes rework	The approving PE, PM, or submittal reviewer — not the AI vendor	Named human sign-off on every AI-assisted item, documented in the log
Insurance exclusions	A claim traces back to an AI-assisted deliverable and the carrier denies coverage under a generative-AI exclusion	The firm carrying the E&O/GL policy	Written AI governance policy; ask your broker to narrow exclusion language at renewal
Contract gaps	A dispute over an AI-caused error has no clause to point to in the AIA/ConsensusDocs agreement	Whichever party ends up litigating without contract language on point	A side-letter addendum on AI verification responsibility and data rights
Prompt injection	A sub's document contains hidden instructions that change what an AI review agent reports	Whoever relies on the agent's flagged (or unflagged) output	Ask vendors about sandboxing and indirect-injection defenses before deploying
Vendor / model shutdown	A foundation-model provider is ordered or chooses to restrict access, and every tool built on it goes dark	Any firm that doesn't know which model powers its AI tools	Inventory the foundation model behind every AI feature in your stack; ask about fallback
CUI / federal compliance	An AI tool processes CUI without meeting NIST SP 800-171 / CMMC controls	Federal GCs and subs, and their C3PAO assessment status	Map which workflows touch CUI; keep those off commercial AI APIs until authorized
OT / commissioning security	Building automation systems carry unrotated credentials and open remote access during handover	The GC and controls contractor during the commissioning window	Spec credential rotation and access decommissioning as Division 25 deliverables

How should a mid-market GC or sub actually manage this in 2026?

1. Inventory the AI in your stack. List every tool with an AI feature, the foundation model behind it, and what happens if that model provider restricts access. Most ops directors can't answer this today — start here.
2. Put your insurance renewal on the calendar early. Ask your broker directly whether your GL/E&O policy carries a generative-AI exclusion and what a documented AI governance policy would do to that language.
3. Write the AI addendum for your standard contract. One page: who verifies AI-assisted output, how disputes involving AI-caused errors get handled, and whether the AI vendor can be joined as a party.
4. Keep CUI off commercial AI APIs. If you hold federal work, map which workflows touch Controlled Unclassified Information and confirm your tools are authorized before they touch that data — not after a C3PAO assessment flags it.
5. Close the commissioning gap in your specs. Add credential rotation and remote-access decommissioning as Division 25 close-out deliverables on any hospital, data center, airport, or utility project.
6. Ask every AI vendor three questions before a pilot goes live: what foundation model do you run, what are your documented defenses against prompt injection, and what happens to our data and our workflow if your access gets restricted. A vendor who can't answer is telling you something too.

None of this is an argument against using AI on a commercial project — the tools are genuinely saving time on submittal review, RFI drafting, and document comparison, and that's not going away. It's the list of items that turn AI adoption from an open liability into a managed one, and most of them cost nothing but a conversation with your broker, your legal team, and your next AI vendor.