Planning & documentation
Recording Applicable Code Editions for US Steel Buildings
Create a dated record of the steel project's governing code editions, local amendments, confirmation source, and affected design packages.
Define the condition and its scope
Record the adopted edition and local amendments rather than assuming the newest model code governs.
US construction requirements depend on the project location, proposed use, and the authority having jurisdiction. A model code title or a state-level map is an initial research aid rather than a complete permit decision. Identify the building department, planning or zoning contact, fire authority, and any separate floodplain or environmental review. Record the adopted editions, local amendments, and submission instructions obtained for the actual property. Keep the owner's intended operations clear so that reviewers are evaluating the building that will really be used.
References: Code adoption resources · Project Planning Guide
Gather the inputs before deciding
Identify the jurisdiction serving the actual property and the requirements relevant to its proposed work and use. Start with ICC resources, then obtain local confirmation of adopted editions and amendments. Include building, existing-building, energy, fire, and other applicable scopes as directed by the responsible team. Record source links and dates. A state-level overview cannot establish every local amendment or project-specific applicability decision.
- Confirmed adopted code editions
- Local amendment references
- Confirmation date and contact
- Affected design packages
References: Code adoption resources · Project Planning Guide
Set observable handoff deliverables
A statewide adoption resource may omit property-specific jurisdiction or project exceptions.
| Input | Evidence to keep with it | Review status |
|---|---|---|
| Confirmed adopted code editions | Jurisdiction edition confirmation | Identify reviewer and written decision |
| Local amendment references | Applicable amendment index | Identify reviewer and written decision |
| Confirmation date and contact | Updated project criteria distribution | Identify reviewer and written decision |
Sequence review and release
Ask the responsible professionals to reconcile confirmed requirements with supplier and foundation assumptions. Note discrepancies by package and obtain their dispositions. Issue the accepted requirements record with the project criteria revision. When submission instructions or adoption information changes, evaluate the affected project basis through the established review process. Do not silently replace one edition with another after a supplier has developed engineering on the previous instructions.
- Locate confirmed adopted code editions in the current record.
- Compare local amendment references with the table's evidence.
- Document the decision: Reconcile governing editions across the project before accepting package assumptions.
Worked project coordination example
Supplier documents cite one edition while the local submission instructions cite another. The team obtains jurisdiction confirmation, updates the criteria register, and routes the discrepancy to the responsible professionals.
Apply the stated release decision to the case: Reconcile governing editions across the project before accepting package assumptions. The responsible team determines acceptance for the actual project and records any condition that still requires resolution.
Keep a closeout record another team can use
Retain local confirmations, amendment references, the dated criteria record, and design-package acknowledgments. Distinguish information retrieved for research from actual project decisions. Future alteration teams need the governing basis and subsequent changes, not a claim that the building followed the latest code. If a later permit uses another basis, preserve both scopes and their decision dates instead of rewriting the original project's record.
For this issue, include updated project criteria distribution in the handoff. If review remains pending, identify the dependent work and its owner; do not present the record as a completed technical acceptance.
Common questions
Does ICC publication equal local adoption?
No. Publication and jurisdictional adoption are separate events.
How should confirmed adopted code editions be documented?
Reconcile governing editions across the project before accepting package assumptions. Retain jurisdiction edition confirmation and check that the decision reached the team performing the dependent work.
Sources & further reading
Use the current documentation for the exact product and project. Source links do not imply a partnership or endorsement.
- Code adoption resources International Code Council
- Project Planning Guide U.S. General Services Administration / WBDG
Prepared with AI assistance. Linked references require current project-specific review. How these guides are prepared.
Prepare a supply inquiry
- Record the project drawing or detail and the specified product, profile, or system.
- List the complete configuration, physical units, quantities, and cuts per piece.
- Request current manufacturer documents; confirm compatibility, price, and availability before ordering.
- Obtain the responsible professional's review for loads, code requirements, or installation.