Information Is Not Intelligence.
The gap between them is where cost and schedule impacts actually live.
For decades, construction has reduced the friction of moving information. Blueprints became PDFs. Plan rooms became cloud platforms. Job trailers became mobile devices. Today, we can move project data across companies, jobsites, and continents in seconds. That transformation was remarkable. But it exposed a new question: what exactly are we moving?
Our industry uses data, information, and intelligence almost interchangeably. This is how I think about it.
Dashboards promise intelligence. AI promises intelligence. Reporting tools promise intelligence. Most of what they deliver is organized information. Those are not the same thing and the gap between them is where cost and schedule impacts actually live.
Impacts are rarely caused by documents. They're created when project data changes: a revised lead time, a spec clarification, a routing conflict, a failed inspection. When information is not available or shows up at the wrong time. It can be a silent margin killer. One change ripples through procurement, fabrication, sequencing, commissioning, billing, often long before it shows up on any dashboard.
Let's get the language straight. Again, this is how I think about it. I invite other viewpoints. The goal is not authority, it is moving work forward.
INPUTS are observations entering the project. A field measurement. A delivery ticket. A photo. An email.
DATA is those observations recorded. Dimensions, dates, part numbers, statuses. Captured reality. It tells us what exists.
INFORMATION is data organized into structures people can use. Drawings, submittals, RFIs, schedules, change orders. Our industry has gotten exceptionally good at creating, storing, and moving this. That progress should not be understated.
INTELLIGENCE begins where information ends. It's knowing what a change means: who's affected, what happens next, what risk was just created.
Information describes the project.
Intelligence explains the project.
For a PM, that's the difference between an RFI log showing a question is open and knowing that RFI, open six days, is about to collide with a prefab delivery already in transit. Before it becomes a field conflict instead of a schedule note.
tellus@hc-build.com