In this episode of Structural Integrity, Tim Miller sits down with veteran civil engineer Tom Hoover to break down what actually goes into site design, drainage, and development planning. From subdivisions and commercial projects to city approvals and grading strategy, Tom shares what decades in the field have taught him—lessons you won’t find in a textbook or a CAD file.

This isn’t just about computers getting it wrong. It’s about understanding the land, respecting the process, and knowing when experience overrides what the screen says.

What We Talked About

• Why civil engineering is everything outside the building—and why it matters more than most people think
• How drainage mistakes happen (and why they’re expensive to fix later)
• The real process behind subdivisions, site planning, and grading
• Why starting at the low point of a site is critical in design
• How working with cities, codes, and approvals can make or break a project
• The difference between what works in theory vs. what works in the field
• Why experience still matters—even in a software-driven world

Key Takeaways

• The land always wins. You can’t design around reality—you have to work with it.
• Drainage is everything. Most long-term problems start with bad grading decisions.
• Experience fills the gaps software can’t. Computers don’t replace judgment.
• Good engineers think beyond the plans. They think about how things will actually perform over time.
• Small decisions have long-term consequences. A driveway, elevation, or slope mistake can create years of issues.

Notable Moments

• How Tom got into civil engineering and why it stuck
• Designing roads to preserve natural features (like saving a 36” tree)
• Real-world drainage failures and what causes them
• The challenges of working with different cities and regulations
• Why some projects look good on paper—but fail in execution

About the Guest

Tom Hoover is a seasoned civil engineer and founder of Thomas Hoover Engineering, LLC. With decades of experience in site development, drainage, and infrastructure design, Tom has worked on everything from subdivisions to large-scale developments across Texas and beyond. His approach blends technical expertise with real-world practicality—focused on building systems that actually work long-term.

Watch / Listen

👉 Watch the full episode on YouTube https://www.youtube.com/@StructuralIntegrityPod

👉 Read more field insights at structuralintegritypod.com

👉 Follow for more episodes of Structural Integrity

This isn’t about renderings or surface-level strategy. It’s about what happens underneath: capital stacks, risk exposure, underwriting discipline, and how experienced operators make go/no-go decisions before a project ever breaks ground.

Jeff walks through the difference between control and non-control investments, and why that distinction directly impacts risk, influence, and outcomes. If you’re not in control, you’re operating downstream from someone else’s assumptions—and that changes everything.

The conversation shifts into asset class strategy, comparing residential development with industrial deals. While industrial may look simpler on the surface, Jeff explains why execution risk still exists—and where operators often get it wrong.

They also break down how fund models spread risk across multiple projects, versus single-asset exposure where one bad assumption can collapse returns.

A major focus is on due diligence discipline. Institutional investors don’t chase upside—they protect against downside. That means structured underwriting, controlled capital deployment, and verifying every assumption before money moves.

At the core of every deal is the financial model. Jeff explains how everything—from rent assumptions to design decisions like unit size—feeds into valuation and ultimately determines whether a deal works at all.

The episode also touches on regulatory constraints in capital raising, the realities of scaling larger funds, and why writing bigger checks requires tighter discipline—not more risk tolerance.

The through-line: Risk is always present. The difference is whether it’s ignored—or engineered.