Your Superintendent Wrote 'Waiting on Engineer' Three Times. Nobody Noticed. The Arbitrator Did. That Cost You $340,000.

I once watched a GC lose an arbitration because his superintendent had written "waiting on structural engineer — no response to RFI #14" in the daily log on a Tuesday, a Wednesday, and the following Monday. Three entries across six calendar days. Owner's counsel highlighted them in yellow, projected them on a screen, and argued that the contractor had documented a known delay without formally notifying anyone under the contract's claims procedure. His own handwriting became the evidence that he knew about the problem and sat on it.

An award of $340,000 in schedule-impact damages landed on the contractor. Not because the delay wasn't real. Because the notice came eleven weeks late.

90,000 Words Nobody Reads

Construction daily logs are required on virtually every project above $500,000 in the United States, with AIA Document G707 defining the standard format. Most superintendents spend somewhere between 15 and 40 minutes filling one out at the end of each shift, recording weather, manpower counts, equipment on site, work completed, and problems encountered. On a typical 14-month custom home build, that produces roughly 300 daily logs containing an estimated 90,000 words of field-level observations.

Almost nobody reads them until something goes wrong.

When something does go wrong, when the schedule slips and the change orders pile up and the lawyers start circling, those daily logs become the most contested documents in construction litigation, the kind of evidence that makes or breaks a seven-figure arbitration. HKA's 2024 CRUX Insight report, which analyzed 2,002 projects across 107 countries with a combined capital expenditure of $2.25 trillion, found that disputed sums totaled $84.4 billion, with average cost overruns reaching 33.2% of budgeted CapEx and schedule overruns averaging 16 months. According to the National Academies, 10 to 30% of all U.S. construction projects produce serious disputes, and one in four generates a formal claim, with transactional resolution costs running $4 to $12 billion annually in the United States alone.

In nearly every one of those disputes, somebody pulls the daily logs. And in a remarkable number of them, the answer was sitting there the whole time, buried in a superintendent's shorthand that nobody bothered to read until it was projected on a conference room screen in front of a panel of arbitrators.

What the AI Actually Does

A UK company called Gather built a platform that reads every diary entry as it's written and cross-references the language against the project's contract terms. Their QS AI Agent, deployed with Balfour Beatty, Costain, Network Rail, and Siemens across UK infrastructure projects, does something no human project manager has the bandwidth to do: it reads every single line of every single diary entry and asks whether that line constitutes a compensable event under the contract.

When a foreman writes "revised drainage layout per client instruction," the AI recognizes it as a change to the Works Information under NEC4 clause 60.1(1), calculates that the contractual notice deadline is approaching, and generates a draft notice with the clause reference attached. That foreman had no idea it was a compensation event, and a diligent project manager might have caught it on Friday when reviewing the week's entries, but Gather's AI caught it in the time it took the foreman to tap "submit."

On Transport for London's 4 Line Modernisation project, Gather claims an 11% reduction in total project cost. Costain's Tideway Secondary Lining Works delivered ahead of schedule, with the project's senior PM crediting Gather's structured data capture for enabling "effective, timely decisions." Circet reported saving over 100 hours per month on assurance documentation alone.

These are infrastructure numbers on large projects with NEC contracts and dedicated commercial managers, and whether that logic scales down to residential is the question that matters for anyone reading this.

Eight Weeks and You Lose Everything

Under the NEC3 and NEC4 contract forms dominant in UK public works, a contractor who fails to notify a compensation event within eight weeks of becoming aware of it is completely barred from claiming additional time or money. This applies even when the employer caused the problem through a breach of contract. Clause 61.3 is unambiguous: miss the window and you lose the claim entirely.

American residential contracts don't typically use NEC forms, but the principle translates directly. AIA A201-2017, the most common general conditions document in U.S. residential construction, requires the contractor to provide "prompt" written notice of claims (Section 15.1.3), with a 21-day deadline for claims related to concealed or unknown conditions (Section 3.7.4). Many custom home contracts include tighter notice requirements negotiated by the owner's counsel.

It fails the same way everywhere: a superintendent notices a problem, writes it in the daily log, and assumes someone will handle it, but nobody issues a formal notice. Weeks pass. By the time the project manager realizes the delay has cascaded into a real schedule impact, the notice period has expired or the contemporaneous documentation is too thin to support a claim. A log entry that should have triggered a formal process became, instead, evidence of awareness without action.

