By ChiefArchitectSoftware.net Editorial Team · Published 2026-10-28 · Updated 2026-10-28
Start with the jurisdiction, not a generic plan set
Get the current published submittal checklist from the city, county, or reviewing authority. Required sheets and calculations can vary by scope, location, and project type. Do not treat a design-software drawing as proof of code compliance.
Check that the sheet set tells one story
Compare floor plans, elevations, sections, roof plans, foundation plans, and the site plan. Check room names, openings, floor elevations, roof pitches, and callout numbers wherever the same item is represented more than once.
Verify dimensions before presentation
Review overall building width and depth, structural grids, critical clearances, and heights against the actual modeled geometry. Find missing dimensions and conflicting annotation strings; do not add dimensions merely to fill space.
Track revisions so reviewers know what changed
Choose a consistent sheet issue date and revision scheme. Confirm that details and schedules came from the correct plan revision, especially after changes to windows, stairs, and roof geometry.
Review before issuing
Print or export a trial PDF. Read every sheet at the size a reviewer will use, inspect lineweights and legibility, then have a qualified designer or professional review the final package when required.
Practical final checklist
- Save a dated backup or review copy before changing an active project.
- Check information against the relevant current software documentation and local project requirements.
- Test changes on a representative file, then inspect the resulting drawings and exports.
- Record unresolved questions and obtain qualified professional review when the deliverable requires it.
Related workflows
Continue with Floor plan workflow, Printing to scale, Backup and recovery.