What the reviewer actually opens first
Reviewers work from the cover sheet outward: code edition and occupancy classification, project data, scope narrative, then site plan, then architectural, then structural and trades. A cover sheet that states the applicable codes, use group, construction type, and scope in one place answers a dozen questions before they become comments.
The comments that get written most often
Across disciplines, the same categories recur. Every one of them is preventable at your desk.
- Drawings not to scale, or dimensions that do not sum to the stated overall.
- Site plan missing property lines, setbacks, easements, or north arrow.
- Scope narrative that contradicts the drawings.
- Missing egress details — window sizes, sill heights, door swings, corridor widths.
- No header, beam, or footing schedule where spans changed.
- Missing energy-code compliance path or documentation.
- Smoke and carbon monoxide alarm locations not shown.
- Fire separation, rating, or penetration details missing at required assemblies.
- Electrical, mechanical, or plumbing scope shown on architectural sheets with no trade detail.
- Contractor license, insurance, or owner authorization not attached.
How to read a correction letter
Each comment cites a code section and requests either a change or clarification. Respond item by item, in the reviewer's numbering, with a written response narrative that says what changed and on which sheet. Resubmitting revised drawings without a response narrative is the fastest way to earn a second round on the same comments.
Clouding and revision discipline
Cloud and delta-tag every revision, keep the revision log current, and never silently change something the reviewer did not ask about. Unclouded changes force the reviewer to re-review the entire sheet, which slows your resubmittal and erodes trust for the rest of the project.
Running your own review first
A pre-submission review applies the same checklist a reviewer would: is every required document present, is every dimension internally consistent, is every code-triggered detail shown, and is every claim supported. Permit Junkie reads your uploaded documents, flags likely comments with the reason and the evidence, and assembles the corrected packet. Sealed drawings and professional judgment stay with your design professional — the AI removes the clerical failure modes, not the expertise.