How Do You Permit a Project That Spans City and County Lines?

I start both permit tracks with a pre-submittal touch at each jurisdiction — not a formal meeting necessarily, but a confirmation of the submittal checklist, the adopted amendments, and the review timeline. Then I submit to the slower AHJ first, usually the county, and finalize the faster jurisdiction's package during the wait. The drawing set is one set with jurisdiction-specific front ends: code compliance sheets that address each AHJ's amendments separately, so each reviewer sees their requirements answered without wading through the other's. When corrections return, I hold the faster jurisdiction's response until I have both lists, then issue one coordinated revision that answers everything at once.

Amendment conflicts cluster in predictable areas: energy code stringency, fire sprinkler thresholds, structural design values for wind or snow, and plumbing fixture requirements. My default resolution is the stricter standard applied project-wide, documented with citations to both amendment packages. Where the stricter standard is genuinely ambiguous — one jurisdiction is stricter on one provision, the other on a different one — I apply each jurisdiction's stricter provision to its own territory and document the split clearly on the plans. The goal is a set that either reviewer can approve without asking the engineer to choose between their amendments.

A boundary-straddling project permits cleanly when these items are handled. The entire strategy is coordination the AHJs do not provide themselves. • Jurisdictional boundary surveyed and tied to official maps — not assumed from GIS • Separate permits identified for each side, with the slower AHJ submitted first • One drawing set with jurisdiction-specific code sheets addressing each amendment package • Single coordinated correction response answering both reviewers' lists at once • Master inspection schedule with the boundary marked, so no work is concealed without the right sign-off