How to Build a Jurisdiction Profile

Why this matters

The first job in a new town is where a shop learns that town's rules the expensive way: a permit application rejected for a missing load calculation, a footing short of a frost depth nobody looked up, an inspector who wants something the last town never asked for. A jurisdiction profile is the one page that answers those questions before the first estimate goes out. Building one takes about two to three hours the first time. Keeping it current is a separate job that The Jurisdiction Profile SOP owns; this card is the compiling, step by step, with the finished page at the end.

What a profile is, and what it is not

A profile is a fact sheet with a source and a date on every line: which codes the authority enforces and in which editions, the local design numbers, what needs a permit and what the application needs, how inspections run, and who to call. It is not a code summary, and it does not interpret anything. Where the department has given the shop an answer to a specific question, the profile links to that entry in the shop's interpretation log rather than restating it. A profile that starts explaining code sections becomes a second, unreviewed code book, and it will be wrong by the next edition.

The steps

1. Find out who actually issues the permit. Look the address up in the county parcel viewer, which usually names the taxing and zoning jurisdiction, and check it against the city limits map. An unincorporated address is usually permitted by the county even when its mailing city is a town; some small towns contract their inspections to the county or to a third-party agency; and electrical or plumbing permits are issued by a state agency in some states rather than by the town. Write down the issuing authority for each trade separately. Skip this and you build a careful profile of the wrong office, and the first application goes to a counter that sends you somewhere else.

2. Find the adoption record for each code. The reliable source is the adopting ordinance or the state's adoption rule, not a summary page. Some states adopt one residential code statewide and limit or forbid local amendments; others leave adoption to each city or county, so two neighboring towns can sit an edition apart. Record each code separately: residential or building, mechanical, plumbing (the International Plumbing Code or the Uniform Plumbing Code, depending on the state), fuel gas, electrical and energy, each with its edition, effective date and whether local amendments exist. Expect mixed editions; a state electrical code and a local building code are often on different cycles. Skip this and the shop builds to the edition it knows, which is the most common source of a correction notice in a new town.

3. Copy the design criteria table whole. Most departments that enforce the IRC publish their filled-in climatic and geographic design criteria, Table R301.2(1) in the 2018 and 2021 editions as adopted locally, with the numbering subject to change between editions. Copy every cell with its unit, including the ones your trade never uses this month, because next month's job may: ground snow load, wind design speed, seismic design category, weathering, frost line depth, termite and decay, winter design temperature, ice barrier underlayment, flood hazard reference, air freezing index and mean annual temperature. If the department also states the outdoor design temperatures it expects in load calculations, copy those. If the table is not published, email the counter and record the written answer with the name and date. Skip this and someone fills the gap from memory or from the shop's home county.

4. Write down what needs a permit and what the application needs. Go through the job types the shop actually sells and mark each permit yes or no from the department's published list, then confirm the borderline ones by email: water heater replacement, condenser or furnace swap, re-roof, service upgrade, fence, deck, a sewer lateral repair. The IRC's list of work exempt from permit, R105.2 in the editions that carry it, is amended locally more often than almost any other section. Then record what each application needs: a load calculation, equipment data sheets, a site plan, a contractor registration number. Record the shop's local registration or license requirement and its expiry date. Skip this and the office finds out about the load calculation when the application bounces, a week after the customer was told an install date.

5. Write down how inspections actually run. Record the scheduling method, the cutoff time for next-day inspections, the inspection window, which inspections each permit type requires, and whether photo or video inspections are accepted and for which work. Then ask two people for the practical requests: the counter staff and a colleague from another shop who works the town. The answers are the useful kind of local knowledge, such as a ladder left at the attic hatch, the combustion printout taped to the furnace, the permit card posted in a front window. Skip this and every first inspection becomes a learning visit.

6. Record the contacts. The permit counter, the inspection line or scheduler, plan review, the chief building official, the floodplain administrator where there is one, and the utility contacts for new services in that area. Call or email each listed contact once to confirm it is reached. Skip this and the profile sends a tech to a phone number nobody answers on the day a question has to be settled.

