3.1 Inspection Types, Action Plan Templates & Onsite Visit Execution

3.1 Inspection Types, Action Plan Templates & Onsite Visit Execution

Regulatory inspections represent the operational enforcement front line of government agencies. Whether auditing commercial restaurants for food safety, evaluating active construction framing for structural integrity, or verifying fire sprinkler compliance in assembly occupancies, public sector organizations require standardized, repeatable, and legally defensible processes. Public Sector Solutions (PSS) delivers this capability through a cohesive data architecture centered on InspectionType, ActionPlanTemplate, ActionPlan, Visit, and Visitor.

Understanding how these objects interact—and how field inspectors interact with them in high-pressure, low-connectivity physical environments—is a core topic on the Accredited Professional AP-222 exam.

---

Standardizing Inspections with the Inspection Type Object

The InspectionType object serves as the foundational catalog and configuration definition for any category of inspection performed by a jurisdiction. Rather than treating each inspection as an ad-hoc calendar event, InspectionType codifies the operational rules, expected timeframes, and required checklist templates for specific regulatory disciplines.

Key Attributes and Operational Behaviors

When configuring an InspectionType in Public Sector Solutions, administrators specify several critical parameters:

• Name and Code: Identifies the inspection category (e.g., Commercial Kitchen Initial Inspection, Annual Life Safety Audit, Residential Rough Plumbing Inspection, Complaint-Driven Code Enforcement).
• Standard Duration (Minutes): Defines the estimated time required to complete the inspection. This duration is leveraged by scheduling engines and dispatch dispatchers to block inspector calendar capacity accurately.
• Recommended Frequency: Defines how often an asset, physical establishment, or licensed business must undergo this inspection (e.g., Annually, Semi-Annually, or Triennially for recurring license renewals).
• Default Action Plan Template Association: Identifies which active ActionPlanTemplate should automatically attach when a visit of this type is provisioned.
• Discipline / Department: Associates the inspection type with the governing regulatory department (e.g., Department of Building Inspection, Environmental Health Services, Fire Prevention Bureau).

Triggering Mechanisms: Application-Driven, Cyclical, and Ad-Hoc

In Public Sector Solutions, inspection visits originate through three primary administrative channels:

1. Application-Driven Inspections: Initiated during the processing of a BusinessLicenseApplication or permit application. For example, before an agency issues a food establishment permit, an initial onsite sanitation inspection must be successfully completed.
2. Periodic / Cyclical Compliance: Automatically triggered for active BusinessLicense records on a recurring basis (e.g., an annual hotel safety audit) using scheduled Salesforce Flows.
3. Complaint-Driven (Ad-Hoc) Inspections: Generated in response to a 311 citizen report or code compliance Case (e.g., illegal dumping, unpermitted structural work, or noise violations).

---

Action Plan Templates and Action Plans: The Compliance Engine

While InspectionType categorizes the visit, the ActionPlanTemplate and its runtime counterpart, ActionPlan, drive the actual execution of the inspection checklist.

Anatomy of an Action Plan Template

An ActionPlanTemplate represents the master checklist definition. When configuring an ActionPlanTemplate for inspections, the Target Object must be set to Visit.

Within each template, administrators configure reusable items:

• Assessment Indicator Definitions (AIDs): The individual compliance metrics, pass/fail questions, or quantitative tests to be evaluated.
• Document Checklist Items: Mandatory physical documents that the inspector must inspect or collect onsite (e.g., Certificate of Occupancy, Pest Management Service Logs).
• Tasks: Operational steps required of the inspector (e.g., "Verify Knox Box emergency key functionality," "Inspect perimeter security fencing").

Template Lifecycle and Versioning Immutability

A critical architectural concept tested on the AP-222 exam is the lifecycle and versioning of ActionPlanTemplate:

[!IMPORTANT] Exam Watchout — Template Immutability: Once an ActionPlanTemplate is activated, it is permanently locked. To modify checklist items or incorporate newly enacted code requirements, administrators must clone the template to generate a new version (e.g., Version 2). Existing in-flight ActionPlan records generated from Version 1 will continue running on Version 1 without interruption, preserving legal integrity and preventing mid-inspection schema shifts.

Runtime Action Plan Instantiation

