• Welcome to the new and improved Building Code Forum. We appreciate you being here and hope that you are getting the information that you need concerning all codes of the building trades. This is a free forum to the public due to the generosity of the Sawhorses, Corporate Supporters and Supporters who have upgraded their accounts. If you would like to have improved access to the forum please upgrade to Sawhorse by first logging in then clicking here: Upgrades

Understanding the ICC's Code Development and Adoption Process

jar546

CBO
Joined
Oct 16, 2009
Messages
12,392
Location
Not where I really want to be
Understanding the ICC's Code Development and Adoption Process

The International Code Council (ICC) plays a crucial role in establishing building safety standards through its model codes, known as the International Codes or I-Codes. These codes are developed through a structured, transparent process that involves input from a wide range of stakeholders. This educational summary outlines how the ICC's code development process works, including the steps and timeframes involved.


1. Code Development Cycle

The ICC updates its codes on a three-year cycle. This regular update schedule ensures that the codes reflect the latest advancements in technology, materials, and building practices, as well as lessons learned from recent events related to building safety.


2. Steps in the Code Development Process

The code development process involves several key steps designed to encourage participation and ensure that the resulting codes serve the public interest.

a. Submission of Code Change Proposals

  • Timeframe: Proposal submission opens approximately 18 months before the publication of the new code edition.
  • Process:
    • Open Participation: Any interested party can submit proposals, including code officials, industry representatives, professionals, and the general public.
    • Proposal Requirements: Each proposal must include the specific code section to be amended, the proposed change, and a reason statement explaining the rationale.

b. Committee Action Hearings

  • Timeframe: Held in the spring of the first year of the cycle.
  • Process:
    • Review by Committees: Expert committees review each proposal. These committees are composed of volunteers with expertise in relevant areas.
    • Public Testimony: Proponents and opponents of proposals can present their views.
    • Committee Votes: Committees vote to approve, approve with modifications, or disapprove each proposal based on technical merit and public safety considerations.

c. Public Comment Period

  • Timeframe: Following the Committee Action Hearings, a public comment period of around two months is provided.
  • Process:
    • Submission of Comments: Stakeholders can submit written comments on the committee's actions, suggesting further modifications or expressing support or opposition.

d. Public Comment Hearings

  • Timeframe: Conducted in the fall of the first year.
  • Process:
    • Final Discussion: Proposals and public comments are discussed.
    • Floor Actions: Modifications can be made based on the discussions.
    • Voting: Attendees vote on each proposal, determining which changes move forward.

e. Online Governmental Consensus Vote

  • Timeframe: Takes place shortly after the Public Comment Hearings.
  • Process:
    • Eligible Voters: Only ICC Governmental Member Voting Representatives (primarily code officials from governmental agencies) participate.
    • Final Decision: Votes are cast online to finalize which code changes are approved for inclusion.

f. Publication of the New Codes

  • Timeframe: The finalized codes are published in the spring of the second year.
  • Process:
    • Compilation: Approved changes are integrated into the new edition of the codes.
    • Distribution: The updated codes are made available to jurisdictions and the public.

3. Adoption by Jurisdictions

While the ICC develops model codes, it does not have enforcement authority. Adoption and enforcement are the responsibilities of state and local governments.

a. Review and Amendment

  • Process:
    • Evaluation: Jurisdictions review the new I-Codes to determine applicability.
    • Customization: Amendments may be made to address specific regional needs, such as climate, geological conditions, or local practices.

b. Legislative or Regulatory Adoption

  • Process:
    • Formal Adoption: Jurisdictions adopt the codes through legislative or regulatory processes.
    • Public Involvement: Some jurisdictions hold public hearings or comment periods before adoption.

c. Implementation

  • Process:
    • Effective Date: The adopted codes become law on a specified date.
    • Enforcement: Local building departments enforce the codes through plan reviews, permits, and inspections.

d. Timeframes for Adoption

  • Varies Widely:
    • Some jurisdictions adopt new codes soon after publication to stay current.
    • Others may delay adoption to allow time for training, public education, or to align with legislative schedules.

4. Benefits of the ICC's Process

  • Inclusivity: The open process allows for participation from all interested parties.
  • Transparency: Hearings and voting are conducted openly, and records are publicly available.
  • Expertise: Committees consist of professionals with diverse backgrounds, ensuring well-rounded code development.
  • Public Safety Focus: Final voting by governmental officials prioritizes the public interest over commercial or private interests.

5. Summary of Timeframes

  • Year 1:
    • January–March: Submission of code change proposals.
    • April–May: Committee Action Hearings.
    • June–July: Public comment period.
    • October–November: Public Comment Hearings.
    • November–December: Online Governmental Consensus Vote.
  • Year 2:
    • Early Year: Finalization and publication of new codes.
  • Year 2–3:
    • Variable: Adoption by jurisdictions.

6. Participation Opportunities

  • Submitting Proposals: Anyone can propose changes to the codes.
  • Attending Hearings: Open to the public for observation or participation.
  • Voting: Governmental members vote in the final phase to ensure public interest is upheld.

TBCF Summary​

The ICC's code development and adoption process is a collaborative effort that balances technical expertise, public safety, and the needs of various stakeholders. By understanding this process, professionals and interested parties can actively engage in shaping the building codes that impact safety, sustainability, and innovation in the construction industry. The structured timeline ensures that updates are systematic and that there is ample opportunity for input and review at each stage.


References
  • International Code Council Official Publications
  • "The Code Development Process" – ICC Resource Materials
  • "Participating in the ICC Code Development Process" – Building Safety Journal
  • "Understanding Model Codes and Their Adoption" – Journal of Construction Regulation
 
