5 step methodology to significantly reduce the risk of late changes and change orders

Knowledge Gap Closure: The Early Decision Practice That Prevents Most Construction Change Orders

Here is a statistic worth sitting with. A study of 600 change orders across 12 construction projects found that more than 80 percent of them traced back to early decisions where knowledge gaps were present. Not construction errors. Not late-stage surprises with no antecedents. Early decisions, made when understanding of the project was at its lowest, that compounded into change orders, delays, and cost overruns across every phase that followed.

This pattern is not unique to those twelve projects. It is structural. Every project has an early phase where decisions carry the most long-term consequence and are made with the least information available. The question is not whether knowledge gaps exist in that phase, they always do. The question is whether the team has a disciplined process for identifying those gaps, sequencing them, and closing them before the decisions that depend on them get locked in.

The Pain of Unmanaged Knowledge Gaps

The countertop example in the original piece is worth using because it is so clear. You want to replace your kitchen countertop with granite. Early decision: order the granite. Assume a simple swap. Done. What could go wrong?

The list is long. The maximum weight the current cabinets can support. The cost and availability of granite versus alternatives. The dimensions of the slab relative to logistics constraints does it need to be cut into sections to get into the kitchen? The location of cut-outs for fixtures. The reason granite was specified in the first place, is it aesthetic, practical, or habitual? which determines whether an alternative could work if a barrier arises.

None of those questions requires expertise to ask. They require only the discipline to ask before ordering rather than after the slab arrives and does not fit the cabinets. Construction projects are full of equivalent situations, at every scale from countertop to foundation design to commissioning sequence. The decisions are made early. The knowledge gaps are ignored. And the change orders arrive later, carrying the accumulated cost of the assumption that was wrong.

Why This Is a System Problem

Early decisions in construction are almost always made under time pressure, with incomplete stakeholder involvement, and before the people with the most relevant knowledge have been brought into the room. Design engineers make structural decisions before construction managers have reviewed constructability. Owners specify materials before trade partners have evaluated installation logistics. Procurement happens before the production plan has been coordinated to the supply chain dates. Each of these is a rational response to the sequence in which people typically get involved. None of them is malicious. But the system that brings people in too late for their knowledge to influence early decisions is the system producing the change orders. Not the people making the decisions.

This is why the Lean Project Delivery System places such emphasis on early involvement. The most valuable time to incorporate knowledge is before decisions are committed. Every stakeholder who enters the project after the early decisions have been locked in becomes a source of change orders rather than a contributor to avoiding them.

The Five-Step Knowledge Gap Closure Method

The methodology below has been applied across hundreds of projects in multiple industries, including both automotive and construction. It is based on a straightforward distinction: there are things you know you do not know explicit knowledge gaps and there are things you do not know you do not know tacit knowledge gaps. Both kinds can be identified and managed through structured, moderated dialogue.

The first step is to perform an early workshop specifically to identify knowledge gaps. This workshop is not a project kickoff meeting and it is not a design review. Its sole purpose is to surface what the team does not yet know that they need to know. Three categories help structure the dialogue: knowledge gaps regarding concepts, what are the options, costs, and implications of specific choices? knowledge gaps regarding constraints, what physical, logistical, regulatory, or structural limitations affect those choices? and knowledge gaps regarding customer needs, what does the customer actually require, and why? Understanding why a requirement exists is often what makes it possible to find an equivalent solution when a barrier to the original specification arises.

The categories are a facilitation tool, not a classification system. The goal is to generate questions. Knowledge gaps expressed as questions stimulate dialogue more effectively than problems stated as concerns. The more experienced and diverse the team in the workshop, the better the questions will be not just more numerous, but clearer in what they require to be closed.

The second step is to sequence and prioritize the gaps. Some knowledge gaps must be closed before others can be addressed. Some can be worked on in parallel. Some unlock a cascade of downstream decisions the moment they are resolved. The sequencing work is what transforms a list of questions into a path through the early phase of the project, a visible roadmap of what needs to be known and when, rather than a collection of open items that get addressed whenever someone gets to them.

