Almost every site plan gets comments on its first review. That is not a sign something went wrong. Plan review exists to catch issues before they are built, and a set of comments is the normal product of a reviewer doing the job.
What varies is how many rounds it takes to clear them. One round of comments is routine. Three or four rounds is where schedules slip, carrying costs pile up, and a project that looked straightforward starts to feel stuck.
Most of the difference comes down to a handful of patterns.
Where comments come from
Reviewers are checking the plan against a defined set of requirements: zoning, the jurisdiction's design standards, stormwater rules, traffic and access criteria, utility provider standards, and fire access. In Huntsville, Madison, Madison County, Knoxville, and Chattanooga, those requirements live in different documents and are often reviewed by different departments.
Comments tend to fall into three groups.
Missing information is the most common. A detail not shown, a calculation not included, a note left off the cover sheet. These are easy to fix and entirely avoidable.
Conflicts with a standard come next. A drive aisle narrower than required, a slope steeper than allowed, a pipe without enough cover. These require a design change, sometimes a small one and sometimes one that ripples through the plan.
Judgment calls are the third. A reviewer reads a requirement differently than the designer did, or asks for something beyond the letter of the standard because of a local condition. These take a conversation, not just a revision.
Comments that should never happen
The first group is where the most time is lost for the least reason. A plan that goes in incomplete will come back, and the review clock usually restarts on resubmittal.
The fix is internal. Before a set goes out, it should be checked line by line against the jurisdiction's submittal checklist, and against the comments that jurisdiction has issued on similar projects. Most offices are consistent about what they look for. A firm that tracks those patterns submits plans that answer the common questions before they are asked.
We run every set through a structured review before submittal for exactly this reason. It is cheaper to find a missing detail in our office than in someone else's.
Responding to comments well
How a resubmittal is packaged matters almost as much as what changed.
A clear response letter that restates each comment, explains how it was addressed, and points to the sheet where the change appears makes the second review faster. A reviewer who has to hunt for changes will find other things while looking.
When a comment calls for a judgment the design team disagrees with, the right move is usually a phone call or a meeting before the resubmittal, not a written argument in the response letter. A five-minute conversation often resolves what three rounds of letters would not.
Every change should also be checked for side effects. Moving a curb to answer a fire access comment can change a drainage area, which changes a pipe size, which changes a grading plan. A resubmittal that fixes one comment and creates two new ones costs a full review cycle.
Front-loading the hard questions
The judgment-call comments are best handled before the first submittal. A pre-application meeting is the place to raise anything unusual about the site or the proposal: an entrance close to an intersection, a stormwater outlet through someone else's property, a building that needs a variance.
Reviewers generally prefer to weigh in early. Once they have seen the issue and offered direction, the plan that comes in later is shaped around it instead of colliding with it.
Coordination with outside agencies
Some reviews are not controlled by the city or county at all. A connection to a state route, a utility extension owned by a separate provider, or work near a regulated stream can bring in another agency on its own schedule.
Those reviews should start as early as the design allows, run in parallel with local review, and be tracked as their own line on the schedule. Waiting for local approval before starting them is one of the more common ways a project loses time it cannot get back.
The takeaway
Comments are part of the process. Multiple rounds of them usually are not.
Complete submittals, clear responses, early conversations about the hard questions, and parallel coordination with outside agencies are what keep a project moving through review. None of it is complicated. It just has to be done every time.
If you have a project heading into review in North Alabama or East Tennessee, we are glad to talk through how to set it up for a clean first round.
