Why Your Civil Engineer Should Be the First Call on Any Land Development Project
It's a scenario I've run into more than once, and it showed up again recently. A developer comes in with a project already well into design — architect under contract, structural and MEP in place, drawings nearly ready for submittal. Everything looks like it's humming along. Except no one has called a civil engineer.
The city sends it back with a standard comment: a civil site plan sealed by a licensed engineer is required before the application can proceed. That's when they call me. And within a short time of pulling the title commitments, zoning records, and utility maps, I'm looking at utility easements that nobody has accounted for, setback violations that put the proposed building in a location that doesn't meet code, and in some cases a situation where I'm not sure the project as designed is even feasible on that particular tract.
This isn't a criticism of those clients or those architects. It's a pattern I see often enough that it's worth writing about directly.
What a Civil Engineer Sees First
Before a building gets designed, the land it sits on needs to be understood. That's the civil engineer's job — not as a support role that comes in after the design team has finished, but as a front-end discipline that shapes everything that follows.
Here's what a civil site review turns up before design even starts:
Easements. Utility easements, drainage easements, and access easements are recorded against a property and run with the land. They don't disappear because no one drew them on the site plan. If a water line easement cuts across the middle of your proposed building footprint, the building cannot go there. Period. This is one of the first things a civil engineer looks for, and it can completely reorient a site layout — or, in some cases, reveal that the project as conceived isn't workable at all.
Setbacks. Every jurisdiction has setback requirements that dictate how close a structure can be to a property line, a street right-of-way, an adjacent land use, or a floodplain boundary. Zoning setbacks, fire separation requirements, and floodplain development restrictions can each independently limit where a building can be placed on a site. When these are checked at the beginning of design — before an architect draws a single floor plan — the design team knows exactly what the buildable envelope looks like. When they're checked after a building has been fully designed, the news is often not good.
Utilities. Where does the water come in? Where does the sewer tie? What size are the mains and are they adequate for the proposed use? Is there adequate fire flow at the nearest hydrant? These questions have engineering answers, and those answers affect whether a building design is even serviceable. An architect can design a beautiful building in a location where there is no practical utility connection. The civil engineer is the one who figures that out before the project is too far along to change course.
Drainage. Grading a site, managing stormwater, and getting drainage to work within the constraints of what's adjacent — neighboring properties, streets, and downstream drainage systems — is a civil engineering function. Stormwater detention requirements in Waco and McLennan County can require significant land area and affect how much of a tract is actually usable for development. That's a site planning constraint, not a detail.
Floodplain. A portion of a tract inside a FEMA-mapped Special Flood Hazard Area changes the math on development significantly. Flood zone restrictions, freeboard requirements, and the possibility of Letters of Map Amendment all need to be evaluated before an architect assumes the entire site is buildable.
The Cost of Getting the Sequence Wrong
These situations are usually recoverable — but recovery costs more than getting it right the first time. It means extra time, likely some redesign, and in some cases a genuine question mark over whether the project as conceived will fit the site at all. That uncertainty is the most expensive part. The architect has been paid. The structural engineer has been paid. The owner is carrying holding costs on the land. And now the project is in a holding pattern waiting on civil site work that should have been done before anyone else picked up a pencil.
In land development, most problems are cheapest to solve at the beginning. An easement conflict caught during a pre-design site review is a conversation. An easement conflict caught after a building has been fully designed and submitted for permit is a redesign — and possibly a re-evaluation of whether the project makes sense at all.
The civil engineering work that gets done early in a project — title review, zoning research, utility coordination, grading feasibility — is often a fraction of the total engineering fee. It's also the work that tells you what's actually possible before you've committed significant resources to a design direction that the land can't support.
How the Right Sequence Works
The civil engineer should be on the phone before the architect starts schematic design. That's not a turf issue — it's a sequencing issue.
A good pre-design civil review gives the design team the information they need to do their job well: here's the buildable envelope, here's where utilities can connect, here's the grading challenge on the east side of the site, here's the drainage constraint that affects where you can put parking. Armed with that information, an architect can design a building that actually works on its site from the first sketch.
That's a better outcome for everyone — the owner, the architect, the engineer, and the project. It's also the only sequence that doesn't risk putting a fully designed building in a location that won't pass a civil site plan review.
A Word on Feasibility
One of the most valuable things a civil engineer can do at the beginning of a project is tell a client that a project isn't feasible — or that it's feasible only in a significantly modified form. That's not a failure. That's the whole point.
Money spent on a civil site feasibility review before design begins is money that either validates that you're headed in the right direction or saves you from spending far more on a direction that was never going to work. Either way, it's one of the highest-return investments available early in a development project.
What We Do at Merritt Engineering
When a developer or property owner calls us before design starts, we can do a preliminary site review that covers zoning setbacks, utility availability, easement identification, floodplain status, and basic grading feasibility. That review becomes the foundation for the civil site plan work that follows — and it gives the rest of the project team what they need to do their work in the right order.
If you're planning a development project in Waco or Central Texas, the best time to call a civil engineer is before you call anyone else. We're happy to have that conversation early. That's exactly where we do our best work.
Reach out and let's talk about your site before the design gets out ahead of the civil.