A lot of good info here but seems like you're overlooking the Group A CAHs in year one, repeat of proposals and input for Group B CAHs in year 2, and then the PCH in year 3. It's not simple and has changed a lot in past few years with pandemic and now the Group A and B business. Not easy to keep track and I feel it's de facto more restrictive and almost requires code consultants to get through it. The process with the legacy codes and early ICC was a fantastic example of democracy in action. Certainly some of the reason I got involved and participate in the committee level also.
 
A lot of good info here but seems like you're overlooking the Group A CAHs in year one, repeat of proposals and input for Group B CAHs in year 2, and then the PCH in year 3. It's not simple and has changed a lot in past few years with pandemic and now the Group A and B business. Not easy to keep track and I feel it's de facto more restrictive and almost requires code consultants to get through it. The process with the legacy codes and early ICC was a fantastic example of democracy in action. Certainly some of the reason I got involved and participate in the committee level also.
Lots of changes and I am an I class right now on the new code adoption process. If there are any changes, I will post it here.
 
A lot of good info here but seems like you're overlooking the Group A CAHs in year one, repeat of proposals and input for Group B CAHs in year 2, and then the PCH in year 3. It's not simple and has changed a lot in past few years with pandemic and now the Group A and B business. Not easy to keep track and I feel it's de facto more restrictive and almost requires code consultants to get through it. The process with the legacy codes and early ICC was a fantastic example of democracy in action. Certainly some of the reason I got involved and participate in the committee level also.
Are you here in Long Beach?
 
Pictures seem to be good summary. As noted above it's gotten very complicated. I wish there was more time for discussion. I'm preparing a comete rewrite of a section in Group B and it simply deserves more time for comittee deliberation.
 
No. My proposals were accepted in Orlando and no comments so on the consent agenda. I'll be in Orlando in spring, or at least plan to be.
And that is the problem with the consent agenda...If comments get missed, the change never really goes to the governmental members for proper vetting like this:

E112-24 IBC: 1028.2; IFC: [BE] 1028.2 Proponents: Jeffrey Grove, Coffman Engineers, Coffman Engineers (jeff.grove@coffman.com) 2024 International Building Code Revise as follows: 1028.2 Exit discharge. Exits shall discharge directly to the exterior of the building. The exit discharge shall be at grade or shall provide a direct path of egress travel to grade. The exit discharge shall not reenter a building. The combined use of Exceptions 1 and 2 shall not exceed 50 percent of the number and minimum width or required capacity of the required exits.
Exceptions:
1. Not more than 50 percent of the number and minimum width or required capacity of interior exit stairways and ramps is permitted to egress through areas, including atriums, on the level of discharge provided that all of the following conditions are met: 1.1. Discharge of interior exit stairways and ramps shall be provided with a free and unobstructed path of travel to an exterior exit door and such exit is readily visible and identifiable from the point of termination of the enclosure. 1.2. The entire area of the level of exit discharge is separated from areas below by construction conforming to the fireresistance rating for the enclosure. 1.3. The egress path from the interior exit stairway and ramp on the level of exit discharge is protected throughout by an approved automatic sprinkler system. Portions of the level of exit discharge with access to the egress path shall be either equipped throughout with an automatic sprinkler system installed in accordance with Section 903.3.1.1 or 903.3.1.2, or separated from the egress path in accordance with the requirements for the enclosure of interior exit stairways or ramps. 1.4. Where a required interior exit stairway or ramp and an exit access stairway or ramp serve the same floor level and terminate at the same level of exit discharge, the termination of the exit access stairway or ramp and the exit discharge door of the interior exit stairway or ramp shall be separated by a distance of not less than 30 feet (9144 mm) or not less than one-fourth the length of the maximum overall diagonal dimension of the building, whichever is less. The distance shall be measured in a straight line between the exit discharge door from the interior exit stairway or ramp and the last tread of the exit access stairway or termination of slope of the exit access ramp.

2. Not more than 50 percent of the number and minimum width or required capacity of the interior exit stairways and ramps is permitted to egress through a vestibule provided that all of the following conditions are met: 2.1. The entire area of the vestibule is separated from areas below by construction conforming to the fire-resistance rating of the interior exit stairway or ramp enclosure. 2.2. The depth from the exterior of the building is not greater than 10 feet (3048 mm) and the length is not greater than 30 feet (9144 mm). 2.3. The area is separated from the remainder of the level of exit discharge by a fire partition constructed in accordance with Section 708. Exception: The maximum transmitted temperature rise is not required. 2.4. The area is used only for means of egress and exits directly to the outside.
3. Horizontal exits complying with Section 1026 shall not be required to discharge directly to the exterior of the building.

4. Exit discharge onto the roof of the same building or onto a horizontal building separation per Section 510.2 is permitted when all of the following criteria are met: 4.1. 4.2. The exit discharge shall be provided with a free and unobstructed path of travel that is readily visible and identifiable, that does not include re-entering the building or utilizing an interior exit stairway or ramp or exterior exit stairway or ramp. The roof assembly, for the structural bays that support the required exit discharge path, shall have no unprotected openings, and not less than a one-hour fire resistance rating, and not less than the fire resistance rating required for the exit enclosure that discharges onto the roof.

Which will now allow egress to almost any roof (as long as it is 1 hour rated) without access to a public way...Also no 50% limitation....I get what they were trying to do, they just screwed it up and hopefully can find a way to fix it...More of us need to be involved when proposals first come out...

1729776752545.png
 
Well, if you miss submitting a comment for CAH2, can't you still submit a comment for the PCH? Maybe you need 2/3s at that point but that seems fair.
 
Back
Top