You are here:
For regulatory inspections, Data Capture forms check work against regulatory codes, capture a compliance status for each question, and generate Regulatory Code Violation records automatically when a response is noncompliant.
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions |
| Available in orgs where Field Service and Discovery Framework are enabled. |
Inspection teams run field inspections for regulatory programs, such as licensing and permits. An inspection checklist is a Data Capture form that an inspector completes in the Field Service mobile app. This topic explains how those forms connect to regulatory codes and generate violation records.
A regulatory code is the standard that an inspection checks against, such as a building or health code. You create each code as a record with a name, subject, type, effective dates, and regulatory authority. See Create Regulatory Code Records. When you build the form, associate a question with the regulatory code it evaluates, so the inspector sees the standard while answering. On the form, the question shows the count of associated regulatory codes—for example, a 3 regulatory codes label—and, for each code, its Name, Subject, effective dates, Type, and Description. Inspectors select the applicable codes from the dropdown. Because inspectors often work offline, prime the regulatory codes for offline use before a visit. See Considerations for Data Capture.
The Assessment Question Status picklist on the Inspection Assessment Indicator object captures compliance status. Define the statuses your inspections use, such as Compliant, Not Compliant, and Not Applicable, and mark the statuses that represent a failure as violating. When an inspector completes the form, they set the compliance status for each question. See Set Up Regulatory Compliance and Automated Violations.
When an inspector submits the form, each question whose response has a violating compliance status generates a Regulatory Code Violation record for the associated regulatory code. Automating these records removes manual data entry in the field and keeps the enforcement trail consistent.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.