{"id":905561,"date":"2026-04-14T16:23:29","date_gmt":"2026-04-14T22:23:29","guid":{"rendered":"https:\/\/www.myconstructionexpert.com\/blog\/?p=905561"},"modified":"2026-04-14T16:23:32","modified_gmt":"2026-04-14T22:23:32","slug":"arbitration-your-choice-you-didnt-choose-this","status":"publish","type":"post","link":"https:\/\/www.myconstructionexpert.com\/blog\/arbitration-your-choice-you-didnt-choose-this\/","title":{"rendered":"You Chose Arbitration. You Didn\u2019t Choose This."},"content":{"rendered":"\n

Angie Nolet | TransPerfect Legal<\/a><\/p>\n\n\n\n

Arbitration promised efficiency. Construction data stole it. GenAI can recover it.<\/h5>\n\n\n\n

I once worked a $25 million construction dispute that cost about $15 million to litigate. 1.2 million documents. A partner, a paralegal, and I all relocated out of state for a month to arbitrate, billing 12 hours a day. A panel of three arbitrators, one of whom charged $7,500 per day. Extensive post-arbitration briefing that dragged on for years.<\/p>\n\n\n\n

The parties had chosen arbitration, of course. The pitch is well-worn: arbitrate, and you get a faster, more-proportionate path to resolution. You escape litigation\u2019s procedural sprawl, its jurisdictional gamesmanship, its discovery free-for-all, plus a decision-maker who understands a schedule delay and can read an MEP drawing.<\/p>\n\n\n\n

What the pitch doesn\u2019t account for is the data. Oh, the data.<\/em><\/p>\n\n\n\n

Construction Dispute Data Is a Double-Whammy Problem: It\u2019s Volume and<\/em> Diversity<\/h4>\n\n\n\n

Here\u2019s what differentiates construction disputes: the documents aren\u2019t documents<\/em>. Not in the sense that a contract, a memo, or an email is a document.<\/p>\n\n\n\n

A construction project generates RFIs\u2014requests for information\u2014that chain across months and reference submittals that reference drawings that reference specifications that reference a change order that was never formally executed but everyone acted on anyway and that three people texted about. It generates daily reports, hand-marked field drawings, schedule files in Primavera or Aconex, BIM models, cost-loaded schedules, critical path planning, subcontractor correspondence scattered across Procore, email, and text. It generates years of data because projects run long and disputes run longer\u2014and the documents accumulate cross-referentially, across platforms and timelines that only make sense if you understand the project.<\/p>\n\n\n\n

1.2 million documents isn\u2019t unusual. That volume alone is manageable.<\/p>\n\n\n\n

The double whammy: those 1.2 million documents speak fifteen different languages, and standard review workflows were built for one or two. A commercial litigation review attorney can parse a long email chain faster than you can say \u201ccritical path.\u201d But they probably can\u2019t parse the relationship between an RFI response, a marked-up drawing, and a change order directive\u2014and understand, intuitively, that the absence of a formal change order despite an undisputed direction to proceed is itself a fact of consequence. The document type is alien. The cross-referential logic is alien.<\/p>\n\n\n\n

Previous Tech Was Good, but Not Right-Fitted<\/h4>\n\n\n\n

Technology assisted review\u2014TAR, predictive coding, call it what you like\u2014cut volume with reasonable accuracy. That ain\u2019t nothing.<\/p>\n\n\n\n

But here\u2019s what TAR couldn\u2019t do: understand that an RFI chain, a change order directive, a set of hand-marked drawings, and a project schedule update are in conversation with each other. It treated your construction documents like emails, processed them accordingly, and offloaded a smaller pile that was still, fundamentally, opaque. That limitation has long defined construction eDiscovery workflows.<\/p>\n\n\n\n

And it\u2019s ironic: construction companies build projects on AI-native platforms. Procore. Primavera. BIM environments that make structural relationships explicit and searchable. Then a dispute arises, and we strip all that intelligence out and flatten the data into a review queue. We take a sophisticated, interconnected data architecture and review it like it\u2019s a box of photocopies someone scrounged up from a storage unit.<\/p>\n\n\n\n

Once upon a time, technological limitations forced us to smoosh our square-peg data into round-hole eDiscovery tools. \u2019Twas the best we could do. But then GenAI arrived. So why are we still self-sabotaging?<\/p>\n\n\n\n

A fable comes to mind: once there was a flea. Fleas are prodigious jumpers and can launch themselves many times their own height. Put one in a jar with a lid, though, and it learns. It jumps, hits the lid, adjusts. After enough collisions, it caps its own jump at lid-height. The interesting part: remove the lid, and it still won\u2019t jump higher. The ceiling is gone. The flea doesn\u2019t know that. It internalized the constraint so thoroughly that the constraint no longer needs to exist.<\/p>\n\n\n\n

The legal industry is the flea. The lid was technological limitation, and the habits calcified. The workflows ossified. We\u2019re still jumping lid-height out of sheer institutional memory and billing accordingly. But GenAI blew the lid off: we can jump higher now.<\/p>\n\n\n\n

Earlier Tech Sorted; GenAI Interrogates<\/h4>\n\n\n\n

First: construction-aware categorization before review begins<\/h5>\n\n\n\n

GenAI doesn\u2019t just cull for relevance. It categorizes documents at a granularity that previous tools couldn\u2019t touch\u2014by trade, by building system, by document type, by project phase. Before a single human reviewer breaks ground, you have a bird\u2019s-eye view of the data landscape\u2014what you have, where it came from, and where the dispute concentrates.<\/p>\n\n\n\n

I once litigated a matter that hinged on metal shavings and damage to a waterproofing membrane. (This was in the days of yore, before GenAI.) I combed hundreds of photos hunting metal shavings; I bored through spec sheets; I sifted thousands of emails for the needle\u2014all at northwards of $500 an hour. Now, I litigate it differently in my head. Armed with GenAI, I\u2019d run the dataset through a platform like eDiscovery AI, drill down on the 600 or so that dealt with metal shavings, and understand the timeline\u2014all within a day or two.<\/p>\n\n\n\n

GenAI tells your outside counsel where to concentrate their efforts. That gives you control over the data they\u2019ll review, and\u00a0that<\/em>\u00a0gives you\u00a0control over the budget<\/a>. Instead of a budget built on assumptions and professional optimism, you get one built on actual data\u2014document counts, document types, review scope. Now, you get the picture before you start the puzzle.<\/p>\n\n\n\n

Second: natural language interrogation of the full document set<\/h5>\n\n\n\n

Ask a retrieval-augmented generation (\u201cRAG\u201d) system: \u201cIs there any evidence the concrete subcontractor used an unapproved grade?\u201d Answering that the old way meant weeks of targeted review across fragmented document sets\u2014daily reports, test logs, submittal records, field correspondence\u2014with no guarantee you\u2019d surface the right documents even then. Now it\u2019s a query; an answer within minutes.<\/p>\n\n\n\n

RAG tools, however, don\u2019t just find documents with the words \u201cconcrete\u201d and \u201cunapproved.\u201d They find documents where the relationship between a submittal approval status and a daily report note implies the answer\u2014across document types, platforms, and the project timeline.<\/p>\n\n\n\n

I\u2019ve seen this surface evidence that linear review would have found late, or not at all. One matter: a contractor believed their engineer had stolen project secrets. A natural language query returned a document containing the sentence \u201cthe key is to have the plans in the bag.\u201d That sentence wasn\u2019t on anyone\u2019s custodian list. No keyword search would have flagged it. RAG found it because it understood the query and the parlance.<\/p>\n\n\n\n

That\u2019s what wins cases: not a smaller review pile, but the right document, at the right moment, before the other side finds it first.<\/p>\n\n\n\n

Third: the timeline your project never kept<\/h5>\n\n\n\n

Delay claims are the engine of construction litigation: who was responsible for which delay, when, in what sequence, with what notice, affecting which critical-path activities? Traditionally, that meant a forensic-scheduling expert, weeks of document review, and a hefty bill.<\/p>\n\n\n\n

Enter GenAI. Feed it the project schedule files, the RFI logs, the daily reports, the change order directives\u2014and ask it to surface the sequence of events on a particular work scope. It won\u2019t replace your expert. But it will gift them a map instead of a blank page, find the document they needed but didn\u2019t know existed, and excavate the gap in notice that rewrites the damages calculation\u2014in days, not weeks.<\/p>\n\n\n\n

Two Questions to Ask Before the Next Matter Begins<\/h4>\n\n\n\n

The goal isn\u2019t to quiz your outside counsel on AI literacy. It\u2019s to signal that you know enough to hold them accountable.<\/p>\n\n\n\n