Delays and cost overruns in construction are no longer surprising. They have become the norm. And with that, a habitual reaction has also appeared.: “It’s construction, nothing you can do.”
But is that really true? Can this be fixed? And if yes, how? Usually, the blame goes to contractors, delayed funding, or weak control. But when the same problems repeat across different projects, it points to something deeper. The issue is in the decision-making system. If the failures are systemic, the solution has to be systemic too.
To see this clearly, let’s look at construction projects through the lens of GAPs. These are gaps between how management should work and how it actually works in practice. Over time, these gaps add up and show up in deadlines, budgets, and quality.
The key gap is in what we actually manage. In practice, “construction” often means just construction and installation works. Management focuses on schedules, budget spending, and contractor control. This creates a stable illusion: if construction is on track, the project is under control.
But construction is just the execution of decisions already made. By the time work starts on site, most key parameters are already fixed: the design, site constraints, technical solutions, and a large share of the total cost. At this point, the ability to influence the project is already limited.
In reality, the object of management is not the construction phase. It is the full life cycle of the asset, from idea to decommissioning. This includes three stages: creation, operation, and end of life.
This approach matters because it shifts the focus from managing construction works to managing the final outcome over the entire life span of the project. Each stage should pass value to the next.
This difference becomes clear in several ways.
First, the most important decisions are made at the very beginning. Up to 70–80% of the total project cost is shaped in the early stages. At the same time, the actual spending at that point is still low. This means one thing: a mistake made early will carry through the entire project.
Fixing it gets more expensive over time. At the design stage, costs increase by 1.5–2 times. During construction, by 2–3 times. During operation, costs can grow by tens of times due to repairs, downtime, and maintenance.
So cutting time and effort at the early stages does not save money. It creates bigger and less controllable costs later.
Second, project cost is not just the construction budget. CAPEX covers construction costs. But the larger share comes from OPEX: operation, maintenance, energy use, and service. If decisions focus only on reducing CAPEX, the result is often an asset that is expensive to operate and inefficient over time.
Third, project stability depends on the quality of initial data. To move into execution, you need confirmed permits, technical conditions, and clearly defined requirements. If these are missing, the project starts with incomplete information. Design and construction move forward while the inputs are still being clarified. This means decisions are temporary and will likely change later. This is where another major gap appears. In theory, decisions should be clarified step by step. In practice, everything moves in parallel, followed by corrections.
Changes discovered during construction lead to immediate cost increases: minor changes add 5–15%, design changes 15–30%, and system-level changes 30–50% or more. This is not an exception. It is a predictable result of unstable inputs. There are also points in the project after which changes become much more expensive.
After the concept is approved, changes are limited. After design documentation is completed and reviewed, changes require redesign. Once construction starts, changes mean rework, delays, and extra costs. After commissioning, mistakes become part of the asset and can only be fixed through additional investment. This is why construction does not create problems. It reveals them and locks them in.
Fourth, the management issue. Projects require clear separation of roles: decision-making, execution management, and expert input. When these roles are not separated, and management turns into a series of ad hoc instructions without clear authority, the project shifts into a reactive mode. Problems are not prevented, they are fixed after they appear.
Fifth, the systemic issue. Regulation and management practices are heavily focused on the construction phase. This shapes behavior: attention goes to the stage where problems become visible, not where they are created.
As a result:
- budget growth starts when initial data is still incomplete
- operational issues are built in at the requirements stage
- conflicts during construction come from weak early decisions
As long as construction remains the main focus, management stays reactive. Shifting focus to the full life cycle changes the logic: first define requirements and constraints, then confirm inputs, then integrate decisions into design, and only after that move to construction.
In the next parts, we will look at how the key gap is formed in the early stages, when a project appears ready even though it is not. Because the real question is not how we build. The real question is what decisions we rely on when we decide to start building.
Svetlana Nurtazina, civil engineer, PhD, certified project manager, specifically for www.economyKZ.org


