Chapter 1 tells you when the IMC applies, how the code official administers it, and what paperwork, permits, and approvals hold the job together.
IMC Chapter 1 Study Guide
IMC Chapter 1 Study Guide
Chapter 1 tells you when the IMC applies, how the code official administers it, and what paperwork, permits, and approvals hold the job together.
At a Glance
| Lens | Notes |
|---|---|
| Chapter focus | Scope and Administration |
| Why it matters | Chapter 1 tells you when the IMC applies, how the code official administers it, and what paperwork, permits, and approvals hold the job together. |
| In the field | In the field, this chapter shows up before the first piece of equipment is set and again when a project goes sideways. It is the chapter behind permit triggers, inspections, corrections, stop-work actions, and appeals. |
Core Fundamentals
- Start here when you need to know whether the IMC, IRC, IFGC, IBC, or another referenced code controls the work.
- Treat Chapter 1 as the rulebook for authority, permits, inspections, and documentation rather than a design chapter.
- Know the difference between approval, permit issuance, final approval, and ongoing maintenance obligations.
Section-by-Section Breakdown
Section 101 - Scope and General Requirements
Fundamentals Section 101 establishes where scope and administration applies and what work it governs.
Field Reality Use this section to decide whether the IMC is even in play. In the field it settles code-scope disputes quickly, especially where IRC or IFGC boundaries are involved.
Exam Focus
- Know when this section controls before a narrower requirement does.
- Track the default rule, then look for the trigger that shifts the answer.
- Use this section to frame the rest of the chapter correctly.
Common Mistakes
- Skipping the scope question and jumping to details too early.
- Treating general language like unenforceable background text.
- Assuming a later section always overrides this one automatically.
Exam Traps
- The stem may sound specific while the real answer is still the chapter-wide rule.
- One choice may fix the detail but miss the controlling path.
- The deciding fact is often whether a more specific section has actually been triggered.
Inspector Flags
- installation or work reviewed under the wrong code path
- partial compliance used to justify the whole installation
- field condition treated as outside the section when it still falls under it
Why It Matters It keeps the code path from being misread before the technical details are applied.
Key Code Hooks , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 102 - Applicability
Fundamentals Section 102 sorts out how general rules, specific rules, existing conditions, and referenced standards interact.
Field Reality This section shows up when existing buildings, alterations, and referenced standards are part of the conversation. It is a common correction-letter section because it explains how to resolve conflicts and what has to be brought up to current code.
Exam Focus
- Know when this section controls before a narrower requirement does.
- Track the default rule, then look for the trigger that shifts the answer.
- Use this section to frame the rest of the chapter correctly.
Common Mistakes
- Skipping the scope question and jumping to details too early.
- Treating general language like unenforceable background text.
- Assuming a later section always overrides this one automatically.
Exam Traps
- The stem may sound specific while the real answer is still the chapter-wide rule.
- One choice may fix the detail but miss the controlling path.
- The deciding fact is often whether a more specific section has actually been triggered.
Inspector Flags
- installation or work reviewed under the wrong code path
- partial compliance used to justify the whole installation
- field condition treated as outside the section when it still falls under it
Why It Matters It keeps the code path from being misread before the technical details are applied.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 103 - Code Compliance Agency
Fundamentals Section 103 identifies the enforcing agency and the official authority behind code administration.
Field Reality This is the chain-of-authority section. It matters whenever you need to know who can interpret, enforce, delegate, or officially act for the jurisdiction.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 104 - Duties and Powers of the Code Official
Fundamentals Section 104 defines what the code official may interpret, inspect, require, approve, or enforce.
Field Reality Inspectors and permit technicians live in this section. It describes the authority to inspect, interpret, enter, issue notices, and maintain department records.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 105 - APPROVAL
Fundamentals Section 105 controls the administrative rule path for approval within scope and administration.
Field Reality This section is the roadmap for alternates and modifications. You see it when a contractor proposes something unusual and needs to prove equivalency instead of just saying it should be acceptable.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 106 - PERMITS
Fundamentals Section 106 controls the administrative rule path for permits within scope and administration.
Field Reality This is the permit trigger section used at counters and during enforcement. It also matters in the field when work has already started and someone is trying to decide whether the permit was required.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 107 - Temporary Equipment, Systems and Uses
Fundamentals Section 107 controls how temporary equipment, systems, and uses stay under code authority during construction or limited operation.
Field Reality Temporary heating, temporary utilities, and construction-phase equipment often land here. This section matters when a job needs to operate before the permanent installation is fully complete.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 108 - Inspections and Testing
Fundamentals Section 108 controls the administrative rule path for inspections and testing within scope and administration.
Field Reality This section controls concealment, scheduling, and who must call for inspection. It comes up every time rough-in work is about to be covered or a failed test has to be repeated.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 109 - Fees
Fundamentals Section 109 controls when fees attach to the permit process and what that means for permit validity.
Field Reality You will mostly see this section in permit administration, but it also matters in enforcement when work started before the permit was issued.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 110 - CONSTRUCTION DOCUMENTS
Fundamentals Section 110 controls the administrative rule path for construction documents within scope and administration.
Field Reality Reviewers and designers use this section to judge whether the submitted package is clear enough to approve. Incomplete drawings often create field confusion that could have been stopped here.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 111 - NOTICE OF APPROVAL
Fundamentals Section 111 controls the administrative rule path for notice of approval within scope and administration.
Field Reality This is the closeout checkpoint showing the difference between installation and approved installation. It matters when the job is functionally done but not yet officially accepted.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 112 - SERVICE UTILITIES
Fundamentals Section 112 controls when regulated systems may be connected, disconnected, or restored to service.
Field Reality You see this section on unsafe installations and early utility requests. It controls when service can be connected, disconnected, or reconnected.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 113 - STOP WORK ORDER
Fundamentals Section 113 controls the enforcement response when work proceeds in violation of the code or in an unsafe manner.
Field Reality This is the enforcement hammer. When work continues in violation or without correction, this is the section that gives the jurisdiction a clean stop-work path.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 114 - MEANS OF APPEALS
Fundamentals Section 114 controls how formal appeals are handled when there is a dispute over code application or interpretation.
Field Reality This section matters when there is a real code interpretation dispute. It helps you understand what can be appealed and what is outside the board's authority.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Section 115 - VIOLATIONS
Fundamentals Section 115 controls the enforcement response when work proceeds in violation of the code or in an unsafe manner.
Field Reality In the field, use this section to verify that the installed condition matches both the code rule and the system's real-world operating risk.
Exam Focus
- Know the trigger, authority, or approval step that makes this section apply.
- Separate permit, inspection, approval, and enforcement actions clearly.
- Track who can act and what must happen before work proceeds or closes out.
Common Mistakes
- Treating administrative rules like paperwork only.
- Assuming field completion is the same as final approval.
- Mixing permit status with inspection status or utility release status.
Exam Traps
- Timing often decides the answer: before work, before concealment, or before service is restored.
- A choice may sound reasonable but assign authority to the wrong party.
- Existing-work language is often used to distract from a current administrative trigger.
Inspector Flags
- work proceeding without the required permit, approval, or inspection step
- documents, scope, or field conditions not matching the approved record
- utility connection or continued work before code authorization
Why It Matters Administrative failure can stop the job even when the installation looks technically correct.
Key Code Hooks , , , , ,
🔒 Expanded Walkthrough
Deeper field examples and exam-focused analysis for this topic are part of the premium study layer.
Study Drills
- Explain when an existing system can stay in place and when alterations trigger current-code compliance.
- Walk through the lifecycle of a permit from application to inspection to final approval.
- Be ready to explain what the code official can approve, modify, reject, or stop.
Website Notes
- Built as modular source content for cards, accordions, quiz support, and premium gating.
- Free-study blocks stay short and extractable; premium bullets hold the deeper decision logic.
- Pair with source code text for verification, not as a replacement for the code book.
Quick Retention
Must Know
- Scope and Administration questions usually turn on the controlling condition before they turn on the technical detail.
- A compliant-looking installation can still fail when the triggering rule path was chosen incorrectly.
- Inspection, exam logic, and real service problems usually point to the same weak spots.
- Read the section title, then verify the installed condition that actually activates it.
Common Exam Traps
- using a familiar trade answer instead of the section-specific code path
- solving a downstream detail while missing the controlling trigger
- mixing a related section into the wrong scenario
- accepting a present component without checking function, location, or approval
Field Failures
- misread trigger in scope and general requirements
- misread trigger in applicability
- misread trigger in code compliance agency
- misread trigger in duties and powers of the code official
- misread trigger in approval
Premium Content
Premium Study Layer
Expanded walkthroughs, deeper study notes, field-level examples, and exam-focused analysis for this section are part of our premium study layer.
Premium study content — available with a premium account.