AHJ Requirements Checklist

The authority having jurisdiction is the body with legal power to approve the installation and enforce the codes where the project sits, usually a city or county building department. It decides which code editions apply locally, what a submittal must contain, whether a professional engineer's seal is required, and what is inspected and in what order. It is not the utility, which runs a separate interconnection approval on its own timeline, and one project can face more than one authority where fire or electrical review is handled separately.

Because almost every constraint on this list changes the drawings rather than the paperwork. Adopted code editions decide what the cover sheet may cite. Locally amended fire setbacks decide how many modules fit. Stamp policy decides whether an engineer has to be engaged, and by when. Discovering any of them after the set is drawn means drawing it again and re-entering a review queue, which is why the cost of a late discovery is measured in weeks rather than in hours of drafting.

Scope. A permit package checklist is per project: it scores whether this submittal contains what it needs to contain. This one is per jurisdiction: it captures what this authority requires of every project you submit there, so the knowledge is reusable rather than rebuilt each time. In practice you complete this once per jurisdiction and keep it, then run the package checklist on each project drawn against it.

The jurisdiction publishes them, though rarely in one place. Adopted editions usually sit in the municipal code or on the building department's website, and local amendments are typically an ordinance that modifies the model code section by section. Where the published information is ambiguous or evidently stale, the reliable route is to ask the department directly and record the answer with a date, because the answer is only as current as when it was given.

It converts the cost of a correction from minutes into weeks. Where a resubmitted set goes to the back of the queue, a trivial correction such as a missing dimension costs an entire review cycle, and two corrections in sequence can cost more calendar time than the original review. Where corrections are handled by the original reviewer, the same fix costs days. This single policy difference explains much of the variation in permitting timelines between jurisdictions that otherwise look similar.

No, though it removes a large part of the plan review wait where a project qualifies. Eligibility is typically narrow, covering straightforward systems within defined limits, and a project falling outside it returns to the standard path. The inspection sequence, the licence registration, the fee schedule and the local amendments all still apply. Treat an expedited path as a faster route through one stage rather than as a different process.

Yes, and it is the item most often left until the crew is already booked. Where a rough-in or in-progress inspection is required, work covered before it takes place has to be uncovered, which turns one visit into three. Booking lead time is equally consequential: identical work produces completely different project schedules under a two-day booking window and a two-week one. Both facts are free to obtain and expensive to discover.