Answer
The problem: Frontline workers often avoid reporting incidents due to complex, time-consuming manual processes. This leads to underreporting and delayed response times.
The solution: Frontline Operations (ANVL) workflows make incident reporting simple and mobile-friendly while ensuring all data flows directly into your Incident Management system.
Key benefits:
Faster reporting: Workers complete intuitive mobile workflows in minutes
Better data quality: Structured questions ensure consistent, complete information
Immediate visibility: EHS teams receive incident notifications instantly
Reduced administrative burden: Eliminates manual data re-entry between
Use the Frontline Operations (ANVL)-Incident Management integration to let frontline users submit Initial Incident Reports in Frontline Operations (ANVL Workflows) and automatically create the related incident in Benchmark Gensuite Incident Management.
This integration only works when the workflow is configured correctly. Successful setup depends on:
the correct workflow structure
required im_field question tags
exact dropdown value matching
correct site / Group mapping
validation testing before go-live
Important: Initial configuration should be completed with your Benchmark Gensuite team. Changes to required fields, tags, dropdown values, or mapping can break the integration.
Steps
Understand what the integration does
A frontline user completes an Initial Incident Report workflow in ANVL Workflows.
The integration creates the corresponding incident in Benchmark Gensuite Incident Management.
The incident is routed based on the mapped site / Group.
Both systems remain linked for traceability.
Example
ANVL Workflow
General Details
Event Type Specific Details
Incident Management Form
Confirm the workflow is in scope
Use this integration for the supported incident types:
Injury
Property Damage
Vehicle Accident
Spill / Release
Near Miss
Confirm the workflow includes the required fields for the incident types you plan to support.
Do not use this setup for custom incident types unless your Benchmark Gensuite team has specifically designed for that use case.
In Scope | Out of Scope |
|
|
Build the workflow with the required fields and tags
Include all required incident questions in the workflow.
Add the required im_field question tag to each mapped question.
Use the correct question type for each field.
Keep the workflow simple and mobile-friendly for frontline users.
Configuration Guidelines
Initial Setup
Your Benchmark Gensuite team will configure the integration with the correct settings. Do not attempt initial configuration without Benchmark support.
PII Data Considerations
Important: We strongly recommend capturing Personally Identifiable Information (PII) directly in Incident Management, not in ANVL workflows.
Specific PII examples by incident type:
Important: We strongly recommend you DO NOT capture this information in ANVL.
Incident Type | PII Examples |
General |
|
Injury Incidents |
|
Property Damage |
|
Vehicle Accidents |
|
Spill/Release |
|
Near Miss |
|
Required Questions Configuration
Critical: ALL required fields MUST be included in your workflow. Missing required fields will cause integration failures.
Category | Question Title | Example Question Text | Required im_field Tag | Question Type | Notes |
General Details | Event Type | "What type of incident occurred?" |
| Checklist Radio |
|
General Details | Description | "Please describe what happened?" |
| Open Text |
|
General Details | Event Date | "When did this occur?" |
| Open Text | Format: dd-mmm-yyyy |
General Details | Shift | "What shift did this occur during?" |
| Checklist Radio | Must match IM dropdown |
General Details | Department | "What department did this occur in?" |
| Checklist Radio | Must match IM dropdown |
Injury | Body Part (Injury) | "What part of the body was affected?" |
| Open Text | Must match IM dropdown |
Injury | Event Attachments | "Please upload photos of the injury" |
| List with Photo Upload |
|
Property Damage | Event Attachments | "Please upload photos of the damaged property" |
| List with Photo Upload |
|
Vehicle Accident | Vehicle Make | "Please provide the MAKE of the COMPANY VEHICLE" |
| Open Text |
|
Vehicle Accident | Vehicle Model | "Please provide the MODEL of the COMPANY VEHICLE" |
| Open Text |
|
Vehicle Accident | License Plate | "Please provide the LICENSE PLATE NUMBER" |
| Open Text |
|
Vehicle Accident | Vehicle Photo | "Please provide photos of the accident" |
| List with Photo Upload |
|
Vehicle Accident | Weather | "What was the weather like at the time?" |
| Checklist Radio | Must match IM dropdown |
Vehicle Accident | Road Conditions | "What were the road conditions?" |
| Checklist Radio | Must match IM dropdown |
Spill/Release | Chemical Name | "What was spilled or released?" |
| Open Text |
|
Spill/Release | Spill/Release to | "Where was this spilled?" |
| Checklist | Must match IM dropdown |
Spill/Release | Event Attachments | "Please upload photos of the incident" |
| List with Photo Upload |
|
Near Miss | Event Attachments | "Please upload photos of the near miss" |
| List with Photo Upload |
|
Configure exact dropdown matches
Use Checklist Radio question types for fields that must map to Benchmark Gensuite dropdowns.
Make sure the workflow answer choices exactly match the values used in Incident Management.
Validate all spelling, capitalization, punctuation, and option values before go-live.
Dropdown Matching Requirements
Critical: These fields must use Checklist Radio question types and values must exactly match your Benchmark Gensuite dropdowns:
Shift
Department
Principle I
Weather Conditions
Road Conditions
Spill Location
Work with your Benchmark team to obtain the exact dropdown values before configuring these questions.
Validate site mapping
Confirm the Group / site in ANVL maps correctly to the destination site in Incident Management.
Test submissions from the intended sites.
Confirm incidents are created in the correct destination site.
Test before go-live
Submit sample workflows for each supported incident type.
Confirm the incident is created successfully in Incident Management.
Verify the mapped fields, site routing, and attachments.
Confirm notifications and follow-up processes are working as expected.
Configuration Validation Checklist
Before going live, verify:
Question text is written for your frontline workers
All required
im_fieldtags are present and correctly formattedDropdown values exactly match Benchmark Gensuite options
Photo upload requirements are clear to users
Workflow has been tested with sample submissions
Integration creates incidents correctly in Benchmark Gensuite
Site mapping works correctly
Notification settings are configured appropriately
Best Practices
Workflow design:
Keep questions simple and clear
Use conditional logic to show only relevant questions
Include helpful instructions for photo uploads
Test workflows with actual frontline workers
Photo requirements:
Specify what should be captured in photos
Include safety reminders (don't photograph PII)
Use "List with Photo Upload" question type to require photos
Maintenance:
Review and update dropdown values regularly
Monitor completion rates and user feedback
Coordinate changes with your Benchmark team
Making Changes
Important: If you need to modify your workflow configuration:
Consult your Benchmark team first - Changes to required fields or tags can break the integration
Maintain required im_field tags - These are essential for data mapping
Test thoroughly - Always test changes in a development environment first
Update dropdown values - Coordinate any dropdown changes with Benchmark team
Remember: Your Benchmark Gensuite team configured this integration with specific requirements. Unauthorized changes may cause integration failures or data loss.
Need help? Contact your Benchmark Gensuite team for configuration support and technical assistance.