We already covered SB 222 from the building department's side of the desk: the July 1, 2027 asynchronous inspection deadline, the July 1, 2028 automated permitting date, the fee caps, how it stacks against AB 1738. That's a procurement and staffing problem, and it belongs to the agency.
This is the other half of the bill. If you're a licensed contractor installing heat pump water heaters or heat pump HVAC systems in California, SB 222 doesn't change what you do on the job. It changes what you hand over afterward, and what you sign your name to. Departments get nine months of planning runway. You get a new documentation habit and a new certification that carries the word "perjury" in the statute. That's not a symmetrical trade.
Strip out the parts of SB 222 that are the department's problem — fee caps, website publication, exemptions for small jurisdictions — and two obligations land squarely on you.
First, the asynchronous submission itself. Once your local agency adopts an asynchronous inspection option, you're the one producing the record the inspector reviews later. Nobody is standing next to you asking you to pan the camera toward the disconnect or the condensate line. If it isn't captured, it doesn't exist for the inspector, and the callback is yours to schedule and yours to eat the cost of.
Second, the load calculation certification. For the automated online permitting track that takes effect July 1, 2028, the bill requires you to certify, under penalty of perjury, that you performed a load calculation to properly size the replacement equipment. That single sentence is doing more legal work than most contractors clock the first time they read it.
Neither of these shows up in the department-facing summary, because neither of these is the department's exposure. They're yours.
It's worth sitting with that for a second, because the framing in most coverage of SB 222 — including our own department-facing piece — treats the bill as a permitting-efficiency story. From the contractor's chair, "efficiency" mostly means the department spends less time on your job and you spend more time producing the record that lets them spend less time on it. That's not a complaint about the bill. It's a description of where the workload actually moved, and workload that moves without anyone naming it tends to turn into liability that nobody budgeted for.
It's worth being precise here, because the two get flattened together constantly and the liability sits in the gap between them.
A live remote video inspection puts you and the inspector on a call at the same time. If the inspector wants a different angle, they ask, and you show them. Whatever the inspector didn't think to request is arguably on the inspector, not on you.
An asynchronous submission removes that safety net entirely. You capture the record, submit it, and the inspector reviews it whenever they get to it — hours or days later, with no one available to redirect you back to the job site. SB 222 explicitly allows the inspector to contact you by phone or video if something's unclear, but that's a courtesy, not a guarantee, and it usually means a second trip. Municipalities already running asynchronous programs — Berkeley's building division and contract-inspection firms like Aoka Engineering among them — report that the submissions succeed or fail based almost entirely on how complete the contractor's first pass is, not on inspector judgment calls. Municipal permit staff building out AR-assisted permit compliance workflows are optimizing for the same thing from their side: a submission that doesn't need a follow-up call.
Translation: in an async world, incomplete documentation isn't a minor inconvenience. It's a direct cost transfer from the department's schedule to yours.
"Certify under penalty of perjury" is not boilerplate. It's the same legal weight as a sworn statement, and it attaches personally to the licensed contractor who signs it — not to the company, not to the technician who actually ran the numbers if that person isn't the one certifying.
Three things follow from that.
The calculation has to actually exist. A certification isn't a formality you complete because the online permitting portal requires a checkbox before it issues a real-time permit. If a load calculation was never performed — or was performed as a rough guess after the fact to satisfy the form — the certification is false on its face, regardless of whether the installed equipment happens to work fine.
"Properly size" is measurable, and disputes will measure it. A load calc that isn't in the file when a homeowner, an HOA, an insurer, or CSLB investigator asks for it is functionally the same as no load calc at all. You want the room-by-room numbers, the inputs you used, and the output attached to the job — not just the certification statement floating on its own.
The exposure outlives the permit. A permit gets closed out and life moves on. A false certification doesn't expire the same way. If an oversized or undersized system later contributes to a comfort complaint, a moisture problem, an electrical failure, or worse, and there's no load calculation behind the certification you signed, you're not defending an installation choice anymore — you're defending a sworn statement.
None of this means the paperwork gets harder in a way that should scare you off heat pump work. It means the paperwork needs to be treated as part of the job, not an afterthought you back into once the automated permitting portal asks for a signature.
Departments will publish their own required-capture lists as they build out asynchronous programs, and those will vary by jurisdiction. But there's a baseline that shows up across every asynchronous and virtual inspection compliance checklist we've seen from other states running the same kind of program, because the underlying question is always the same: can a reviewer who wasn't there confirm the work meets code from what you sent them?
Every one of those shots needs to be tied to the correct job, the correct address, and the correct date, or the record is worthless the moment anyone questions it. That's a bigger ask than it sounds like when you're managing a dozen jobs in a week, which is why a growing number of contractors have shifted away from the default camera roll toward tools built specifically for GPS- and timestamp-verified field photos. If you're already comparing options, the category breakdown for timestamped photo apps built for contractors and the HVAC-specific documentation tools are worth a look before you standardize your crew on whatever's already on their phones.
Here's the scenario that should worry you more than a rejected permit: the job closes, everyone moves on, and eight months later a homeowner disputes whether a wall was already damaged before your crew touched it, or an insurer questions whether the equipment installed matches what was certified on the permit.
If your documentation lives on an individual technician's personal phone, in a text thread, or in a folder of unlabeled images, you don't have a record — you have a claim that's your word against someone else's. That's exactly the gap that protects contractors from damage disputes when the record is tied to the job rather than to whoever happened to be holding the phone that day. It's the same logic that applies when documenting job site photos for insurance claims: the value isn't the photo, it's the verified metadata that photo carries and the fact that it's stored somewhere the company controls, not somewhere an individual employee's device controls.
The distinction between a standard phone camera and GPS- and timestamp-verified capture matters most exactly when nobody expected it to matter — months after the job, when memory is unreliable and the only thing that settles the question is whether the record can prove where and when a photo was taken. And because that record needs to survive staff turnover, a lost phone, or a change of employer, it's worth knowing how the underlying photo data is stored and secured before you're relying on it in a dispute.
The same discipline pays off on the closeout side of the job, too — structured photo documentation speeds up punch list closeout for the exact same reason it protects you in a dispute: everything is already organized by job instead of scattered across a device.
The contractors who find asynchronous inspection painless are the ones who built the habit before their jurisdiction made it mandatory. Practically, that means a per-job folder — physical or digital — that holds four things: the shot list results, the load calculation worksheet with its inputs and outputs, the submission confirmation from the permitting portal, and any correspondence from the inspector.
If you're setting this up for the first time, organizing field inspection photos by job rather than by date or by technician is the detail that makes the difference when someone needs to pull a specific record fast. And if you're evaluating documentation tools more broadly rather than just for heat pump work, the category comparisons for construction jobsite photo documentation and the wider building inspection software landscape are a reasonable place to start before you commit a crew to a workflow.
A closed permit feels like the end of the story. It isn't, for two separate reasons.
CSLB complaints and civil claims tied to a heat pump installation routinely surface long after the inspection card is signed off — a comfort complaint the first summer, a moisture issue the following winter, a resale inspection two years out that flags something the original permit was supposed to cover. Your state's statute of limitations for a construction defect or licensing complaint is measured in years, not in however long the permitting portal keeps a copy of what you submitted. If your only copy of the load calculation and shot list lived on a phone that's since been replaced, you don't have a file — you have a gap exactly where a defense should be.
The practical rule is simple even if it's inconvenient: keep the load calculation, the submission record, and the shot list for at least as long as your state's applicable statute of limitations for construction claims, and treat "the permitting portal has it" as a convenience, not a backup.
Before you send an asynchronous submission or sign a load calculation certification, run down this list:
California isn't alone in building this kind of asynchronous, contractor-documented permitting path. Florida's HB 667 pushed building departments toward a similar virtual inspection compliance model, and Maryland's solar permitting fight, which died as HB 1104 and passed as a different bill entirely, landed on the same underlying shift: less inspector time on-site, more weight on what the contractor documents. If you work across state lines, the shot-list-and-certification pattern in SB 222 is worth treating as a preview of what's coming to your other jurisdictions, not a California-only quirk.
Most of what departments deploy for asynchronous review — platforms like Blitzz Inspect — is built for the inspector's side of the review, with permitting-system integrations and a structured inspection report on the back end. That solves the department's problem. It doesn't solve yours, which is what happens before you ever hit submit.
That's the gap BlitzzCam is built for: GPS- and timestamp-verified capture that's organized by job automatically, so the shot list above becomes a checklist you complete once per job instead of a scramble you reconstruct from memory when a submission bounces back. If you're getting your crew set up on it for the first time, the onboarding walkthrough covers what the first week actually looks like.
If you work with municipalities directly on the inspection side rather than as a field contractor, the government customer and construction pages cover that half of the workflow, and you can see current pricing or schedule a walkthrough of both sides of the record — what the contractor submits and what the inspector reviews — side by side. For anything specific to your jurisdiction's rollout, reach out directly; asynchronous requirements are still being finalized city by city, and the shot list your department eventually publishes may add a few items to the baseline above.
It's worth spending more time on BlitzzCam specifically, because it's built around the exact gap this article has been describing: the contractor's side of an asynchronous submission, not the inspector's review queue.
The mechanics are deliberately simple. Every photo and video captured through the app is stamped with GPS location and a timestamp at the moment of capture, then filed automatically under the correct job — no renaming files, no dragging images out of a camera roll at the end of the day, no guessing which address a photo belongs to three jobs later. For SB 222 specifically, that means the shot list for a heat pump water heater swap or an HVAC changeout becomes a guided capture flow rather than something a technician has to remember unprompted, and the record that comes out the other end is already organized the way a load-calc certification file or a CSLB request would need it.
A few details matter more than they look like they should once you're relying on the record months later:
If you're already running a jobsite photo tool and weighing whether to switch, the side-by-side breakdowns against CompanyCam and against TrueLook's fixed camera model cover the trade-offs more specifically than a general features list would. The honest caveat is that BlitzzCam is newer than some of the established players in that category and is still in early access for some features — worth knowing going in, not something to discover after you've standardized a crew on it.
None of this replaces the load calculation itself, and it doesn't make the certification any less of a sworn statement. What it does is remove the excuse that the documentation was too much friction to do consistently, which is the excuse that shows up most often when a contractor is explaining, after the fact, why a shot is missing from a file that a department, a homeowner, or CSLB is now asking to see.
SB 222 reads, on the surface, like a permitting efficiency bill. For the department, it mostly is. For the contractor signing the load calculation certification and building the asynchronous submission, it's a liability shift dressed up as a scheduling convenience.
The bill doesn't ask you to do anything differently on the install itself. It asks you to prove, later, to someone who wasn't there, that you did it correctly — with a shot list that has to be complete the first time, and a certification that has to be backed by a calculation that actually exists. Neither of those is optional once your jurisdiction adopts the asynchronous option, and neither of those gets easier by waiting until July 2027 to think about it.
The contractors who come out ahead here aren't the ones with the fastest installs. They're the ones who treat the shot list and the load calculation file as part of the job, standardize how the crew captures and stores that record, and never have to reconstruct any of it from memory when a submission bounces back or a complaint lands two years later. Build that habit now, and SB 222 is a form to fill out. Skip it, and it's the sworn statement you can't back up when someone finally asks to see the file behind it.