ICC 64 study materials
ICC 64 study resources

ICC 64: General Building Code Knowledge

ICC 64 · Work through your exam, one topic at a time.

All guide sections

General Building Code Knowledge

General Building Code Knowledge

This domain tests how well you understand the IBC’s legal and technical framework: scope, adoption, definitions, referenced standards, and the rules for approving alternative materials and methods. The CBO exam expects applied knowledge of how the code becomes enforceable and how its provisions interlock.

Core rules

  • The IBC is a model code. It is enforceable only through adoption by a state or local jurisdiction, often with amendments. Know which edition is in force and how local amendments change the text.
  • Scope covers new construction, alterations, additions, repairs, and existing structures. The building code does not replace plumbing, mechanical, electrical, or fire codes; those are separate adopted codes.
  • Referenced standards such as ASTM, NFPA, ASCE, ACI, and AISC are enforceable as though copied into the code, including the specific edition cited.
  • Section 104.11 allows alternative materials, designs, and methods when the building official finds them equivalent in performance, quality, strength, effectiveness, fire resistance, durability, and safety.
  • Definitions control classification. Terms such as “building height,” “story,” “floor area,” and “occupant load” have code-specific meanings that may differ from ordinary usage.

Worked example

A designer proposes a proprietary insulated concrete form wall that is not listed in the code’s prescriptive tables. The contractor asks whether it can be used. Under Section 104.11, the building official may approve it after reviewing test data, engineering analysis, or an evaluation report that shows equivalence to the code’s performance requirements. The decision must be documented and based on evidence, not simply on a manufacturer’s claim that the product is “code compliant.” Approval is an alternative-method determination, not a variance.

Traps

  • Applying the model code while ignoring local amendments.
  • Treating a referenced standard as advisory rather than mandatory.
  • Confusing an alternative-method approval with a variance: a variance changes a requirement, while an alternative meets the code’s intent by other means.
  • Citing the wrong edition of a referenced standard.