When an inspector or automated Flow creates an inspection Visit, an ActionPlan is instantiated from the active ActionPlanTemplate. The ActionPlan creates concrete child tasks and assessment indicators directly linked to the target Visit. If a template specifies ten assessment indicators, the resulting ActionPlan provisions those ten indicators ready for field evaluation.

---

Scheduling and Dispatching: Visit and Visitor Architecture

The Visit and Visitor objects model the physical reality of public sector field operations.

The Visit Record

The Visit record represents the single inspection event. Its essential relationships include:

• Place / Location (PlaceId): The physical building, parcel, or geographical point where the inspection takes place.
• Context Record (ContextId): A polymorphic lookup linking the visit to its originating business context, such as a BusinessLicenseApplication, an active BusinessLicense, a building permit, or an enforcement Case.
• Status Progression: Standard lifecycle stages: Planned -> In Progress -> Completed (or Canceled / Rescheduled).
• Timestamps: Tracks scheduled windows (PlannedStartTime, PlannedEndTime) against audited reality (ActualStartTime, ActualEndTime).

The Visitor Object: Multi-Disciplinary Joint Inspections

A common pitfall on the AP-222 exam is assuming that assigning an inspector to a visit is done simply through the Visit.OwnerId field. While Visit.OwnerId assigns record ownership, real-world public sector operations require joint, multi-disciplinary inspections.

The Visitor junction object links multiple User records (Inspectors) to a single Visit:

• Joint Agency Operations: For complex venues (e.g., a newly constructed nightclub or industrial chemical facility), building codes require simultaneous inspection by a Building Structural Inspector, a Fire Marshal, and a Public Health Officer.
• Role Designation: Visitor records can designate a "Lead Inspector" alongside "Secondary Inspectors" or "Subject Matter Experts."
• Attendance & Audit: Captures individual arrival and sign-offs for administrative hearing defensibility.

---

Mobile Field Execution & Offline Resilience

Field inspectors rarely perform their duties sitting at a desktop terminal. Public Sector Solutions optimizes inspection execution for mobile devices via the Salesforce Mobile App.

Field Inspector Mobile Workflow

1. Daily Roster Review: The inspector opens the Salesforce Mobile App to review their assigned Visit itinerary, optimized by appointment window and geographical location.
2. Onsite Check-In: Upon arrival at the physical establishment, the inspector taps Check In. PSS captures mobile GPS coordinates and stamps ActualStartTime.
3. Checklist Execution: The inspector opens the attached ActionPlan and evaluates each Assessment Indicator.
4. Rich Evidence Capture: For each checkpoint, the inspector logs compliance status, inputs quantitative readings, records notes, and captures real-time camera photos. Photos are instantly linked via ContentDocumentLink to the inspection result record.
5. Constituent Signature & Check-Out: The inspector reviews the findings with the business owner or site superintendent, captures a digital signature on the mobile screen, taps Complete, and the system stamps ActualEndTime.

Offline Execution with Briefcase Builder

A primary technical challenge in field inspections is inconsistent or nonexistent cellular connectivity. Inspectors frequently enter reinforced concrete basements, subterranean parking structures, elevator shafts, or remote rural facilities.

Public Sector Solutions addresses this using Briefcase Builder:

• Data Priming Rules: Briefcase Builder rules are configured to pre-cache relevant records onto the inspector's mobile device prior to departing for the field.
• Cached Objects: The briefcase rule primes assigned Visit records, related Visitor entries, parent Place and Account records, child ActionPlan instances, and all associated AssessmentIndicatorDefinition items.
• Seamless Local Write: When offline, the inspector completes checklists, inputs numerical measurements, and captures camera photos locally into the encrypted SQLite device cache.
• Background Synchronization: Upon regaining cellular or Wi-Fi connectivity, the Salesforce Mobile App automatically pushes queued transactions to the cloud. If conflicts arise, standard last-write-wins or administrative sync rules resolve data state.

---

Comparison: Key Inspection Objects

[!TIP] Scenario Strategy: When an exam question describes a requirement for multiple inspectors from different departments to inspect a facility at the same time and record their individual findings under a unified inspection event, always select the Visitor junction object rather than creating duplicate Visit records or sharing ownership via Public Groups.