Getting your building department ready for AB 1738 means setting up technology, protocols, staff training, and audit safeguards well before the July 1, 2027 deadline, so remote inspections run as smoothly as in-person ones.

Step 1: Understand What The Law Requires

Before building anything, get clear on the actual mandate. AB 1738 requires cities, counties, and charter cities to offer homeowners and contractors the option of a remote inspection for a specified list of building permit work on one- and two-family dwellings, with compliance required by July 1, 2027.

Eligible project types typically include things like water heaters, solar installations, and accessory dwelling units, so start by identifying which of your department's existing permit categories fall under the bill's scope.

The law also extends the same legal immunities inspectors already have for in-person visits to remote inspections, and it lets your department set up onsite audits and temporarily suspend remote access for anyone caught misrepresenting completed work.

Beginning with the report due April 1, 2028, your department will need to confirm compliance in its standard annual planning report, so build that reporting step into your compliance timeline now.

Step 2: Choose Your Remote Inspection Method

The bill specifies that remote inspections can be conducted offsite using either a live video call or recorded photos and video submitted by the homeowner or contractor.

Decide early whether your department will rely on common video platforms like FaceTime and Zoom, similar to Santa Rosa's approach, or invest in dedicated inspection software like Virtual Inspection Pro that also handles scheduling, security, compliance and reporting.

Many jurisdictions that already run mature programs, including Los Angeles and San Bernardino County, use a mix of both, offering live video for straightforward walkthroughs while allowing photo or video submission for simpler self-certification cases.

Whichever path you choose, make sure the platform can capture and store timestamped documentation, since digital recordkeeping becomes especially important if a remote inspection is ever audited or challenged.

Step 3: Set Up Equipment And Technical Standards

Your department and the public both need the right tools for remote inspections to work reliably. On the department side, equip inspectors with a large monitor or laptop screen so they can clearly see what's being shown on camera, and have them practice conducting mock inspections before going live with real applicants.

For applicants, publish a clear equipment checklist so they arrive prepared rather than scrambling mid-call.

  • A smartphone, tablet, or laptop with a webcam and stable internet or cellular connection

  • A flashlight for crawlspaces, attics, or electrical panels

  • A tape measure and level for confirming dimensions or clearances

  • A ladder, if the inspection requires reaching elevated areas

  • Approved construction plans and any relevant reports, such as HERS or structural observation reports, available to show on request

Step 4: Write Clear Administrative Protocols

AB 1738 authorizes local agencies to adopt reasonable protocols governing how remote inspections are technically conducted, so use that discretion to write clear internal procedures.

Document exactly which permit types qualify, how appointments get scheduled, what happens if a video call drops mid-inspection, and what backup process applies if a remote inspection can't be completed.

Santa Rosa's model offers a useful template: applicants get a call the morning of the inspection informing them whether it will be in-person or remote, along with a scheduled arrival window. Inspections there typically begin with the applicant showing the property's street address on camera, followed by a guided walkthrough of the specific work, and results get delivered in writing by email afterward.

Step 5: Train Inspectors On Remote-Specific Skills

Conducting a remote inspection well requires different skills than an in-person visit, so build dedicated training around it rather than assuming existing inspectors will adapt automatically.

Inspectors should have a clear script or set of directions ready to use while guiding an applicant through the property, along with a consistent, methodical approach to moving through rooms or components.

Training should also cover privacy safeguards, since inspectors may be viewing the interior of someone's home; using a dedicated device on a secure network and conducting calls from a private office setting helps protect both the applicant's and the department's interests. Inspectors also need practice recognizing when a project is too complex for remote review and should instead be escalated to an in-person visit.

Step 6: Build In Fraud Prevention And Audit Processes

Since AB 1738 explicitly authorizes onsite audits, decide upfront how your department will verify that remote inspections weren't misrepresented.

Consider a random or risk-based audit schedule where a percentage of remote inspections get a follow-up in-person check, and document the process clearly so it's applied consistently across applicants.

Establish clear consequences for misrepresentation as well, since the law allows a temporary ban on remote inspection access for anyone found to have willfully misrepresented completed work. Communicating these rules to contractors and homeowners in advance can also discourage misuse before it happens.

Step 7: Track Costs And Reporting Obligations

Because the bill doesn't come with state reimbursement for local implementation costs, budget early for the technology, staff time, and training needed to stand up a compliant program.

Some opponents of the bill have raised exactly this concern, so departments that plan financially ahead of the 2027 deadline will be in a stronger position than those scrambling at the last minute.

Finally, build your compliance reporting into existing workflows now, since your department will need to confirm implementation in its annual planning report starting with the submission due April 1, 2028.

Setting up a simple internal tracking log of remote inspections completed, audited, and any misuse cases found will make that annual reporting far easier when the deadline arrives.

How we can help you

Virtual Inspection Pro can help building departments meet AB 1738 requirements out of the box by automatically capturing timestamps, GPS locations, and secure video recordings for every inspection, so compliance documentation is built into the workflow rather than added afterward.

Every session gets recorded and securely archived in the cloud automatically, with recall available for previous inspection data and results whenever a department needs to reference past work. Inspectors can capture in-session screenshots of key inspection items, and reports get auto-populated with photos, status, notes, and comments taken directly during the call.

Virtual Inspection Pro software app automatically geolocation-tag every session with near real-time accuracy and apply automatic date and time stamps, creating a verified inspection record that meets or exceeds local code requirements without any extra staff effort.

The platform validates GPS location, timestamps, and metadata authenticity during each session, flagging anything suspicious before a report is even finalized.

This kind of built-in verification directly supports AB 1738's requirement that remote inspections carry the same legal standing and reliability as in-person visits.

Our software applies algorithmic geo-tagging to authenticate and integrate permit information directly with the property address and location being inspected, reducing the chance that an applicant could misrepresent which site is actually being reviewed.

Since AB 1738 explicitly allows local agencies to audit remote inspections and penalize misrepresentation, having this validation happen automatically at the point of capture makes those audits far easier to run.

If you would like a free demo, please contact us at this link or email help@virtualinspection.app.

Sources