How to Check Drawings Against City Amendments and Custom Jurisdiction Codes

Why Base-Code Checks Fail When Amendments Are in Play

The plan examiner reviewing your permit drawings is not working from the current International Building Code (IBC) edition. They are working from whatever edition the jurisdiction adopted, modified by state-level changes, and further adjusted by local amendments the city or county approved on top of that. A drawing set detailed to IBC 2021 submitted to a jurisdiction still enforcing IBC 2018 with its own local amendments is not a version preference issue. It is a correctable error that triggers plan check comments, delays permit issuance, and forces resubmission.

The amendment structure operates in three layers:

• Model code edition: the jurisdiction adopts a specific model code edition, which may lag the current edition by one or two cycles.
• State modifications: the state applies its own changes before local adoption takes effect.
• Local amendments: the local Authority Having Jurisdiction (AHJ) layers additional amendments on top of the state-adopted version.

A structural engineer who details roof framing to ASCE 7 ground snow load defaults without checking Denver's local amendment table will produce drawings a Denver plan examiner flags on first review. Denver adopted the IBC 2021 with local amendments effective December 31, 2024, per Denver's Community Planning and Development department, and those amendments include snow load values that differ from ASCE 7 defaults.

This is not a Colorado-specific problem. Every jurisdiction that has adopted any model code has its own amendment document. Base-code-only checks do not catch what those documents modify.

The Three Amendment Layers Every Project Must Resolve

Denver adopted IBC 2021 with local amendments published by its Community Planning and Development office. Those amendments are a separate document from the IBC itself, with their own section references and effective dates. Austin publishes local amendments to the 2021 IBC through the Austin Development Services Department. Again, a separate document, a separate retrieval step, a separate mapping exercise.

The point is not what each city's amendments say. The point is that every city has its own document, and a designer cannot assume the base code applies without retrieving it. That retrieval step is project-specific and cannot be performed once and reused across projects in different jurisdictions.

Version Mismatch: The Compliance Risk No One Tracks at the Sheet Level

A drawing callout to an IBC 2021 section that does not exist in the jurisdiction's adopted IBC 2018 edition is a plan check comment waiting to happen. Version mismatch is not caught by reading the base code. It requires confirming the adopted edition with the AHJ or the jurisdiction's published code adoption page before detailed drawing production begins.

State electrical preemption adds a separate complication. In Colorado, the National Electrical Code (NEC) adoption is governed at the state level through the State Electrical Board, not by the local AHJ. Checking the local ordinance for electrical code applicability in Colorado produces the wrong reference. This is a jurisdiction-specific lookup that base-code checks will never surface.

Step-by-Step: How to Locate a Jurisdiction's Amendment Ordinance

Retrieving the wrong document, or using an outdated amendment ordinance, produces the same outcome as not checking at all. The following workflow applies to any US jurisdiction.

