Building Permit Application Intake and Routing Checklist

This template covers the front-end intake of a building permit application: applicant details, parcel verification, scope and occupancy, plan set completeness, required technical documents, fee confirmation, and routing to the correct reviewers. It is designed for permit technicians who need a consistent yes/no workflow before a package enters plan review. It does not replace the technical review itself. Instead, it makes sure the submittal is complete enough to move forward.

It works best for building permits that require plan review, especially new construction, additions, tenant improvements, and alterations with multiple disciplines involved. Smaller over-the-counter permits may only need a trimmed-down version. Jurisdictions can also customize it for residential, commercial, or mixed-use intake. If your department has separate workflows for trade-only permits, this checklist should stay focused on building department routing.

Use it every time a permit application is received for intake, whether the submission arrives in person, by email, or through a permit portal. If your office accepts resubmittals, use the same checklist again to confirm the revised package still meets intake standards. A recurring task version can also support daily or shift-based intake queues. The key is consistency so incomplete packages do not reach plan review.

Permit technicians, permit coordinators, or front-counter staff usually run it first. In some jurisdictions, a supervisor may review flagged items such as mixed occupancy, special inspections, or unusual code triggers. The checklist should have a clear DRI so one person owns the intake decision, even if multiple departments later review the package. That prevents handoff gaps and duplicate follow-up.

Yes, it supports compliance-driven intake by checking for the documents and declarations that plan reviewers need to apply the adopted building code, energy code, and local submittal rules. It is not a substitute for code interpretation or engineering review. The value is in verifying that the application package is complete enough for the correct reviewers to do their jobs. That reduces avoidable rework and missing-document delays.

Common misses include blank application fields, parcel numbers that do not match county records, missing plan sets, unsigned or unstamped drawings, and energy documents that do not match the project scope. Teams also often forget to route mixed-occupancy projects to the right senior reviewer or to flag special inspection requirements early. This checklist makes those checks explicit and independently verifiable. That is much safer than relying on memory or informal handoffs.

Yes. You should tailor the required plan set count, local fee steps, adopted code references, routing destinations, and any jurisdiction-specific submittal standards. Many departments also add local forms, fire flow documentation, stormwater review triggers, or historic district checks. Keep each checklist item atomic so staff can answer yes, no, or not applicable without ambiguity. That makes the template easier to train on and easier to audit.

An ad hoc process depends on whoever is at the counter remembering every required document and routing rule. That often creates inconsistent decisions, missed attachments, and back-and-forth with applicants. This checklist standardizes the intake sequence so each package is screened the same way. It also creates a clearer record of what was verified before the permit moved forward.

Yes. The checklist can be used alongside a permit management system to confirm that digital PDFs are uploaded, fees are recorded, and routing tasks are assigned to the correct review queues. It also works well when paired with attachments, comments, and status updates in the system of record. If your workflow supports task assignment, use the checklist result to trigger the next review step. That keeps intake and routing aligned.