A site design review sounds like a formality. It isn’t. Done right, it’s the one meeting that catches conflicts before they turn into change orders. For developers working in Memphis, TN, skipping a real design review is one of the fastest ways to end up redoing work that was already stamped and submitted.
This article explains what a site design review actually covers, why mid-project changes cost so much, and how to build this checkpoint into a project without slowing everything down.
What a Site Design Review Actually Is
A site design review is a checkpoint. It happens before drawings get finalized, not after.
At this stage, every discipline involved in the project puts their plans on the table together. Architecture. Civil. Landscape. Structural. MEP. The goal is simple: find the conflicts now, while they’re cheap to fix, instead of finding them during construction, when they’re not.
A real design review is a structured form of interdisciplinarity, where architecture, civil engineering, structural, MEP, and landscape teams align their plans to identify conflicts early. It is not a quick email chain or a single person glancing at a plan set. It’s a structured session where each discipline walks through their portion of the site and flags anything that doesn’t line up with the others.
Why Mid-Project Changes Cost More Than They Should
A change made on paper costs almost nothing. The same change made after construction starts costs a lot more.
Here’s why the cost jumps so fast:
- Materials already ordered or installed may need to be removed and replaced.
- Subcontractors scheduled for later phases sit idle while the change gets sorted out.
- Design fees increase when drawings need to be reissued and re-stamped.
- Permitting offices may require a resubmission if the change affects approved plans.
- Project timelines shift, which can push completion past contract deadlines and trigger penalties.
Memphis has seen steady commercial growth in recent years, and tighter construction schedules mean less room for a mid-project surprise to absorb without real cost.
What Gets Caught in a Site Design Review
A thorough review looks past the obvious and checks how each piece of the site actually fits together.
Common conflicts a design review catches:
- A building footprint that overlaps with a required drainage easement.
- Landscape plans that place trees or plantings over underground utility lines.
- Grading that doesn’t match the elevations assumed in the architectural plans.
- Parking layouts that don’t leave enough clearance for fire access or loading zones.
- Structural column placements that conflict with mechanical or plumbing routing.
Each of these looks small on paper. Each one becomes a real problem once concrete gets poured or utilities get trenched.
Who Needs to Be in the Room
A design review only works if the right people are actually part of it. Skipping a discipline defeats the purpose.
At minimum, the review should include:
- The architect responsible for the building design.
- The civil engineer handling grading, drainage, and site utilities.
- The landscape designer, especially on sites with tight setbacks or drainage features.
- The structural engineer, to confirm foundation and column placement works with the site plan.
- A representative from the contractor’s team, if construction is already lined up, since they often catch practical issues designers miss.
Leaving out even one of these voices means their portion of the plan doesn’t get checked against everyone else’s. That’s usually where the conflict shows up later.
Building a Design Review Into Your Project Schedule
A design review works best when it’s planned, not squeezed in at the last minute.
A few habits that make this checkpoint actually effective:
- Schedule the review once schematic design is far enough along to show real conflicts, but before construction documents are finalized.
- Require every discipline to bring current plans to the meeting, not outdated versions from a prior phase.
- Assign someone to document every issue raised and confirm it gets resolved before moving forward.
- Build a second, shorter review into the schedule before final submission, to catch anything that changed since the first pass.
For developers managing multiple projects in Memphis, treating the design review as a fixed step on every project, not an optional one, keeps costly mid-project surprises rare instead of routine.
Frequently Asked Questions
When should a site design review happen in the project timeline?
A site design review should take place after schematic design is developed enough to reveal real coordination issues but before construction documents are finalized. Reviewing too early may miss key details while reviewing too late can limit the ability to make cost-effective changes.
Who should lead a site design review?
Typically, the civil engineer or project architect leads the review because site-wide conflicts often involve both building placement and grading design. The lead should have the authority to recommend and implement changes before the review is closed.
Can a design review replace a permitting review?
No. A design review is intended to identify coordination issues between disciplines while a permitting review ensures compliance with local codes and regulations. Both are necessary and serve different purposes.
How long does a proper site design review usually take?
The duration depends on project size and complexity but a focused, well-coordinated session with all disciplines present is generally far more efficient than resolving issues later during construction or after permit submission.
What happens if a conflict is found after construction has already started?
If a conflict is discovered during construction, the project may need to pause while the issue is resolved. This often results in design modifications, change orders, and potentially permit revisions, all of which are typically more costly and time-consuming than addressing the issue during early design.