1. Identify the AHJ and confirm the adopted code edition. Do not assume. Check the jurisdiction's official building and development page or call the building department directly. The ICC's jurisdiction adoption status for IBC editions maintains adoption records by state, though local adoption within a state requires a separate confirmation step.
2. Locate the local amendment ordinance. This is a separate document from the base code. For incorporated cities it is typically found in the municipal code, often under a title covering buildings or construction (Denver's local amendments appear under Title 10 of the Denver Municipal Code). For counties it may be a board resolution. The city clerk's office or the community planning department is the correct first contact.
3. Download the amendment document and note its effective date. Amendments are periodically revised. On a project with a long design phase, confirm that the amendment document you downloaded at schematic design is still current at permit submission.
4. Map each amendment section to the drawing sheets it affects. A snow load amendment maps to the structural general notes and the roof framing sheets. A fire separation amendment maps to floor plans showing rated assemblies. An energy code amendment maps to envelope details and mechanical equipment schedules. This sheet-level mapping is the step that converts a retrieved document into an actionable check.
5. Confirm the energy code edition independently. Many states operate energy codes on a separate adoption cycle from the IBC or IRC. Energy code compliance review must be confirmed against the correct energy code edition for that jurisdiction, not inferred from the IBC adoption status.

Building an Amendment Tracking Matrix for Your Drawing Set

An amendment tracking matrix is a table that lists each local amendment section number, the base code section it modifies, and the drawing sheet or specification section where compliance must be demonstrated. It is an internal QA tool, not a submittal document. A minimal matrix needs four columns: Amendment Ref, Modified Code Section, Drawing Sheet(s) Affected, and Compliance Note.

This matrix becomes the drawing sheet compliance checklist a plan check reviewer can use to confirm that each flagged amendment has been addressed in the document set. When an amendment is revised mid-project, update the matrix immediately and flag any sheets where the prior amendment version drove a specific detail or callout.

Custom Jurisdiction Code PDFs as a Live Review Reference

Even with an amendment tracking matrix, cross-referencing every drawing callout against a jurisdiction-specific PDF during code compliance review is manual and prone to the same reading-fatigue errors it is meant to prevent. The problem is not that designers lack the documents. It is that applying those documents systematically across a full construction document set requires more parallel attention than a single-pass review delivers.

A drawing review workflow that accepts uploaded jurisdiction-specific code PDFs, including custom local amendment ordinances, AHJ policy bulletins, and non-standard local design criteria, uses those uploaded documents as the live reference during cross-check rather than relying on a static base-code library. The practical difference is significant:

• An Austin project has a local amendment modifying IBC Section 903.2 sprinkler system thresholds differently from the base code.
• A reviewer who uploads the Austin local amendment PDF alongside the drawing set receives findings that cite the Austin amendment section, not just the IBC section a base-code check would flag.
• That citation names the specific local document the plan examiner will use. A generic code alert does not.

This capability directly addresses the plan review process gap that manual amendment checks cannot close: citation specificity at the sheet level, referenced to the actual document the AHJ will enforce.

Where Amendment Violations Most Commonly Survive to Submission

Amendment violations reach the plan examiner when the base-code check passes and the amendment check never happens. Specific failure categories appear on specific sheets.

• Structural load amendments (snow, wind, seismic) are the most common. A structural general notes sheet that references ASCE 7 default values without reflecting the jurisdiction's amended values will be flagged by the plan examiner even though the engineering is internally consistent. The ASCE 7 ground snow load data provides base values, but local amendments in jurisdictions like Denver modify those defaults and are not reflected in ASCE 7 tables.
• Energy code amendments on a separate adoption cycle are the second category. A building that complies with IECC 2021 envelope requirements may not comply with the jurisdiction's adopted IECC 2018 with local modifications. That gap lives on the envelope details and the mechanical equipment schedules, not on the architectural floor plans where most coordination review is focused.
• Fire code modifications that change sprinkler thresholds or fire separation requirements by occupancy classification are the third. IBC Section 903 sprinkler requirements vary with occupancy, and local amendments that adjust those thresholds are reflected in the AHJ's amendment document, not in the base IBC. Floor plans showing rated assemblies and fire barrier locations are where these violations appear.
• Accessibility amendments that modify the state's version of ANSI A117.1 affect accessibility plan detail callouts. A state-adopted version of ANSI A117.1 with local modifications may require different dimensional clearances than the base standard. Those differences live on the accessibility details, not the general floor plans.
• Electrical scope preempted by state boards in some jurisdictions produces the wrong reference entirely when a designer checks the local ordinance. The permit correction cycle on electrical work in these jurisdictions often traces back to this lookup error at the start of design.

How InspectMind Checks Drawings Against Local Amendments and Custom Jurisdiction Codes

InspectMind's building codes checker accepts your full construction document set alongside uploaded jurisdiction-specific amendment PDFs, AHJ policy bulletins, and custom local design criteria documents. The review cross-references each drawing sheet against both the applicable base code and the uploaded local documents, returning findings that cite the specific amendment section and the sheet where the conflict appears. For structural load amendments, energy code modifications, and fire separation requirements, findings are tied to the sheet and detail level where compliance must be demonstrated. Upload your document set, from $50 per upload, with a 5+ issue guarantee or a full refund.

For more on reducing plan check comments before submission, see how to reduce plan check comments and the pre-permit QA guide. For the distinction between what happens during formal review versus what your team controls before submission, see plan check vs plan review. For projects with jurisdiction-specific seismic requirements, see seismic design code compliance.

Frequently Asked Questions

How do local code amendments differ from the base model building code?

The base model code is the edition published by the International Code Council or a similar standards body. Local code amendments are changes that a state or municipality applies on top of the adopted edition. Amendments can modify thresholds, add requirements, or delete provisions from the base code entirely.

How do you find a city's specific building code amendments before submitting plans?

Check the jurisdiction's official building or community development department website for a published amendment document or local ordinance. For incorporated cities, the municipal code database is often the correct source. If the document is not posted online, contact the building department directly and request the current adopted code and local amendments with their effective dates.

What happens if construction drawings do not comply with local jurisdiction amendments?

The plan examiner will issue redline corrections identifying each non-compliant element. The applicant must revise the drawings, resubmit, and wait for a second review cycle. Each permit correction cycle adds time and cost before permit issuance.

Who is responsible for checking plans against local code amendments during plan review?

The design team, typically the architect and engineer of record, is responsible for checking construction documents against jurisdiction-specific requirements before building permit submission. The plan examiner identifies violations but does not correct them. Pre-submission QA is the design team's responsibility.

Can a drawing review tool use a custom jurisdiction PDF instead of a generic code library?

Yes. A review workflow that accepts uploaded jurisdiction-specific PDFs can cross-reference drawing callouts against the actual local amendment document rather than a static base-code library. This produces findings that cite the specific amendment section the plan examiner will enforce, rather than a generic IBC flag.

What is the risk when a jurisdiction has not adopted the current IBC edition?

A designer who details drawings to IBC 2021 and submits to a jurisdiction enforcing IBC 2018 will produce callouts to section numbers that do not exist in the adopted code. The plan examiner flags these as non-compliant references. Confirming the adopted edition with the AHJ at the start of design is the only way to prevent this category of plan check comment.