7. Stamp it and give it an owner. Put the verified date, the person who built it, the person who owns it from now on, and the review date at the top, and a source beside every line. Publish it where estimators read at intake. A profile without an owner and a date reads as current forever, which is worse than no profile, because the shop trusts it.

The finished page

A profile built for a city where a shop was taking its first jobs. Every value below is this city's, as the shop recorded it on the day it built the page, not a typical figure.

JURISDICTION PROFILE    City of [name] (inc.)
built 03/11 TR   owner TR   next review 06/11
ISSUING AUTHORITY
 bldg/mech/plmb/gas  City Bldg Dept
 electrical          STATE elec. board
CODES (source: ord. + state rule, 03/11)
 IRC 2018 w/ local amend.   eff. 01/01
 IMC 2018 / IFGC 2018       eff. 01/01
 IPC 2018                   eff. 01/01
 NEC 2023 (statewide)       eff. 07/01
 IECC 2018 w/ state amend.  eff. 01/01
DESIGN TABLE R301.2(1) (dept page 03/11)
 snow 30 psf  wind 115 mph  SDC A
 frost 36 in  termite mod-heavy  decay slight
 winter design 7 F   ice barrier: YES
 flood: FIRM, eff. date per panel
PERMITS
 WH replace: YES  condenser swap: YES (mech)
 re-roof: YES  fence under 6 ft: NO
 load calc + AHRI sheet w/ mech app
 city contractor reg. exp. 11/30
INSPECTIONS
 portal, cutoff 3 pm for next day
 photo insp.: WH and condenser swaps only
 leave ladder at attic hatch (counter)
CONTACTS  counter, insp. line, plan review,
 floodplain admin.  (all reached 03/11)
LOG ENTRIES  none yet

Three things in that page changed what the shop quoted on its first week there:

• Two issuing authorities. The electrical permit for a condenser swap came from the state board, not the city, so a condenser job needed two applications, and the office learned it from step 1 rather than from a rejected application.
• Mixed editions. The building side was on 2018 codes while electrical was on the 2023 NEC statewide, so the shop's electricians worked to the newer edition's requirements in a town where its HVAC techs worked to the older mechanical code. Both were correct, and the page said so plainly.
• Ice barrier YES and frost at 36 in. The roofing crew's habit in its home county, where the table reads NO for ice barrier, would have left out a required underlayment on the first re-roof, and the deck crew's frost depth was 6 in deeper than this city's 36 in, which is conservative and harmless, but the profile now says which number this city enforces.

How to tell the page is done

Hand the profile to someone who did not build it, ideally the newest estimator, and ask five questions it should answer: who issues the electrical permit for a condenser swap, what frost depth applies, does a water heater replacement need a permit and what goes with the application, can that inspection be done by photo, and who decides a floodplain question. If each answer takes under two minutes and comes with a source on the page, it is done. If any answer needed a phone call, the page has a gap, and the gap goes back to the step that should have filled it.

Then check that no line is missing its source or its date. A value with no source cannot be re-checked at the next review, and the review is the only thing that keeps the page from going stale.

Where profiles go wrong

• The neighbor's page copied as a template. Starting from a nearby town's profile saves twenty minutes and imports that town's editions and frost depth into every line nobody re-checks. Start from a blank page with the same headings.
• A summary page trusted over the ordinance. Department web pages lag adoptions by months. When the page and the ordinance disagree, the ordinance and the counter's written answer win, and the profile says which one it relied on.
• A profile that grows into interpretation. When the page starts carrying paragraphs about what a code section means, move them to the interpretation log and link them; the profile stays a fact sheet.

References

• The jurisdiction's adopting ordinance and the state's code adoption rule, for codes and editions.
• International Residential Code Table R301.2(1) and R105.2, in the edition your jurisdiction adopted, with its local amendments.
• See related: The Jurisdiction Profile SOP; The Local Design Criteria Table; How to Find the Local Design Criteria for a Jurisdiction; Working With the Authority Having Jurisdiction: The Basics.