The standard AIA contract was designed for a world where information moved slowly and decisions were made by people in the same room.

That world is gone. The contract is still here.

What hasn’t changed

Walk through a typical project delivery sequence and the bones are the same they’ve been for decades. Owner hires architect. Architect produces drawings. GC prices and builds from drawings. Change orders capture everything the drawings didn’t. Owner pays and occupies.

The assumptions embedded in this model: design is substantially complete before construction starts, information is complete enough to price accurately, problems are discovered sequentially and resolved before they compound.

None of these assumptions reliably hold on complex projects. The drawings are never truly complete. Information is never fully accurate at bid. Problems cascade in parallel, not sequentially.

The contract pretends otherwise. And the gap between what the contract assumes and what actually happens on projects is where most of the money gets lost.

AI and the information problem

The AEC industry’s reluctance to change isn’t primarily a technology problem or a culture problem. It’s an information problem. Decisions get made on incomplete, outdated, or fragmented data because the systems for capturing and sharing real-time project information have never worked well enough.

When the GC doesn’t know that the architect revised the specification until three weeks after the revision, the GC is making decisions based on outdated information. When the owner doesn’t know the schedule has quietly slipped until the monthly report arrives, the owner can’t make decisions early enough to change the trajectory.

AI changes the information environment. Not by making people smarter, by ensuring that the right information reaches the right people at the right time. The GC sees the spec revision the day it’s issued. The owner sees the schedule pressure the week it appears, not the month it becomes a crisis.

That capability doesn’t require a new contract. But it does require the project team to be organized around information transparency rather than information control.

The firms that are leaving legacy players behind

There’s a real and widening gap between firms that have rebuilt their workflows around real-time information and firms that haven’t.

The firms ahead of the curve have stopped treating project management software as an archive and started treating information flow as the actual product of project management. They’re generating owner-facing transparency continuously, not monthly. They’re surfacing risks as they emerge, not after they’ve compounded. They’re using AI to handle the documentation and coordination work so their experienced people can focus on the judgment calls that change outcomes.

The firms behind the curve are still managing projects the same way they managed them in 2015, with better-looking reports.

The gap shows up most visibly when something goes wrong. The firms ahead of the curve catch it early. The firms behind it discover it when someone calls a meeting.

What to look for

Old-school risk management is “identify risks, put them on a register, review monthly.” New risk management is “maintain continuous visibility into project state so risks are visible before they become problems.”

The question to ask your project partners: when was the last time you told me about a risk before I would have found out about it anyway? How did you know? What did we do differently because we knew earlier?

If they can answer that with specifics, the information environment on your project is working. If they describe their risk register, you’re still operating on the old model.

The contract will catch up eventually. In the meantime, the transparency is available if you know what to ask for and who to work with.