Five years after a hospital opens, the HVAC in one wing consistently underperforms. The facilities team investigates. What do they have? Equipment manuals and as-built drawings. What do they need? The reasoning behind the original design, the value engineering decisions that affected capacity, the commissioning data showing actual versus designed performance, the mechanical engineer’s notes about site-specific conditions.

That information existed. It was in the heads of the MEP engineer, the commissioning agent, the contractor’s coordination lead. But the project ended. Those people scattered to other projects. The reasoning is gone.

The owner paid to have all that knowledge created. Now they’re paying again (in troubleshooting time, consultant fees, and years of suboptimal operations) because they can’t access it.

This is the dissolution tax.

What happens when a project ends

Construction is the only industry where we form a $500 million company, build a world-class product, and then disband the team and lose the institutional knowledge the day we finish.

When you break ground on a new building, you’re not just starting a project. You’re creating a temporary enterprise. The owner, the owner’s rep, architects, structural engineers, MEP engineers, the GC, dozens of specialty subcontractors, suppliers, inspectors, a significant project might involve a hundred or more independent companies working together over three to five years.

When construction ends, that enterprise dissolves. The companies scatter to other projects. The teams reconstitute with different participants. The relationships, workflows, and institutional knowledge all disperse.

This is fundamentally different from how any other industry operates. A software company that builds a product keeps the team. The organization that made the product continues to exist, can learn from what they built, can fix problems that emerge later. A construction project’s “organization” ceases to exist the moment the project closes out.

What the dissolution tax actually costs

The numbers are not abstractions. More than 70% of capital projects exceed their original budget. About 40% of project costs (not profit, not legitimate overhead, but waste) disappears into coordination failures, rework, and fixing problems that shouldn’t have happened. On a $200 million hospital project, that’s $80 million that benefits no one.

And construction productivity has declined for 40 years while every other major industry improved. Manufacturing doubled productivity. Information services tripled it. Construction went backwards.

This isn’t because construction people are less capable. It’s because the structure of how construction work gets organized prevents the kind of learning and compounding improvement that happens in persistent organizations. When every project is a new temporary enterprise that dissolves at completion, there’s no mechanism for improvement to compound across projects.

Why the software investments haven’t worked

If you’ve spent the last decade investing in construction technology and been disappointed by the results, this is why.

Procore, Autodesk, P6, and every other project management platform were built for persistent organizations. They assume there’s one company managing the project. On a construction project, there are fifty or a hundred companies, each with their own systems, each with different incentives about what to share and what to protect.

You can require subcontractors to enter data into your Procore instance. That doesn’t make it their source of truth. They’re maintaining two systems, theirs and yours, and theirs is the one they actually trust.

More fundamentally: these tools capture state, not reasoning. Your project management software can tell you the RFI was answered on Thursday. It cannot tell you why it was answered that way, what alternatives were considered, or what the underlying coordination problem really was.

The state clock, what’s true right now, gets updated. The event clock, how things got to be this way, stays empty.

Research suggests roughly 40% of owner-useful asset data ends up stranded in PDFs, essentially inaccessible for the thirty to fifty years of building operations ahead. The owner paid for all that information to be generated. Almost none of it survives in usable form.

The gap between design intent and operational reality

The lifecycle of knowledge on a typical project follows a consistent pattern.

During design, the architect evaluates multiple structural system options. They weigh cost, schedule, constructability, and aesthetic intent. They make a decision. What gets documented: the final design. What gets lost: the alternatives considered, the reasoning, the tradeoffs that make the final choice make sense.

During construction, an unforeseen condition requires a workaround. Three subcontractors coordinate. Schedules adjust. What gets documented: a change order showing cost and time impact. What gets lost: the problem-solving process and what was learned from it.

At handover, the owner gets boxes of closeout documents: O&M manuals, warranties, as-built drawings. What gets documented: final state of systems. What gets lost: design intent, commissioning learnings, known operational issues, recommendations from the people who built it.

The owner now owns a building whose full story they don’t know, built by an organization that no longer exists.

What would actually help

The structural problem points toward a different kind of solution.

Capture reasoning, not just outcomes. The most valuable information isn’t the final schedule or the as-built drawings. It’s the decision logic. When your team makes a significant decision, five sentences explaining why (what was considered, what constraint drove the outcome) are worth more than a hundred pages of documentation about what was decided.

Own the information, not just the building. As an owner, you should push for information handoffs that survive project close-out. Not PDFs, queryable, searchable knowledge about why your building was built the way it was. The contractor who can deliver that alongside the building is delivering something genuinely more valuable, and you should compensate accordingly.

Prioritize persistent relationships. The dissolution tax is worst when every project assembles a completely new cast. It’s less severe when you work with the same architects, the same GC, the same key subs across multiple projects. In those repeat relationships, some institutional knowledge does persist. The cost savings from maintaining strategic relationships may exceed the savings from price competition, when you account for the coordination-failure waste that comes with constantly new teams.

The $10 trillion construction industry has smart, hardworking people. It also has a structural problem that prevents it from learning from itself. The dissolution tax explains why productivity has declined for forty years despite enormous technology investment.

Better software on a broken structure is still a broken structure. What the industry needs, and what the best owners are already demanding, is a different relationship with information. One where the reasoning behind the building survives long enough to help the people who have to live with it.