The third step is balancing being right against being quick. This is the most difficult part and the one that requires the most skilled facilitation. Every team has people who want to make decisions quickly to feel progress, willing to carry assumptions and risks rather than surface them. And every team has people for whom no amount of data feels sufficient to make a decision with confidence. Both patterns are understandable. Both are counterproductive when left unmanaged.

The practical questions that help find the balance are worth applying deliberately. What is the lowest level of knowledge needed to make progress on this decision? The knowledge gap may not need to be fully closed to allow the decision to move forward, a partial closure may be enough to reduce risk to an acceptable level. What is the cheapest way to acquire the knowledge needed? Does it require primary data from measurements, or can a qualified estimate with accessible secondary data provide sufficient confidence? Can a few hours with an expert close the gap? Can a question to a similar project produce useful insight? The goal is not perfect information. It is enough information to make a decision that will not require revision downstream.

The fourth step is securing ownership and deadlines. Closing a knowledge gap requires specific tasks and deliverables. Someone owns each one. There is a deadline. Without ownership and deadlines, the knowledge engine identifies the gaps but never closes them. This is not unique to knowledge management; it is the same discipline that makes any project management system functional. But it is worth naming explicitly because the temptation in early project phases is to treat open questions as shared concerns rather than as assigned deliverables.

The fifth step is to keep the knowledge engine running. Knowledge gaps are iterative. As initial gaps get closed, new ones emerge from the clarity that resolution creates. The methodology does not have a completion point, it runs continuously through the project’s early phases, with each iteration producing a better-understood project and a more reliable foundation for the decisions that follow. Projects managed without explicit attention to knowledge gaps are still implicitly managing them, every calculation task, every coordination review, every design iteration is triggered by a knowledge gap. The discipline of naming them explicitly simply makes the process faster, more reliable, and more visible.

Here are the signals that a project team is managing knowledge gaps rather than ignoring them:

• Early decisions carry documented assumptions rather than appearing as certain conclusions.
• The team has a visible sequencing of open questions that need resolution before specific decisions can be locked in.
• Subject matter experts are brought into planning conversations before the specifications that depend on their expertise are committed.
• Change orders are tracked back to their origin and the team asks whether an earlier dialogue would have prevented them.
• The early phase includes structured time for identifying what the team does not yet know, not just for making plans.

Connecting to the Mission

At Elevate Construction, we teach that the project planning phase is the largest single determinant of project success. The First Planner System, pre-construction planning, pull planning with trade partners, conditions of satisfaction, all of these are expressions of the same principle that knowledge gap closure formalizes: the time to apply knowledge is before decisions are locked in, not after they become change orders. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The early decisions matter most. Make them with the right knowledge, from the right people, asked as specific questions, sequenced in the right order. The 80 percent of change orders that trace back to early knowledge gaps are avoidable. Not by knowing everything at the start, that is impossible. By knowing what you do not know and managing the process of closing those gaps before they close themselves in the form of a change order.

On we go.

Frequently Asked Questions

What is a knowledge gap in construction project delivery?

A knowledge gap is anything the project team does not yet know that they need to know in order to make a reliable decision. Explicit knowledge gaps are things you know you do not know. Tacit knowledge gaps are things you do not know you do not know and structured dialogue is what surfaces them.

Why do most change orders trace back to early decisions?

Because early decisions carry the most downstream consequence and are made when project knowledge is at its lowest. Decisions locked in before the relevant expertise, constraints, and customer requirements are fully understood tend to require revision when reality diverges from the assumptions those decisions were based on.

What is the difference between balancing being right and being quick?

Some decisions need to be made before all knowledge is available. The discipline is knowing what minimum level of knowledge is sufficient to make a decision that will hold, and finding the cheapest way to acquire that knowledge rather than either guessing or waiting for certainty.

Who should attend a knowledge gap identification workshop?

The most knowledgeable and diverse group that can be assembled for the project’s early phase including design professionals, the construction team, key trade partners, and end users where possible. The quality of the knowledge gaps identified is directly proportional to the breadth and depth of the people in the room.

How does knowledge gap management connect to Lean project delivery?

It is the practical mechanism for the Last Responsible Moment principle in Lean design. Decisions are not made earlier than necessary, and knowledge gaps are actively managed so that when the last responsible moment arrives, the team has the knowledge needed to make the decision well.