The Incident Management dashboard helps you see the full picture of what your organization is reporting — across all incident types — and then drill into the three operational subsets that have their own data needs: Environmental, Property Damage, and Motor Vehicle Accidents. Use it to monitor reporting health, spot facilities or departments with concentrated incident activity, and follow up on cases that still need linked corrective actions.
This dashboard is designed for Regional and Site leaders, EHS managers, and safety, environmental, and risk professionals who need a portfolio-level view of all incident types and the ability to investigate specific subsets in detail.
Note: For deeper analysis of injury and illness incidents specifically — including OSHA rates, severity, and OSHA 300A reporting — see the Injury and Illness Incident Summary dashboard. Injuries appear here in the Overview only.
The dashboard pulls from incident records in Dakota Scout. Records without a site-level parent folder are excluded from every visualization.
A few terms used throughout this article:
Incident Type. The category assigned to an incident record — for example, Environmental, Injury/Illness, MVA, Near Miss, Property Damage, or Security.
Near Miss. A reported event where something could have gone wrong but did not. Near Miss records are included in totals on the Overview page but excluded from the # Incident Reports Excluding Near Misses KPI.
Potential SIF. Potential for Significant Injury or Fatality — a user-assigned classification flag that captures latent severity regardless of the actual outcome. A low-severity event or near miss can still have high SIF potential.
Linked Actions. Corrective or preventive actions associated with an incident in Tracer. An incident without linked actions has no documented follow-up.
Reportable Release. An Environmental incident whose released quantity exceeded a reportable threshold requiring notification to a regulatory agency.
Offsite. A flag indicating an incident occurred beyond the facility boundary (e.g., on public roads, customer sites, or other third-party property).
For information on how data is synchronized from ProActivity into Insights, see Getting Started with Dakota Insights.
The Incident Management dashboard supports filter slicers on every page. The available slicers differ slightly between pages:
All pages: Date Range, Region, Business Unit, Facility Name
Overview (page 1) only: Incident Type
Environmental, Property Damage, and MVA pages (pages 2–4): Employee Department
The Date Range slicer defaults to the past 12 months on every page.
For general guidance on using filters, see Filtering Dashboards in Dakota Insights.
The Overview page gives you the cross-type view: how many incidents have been reported, the mix by type and status, what is trending month over month, where activity concentrates by department and facility, and how well incidents are being followed up.
# All Incident Reports. Total count of incident records of all types in the selected period and scope. A top-level volume metric that captures the full reporting activity. A rising count is generally a positive signal that the reporting culture is strong — for that reason this tile uses a neutral color and no "good/bad" trend.
# Incident Reports Excluding Near Misses. Total count of incidents excluding Near Miss records. Isolates events that actually happened from events that were narrowly avoided. Useful when explaining reporting volume to audiences who conflate near misses with incidents.
Incidents by Type (pie). Share of incidents by Incident Type. Shows the composition of the organization's incident portfolio, which drives where safety, environmental, and security resources should be focused. Also surfaces the share of Near Misses — a leading indicator of reporting health.
Incidents by Status (pie). Share of incidents in each workflow status: New, Open, Closed. A large New or Open share may indicate that investigations are stalled.
Incidents by Type per Month. A vertical stacked column chart of incident counts per month, stacked by Incident Type. Surfaces both overall volume trends and shifts in incident composition — a growing Near Miss stack with flat overall counts suggests improving reporting culture, while a growing Injury/Illness stack warrants direct attention.
Involved Employee Department (Top 20). A horizontal bar chart, Pareto sorted, of incident counts grouped by the Department of the involved employee, limited to the top 20. Focuses organizational attention on the departments where activity is concentrated — complements Facility-level views with a functional lens.
Note: Department is a user-maintained field. Inconsistent naming across facilities (e.g. Shipping vs. Shipping Dept) will fragment this chart; standardize Department names in Scout to keep it meaningful.
Incidents by Potential for Significant Injury or Fatality (SIF) and Incident Type. A horizontal stacked bar chart of incident counts per Incident Type, with each bar segmented by Potential SIF flag (Yes, No, blank). Near misses and low-severity events can still have high SIF potential; this chart surfaces those latent risks by type. A large blank segment represents a data-quality gap — incidents where the SIF flag was never set.
Incident Type by Facility. A horizontal stacked bar chart of incident counts per Facility, stacked by Incident Type. Combines facility-level volume with type mix in a single view — makes it easy to spot facilities with unusual distributions, such as disproportionate Near Misses or a type that never appears.
Four KPI tiles measure how disciplined the organization is at attaching corrective actions to its incidents.
Incidents with Linked Actions. Count of incidents in the selected period that have at least one linked corrective or preventive action.
% Incidents with Linked Actions. Linked-action incidents divided by total incidents. Normalizes the count for fair comparison across periods and facilities.
% Potential SIF Incidents. Potential-SIF incidents divided by total incidents. Highlights latent severity regardless of outcome — a high share even with low serious-injury rates means high-risk near misses deserve investigation.
% Potential SIF Incidents with Linked Actions. Potential-SIF incidents with at least one linked action, divided by total Potential-SIF incidents. The critical accountability metric: SIF incidents without linked actions are the most serious kind of unresolved risk. A low value here should prompt immediate review.
Page 2 focuses on Environmental incidents — spills, releases, and other environmental events — with the detail needed for reportability assessment and regulatory follow-up.
# Environmental Incidents. Count of incidents classified as Environmental in the selected period.
# Reportable Releases. Count of Environmental incidents that exceeded a reportable threshold requiring notification to a regulatory agency. Reportable releases trigger regulatory timelines, fines, and reputational risk; isolating them keeps the subset with external obligations visible.
# Offsite Releases. Count of Environmental incidents that released material beyond the facility boundary. Offsite releases amplify community, regulatory, and liability risk compared to onsite-contained releases.
Environmental Incidents per Month by Status. A vertical stacked column chart of Environmental incident counts per month, stacked by Status. Combines volume trend with case-management health — a growing New or Open backlog indicates the response process is not keeping up with incident volume.
Environmental Incidents by Facility. A horizontal bar chart of Environmental incident counts per Facility, sorted descending. Isolates the facility dimension for environmental risk; useful for prioritizing environmental-management investments and audits.
Material Spilled. A donut chart showing the share of Environmental incidents by Material Spilled category. Helps target spill-prevention, containment, and cleanup investments at the specific materials involved; a concentrated material profile may justify specialized response equipment.
Environmental Incidents by Location. A donut chart showing Environmental incident share by Location (e.g. Loading Dock, [blank]). Location is more specific than Facility, supporting physical-control improvements like drainage, containment, and bollards. A large [blank] slice represents a data-quality gap.
Environmental Incidents by Department. A horizontal bar chart of Environmental incident counts grouped by involved employee Department, sorted descending. Functional view complements the Facility and Location dimensions; useful for targeting department-level training and procedures.
Environmental Incident Data (table). A detail row per Environmental incident with columns for Facility, Incident ID, Status, Event Date, Material Spilled, Amount (lbs), Over Reportable Threshold, Spilled To, Recovery Method, Release Duration (min), and Observation Method. Supports investigation, regulatory reporting, and audit trails without leaving the dashboard. Paginated when many rows are present.
Note: For customers with few Environmental incidents, the monthly trend chart will look sparse — that is expected and not a data error.
Page 3 focuses on Property Damage incidents — events that affected company or third-party property — with the detail needed for insurance, liability, and asset-availability follow-up.
# Prop. Damage Incidents. Count of incidents classified as Property Damage in the selected period.
# Offsite Incidents. Count of Property Damage incidents occurring outside the facility boundary — e.g. damage to third-party property or off-premises company assets. Offsite incidents often involve third-party liability exposure; a separate count helps insurance and legal teams isolate the relevant cases.
Property Damage Incidents per Month by Status. A vertical stacked column chart of Property Damage incident counts per month, stacked by Status. Combines volume trend with case-management health for the property-damage subset.
Property Damage Incident by Facility. A horizontal bar chart of Property Damage incident counts per Facility, sorted descending. May point to aging infrastructure, traffic-flow issues, or maintenance gaps at facilities with concentrated activity.
Property Damage Incidents by Department. A donut chart showing Property Damage incident share by involved employee Department. A [blank] slice indicates Department was not recorded.
Property Damage Incident Data (table). A detail row per Property Damage incident with columns for Facility, Incident ID, Status, Event Date, Department, Location, Property Category, and Total Cost. The Total Cost column keeps financial impact visible alongside the case details. Paginated when many rows are present.
Note: For customers with few Property Damage incidents, the monthly trend chart will look sparse — that is expected and not a data error.
Page 4 focuses on Motor Vehicle Accidents — incidents involving company vehicles or company drivers — with the detail needed for DOT and insurance follow-up.
# MVAs. Count of incidents classified as Motor Vehicle Accident in the selected period.
# Offsite MVAs. Count of MVA incidents occurring outside the facility boundary — public roads, customer sites, and so on. Most MVAs occur offsite; separating onsite (lot or yard) from offsite (public road) supports different prevention strategies — lot design versus driver training and route planning.
MVAs per Month by Status. A vertical stacked column chart of MVA incident counts per month, stacked by Status. Combines volume trend with case-management health for the MVA subset.
MVAs by Facility. A horizontal bar chart of MVA incident counts per Facility, sorted descending. Associates MVAs with the facility that owns the vehicle or employs the driver, even when the accident occurs offsite — useful for fleet-risk analysis.
MVAs by Department. A donut chart showing MVA incident share by involved employee Department. A [blank] slice indicates Department was not recorded.
MVA Data (table). A detail row per MVA with columns for Facility, Incident ID, Status, Event Date, Injuries, Injuries - Other, DOT Recordable, Location, and Damage Estimate. The Injuries and DOT Recordable flags sit alongside Damage Estimate so safety and financial impact stay visible together. Paginated when many rows are present.
Note: For customers with few MVA incidents, the monthly trend chart will look sparse — that is expected and not a data error.
The data in this dashboard refreshes every four hours. For details on synchronization timing and what's included from each ProActivity product, see Getting Started with Dakota Insights.