Currie & Brown's Construction Certainty Index 2025 surveyed over 1,000 decision-makers managing portfolios averaging $12.9 billion in construction activity. They found that uncertainty erased approximately $2.5 trillion in projected global construction activity over the prior year, with an average 13.7% financial loss across portfolios. Twenty-nine percent of projects experienced delays, and only one in five leaders expressed full confidence in delivering projects within budget.

Nobody in that survey said "we need better daily logs." They should have. Qureshi's 2026 systematic review of 60 peer-reviewed studies on AI in construction management, published in Frontiers in Built Environment, identified exactly this gap. Risk detection systems and schedule optimization systems both exist, but neither talks to the other. "Projects generate enormous amounts of warning data every day," Qureshi wrote, "but nothing in the schedule actually changes when these signals appear."

The Residential Gap

Procore, the dominant U.S. construction management platform, offers daily log functionality but doesn't include AI-driven clause analysis, and a residential GC running three $2M custom homes simultaneously is not Gather's customer. But the math still applies even at smaller scale. NAHB estimated that the latest round of tariffs has increased construction costs by $10,900 per home. That number doesn't include the cost of the change orders those tariffs will generate as material substitutions ripple through projects already under contract, and every substitution is a potential dispute, and every dispute turns on documentation.

Researchers at Michigan Technological University and Hong Kong Polytechnic demonstrated in 2024 that ChatGPT combined with computer vision could automatically generate construction daily reports from jobsite video footage, validated on a real construction site over a 30-day period. Automated diary generation from video footage is technically feasible. AI-driven diary analysis against contract terms exists in production. Nobody has combined them for residential at an accessible price point.

A residential builder who wanted to build this today could approximate it: feed daily log entries into an LLM prompted with the project's contract terms and a list of notification triggers. It wouldn't be Gather and it wouldn't integrate with scheduling software, but it would catch "waiting on engineer — day 3" and flag it before week eight.

What This Means if You're Building a House

If you're a GC running residential projects between $1M and $5M, your daily log is already the most important legal document your superintendent produces, and it's probably being written on autopilot at 4:30 PM by someone who wants to go home. An AI that reads those entries against your contract terms and flags notification deadlines would cost less to deploy than a single missed change order claim. Both technologies exist. A residential-specific product at the right price doesn't, yet.

If you're a homeowner in the middle of a build, ask your builder whether their daily logs are digital, whether anyone reviews them systematically, and whether they have a formal process for issuing change-order notices within the contractual window. If the answer to any of those is no, you're both exposed.

If you're a superintendent, write better entries. "Weather delay" tells a lawyer nothing. "Rain from 7:00 AM to 2:15 PM, 1.3 inches measured at site, foundation excavation standing water, crew sent home at 10:00 AM, lost 6 man-hours framing crew plus 4 man-hours excavation crew" tells an arbitrator everything. That level of specificity takes an extra five minutes. It is worth more than you will ever know until the day it saves you.

Limitations

Gather's published results come from UK infrastructure projects running NEC contracts with dedicated commercial teams. Translating those percentage savings directly to U.S. residential work overstates the case: different contract forms, different scales, different organizational capacity. The 33.2% average cost overrun from HKA's data reflects global megaprojects averaging $1.28 billion in CapEx, not custom homes. No published study quantifies what percentage of construction disputes are caused specifically by missed notification deadlines versus substantive disagreements about scope or quality. Academic ANN cost-prediction models achieving R² values above 0.99 have not been validated on messy, inconsistent residential daily log text. AI diary analysis requires digital input, and a meaningful share of residential projects still run on paper logs, WhatsApp threads, and memory.

Skeptics will argue that a superintendent on a $3M house doesn't need a machine to tell them "waiting on engineer" three days running is a problem, that what they actually need is the discipline to escalate it, the contractual literacy to recognize it as a notification trigger, and a project manager who picks up the phone when the super calls. Technology cannot fix a culture that doesn't value documentation. It can only make documentation less painful, and hope that reduced friction produces better data.

Gather's evidence suggests that it does. When diary entry time dropped from 30 minutes to 5 minutes and compliance became frictionless, the quality of the record went up, not down. That is the bet worth making for residential, if someone builds the product at the right price point.