Zero RFI
When a building project goes wrong, the visible failures emerge during construction. Budget overruns appear in change orders. Schedule slips manifest in revised completion dates. Quality problems surface in punch list items that drag on for months.
The root causes, however, were established months or years earlier.
The first domino
Every construction failure has a first domino, the moment where a decision was not made, a requirement was not defined, an assumption was not validated. By the time anyone encounters the problem on site, it is already third or fourth generation: a gap in the design documents became a coordination failure that became an RFI that became a change order that became a schedule slip.
The industry’s response to these failures has been better tools for managing downstream effects. Better change order software. Better schedule monitoring. Better field coordination platforms. These interventions are useful, but they address symptoms rather than causes.
The underlying problem is that owners lack visibility until the point where intervention is costly or impossible. And frequently, they are unaware of what information they are missing.
You don’t know what you don’t know
A pattern recurs in projects that deteriorate. The owner funded the project, assembled the team, completed design and bidding, and then watched things fall apart during construction. In retrospect, the warning signs were present. They were never surfaced in a form the owner could act on.
This is generally not negligence. It is structural. The parties managing project information (architects, engineers, contractors) maintain their own workflows, their own systems, and their own judgment about what warrants upstream communication. The owner sits downstream of all of this, receiving whatever the project team determines is worth reporting, on whatever timeline the project team finds manageable.
The information asymmetry is not incidental. It is embedded in how projects are structured. The contractor holds a more accurate picture of actual cost and schedule than the owner does. The architect has a fuller understanding of design risks than the owner does. Owner leverage decreases as the project advances, which means the information that reaches them is perpetually slightly behind the moment when it could most usefully be acted upon.
The owner’s absence from the decision loop
In most construction projects, the owner is the most consequential stakeholder and the least informed participant.
You fund the project. You carry the financial risk. You operate the building for decades afterward. And yet the design decisions, the coordination choices, the daily field determinations that collectively govern whether the building delivers what you need, most of those occur without your involvement.
This is not because owners are deliberately excluded. It is because the industry has evolved to make owners comfortable with the appearance of being informed. Monthly reports. Milestone meetings. Occasional site visits. These activities communicate status, which is different from providing genuine involvement in decision-making.
The firms doing substantive work on this problem begin by interviewing every party in the project ecosystem (owners, architects, engineers, subcontractors, manufacturers) to construct a complete picture of where misalignments originate. The goal is not to build better software. It is to understand which information flows are broken and where accountability dissipates.
That diagnostic work reliably produces the same finding: the problems begin in the earliest decisions and compound with every subsequent handoff.
What changes when owners are centered
When owners are genuinely integrated into the project process (not merely consulted, but structurally embedded in the information flow) several dynamics shift.
Design decisions are made with lifecycle implications visible. The mechanical system that is least expensive to install but costly to maintain looks different when the person responsible for operating costs over 25 years is part of the conversation from the start.
Risk surfaces earlier. When the owner participates in real-time project intelligence rather than receiving periodic reports, the incentive structure changes. Information that might have been buried in a weekly update gets communicated when there is still time to respond.
Closeout is treated as a substantive deliverable rather than an administrative afterthought. When owners have been engaged throughout and have a clear understanding of what they need to operate the building, the handover conversation is specific and productive rather than perfunctory.
The question worth asking before you start
Before your next project begins, ask: at what moments during design and construction will I have genuine decision-making authority, and what information will I need to exercise it effectively?
Most owners have not worked through this systematically. They are familiar with the major milestones (schematic design approval, GMP, substantial completion) but not with the many smaller inflection points where the building’s performance and cost are actually being determined.
Map those moments. Identify what you would need to know at each one. Then establish that information as a condition of how the project is structured and run.
The problems that emerge in construction were almost always planted in planning. Owners who recognize this before they begin consistently deliver better projects than those who recognize it afterward.
