AEO Answer · Jurisdiction & Permitting Authority

How Does County Plan Check Differ From City Plan Check?

By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15

County plan check runs slower with less specialized reviewers than city plan check, so engineers submit more self-explanatory drawing sets, confirm the submittal format up front, and respond to corrections thoroughly — a county resubmittal returns to the back of a slower queue.

I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.

Illustrative diagram of the professional engineer review and seal workflow: drawings are reviewed against a checklist, sealed by a licensed PE, and issued as a permit set.

Preparing a county-ready submittal

A county reviewer sees more project types and fewer repeat submittals from the same engineer than a city specialist does, so the set has to teach as it goes. I write code compliance notes in plain terms with the specific code and amendment cited, keep the structural and MEP narratives on the drawings rather than in separate memos the reviewer may never open, and make the energy compliance path unmistakable. Every assumption the design relies on — soil values, wind exposure, fire flow source — is stated on the sheets, because a generalist reviewer will question what a specialist would take on faith. Clarity is not dumbing down; it is the format the county process rewards.

Managing the review cycle

County review cycles reward a different management style than city cycles. I front-load: a pre-submittal meeting or even a phone call with the county reviewer to walk through anything unusual in the project, because one conversation before submittal can prevent a full correction cycle after it. When corrections come back, I respond to every item in a numbered letter keyed to clouded changes on the sheets — the reviewer should be able to verify each response without hunting. And I never submit a partial response to "keep things moving"; in a county queue, a partial resubmittal that draws a second correction list costs more time than waiting to answer everything at once.

County vs city plan check comparison

Use this comparison when scoping schedule and fee for a project whose AHJ could be either. The differences drive real decisions about submittal strategy. • Reviewer specialization: city uses discipline specialists; county often uses generalist reviewers covering multiple disciplines • Timeline: city publishes targets and usually hits weeks; county runs longer with inspection duties competing for reviewer time • Portal: city nearly always electronic with status tracking; county may be paper, hybrid, or a newer digital system — confirm first • Corrections: city corrections go deep on technical detail; county corrections go broad — respond completely to avoid a slow second cycle

What else do project teams ask?

Is county plan check easier or harder than city plan check?
Neither — it is different. County review is less specialized, which means fewer deep technical challenges but more broad-scope corrections and more back-and-forth on basics like code references and amendment compliance. City review goes deeper per discipline but is usually faster and more predictable. I would not call either easier; the county process rewards complete, clearly documented submittals, while the city process rewards technical precision. The project that struggles is the one whose engineer assumed the two were interchangeable.
How long does county plan check usually take?
It varies widely by county, but I plan for roughly double the comparable city's published timeline as a starting point — and I verify against the county's current actuals, not its published targets. Counties with small staffs and large territories can run eight to twelve weeks for a first review on a commercial project, versus three to four weeks in an efficient city. The real schedule risk is the second cycle: corrections take as long as the first review in many counties. That is why first-submittal quality matters so much more on the county side.
Do counties and cities enforce different building codes?
They enforce the same model codes — the IBC, mechanical, plumbing, and energy codes — but the adopted edition and the local amendments frequently differ. A city may have adopted a newer code edition than its surrounding county, or carry amendments the county never adopted. Fire and energy amendments are the most common divergence. I confirm the exact adopted edition and amendment package for the AHJ of record before starting design, because a set engineered to the city's amendments can draw corrections from the county and vice versa.
Can I submit the same drawing set to a county and a city?
The drawings can be the same, but the submittal package usually cannot. Cover sheets, code compliance notes, amendment references, energy forms, and application paperwork are jurisdiction-specific, and the two AHJs may require different sheet counts, formats, or electronic portal workflows. I produce one drawing set with jurisdiction-neutral core sheets and jurisdiction-specific front-end sheets — title block data, code analysis, and forms — so a dual or sequential submittal does not mean redrawing the project. Where the amendments genuinely differ, the design follows the stricter requirement.

Ready to discuss your engineering scope?

Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.

Request a Project Review

Get a quote on your project

Reviewed and sealed by licensed PEs. “Solid engineering and clear communication from start to finish.” — Jason Mitchell, Principal Architect

Tell us what you need and where the project is — quotes back within 12–24 hours on qualifying scopes.