3.3 Regulatory Code Violations, Enforcement Actions & Remediation Workflows

3.3 Regulatory Code Violations, Enforcement Actions & Remediation Workflows

When an inspection reveals that a business, property owner, or contractor has failed to satisfy regulatory standards, public sector agencies must initiate code enforcement. However, government enforcement is not merely punitive; it is governed by legal due process and structured to encourage voluntary compliance. Agencies provide constituents with formal notices, defined cure periods, and clear pathways to submit proof of remediation before escalating to civil fines, stop-work orders, or license revocations.

Public Sector Solutions orchestrates this complex compliance journey through the RegulatoryCodeViolation and ViolationEnforcementAction objects, powered by automated Salesforce Flows and Experience Cloud self-service portals. Mastering these mechanics is essential for achieving the AP-222 certification.

---

Recording Non-Compliance: The Regulatory Code Violation Object

The RegulatoryCodeViolation (RCV) object records each specific breach of law or regulation observed during an inspection visit or reported through code enforcement intake.

Core Fields and Relationships

• InspectionId: A lookup to the Visit during which the infraction was discovered.
• RegulatoryCodeId: A lookup to the specific RegulatoryCode that was violated.
• AssessmentIndDefinitionId: A lookup to the failed checklist question or metric.
• Severity: Categorizes the threat level: Minor, Major, Critical, or Immediate Life Safety Hazard.
• Status: Tracks the lifecycle of the violation: Open, In Remediation, Remediation Submitted, Cured / Resolved, Escalated, Appealed, Closed.
• DateObserved: The date and time when the violation was verified.
• ComplianceDueDate (Cure Deadline): The statutory date by which the constituent must remediate the non-compliant condition.
• CorrectiveActionSummary: Inspector instructions detailing the exact physical or operational changes required to achieve compliance.

Automated Generation vs. Ad-Hoc Violations

Violations are introduced into PSS via two standard operational pathways:

1. Automated Inspection Generation: When an inspector evaluates an Action Plan checklist on their mobile app and flags an Assessment Indicator as Non-Compliant, PSS automates the creation of a RegulatoryCodeViolation record, automatically populating the code citation and severity from the template.
2. Ad-Hoc / Discretionary Violations: If an inspector conducting a routine plumbing visit spots exposed high-voltage wiring, they can manually log an ad-hoc RegulatoryCodeViolation against the Electrical Safety Code, even though electrical checks were not part of the scheduled plumbing Action Plan.

---

Progressive Discipline & The Violation Enforcement Action Object

Administrative law requires agencies to practice progressive enforcement—applying graduated corrective measures commensurate with the severity of the infraction and the violator's history of non-compliance.

While RegulatoryCodeViolation records what law was broken, the ViolationEnforcementAction (VEA) object records what legal remedy or penalty the agency is imposing.

Progressive Enforcement Hierarchy in Public Sector Solutions

Structure of the Violation Enforcement Action Record

A ViolationEnforcementAction record connects to the RegulatoryCodeViolation (or rolls up to the parent BusinessLicense / Account) and tracks:

• ActionType: Picklist defining the remedy (NOV, Fine, Stop-Work, Suspension, Revocation Notice).
• PenaltyAmount: Currency field capturing assessed monetary penalties.
• IssuedDate & EffectiveDate: Stamping official legal notice delivery and enforcement commencement.
• PaymentStatus: Tracks penalty collection (Unpaid, Paid, Waived, Collections).
• AppealDeadline: The statutory date by which the constituent must file an administrative appeal before the order becomes legally final.

---

Automating the Enforcement Pipeline with Salesforce Flow

Public Sector Solutions leverages record-triggered Salesforce Flows to orchestrate the compliance pipeline, eliminating human delay and ensuring procedural fairness.

Architecture of an Enforcement Flow

When a RegulatoryCodeViolation record is created, a Record-Triggered Flow executes:

[RegulatoryCodeViolation Created]
              |
              v
      <Check Severity Tier>
         /           \
        /             \
   [Critical]      [Minor / Major]
      /                 \
     v                   v
1. Generate Stop-Work   1. Calculate ComplianceDueDate
   Enforcement Action      (e.g., Today + 30 Days)
2. Update License to    2. Create Notice of Violation (NOV)
   'Suspended'          3. Issue Formal NOV Document to Portal
3. Trigger Urgent SMS   4. Schedule Follow-Up Reinspection
   to Constituent          Visit (DueDate + 2 Days)

Automated Calculations and Scheduling

• Dynamic Due Date Calculation: The Flow uses business day formulas based on violation severity. Minor zoning infractions receive a 30-calendar-day cure period; critical refrigeration failures receive 24 to 48 hours.
• Document Generation: The Flow calls OmniStudio Document Generation to merge violation details, photos, and statutory citations into an official PDF Notice of Violation.
• Reinspection Provisioning: The Flow creates a future Visit record of type Reinspection, linked to the same Place and ContextId, scheduled for two business days following the ComplianceDueDate.

---

Constituent Cure Periods & Digital Remediation Workflows

A modern public sector agency provides transparent, digital self-service tools for constituents to correct violations without requiring unnecessary administrative overhead.

The Experience Cloud Remediation Journey

1. Digital Notice Delivery: The business owner receives an immediate email alert and logs into the agency's Experience Cloud Portal.
2. Violation Transparency: On their Business License portal page, a dedicated FlexCard displays active violations, showing the violated code, inspector photos, inspector corrective instructions, and an active countdown to the cure deadline.
3. Remediation Submission OmniScript: The constituent clicks Submit Proof of Remediation. A guided OmniScript prompts them to:
   • Describe the corrective actions taken.
   • Upload repair receipts, contractor invoices, or certified test reports.
   • Upload new photos demonstrating that the physical condition has been resolved.
4. Status Transition: Submitting the form updates RegulatoryCodeViolation.Status to Remediation Submitted and posts a task to the assigned compliance officer's queue.

---

Verification, Reinspections & Business License Standing

Closing a violation requires formal verification by the regulatory authority. PSS supports two verification pathways:

Verification Pathways

• Desk Review Verification: For minor documentation infractions (e.g., missing fire evacuation signage), an office caseworker reviews the constituent's uploaded photos and receipts in the Service Console and marks the violation as Closed - Resolved without dispatching a field inspector.
• Onsite Reinspection Visit: For physical, structural, or life-safety violations, the assigned inspector conducts the automated follow-up Visit. The inspector re-evaluates the failed assessment indicator. If verified compliant, the inspector marks the item passed.

Governing Business License Standing

A core topic on the AP-222 exam is how violation statuses govern the operational standing of the parent BusinessLicense:

• Conditional Standing: When an active business incurs a non-critical RegulatoryCodeViolation, an automated Flow updates BusinessLicense.Status from Active to Conditional. The business may continue operating, but permit renewals and expansion requests are frozen.
• Suspended Standing: When a critical violation occurs or an NOV cure deadline expires without remediation, Flow updates BusinessLicense.Status to Suspended and halts legal operation.
• Automated Reinstatement: When an inspector or caseworker marks a violation Closed - Resolved, a Flow evaluates all sibling RegulatoryCodeViolation records linked to that BusinessLicense:
  • If any blocking violations remain open, the license remains Conditional or Suspended.
  • If zero open violations remain, the Flow automatically updates BusinessLicense.Status back to Active (Good Standing) and stamps ReinstatementDate.

[!IMPORTANT] Rollup Governance Rule: A BusinessLicense must never be automatically returned to Active status based on the resolution of a single violation if other open, unresolved violations remain on the license record. Flow logic must perform a comprehensive query across all child RegulatoryCodeViolation records before updating license standing.