A permit set has one job: to let a plan reviewer confirm the proposal complies with the applicable codes. It is not a construction set and it is not a presentation. Understanding that distinction keeps sets lean and approvals quick.
The reviewer's perspective
A plan reviewer works through a checklist. They are looking for specific information in predictable places. If they cannot find it quickly, the set comes back with comments, and each round of comments costs weeks. Most rejections are not design failures, they are information failures.
What a typical set contains
Cover sheet. Project data, applicable codes and editions, occupancy classification, construction type, building area and height, allowable versus proposed, and a sheet index. Reviewers start here, and a well built code summary sets the tone for the whole review.
Site plan. Property lines, setbacks, easements, existing and proposed structures, parking, accessible routes, and drainage where required.
Life safety plans. Occupant loads by area, egress paths with travel distances, exit widths, fire separations and ratings. On many projects this is the single most scrutinised sheet.
Floor plans. Dimensioned, with room names and areas, door and window references, and wall types keyed to a legend.
Elevations and sections. Heights, levels, materials, and enough section information to show assemblies and their ratings.
Accessibility details. Clearances, mounting heights, accessible fixtures, ramp and stair configurations. Reviewers check these closely.
Assemblies and schedules. Wall, floor and roof types with rated assembly references, plus door, window and finish schedules as applicable.
Structural and MEP to the extent the jurisdiction requires them at permit stage, which varies considerably.
What usually does not belong
Furniture layouts, extensive interior detailing, presentation renders and shop drawing level information rarely help. They enlarge the set, slow the review, and occasionally invite comments on things nobody needed to look at.
The variable that matters most
Requirements differ by jurisdiction, sometimes markedly between neighbouring counties. Before starting, get the authority's own submission checklist and build the set against it. That single step prevents most avoidable comment rounds. Where a checklist is unavailable, a call to the department is usually more productive than an assumption.
Make it easy to review
Consistent sheet numbering, a clear index, legible text at printed size, complete title blocks, and code references stated rather than implied. A reviewer who can find things forms a good impression of the whole submission, and that matters more than architects tend to assume.