Pool Permit Comments: How to Prepare a Coordinated Engineering Response

When a pool permit review returns comments, start by assembling the complete comment letter and the exact drawing set that was reviewed. Sending a short excerpt without the referenced sheets can make it harder to understand what the reviewer is asking.

A coordinated response connects each comment to an action, responsible party and revised document. It also distinguishes engineering response time from the jurisdiction’s review and approval process.

FLORIDA ENGINEERING | EXPLAINED

RECORD

Keep the full comment, permit reference and exact reviewed set.

RESOLVE

Assign the responsible party. Confirm selections and linked changes.

REFERENCE

Identify the revised sheet/calculation and current issue date. Confirm submission responsibility.

Illustrative process. Engineering response, resubmission and jurisdiction approval are separate milestones.

Keep the complete review record

Include comments from all relevant disciplines, attachments and marked-up drawings. Identify the permit number, jurisdiction, review date and any resubmission instructions. If a comment refers to an earlier response, include that response as well.

Keep the reviewed set intact. Separately identify the latest proposed changes so the team can distinguish what the reviewer saw from what has changed since submission.

Create one response matrix, not several disconnected email threads

A compact matrix can include six fields: comment number, original request, responsible party, action, document reference and status. Keep the original comment intact and put the response beside it. This allows the project team to distinguish what the jurisdiction requested from its own interpretation.

For a hypothetical comment asking for revised hydraulic information, the action might be “confirm selected equipment and coordinate calculation and schematic revisions.” The status should remain open until the required review and documents are complete. Writing a planned response is not the same as completing the correction.

Assign each comment before editing

Some comments may require engineering revisions; others may need information from the owner, builder, equipment supplier or another design professional. A single list helps prevent two people from answering the same issue differently or assuming someone else handled it.

Use a response log with the original comment, responsible party, proposed action, affected sheet and status. Keep the reviewer’s numbering so the finished response can be followed without searching through unrelated notes.

Separate missing information from a design change

A reviewer may be asking for documentation of an existing design decision, or the comment may require the team to reconsider the design. Those are different tasks. Identify which information already exists before ordering a redesign or promising that the response is a quick drafting edit.

An owner-requested change made during the review cycle should also be recorded separately from the jurisdiction’s comments. Otherwise, the team may believe a revision was required by the reviewer when it was actually a new selection or scope decision.

Check connected documents

A change made to answer one comment may affect another drawing or calculation. For example, in a hypothetical project, a revised equipment selection could require a review of the related piping information and hydraulic calculations. Updating only the equipment label would leave the coordination question unresolved.

The engineer should determine the actual effects of the change. The example is a coordination prompt, not a direction to redesign equipment without review.

A coordinated response example

Imagine a review letter asking the team to clarify the equipment schedule and its relationship to the circulation documents. The builder confirms the intended equipment model; the engineer checks the relevant design; the drawing and calculations are revised where necessary; and the response identifies the updated documents.

The useful record includes the confirmed selection and the revision references. It does not stop at forwarding an equipment brochure. Nor should someone alter a sealed calculation file to make a label match without the responsible professional’s review. This example illustrates document coordination rather than a universal permit requirement.

What to do when a comment is unclear

Identify the specific question and seek clarification through the agreed project contact. Sending a speculative revision can create a second round of confusion if it answers something the reviewer did not ask. Keep any written clarification with the response record so the basis for the action remains visible.

If the comment concerns another discipline’s work, identify that responsibility instead of answering outside the engineering assignment. Some comments can only be closed after another party provides information. Record the dependency so the resubmission date is planned from the complete package.

Prepare a clear resubmission record

Identify the revised sheets and dates, and retain a record of what each revision addresses. Follow the jurisdiction’s instructions for document formatting and resubmission. A response stating only “corrected” can be less useful than one identifying where the correction appears.

Before resubmission, confirm that the responsible professionals have reviewed their documents and that obsolete versions will not be mistaken for the current set. Confirm separately who is responsible for the actual submission.

Measure the right turnaround interval

Keep separate dates for comment receipt, receipt of complete information, engineering response, resubmission and jurisdiction decision. The difference between comment receipt and engineering completion is not the same as the authority’s review duration. Combining those intervals can produce misleading statements about performance.

This is especially relevant to the Next Level case study. Its revision-cycle discussion should be read with the case’s stated measurement limits; it is not evidence of a guaranteed permit approval period. For your own project, ask for timing based on the actual comments, completeness of inputs and scope.

Should we resubmit one corrected sheet immediately?

Follow the jurisdiction’s instructions and the coordinated submission plan. A partial upload may leave related documents inconsistent. Confirm the complete intended resubmission package before sending files.

Should a contractor edit the engineer’s documents?

Requested changes should be marked and returned to the responsible professional for review and proper issuance. Keep contractor observations and proposed revisions identifiable rather than presenting them as an engineer-approved change.

How is this different from preparing the first package?

The first package establishes the design and initial submission. A response package preserves a traceable relationship between reviewer comments and corrections. Both need current information, but the response matrix is specific to the review cycle.

A useful response checklist

• Complete review letter and attachments.
• Exact reviewed drawing set and permit reference.
• Current proposed changes and equipment information.
• Comment log with responsibility and status.
• Revised documents identified by sheet and date.

Florida Engineering’s Next Level Pools & Spas case study highlights the value of checklists, communication and coordinated review. These are process practices, not promises about how quickly a jurisdiction will approve a permit.

For an existing assignment, send the organized package through Project Support. For a new engineering request, visit our pool engineering services page. Scope, deliverables and timing are confirmed for the work requested; additional revisions may need a separate scope review.