Short answer: A building department can stand up a working remote video inspection program in about 90 days by limiting scope to a handful of low-risk inspection types, publishing a one-page policy, training inspectors on a single tool, and measuring three numbers: inspections completed remotely, average time per inspection, and re-inspection rate.
Days 1–30: scope and policy
Do not start with technology. Start by choosing five inspection types that are low risk and high volume — typically water heater replacement, HVAC changeout, residential solar, re-inspections, and minor electrical rough-in. These generate the most windshield time per dollar of risk.
Then write the policy. One page is enough, and it should state:
- Eligible inspection types and any square-footage or occupancy limits.
- Who may hold the camera (licensed contractor, homeowner, or authorized agent).
- Connectivity and lighting expectations, and the inspector's right to convert to an on-site visit.
- Evidence requirements: timestamped media, verified location, retention period.
- How the record attaches to the permit file.
Days 31–60: technology and pilot
The tool requirements follow the policy, not the other way around. At minimum the department needs live two-way video, no app install for the field participant, still capture during the call, location verification, annotation so the inspector can point at what needs correcting, and an exportable record. A consumer video app fails on the last three.
Run a pilot with two or three inspectors and a small group of cooperative contractors. Twenty to thirty inspections is enough to expose the real problems, which are almost never the video: they are scheduling windows, cell coverage at rural sites, and contractors who join from a laptop instead of a phone.
Days 61–90: train, publish, measure
Inspector training takes under an hour if the tool is right. The parts worth rehearsing are directing the camera operator verbally, capturing evidence before giving a verdict, and ending a call cleanly when conditions are inadequate.
Publish the program page for contractors with eligible types, how to request, and what to have ready. Then track:
| Metric | Why it matters |
|---|---|
| Share of inspections completed remotely | Adoption; drives the savings case |
| Average minutes per inspection | Remote should be materially shorter than a drive-plus-inspect cycle |
| Re-inspection rate, remote vs. on-site | The quality control number your council will ask for |
| Same-day scheduling rate | The benefit contractors feel first |
The three failure modes
Scope creep. Adding complex framing in month two produces a bad inspection and kills the program politically. Expand only after the re-inspection numbers hold.
Evidence gaps. If the record is a screenshot in an email, the program cannot survive a dispute. Use verified capture with content credentials and an audit trail so the file proves when and where it was taken.
Contractor friction. If the field participant has to install an app or create an account, adoption stalls. A one-tap link is the difference between a program and a pilot that quietly ends.
A sample 90-day launch calendar
| Week | Milestone |
|---|---|
| 1–2 | Pick five eligible inspection types; draft one-page policy |
| 3–4 | Legal and building official sign-off on policy language |
| 5–6 | Select tool; confirm no-app-install guest join and evidence retention |
| 7–8 | Train two to three pilot inspectors |
| 9–10 | Run pilot with cooperative contractors; log every issue |
| 11–12 | Fix scheduling and connectivity issues found in pilot |
| 13 | Publish public program page and contractor instructions |
Budgeting the program: what actually costs money
Departments often assume the biggest cost is the software license. In practice the recurring costs are staff training time, updating the permit portal to flag remote-eligible types, and ongoing evidence storage. Session-based pricing models, where a department pays per inspection rather than per named inspector seat, tend to match budget cycles better for departments that expect adoption to grow gradually rather than all at once.
How to justify the program to a council or board
Councils generally want to see two things before approving budget: a quality safeguard (the re-inspection rate comparison) and a resident-facing benefit (same-day scheduling, fewer missed-appointment windows). Framing the pilot results around those two numbers, rather than around the technology itself, is what tends to get a program funded past the pilot stage. Departments that ran successful programs, such as those covered in the state-by-state tracker, consistently lead with adoption and re-inspection metrics rather than technical specifications when reporting back to their governing bodies.
Common objections from inspectors and how programs address them
Inspector buy-in is usually the deciding factor in whether a 90-day launch survives past the pilot. The most common objection is a fear that remote inspections will be blamed if something is missed. Programs that succeed address this directly in the written policy: the inspector retains full authority to fail an inspection, request additional angles, or convert to an on-site visit at any point, and the retained evidence protects the inspector's decision just as much as it protects the contractor's record.
What to include in the contractor-facing instructions
The public program page should answer four questions in plain language: which inspection types qualify, how to request one, what to have ready on site (phone charged, work exposed, tape measure and level on hand), and what happens if the connection fails mid-call. Departments that publish this as a short checklist rather than a policy document see faster contractor adoption, because most contractors will read a checklist and skip a policy PDF.
FAQ
How many inspectors does a program need to start?
Two. A small pilot group builds the internal playbook faster than a department-wide launch.
Does remote inspection reduce headcount?
In practice it reduces backlog and windshield time rather than staff. Departments typically report more inspections completed per day with the same team.
What about jurisdictions facing AB 1738?
The 90-day plan is the compliance path. See getting ready for AB 1738 and the state-by-state tracker.
What is the minimum viable technology for a first pilot?
Live two-way video with no app install for the field participant, in-session still capture, and location verification. Annotation and automated reporting can be added once the pilot proves out.
How do we know when to expand beyond the initial five inspection types?
Expand only after the pilot's re-inspection rate for remote inspections is at or below the on-site rate for at least one full reporting cycle.
Keep reading
- What the IBC and IRC Say About Remote Virtual Inspections — the code authority a department's policy relies on.
- Virtual Building Inspections by State — how programs vary once launched.
- Virtual Inspection Checklist: Footing, Framing, and Final — the field checklist inspectors and contractors need on day one.
- California Bill AB 1738 — the deadline driving many California launches.
Common reasons 90-day programs slip
- Scope creep at week two. Every additional inspection type adds a capture sequence, a training session, and an exception. Ship a short list and extend later.
- Technology chosen before policy. The eligibility rules and evidence standard determine what the tool must do; picking a tool first inverts that.
- No abort path. Inspectors who are not told that ending a call is an acceptable outcome will approve things they could not see.
- Records handled as an afterthought. Retention and public-records handling must match the permit schedule from day one, not after the first request.
- No contractor communication. Adoption comes from published sequences and predictable slots, not from an announcement.
Track three numbers through the pilot: share of eligible inspections completed remotely, share aborted to a site visit, and time from request to result. They tell you whether to widen the eligibility list or tighten the capture sequences.
Keep reading
- Footing, framing and final checklist — the capture sequences.
- What ICC and IBC say about remote inspections.
- California AB 1738 — a statewide driver.
- Chain of custody for inspection evidence.
- Virtual building inspections by state.