PUBLIC CODE CHANGE PROPOSAL FORM 

FOR PUBLIC PROPOSALS TO THE INTERNATIONAL CODES 

2012-2014 CODE DEVELOPMENT CYCLE 

CLOSING DATES: Group A Codes: January 3, 2012 

Group B Codes: January 3, 2013 

Group C Codes: January 6, 2014 

*See Item 3 of these instructions for additional information concerning Group A and Group B Code 

 Development Committees Responsibilities* 

1)

Name: Date: 

Jurisdiction/Company: 

Submitted on Behalf of: 

Address: 

City: State: Zip Code: 

Phone: Ext. Fax: 

E-mail address (see # 4 below): 

2) Copyright Release: In accordance with Council Policy #28 Code Development, all Code Change Proposals, Floor Modifications and 

Public Comments are required to include a copyright release. A copy of the copyright release form is included at the end of this form. 

Please follow the directions on the form. This form as well as an alternative release form can also be downloaded from the ICC website 

at www.iccsafe.org. If you have previously executed the copyright release for this cycle, please check the below:

______2012-2014 Cycle copyright release on file 

3) Code: Indicate appropriate International Code(s) associated with this Public Proposal – Please use Acronym: ___IECC_____ 

 

If you have also submitted a separate coordination change to another I-Code, please indicate the code: ________ 

(See section below for list of names and acronyms for the International Codes). 

NOTE: Sections of the International Codes that have a letter designation in brackets in front of them are the responsibility of a 

different committee than the committee normally responsible for that code. For instance, Section 301.1.4 of the IEBC has a [B] in front 

of it, meaning that this section is the responsibility of one of the IBC Code Development Committees (in this case, IBC-S). Any

proposed changes to Section 301.1.4 will be heard by the IBC-Structural committee. 

Therefore, some code change proposals to Group B code text may be due by January 3, 2012, in order to be heard by Group A 

code development committees, and vice versa (proposed revision to a Group A code due January 3, 2013.) Please go to 

www.iccsafe.org/responsibilites for detailed information on Group A and Group B Code Development Committee 

responsibilities. 

4) Multiple Proposals: A proponent shall not submit multiple code change proposals to the same code section. When a proponent 

submits multiple code change proposals to the same section, the proposals shall be considered as incomplete proposals and not 

processed in accordance with Section 4.3 of CP #28. This restriction shall not apply to code change proposals that attempt to address 

differing subject matter within a code section. 

5) Referenced Standards: Check here if this code change proposal includes reference to a standard that is not currently referenced in 

one of the I-Codes. _____

 NOTE: If a new referenced standard is proposed, a copy of the standard must be provided by the proponent of the code change 

proposal. (This code change proposal will be considered incomplete and not processed if the new standard is not submitted in at least 

consensus draft form in accordance with Section 3.6 of Council Policy CP #28.) If you have forwarded a copy of the standard(s) to 

ICC please check below: 

 ______ Copy of new referenced standard(s) sent. (Please check: Electronic ___ or Hard Copy ___) 

6) E-mail address: Your email address will be published with your code change proposal unless you check here: ______

7) Information required: Be sure to format your proposal and include all information as indicated below and in the Code Change Proposal 

 Instructions’ section on Page 2 of this form. 
 

8) Format: Proposals should be sent to the office below via regular mail or email. An e-mail submittal is preferred, including an 

electronic version, in either WordPerfect or Word (see proposal formatting section on Page 2 of this form). 

Please use a separate form (see page 3) for each proposal submitted. Note: All code changes received will receive an acknowledgment 

by approximately two weeks after the code change deadline. Please contact the ICC staff listed below if you have not received an 

acknowledgment by two weeks after the code change deadline.

Group A Group B Group C Send to: 

IBC - International Building Code 

IFGC - International Fuel Gas Code 

IMC - International Mechanical 

Code 

IPC - International Plumbing Code 

IPSDC - International Private 

Sewage Disposal Code 

IADMIN – International Administrative Code 

(Chapter 1 of I-Codes except the IRC and the 

IECC, and Referenced Standards Updates) 

IEBC - International Existing Building Code 

IECC - International Energy Conservation 

Code 

IFC - International Fire Code 

ICC PC - ICC Performance Code 

IPMC - International Property Maintenance 

Code 

IRC - International Residential Code 

IWUIC - International Wildland-Urban 

Interface Code 

IZC - International Zoning Code

IgCC – International Green 

Construction Code 

ISPSC – International Swimming 

Pool and Spa Code 

International Code Council 

Chicago District Office 

Attn: Dynice Broadnax 

4051 West Flossmoor Road 

Country Club Hills, IL 60478-

5795 

Fax: 708/799-0320 

codechanges@iccsafe.org

CODE CHANGE PROPOSAL INSTRUCTIONS 

Please provide all of the following items in your code change proposal (see form on page 3). Your proposal should be entered on

page 3 as a separate file. However, please read the instructions provided below for each part of the code change proposal. The 

sections identified in parentheses are the applicable sections from CP #28 Code Development. The full procedures can be 

downloaded from www.iccsafe.org. 

PROPOSAL FORMATTING:

Show the proposal (see form on page 3) using strikeout, underline format. At the beginning of each section, one of the following instruction 

lines are also needed: 

 •Revise as follows 

 •Add new text as follows 

 •Delete and substitute as follows 

 •Delete without substitution 

The only formatting that is needed is BOLDING, STRIKEOUT AND UNDERLINING. Please do not provide additional formatting such 

