Capital projects don’t just transfer buildings. They transfer the consequences of decisions—often without transferring the reasoning behind them.

I’ll never forget a General Manager saying to me,

“We outgrew the building before the shovels hit the ground.”

He couldn’t understand how that could happen. From his perspective, it looked like poor planning.

We had both inherited the project as it was heading into permitting—he as the future General Manager who would eventually operate the building. I would help deliver it.

Neither of us had participated in the executive discussions that shaped the building.

Neither of us inherited that history.

As I pieced the project’s history together, the answer became clear.

The original building had been larger.

When the bids came back over budget, executive leadership made a financial decision to reduce the program so the project could move forward. The architects and engineers redesigned the building around the new budget, coordinated the impacts across every discipline, and completed the design.

Years later, the General Manager inherited the building.

I inherited the project.

Neither of us inherited one of the most important executive decisions that shaped what we now owned.

This Isn’t a Documentation Problem

That experience changed the way I think about project turnover.

I’ve lost count of how many times I’ve called an architect or engineer years after a project was completed.

The drawings told me what had been built. The files told me when it happened.

I needed someone who could tell me why.

They usually could. 

Not every detail, but they remembered the conversations. The alternatives that were considered. The assumptions that shaped the recommendation. The compromises leadership accepted.

That never surprised me.

The design team couldn’t do their work without understanding why the decision had been made.

A budget reduction isn’t construction documentation.

It’s an executive business decision.

The design team has to translate that decision into a building.

They determine what changes, what stays, what moves, what disappears, and how one decision ripples across every discipline.

That’s why they remember the reasoning years later.

But once the project is complete, who is responsible for ensuring the organization understands why those decisions were made ten years later?

In most organizations, the answer is nobody.

Consultants complete their work and move on. That’s expected.

Executives change priorities, get promoted, or leave. That’s expected too.

What rarely happens is that someone inside the owner’s organization inherits responsibility for preserving the project’s history.

The knowledge doesn’t disappear because people leave.

It disappears because the organization never assigned ownership of preserving it.

The building is formally transferred.

The reasoning rarely is.

Every Capital Project Leaves Behind Two Assets

Years later, someone walks through the building and asks,

“Why did they do it this way?”

The drawings explain what the building became.

They rarely explain why it became that building.

Without that context, people naturally fill in the gaps.

Sometimes they’re right.

Sometimes they’re evaluating the result of a financial decision, a strategic compromise, or an operational priority they were never told about.

Every capital project leaves behind two assets.

One is the building.

The other is its decision history.

We manage the first as though it’s permanent.

We treat the second as though nobody will ever need it again.

The Cost Doesn’t Show Up Until Years Later

This isn’t a problem at project closeout.

It’s a problem during the next renovation. Or the next expansion.

Why wasn’t this infrastructure installed? Why was this system sized this way?

Without an organizational record of the decision history, the organization starts investigating decisions it has already made.

Sometimes those decisions still make perfect sense.

Nobody knows.

Sometimes the conditions have completely changed.

Nobody knows that either.

The organization spends time, money, and executive attention rediscovering decisions it already made instead of building on the knowledge it once had.

Every renovation eventually becomes an investigation.

The Governance Gap

We’ve defined project turnover too narrowly.

We celebrate the transfer of the facility. We verify the drawings. We collect warranties. We assemble operation and maintenance manuals.

Then we declare the project complete.

But one of the project’s most valuable deliverables has never been formally transferred.

Its decision history.

Most organizations already have a place where they preserve what they can’t afford to forget. It’s called governance.

Policies live there. Delegations of authority live there. Financial controls live there.

Decision history usually doesn’t.

Instead, it lives in the memory of whoever happened to be in the room—until they retire, get promoted, or move to another company.

That’s not a documentation failure. It’s a governance gap.

The organization never decided who should own preserving its decision history.

Before declaring a capital project complete, ask one more question:

If everyone who made these decisions left tomorrow, would the next leadership team understand why this building became what it is?

If the answer is no, the project isn’t fully turned over.

---

 

Next in the Series

The Capital Decision Review

Every capital project leaves behind a small number of executive decisions that permanently shape what the organization ultimately owns.

Most organizations preserve the building.

Very few preserve the decision history that explains why it became that building.

The next article explores what it would look like if organizations preserved that decision history as deliberately as they preserve the building itself.