Existing Records Don't Always Tell the Whole Story

Why existing conditions influence infrastructure planning, project risk, and decision-making

By Andrew Johnson, Group Lead, Civil Engineering

Infrastructure projects often require important decisions to be made before teams fully understand existing conditions.

Drawings, utility records, site investigations, and historical documentation provide a valuable starting point, but they don't always capture every modification, operational reality, or field condition that may affect a project. Infrastructure systems are often built, repaired, expanded, and modified over decades, making it difficult for any single source of information to provide a complete picture.

As a result, conditions encountered in the field don't always align with what existing documentation suggests. That's not unusual. It's one of the realities of working with infrastructure that has evolved over time. Understanding that reality is an important part of making informed infrastructure decisions.

The Cost of Discovering Something Too Late

Most infrastructure challenges aren't difficult because they exist. They're difficult because they're discovered when there are fewer options available and less time to address them.

A capacity limitation identified during planning can often be evaluated alongside multiple alternatives. The same issue identified later may affect budgets, schedules, approvals, procurement strategies, or construction activities that are already underway. The challenge itself hasn't changed. The flexibility to respond to it has.

Whether the issue involves underground utilities, existing infrastructure, site constraints, or system capacity, identifying it early typically creates more opportunities to evaluate alternatives before project schedules, budgets, or construction plans become constrained.

That's one reason understanding existing conditions is so important. The value of additional information isn't always that it eliminates risk. Often, it's that it preserves options. The earlier teams understand potential constraints, the more flexibility they have when evaluating solutions and making decisions. When issues are discovered later in a project, many potential solutions may no longer be practical because schedules, budgets, approvals, procurement strategies, or construction plans are already in place. Addressing those issues can require redesign, rework, or changes to work that has already been completed, which can increase project costs and affect delivery timelines. Understanding existing conditions early helps teams make informed decisions while there is still time and flexibility to evaluate alternatives.

Understanding What's Really There

Understanding existing conditions isn't always as simple as reviewing available records.

Depending on the project, it may require site visits, utility locates, field investigations, condition assessments, surveying, geotechnical testing, capacity analysis, or conversations with the people responsible for operating and maintaining the infrastructure.

Each source of information contributes part of the picture. The objective is developing a thorough enough understanding of existing conditions that major decisions can be made with confidence.

The effort invested in understanding what's already there often pays dividends later. The more accurately teams can identify constraints, confirm assumptions, and understand how infrastructure systems actually function, the better positioned they are to evaluate options and reduce the likelihood of unexpected issues later in the project.

Asking Better Questions

Understanding existing conditions starts with asking the right questions.

What information are we relying on? What conditions still need to be confirmed? What infrastructure assets may require further investigation? Where are the areas of greatest uncertainty?

Questions like these help teams identify potential blind spots before they become project issues. They also create opportunities to gather additional information while flexibility still exists. Asking the right questions early helps teams understand what still needs to be confirmed before major decisions are made, and in many cases, that is what preserves flexibility later in a project.

Why Experience Matters

Two infrastructure projects can appear very similar on paper and present very different realities once work begins. That's one reason experience remains such an important part of infrastructure delivery.

Experience helps teams recognize where information gaps are most likely to exist, what questions deserve closer attention, and which conditions may influence delivery later in the project lifecycle. It doesn't eliminate uncertainty. It helps teams understand where uncertainty may exist and how it could influence future decisions.

That's often the difference between reacting to information and planning for it. The longer someone spends working around infrastructure systems, the more they recognize that understanding what hasn't been confirmed can be just as important as understanding what has.

How Allnorth Approaches Infrastructure Projects

At Allnorth, we spend a significant amount of time understanding existing conditions before major infrastructure planning, design, and construction decisions are made. That includes reviewing available information, identifying potential constraints, and helping clients determine where additional investigation may provide value.

It isn't always the most visible part of a project, but it often has a significant influence on the decisions that follow. Strong infrastructure projects are built on informed decisions, and informed decisions depend on understanding both what is known and what still needs to be confirmed.

Better Decisions Start with Better Understanding

Some of the most significant infrastructure decisions are made long before fieldwork begins.

The earlier teams identify constraints, validate assumptions, and develop a clear understanding of existing conditions, the more flexibility they typically have when evaluating options, managing risk, and responding to challenges.

Infrastructure projects will always contain unknowns. The goal isn't to eliminate them. It's to understand which ones matter most before major decisions are made. Strong infrastructure projects aren't defined by what teams know on day one. They're defined by how effectively they reduce uncertainty before it becomes a project issue.

Learn more about how Allnorth supports infrastructure projects from planning through delivery:

Explore Allnorth Infrastructure Services.

About the Author

Andrew Johnson is Group Lead for Civil Engineering in Allnorth’s Kelowna office, bringing more than 20 years of industry experience and approximately 15 years in project management. He specializes in municipal and industrial infrastructure projects, leading multidisciplinary teams to deliver complex water, wastewater, transportation, and civil infrastructure solutions while balancing client priorities, budgets, and timelines.