as tabs, columns etc. as this will be done by ICC. DO NOT USE THE TRACKING CHANGES OPTION, AUTOMATIC 

NUMBERING, OR ANY OTHER ADVANCED FORMATTING TOOLS PROVIDED BY WORD. 

SEPARATE GRAPHIC FILES ARE REQUIRED FOR GRAPHIC MATERIALS. Graphic materials (Graphs, maps, drawings, charts, 

photographs, etc.) must be submitted as separate electronic files in .CDR, IA, TIF or .JPG format (300 DPI Minimum resolution; 600 DPI 

or more preferred) even though they may also be embedded in your Word or WordPerfect submittal. 

SUPPORTING INFORMATION: (3.3.4 & 3.4) 

The following items are required to be included in your proposal (see form on page 3): 

1. The proponent shall clearly state the purpose of the proposed code change 

2. The proponent shall provide a logical explanation which clearly shows why the current Code provisions are inadequate or overly

restrictive, specifies the shortcomings of the current Code provisions and explains how such proposals will improve the Code. 

3. The proponent shall substantiate the proposed code change based on technical information and substantiation. A minimum of two copies 

of all substantiating information shall be submitted. 

4. The proponent shall submit a bibliography of any substantiating material submitted with the code change proposal. 

REFERENCED STANDARDS: (3.4 & 3.6) 

List any new referenced standards that are proposed to be referenced in the code and provide a minimum of two copies. See also Item 5 on 

page 1 regarding proposed new referenced standards. Updates to currently referenced standards will be processed as a Group B proposal. 

For ICC rules on referenced standards, see Section 3.6 of CP #28. Additional copies will be required for committee members. ICC staff 

will provide you with a mailing list for the appropriate committees.

COST IMPACT: (3.3.5.6) 

The proponent shall indicate one of the following regarding the cost impact of the code change proposal: 

1) The code change proposal will increase the cost of construction; or 
 

2) The code change proposal will not increase the cost of construction.

The proponent should submit information that supports their claim. Any information submitted will be considered by the code development 

committee. This information will be included in the bibliography of the published code change proposal.

CODE CHANGE SUBMITTAL EXAMPLE

Code: IBC–12/13

705.1 

Proponent: John Doe, P.E., Acme Building Corporation, Inc, representing self

Revise as follows:

705.1 General. Each portion of a building separated by one or more a fire walls that comply

complies with the provisions of this section Section 705 shall be considered a separate building. 

Reason: A fire wall complying with Section 705 establishes the equivalent of separate buildings on either side of the fire 

wall. This proposal provides text that more succinctly states this purpose of a fire wall. 

Cost Impact: The code change proposal will not increase the cost of construction. 

Public Hearing: Committee: AS AM D 

 Assembly: ASF AMF DF 

CODE CHANGE PROPOSAL FORM 

(See instructions on page 2) 

Code: ____IECC____ –12-14

Code Sections/Tables/Figures Proposed for Revision (3.3.2); Note: If the proposal is for a new section, indicate (new). 

Section R401.2.

Proponent: Name/Company/Representing (3.3.1): (NOTE: DO NOT USE ACRONYMS FOR YOUR COMPANY OR 

ORGANIZATIONAL NAME)

Revise as follows: 

R401.2 Compliance. Projects shall comply with all Sections identified as “mandatory” and with either of the following:

sections identified as “prescriptive” or the performance approach in Section R405.

1. All sections identified as “prescriptive.”

2. Section R405.

Reason: 

The proposed change provides a clarification. The current wording in the code has led to some confusion as to whether the mandatory lighting 

provisions of Section R404 are required when a home complies via the performance path of Section R405. 
 

Cost Impact: 

The code change proposal will not increase the cost of construction.

Public Hearing: Committee: AS AM D 

 Assembly: ASF AMF DF 

COPYRIGHT RELEASE FOR 

2012-2014 PROPOSALS, MODIFICATIONS and PUBLIC COMMENTS 

SUBMITTED ON 

ICC CODES 

PRODUCED & PUBLISHED BY THE

INTERNATIONAL CODE COUNCIL 

This form is required for all Proposals, Floor Modifications and Public Comments submitted to the 

International Code Council. Only one signed Copyright release form is required for the entire 2012-

2014 Cycle and will be kept on file and can be used for all Proposal, Floor Modification and Public 

Comment submittals you submit to ICC unless you represent multiple entities. An executed form is 

required for each entity represented. 

I hereby grant and assign to ICC all rights in copyright I may have in any authorship contributions I 

make to ICC in the 2012-2014 Cycle in connection with any proposal and public comment, in its 

original form submitted or revised form, including written and verbal modifications submitted in 

accordance with Section 5.5.2 of CP #28. I understand that I will have no rights in any ICC 

publications that use such contributions in the form submitted by me or another similar form and 

certify that such contributions are not protected by the copyright of any other person or entity. 

Signature: ________________________________________________________________ 

Please type or print full name: 

Jurisdiction/Company: _________________________________________________ 

Entity Represented: ___________________________________________________

Contact info: Phone: _________ Email: ___________________________________

Date signed: _________________________________________________________

PLEASE FAX OR MAIL THE SIGNED COPYRIGHT RELEASE TO:

Fax: ICC Codes & Standards Department - 708-799-0320 
 

Email: dbroadnax@iccsafe.org 

Mail: ICC Codes & Standards Development 

Chicago District Office 

4051 W. Flossmoor Road 

Country Club Hills, IL 60478-5795