Remote work policies, digital permitting and inspections, communication systems, and operational continuity during emergencies.
2
hours
0.2
CEUs
Health, Safety & Code Enforcement
1.7.6
Remote work policies, digital permitting and inspections, communication systems, and operational continuity during emergencies.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamEstablish remote work procedures for building departments
A building department's obligations do not pause when its building closes. Permits must still issue, plans must still be reviewed, inspections must still verify compliance, and records must still be kept. Remote operations are the procedures that keep those functions running when staff cannot work from the office, customers cannot reach the counter, or inspectors cannot travel to every site.
Distinct triggers activate remote procedures, and each stresses the department differently. A public health emergency — the 2020 pandemic is the defining example — leaves facilities and technology intact but removes the ability to gather people: no counter traffic, no crowded jobsite walkthroughs, staff at home for months. Building Department Administration (5th Edition) observes that the pandemic forced jurisdictions to implement in weeks technologies they had been considering for years; ICC responded in May 2020 by publishing Recommended Practices for Remote Virtual Inspections (RVI). A facility loss — fire, flood, or storm damage to the municipal building — is the opposite problem: staff are available but the office, and possibly an on-premises permit server and paper records, are not. Severe weather may interrupt operations for days, and a post-disaster surge combines the worst of both: demand for repair permits and damage inspections spikes exactly when the department's capacity is most degraded.
The core discipline is standard continuity planning: identify the critical functions — intake and permit issuance, plan review, inspections, fee collection, records — and document an alternate procedure for each before the disruption, not during it. The BDA text notes that organizations with critical computer operations have long arranged alternate facilities or outside service providers so a disaster at the primary facility cannot take down essential services; the building-department equivalent is cloud-hosted permitting and electronic document management, which make records and workflow reachable from anywhere. A department whose permit history and approved plans exist only in one file room, or on one server in the basement, has a single point of failure no improvisation will overcome.
Written procedures matter as much as technology. Ad hoc remote work — every inspector improvising a different video-call method, every technician keeping records a different way — produces inconsistent enforcement and indefensible records. Before activating remote operations, the department should be able to answer in writing: which services continue through what channel, what technology and documentation standards apply, who may approve what remotely, and how disruption-period work is reconciled into the permanent record.
A river flood puts three feet of water into the ground floor of city hall, taking the permit counter, plan-review room, and paper files out of service indefinitely. Because the department moved to a cloud-hosted permitting platform two years earlier, staff working from home the next morning still see every active permit, approved plan set, and scheduled inspection. The building official activates the written continuity procedure: intake shifts to the online portal, plan review continues on electronic submittals, qualifying routine inspections move to RVI, and field staff concentrate on damage assessment and emergency repair permits. A website notice states which services are running, which are suspended, and the adjusted turnaround times. The department never stops issuing permits — and every emergency-period action lands in the same system of record as normal work.
The classic failure is planning to write the plan later: departments that first consider remote procedures during the emergency spend the crisis improvising, and improvised processes leave gaps in the record that surface years later in enforcement actions and lawsuits. A second is technology dependence without fallback — assuming the permit system, network, and power will all be available, when the disruption may be precisely their loss. A third is silent service degradation: accepting applications at normal volume while quietly falling weeks behind. The corrections: document alternate procedures in advance, host records so they survive the loss of any one facility, plan a manual fallback for the systems, and publish adjusted service levels the moment they change.
Implement digital permitting and inspections
Electronic permitting is the backbone of continuity. The BDA text describes the shift to online, vendor-hosted permitting platforms through which customers apply, pay fees, submit plans, schedule inspections, and track project status without entering the building department — and because these platforms live outside the municipal facility, they keep running when the facility does not. Even so, permitting needs its own fallback: when the software, network, or payment processor is down, a documented manual process — simple forms, logged sequential permit numbers, receipts for fees — lets critical permits issue, each reconciled into the primary system once restored. Never acceptable is the undocumented permit: work authorized verbally, with no record, is a liability the department carries for the life of the building.
Remote virtual inspection is the second pillar. As defined in ICC's Recommended Practices for RVI, an RVI is a visual inspection using visual or electronic aids — in practice, a live video call from the jobsite — that lets an inspector observe construction from a distance when circumstances prevent an in-person inspection. Two principles anchor the program: the codes do not change — the inspector checks the permitted work against the same adopted codes, no differently than if standing on the site — and the decision to allow an RVI rests at the sole discretion of the authority having jurisdiction, inspection type by inspection type and site by site.
Not every inspection suits the format. The ICC recommended practices list examples commonly qualified for RVI: water heater or water softener direct replacements, HVAC direct replacement or repair, plumbing repairs and fixture replacements, minor residential electrical work, re-roofing, rooftop photovoltaic systems, utility clearances, pool excavations, construction trailer installations, manufactured home installation verification, and residential plumbing and framing rough-ins. The common thread is work an inspector can fully evaluate through a camera: discrete, visually accessible, limited in scope. Complex, large, or judgment-intensive work — and anything the camera cannot adequately reach or resolve — stays on-site.
Process discipline makes the inspection defensible. There must be an active permit, and the permit holder or representative signs a notice acknowledging consent to the remote format, responsibility for their own safety, the AHJ's full use of the resulting video and photos, truthful presentation of the work, and the AHJ's sole discretion over the method. An adult conducts the site side of the scheduled call and stays in verbal communication with the inspector throughout. Preparation is specific: a charged device with backup power, strong Wi-Fi or cellular service, good lighting, a cleaned lens, notifications silenced, the approved plans and permit card on site, and the tools the inspection requires — flashlight, tape measure, level, ladder, receptacle tester, and an extension pole to bring the camera close to high or awkward locations.
The inspection begins with location verification: the call opens at the street view with the structure and posted address visible on camera, and the inspector may additionally verify the site by GPS or geotagging. From there the inspector — not the camera operator — directs the sequence, telling the customer where to point the device and pausing wherever needed. Every feature the inspection covers must be visible and captured clearly enough to evaluate; stills and video may be kept. Results are entered into the permit database as soon as practicable, noting the remote method, and all records — recordings, photos, correction notices — are retained under the AHJ's records policy and may be subject to public disclosure.
Finally, the exit ramp: whenever the inspector believes the remote process is not allowing a proper assessment of compliance — connectivity drops, lighting fails, the work is more extensive than described — the inspector may stop and require an on-site inspection. Where connectivity is the only obstacle, some jurisdictions allow contractor-submitted photo and video documentation for later review, at the inspector's discretion.
A contractor requests a remote inspection for a direct water heater replacement — a textbook RVI candidate. The permit is active, the signed consent notice is on file, and at the scheduled window the contractor answers the video call at the curb with the house number in frame. The inspector confirms the address, directs the walk to the utility room, and has the camera move slowly over each element of the installation, using the contractor's flashlight and tape measure where a closer look is needed. Fifteen minutes later the inspection passes, the result is entered flagged as an RVI, and the captured images go into the record — no truck roll, no delay. The same morning, another contractor asks to handle a rough framing inspection on an engineered multi-story addition by video. The inspector attempts it, but the basement has almost no signal, the lighting is poor, and the framing connections cannot be resolved on screen. The inspector stops the call and converts to an on-site visit — exactly the judgment the framework calls for.
The recurring errors: treating RVI as a customer entitlement rather than an AHJ-discretion tool; letting scheduling pressure push unsuitable inspections into the remote format; skipping consent and documentation, leaving an inspection the department cannot prove happened; never verifying the address, which invites inspecting the wrong site — or a staged one; and hesitating to convert to on-site once an RVI is clearly failing. The corrections: publish which inspection types qualify, require the signed acknowledgment before scheduling, open every call with location verification, record results and media like any inspection, and empower inspectors — in writing — to end any RVI that cannot demonstrate compliance.
Maintain communication and operations remotely
Remote plan review was proving itself before any recent disruption — the BDA text lists digital plan submittal and review among the digitization steps jurisdictions had already adopted — but running it as the only review channel demands discipline in three areas. First, submittal standards: electronic plans must meet published legibility and completeness requirements, and the test is whether the examiner can actually read every note and dimension at review scale — not whether the file cleared an upload threshold. Illegible sheets get returned, not guessed at. Second, version control: one authoritative current plan set per project, resubmittals versioned, superseded sheets marked, so no reviewer comments on — and no inspector builds from — an outdated sheet. Third, markup discipline: corrections consolidated into a letter identifying each item by sheet and detail, so designers can respond point by point and the review history remains reconstructible.
Internal communication is the part of remote operations most often left to chance. When counter conversations and hallway questions disappear, structure must replace them: a scheduled daily virtual check-in for assignments and problem cases; a shared schedule showing who is on remote inspections, in the field, or reviewing plans; and a defined escalation path so a permit technician at a kitchen table knows who resolves the question a supervisor would normally answer in passing. The same virtual platforms that carry inspection calls carry staff meetings equally well. Training belongs here too: the ICC recommended practices emphasize training both staff and customers — permit technicians on reviewing applications against RVI requirements and collecting fees remotely, inspectors on the video platforms, procedures, and recording of results — because an untrained program produces exactly the inconsistency the written procedures exist to prevent.
External communication is a matter of service-level honesty. During a disruption the department should publish, prominently and early, which services are operating and through which channel, the actual adjusted turnaround times, the hours within which remote inspections can be scheduled, and how emergency and after-hours needs are handled. Customers can plan around a slower, clearly stated service level; they cannot plan around silence or promises the department cannot keep. The recommended practices add considerations easy to overlook: adopt basic online security practices with IT, involve legal counsel on federal, state, and local compliance — including whether releases are needed — ensure remote staff have electronic access to the adopted codes, and document lessons learned so the emergency program can mature into a permanent service improvement.
Three weeks into a facility closure, a department's plan-review backlog is growing and contractors are calling individual staff cell phones for status. The building official responds with structure: the website now states review turnaround honestly — fifteen business days instead of the normal ten — along with the RVI scheduling window and the emergency-permit channel. A fifteen-minute morning video huddle assigns the day's work, a shared status board replaces the missing whiteboard, and one supervisor becomes the single escalation point. Plan reviewers stop accepting piecemeal emailed sheets and require versioned resubmittals through the portal, each answered with a consolidated, sheet-referenced correction letter. Complaint calls drop within a week — not because service got faster, but because customers know what to expect and staff give consistent answers.
Common failures: forcing examiners to review illegible or fragmentary electronic plans; letting multiple plan versions circulate until reviewer and contractor work from different sheets; scattering review comments across emails and calls that never reach the project record; assuming staff coordination will happen naturally without the office; and publishing no service-level information, leaving every customer to discover the backlog one frustrated call at a time. The corrections: enforce submittal and legibility standards, maintain one versioned authoritative plan set, consolidate corrections into sheet-referenced letters, schedule the communication that used to happen spontaneously, train staff and customers, and state real service levels publicly — updating them as they change.
Continuity for a building department is built, not improvised. The foundation: know the triggers — pandemic, facility loss, severe weather, disaster surge — identify the critical functions, and document an alternate procedure for each, with records and workflow in systems that survive the loss of any one building. The operational core: cloud-hosted permitting with a manual fallback, and remote virtual inspection run to the ICC recommended-practices discipline — suitable inspection types, signed consent, verified location, inspector-directed video, full documentation, and conversion to on-site whenever compliance cannot be clearly demonstrated. The connective tissue: remote plan review with legibility standards, version control, and markup discipline; structured internal communication and training; and honest, published service levels. A department that prepares in advance keeps issuing permits, reviewing plans, and verifying compliance through any disruption — with a record as defensible as normal work.