When Public Infrastructure Becomes Private Loss
Takings risk belongs in the development file before the government action becomes the project’s hidden cost.
The public project can still create a private loss
Commercial real estate underwriting often treats public infrastructure as background. Roads, drainage, flood control, utility routing, access, medians, easements, detention, and public improvements are considered part of the civic environment around the project.
But public infrastructure can become a direct private loss.
When government action changes how water moves, limits access, burdens development, redirects traffic, imposes exactions, or physically affects property, the result may not be a normal market risk. It may be a compensable property injury, a valuation impairment, or a transaction condition that should have been identified before capital was committed.
The point is not that every government burden is a taking. The point is that public-action risk must be documented before the project is trapped inside it.
The DeVillier lesson
In DeVillier v. Texas, property owners alleged that Texas’s construction of a highway median barrier caused floodwaters to be stored on their land, damaging the property. The Supreme Court allowed the owners to pursue their Takings Clause claims through the cause of action available under Texas law. The underlying principle is that when private property is taken for public use, just compensation is not optional.
For CRE stakeholders, the lesson is practical. A public improvement can improve one system while impairing another. A flood evacuation route may serve a public purpose and still concentrate loss on private land. A drainage improvement may protect one area while burdening another. A road redesign may solve traffic flow while undermining access, visibility, or development assumptions.
The legality of the government action and the economic impact on the property are related but distinct questions.
Why this belongs in the underwriting file
Takings and public-action issues often emerge late because they are not always framed as transaction risks at the start.
A site may have access today. Drainage may appear adequate today. Municipal approvals may seem routine today. But the diligence file should ask what public projects, easements, exactions, stormwater plans, road improvements, utility relocations, or flood-control measures could materially affect the property’s use, value, access, or development timeline.
If the project depends on ingress, egress, drainage, grading, detention, visibility, traffic counts, utility service, or municipal approvals, public-action risk is not peripheral. It is part of the value model.
The documentation problem
The hardest part of a public-action dispute is often not the theory. It is the record.
What did the property look like before the public action? What did the government build, approve, require, alter, or deny? When did the impact begin? Who received notice? What studies existed? What objections were made? What damages occurred? What mitigation was attempted? What alternatives were rejected? How did the action affect value, use, financing, insurance, or saleability?
If those facts are not preserved contemporaneously, the owner’s position weakens. Memory becomes the archive. That is not a defensible record.
Public action and private capital
This matters especially in financed and syndicated projects.
A sponsor may underwrite an asset based on future development capacity. A lender may rely on an appraisal that assumes access and entitlements. An investor may accept a business plan that assumes drainage, utility service, or municipal approval. If public action later alters those assumptions, the issue becomes more than a land-use dispute. It becomes a capital-stack problem.
The project team must be able to explain whether the loss is regulatory, physical, economic, temporary, permanent, insured, uninsured, compensable, curable, or merely absorbed by the deal.
That explanation requires a record.
The operational response
The proper response is disciplined reconstruction.
Public-action materials should be gathered into a single file: plats, surveys, title exceptions, easements, municipal correspondence, engineering reports, hydrology studies, traffic studies, permit history, meeting minutes, public notices, appraisals, photographs, incident reports, lender communications, insurance correspondence, and stakeholder updates.
Then the chronology should be built. Before condition. Government action. Impact. Notice. Response. Financial consequence. Mitigation. Open issues.
This does not replace legal analysis. It gives legal analysis something to stand on.
Working with counsel
AEEA does not determine whether a taking occurred or provide legal advice concerning constitutional claims. That judgment belongs to counsel. AEEA’s work is business-side record discipline: organizing facts, reconstructing chronology, preserving documents, identifying missing proof, and preparing a counsel-ready file for evaluation.
Public infrastructure may be public. The loss record is private.
If the project has been affected by government action, the first question is not whether the dispute will be litigated. The first question is whether the file can prove what happened.
AEEA provides this perspective for general information. It is not legal advice. For a specific matter, work with your counsel — AEEA supports that work operationally.