Re-submitting permits after receiving revision requests is often the most critical juncture in the approval workflow. A mishandled re-submission can derail project timelines, inflate costs, and frustrate stakeholders. Yet with a structured approach, applicants can turn this step into a smooth, predictable process. This expanded guide provides a comprehensive roadmap—from interpreting feedback to final approval—to help you navigate re-submissions with confidence and efficiency.

Understanding the Re-Submission Process

When a permitting authority requests revisions, they are not rejecting your application outright. Instead, they are providing a path to compliance. Re-submission means updating your original application materials—plans, forms, supporting documents—to address specific concerns, and then re-presenting them for review. The process can range from a simple correction (e.g., a missing signature) to a complex redesign of building systems or site layout.

It’s essential to recognize that the re-submission process is iterative. Most jurisdictions allow two to three review cycles before requiring a formal appeal or resubmission fee. Understanding the local rules—including typical turnaround times, fee structures for re-submissions, and accepted formats—can save weeks of back-and-forth. Many permitting authorities publish their revision and re-submission procedures online; bookmark these pages and refer to them at each step.

Common triggers for revisions include code compliance issues, incomplete documentation, conflicting drawings, or concerns about environmental impact, fire safety, accessibility, or zoning. By categorizing feedback into technical, administrative, and design categories, you can assign the right resources to resolve each issue efficiently.

Step-by-Step Re-Submission Guide

Below is a detailed, action-oriented sequence to follow. Each step builds on the previous one, helping you maintain momentum and avoid common pitfalls.

1. Thoroughly Review the Revision Request

Begin by reading every comment from the permitting authority, even those that seem repetitive. Often, comments are grouped by discipline (structural, electrical, plumbing, etc.) or by sheet number. Create a master checklist that maps each comment to a specific action item. This checklist will serve as your quality control tool throughout the revision process.

Key actions at this stage:

  • Highlight comments that require design changes vs. clarifications vs. administrative corrections.
  • Note any references to specific code sections or standards—look them up to ensure your response addresses the underlying requirement, not just the symptom.
  • Identify comments that may conflict with each other or with your original design intent. Flag these for discussion with the reviewer through a formal inquiry or pre-submission meeting, if allowed.
  • Determine the deadline for re-submission (if any) and whether partial re-submissions are permitted.

Also, look for patterns. If multiple reviewers ask for the same missing information (e.g., structural load calculations), it’s likely a gap in your original package. Addressing these systemic issues early prevents repeated delays.

2. Execute the Revisions Methodically

Once you have a clear list of required changes, assign each item to the appropriate team member—architect, engineer, consultant, or internal project manager. Use a revision tracking spreadsheet or project management tool to monitor progress and ensure nothing falls through the cracks.

Best practices for making revisions:

  • Use redline or cloud mark-ups: Clearly indicate where changes have been made on drawings and documents. Many jurisdictions require a revision cloud or a separate revision sheet to facilitate quick review.
  • Update all related documents: A change to the floor plan may affect the reflected ceiling plan, MEP layouts, or schedules. Check cross-references.
  • Write a clear response narrative: In addition to visual mark-ups, include a written response that states how each comment was addressed. This helps the reviewer verify compliance without hunting through every sheet.
  • Double-check for consistency: If you change dimensions on one page, ensure corresponding elevations, sections, and details align.
  • Involve a peer review: Have a colleague who was not involved in the original design review the revised package for completeness. Fresh eyes often catch overlooked errors.

For complex projects, consider hiring a third-party code consultant to review the revisions before submission. The upfront cost is often offset by avoiding another review cycle.

3. Compile the Complete Re-Submission Package

Your re-submission package must be more than just revised drawings. It should include a cover letter or transmittal form, the revised documents (with changes clearly identified), a response to comments table, and any new supporting calculations or certifications.

Typical contents of a thorough re-submission package:

  • Cover letter / transmittal: Include project name, permit application number, date, and a concise summary of changes. State that all comments have been addressed and attach the response matrix.
  • Response to review comments: A table listing each comment verbatim, followed by the applicant’s response (e.g., “Revised per comment – see sheet A-301”). Number comments exactly as in the review letter.
  • Revised drawings and specifications: Provide full revised sheets, not just the changed areas. Clearly mark revisions with clouds and include a revision number/date.
  • Supporting documents: Updated calculations, product cut sheets, geotechnical reports, or energy compliance forms as needed.
  • Application forms: Some jurisdictions require a new or amended permit application form for re-submissions. Check local requirements.
  • Proof of re-submission fee payment: If applicable, attach the receipt or fee waiver.

