Short answer: The model codes do not name "virtual inspection" as a separate inspection type. They give the building official authority over how inspections are conducted and a formal path to approve alternative materials, designs, and methods. Remote video inspection is normally authorized under that discretion plus a written departmental policy.
The two provisions that matter
Duties and powers of the building official. The IBC and IRC both charge the building official with making required inspections, and allow acceptance of reports from approved agencies or individuals. That is the hook departments use to define how an inspection is observed.
Alternative means and methods. Both codes allow the building official to approve an alternative where the proposed method is satisfactory and complies with the intent of the code, and is at least equivalent in quality, strength, effectiveness, fire resistance, durability, and safety. Remote observation is evaluated the same way: does it let the official verify compliance to the same standard?
What "equivalent" means in practice
An inspector standing on site can change viewpoint, touch materials, smell a gas leak, and measure. A remote inspection has to compensate deliberately:
- Viewpoint control — the inspector directs the camera and can request specific angles, plus zoom and torch control on the field device.
- Scale and measurement — a tape or known reference in frame for anything dimensional.
- Identity and location — proof the footage is from this address, this day. See GPS geofencing and GPS accuracy.
- Integrity — media that cannot be swapped or edited without detection. See C2PA content credentials and tamper detection.
- Record — the inspection evidence retained with the permit file, not on a phone.
Where a remote method cannot deliver equivalence — concealed conditions, destructive verification, hazardous occupancies — the correct answer is an on-site visit. Programs that state this explicitly are the ones that last.
Special inspections and third-party reports
Chapter 17 special inspections remain the domain of approved agencies. Remote tools are used there mainly for supervision, documentation, and follow-up verification rather than replacing the required inspection itself. Departments that accept third-party reports often accept remotely captured supporting evidence when it carries verifiable provenance.
Documentation that survives an appeal
If a remote approval is ever challenged, the department needs to show three things: the policy that authorized the method, the evidence captured during the inspection, and an unbroken chain of custody for that evidence. An audit trail covering capture, view, export, and share events is what turns "we did a video call" into a defensible record. See also whether verified media is admissible.
How this differs from a state or local mandate
It is worth separating two different questions that get conflated: "does the code allow it" and "does the local government require it." The IBC and IRC answer the first question by staying silent on medium and delegating discretion to the building official — they neither require nor forbid remote inspection. Laws like California's AB 1738 answer the second question by mandating that departments offer the option for specific residential permit types, regardless of whether a given official would have chosen to adopt it. A jurisdiction can be fully code-compliant while running zero remote inspections, and a jurisdiction can be required by state law to offer remote inspection while the code itself never uses the phrase.
A practical equivalence checklist for building officials
Departments drafting or reviewing a remote inspection policy against the alternative-means standard can use a short checklist to document their reasoning, which is useful both internally and if the policy is ever challenged:
| Code equivalence factor | Remote inspection compensating control |
|---|---|
| Quality of observation | Inspector-directed camera control, zoom, and torch on the field device |
| Verification of location and time | GPS-verified, timestamped capture rather than a phone screenshot |
| Effectiveness of the record | Retained media attached to the permit file, not left on a personal device |
| Resistance to falsification | Tamper-evident media with content credentials, such as a C2PA seal |
| Fallback for inadequate conditions | Documented right to convert to an on-site visit without additional fee |
A department that can check each row of this table has effectively built the equivalence argument the code requires, whether or not it labels the document that way.
Why the model code approach favors verified capture over consumer video
Because the equivalence standard is about the quality and durability of the record, not just the ability to see the work live, a plain video call satisfies the "observation" half of the equivalence test but not the "record" half — there is nothing left to audit once the call ends. Tools built specifically for inspections, like Virtual Inspection Pro, close that gap by producing a permanent, verifiable file alongside the live session, which is closer to what the alternative-means provision is actually asking building officials to certify.
How this maps to insurance and warranty disputes
Building officials are not the only audience for this equivalence question. When a structural defect claim or warranty dispute arises years after a project closes out, the inspection record is often the first document requested. A remote inspection that produced only a verbal pass, with no retained media, gives a department nothing to point to. A remote inspection that produced GPS-verified, tamper-evident photos tied to the permit gives both the department and the property owner something closer to what an in-person inspection with photo documentation would have produced. This is one reason departments that adopt remote inspection tend to also tighten their evidence retention policy at the same time, rather than treating the two as separate decisions.
What contractors should ask before assuming a job qualifies
Because the code leaves the equivalence judgment to the local building official, contractors working in an unfamiliar jurisdiction should not assume a given inspection type is remote-eligible just because it was in the last county. Three questions settle it quickly: is this specific inspection type on the department's published remote-eligible list, does the department require a specific capture tool or will any live video work, and what happens if the inspector determines mid-call that the view is not sufficient. Getting these answers before scheduling avoids a wasted appointment window.
FAQ
Does the ICC prohibit virtual inspections?
No. The model codes are silent on the medium and place the decision with the building official, subject to state and local amendments.
Do we need a code amendment to run remote inspections?
Usually not. Most departments proceed on a written administrative policy under the building official's existing authority; some states have added enabling language.
Which inspections should never be remote?
Anything requiring physical verification of concealed or structural conditions, and any inspection where connectivity prevents a complete view of the work.
Is there a specific IBC or IRC section for virtual inspections?
No single section names remote inspection. Departments rely on the general inspection-authority sections and the alternative materials, design, and methods sections, then layer a local policy on top.
Do model codes require a licensed contractor to hold the camera?
The model codes do not address this; it is set entirely at the local policy level, and requirements vary by inspection type and jurisdiction.
Keep reading
- Virtual Building Inspections by State — how model-code discretion plays out differently across jurisdictions.
- How a Building Department Launches a Remote Inspection Program in 90 Days — turning code authority into a working policy.
- Virtual Inspection Checklist: Footing, Framing, and Final — what equivalence looks like at the inspection-item level.
- California Bill AB 1738 — a statewide mandate layered on top of model-code discretion.