Organize the package logically—typically in the same order as the original submission. If submitting digitally, name files clearly (e.g., “A-101_FloorPlan_Rev2.pdf”) and combine related files into a single PDF where possible. Many online portals have file size limits; compress large files without sacrificing legibility.

4. Submit Using the Specified Method

Follow the submission instructions exactly as defined by the permitting authority. Common methods include online portals, email (with strict naming conventions), physical delivery, or in-person drop-off. Each has its own nuances.

  • Online portals: Register for an account, upload files, and fill out required fields. Some portals require you to re-enter the application number and project details. Keep a screenshot of the submission confirmation.
  • Email: Use the subject line format specified by the agency. Attach files in the approved format (usually PDF, sometimes DWG). Set “read receipt” if allowed.
  • Physical delivery: Print required number of copies (e.g., three full-size sets, one half-size set). Use reputable courier service with tracking. Include a return label if you need stamped copies back.
  • In-person: Check counter hours and whether appointments are needed. Bring a copy of the review letter and your checklist to answer questions on the spot.

Regardless of method, retain proof of submission: portal confirmation number, email timestamp, courier tracking, or dated receipt from the counter.

5. Confirm Receipt and Track Progress

After submission, do not simply wait for a response. Proactively confirm that your package was received and is in the review queue. Many online systems update status to “Under Review” or “Revisions Received.” If no update appears within a few business days, call or email the assigned plan reviewer.

Follow-up best practices:

  • Note the expected review cycle duration (often 2–6 weeks depending on jurisdiction complexity).
  • Keep a log of all communications: dates, names, what was discussed.
  • If the reviewer requests additional information during the second review, respond promptly and consider it a continuation of the same cycle.
  • Avoid submitting unrelated changes—those can reset the review clock.

If the review period passes without a decision, follow up politely. Persistence shows commitment, but respect the reviewer’s workload.

Common Pitfalls in Re-Submissions (and How to Avoid Them)

Even experienced applicants make mistakes. Here are the most frequent errors and strategies to steer clear of them.

  • Ignoring minor comments: A “non-substantive” comment can still trigger a return. Treat every comment with equal seriousness.
  • Submitting incomplete mark-ups: If you change the location of a fire extinguisher, also update the corresponding legend and schedule. Reviewers spot inconsistencies quickly.
  • Using inconsistent file names or versions: “A-101_Final_Rev2_Final(1).pdf” confuses everyone. Use a clean versioning system (e.g., Rev 0, Rev A, Rev B).
  • Failing to include the response matrix: Without a clear response, the reviewer must hunt for changes, increasing the chance of missed items and a second round.
  • Missing the deadline: Some jurisdictions treat missed re-submission deadlines as an abandoned application. Mark your calendar and set reminders.
  • Not updating all affected disciplines: A structural change may impact architectural clearances. Coordinate among all consultants before submission.

Streamlining the Process: Advanced Tips

Beyond the basics, these proven techniques can reduce the number of review cycles and accelerate approval.

Leverage Pre-Submittal Meetings

Before submitting your first revision, ask for a brief meeting (in person or virtually) with the plan reviewer. Clarify ambiguous comments and confirm your intended approach. Reviewers appreciate being consulted early and are often willing to offer guidance that prevents misguided revisions.

Use a Standardized Response Format

Create a template for your response to comments that includes columns for: Comment ID, Comment Text, Applicant Response, and Reference (sheet/section where change appears). This transparency builds trust with the reviewer.

Maintain a Document Control Log

Track every version of every document, including dates, authors, and changes. When disputes arise—or when a new team member joins mid-project—your log provides a single source of truth.

Invest in Digital Collaboration Tools

Platforms like Bluebeam Revu or Procore allow real-time markup, comparison of revisions, and cloud-based review. These tools reduce the time spent on manual coordination and file shuffling.

Build Relationships with Local Authorities

Long-term, developing a professional rapport with permitting staff can pay dividends. They are more likely to give you the benefit of the doubt and provide early warnings about potential issues.

Conclusion

Re-submitting permits after revisions is not a bureaucratic hurdle—it is a quality control step that ensures your project meets safety, zoning, and environmental standards. By systematically reviewing feedback, executing precise revisions, and compiling a clear re-submission package, you can turn a potentially frustrating process into a predictable workflow.

For further reading on permit best practices, the EPA’s permitting guidance offers federal-level insights, while many local building departments (such as NYC DOB) provide detailed re-submission instructions. Additionally, the International Code Council (ICC) has resources that help decode code-related revision comments.

Remember: each revision cycle is an opportunity to refine your project. Treat it with the same care as the original submission, and you will move one step closer to breaking ground.