Case Study

Investigation closures became predictable across automated food plants

A large food processing & FMCG manufacturer replaced ad-hoc investigations, manual audit tracking, and fragmented training records with structured RCA workflows, action automation, and cross-plant dashboards.

resources-about-oqsha-feature-icon-1
Multi-plant
resources-about-oqsha-feature-icon-2
Audit-heavy compliance
resources-about-oqsha-feature-icon-3
6 min read
Factory Worker with Tablet

Client Highlights

Check Icon Modules: Incident Investigation, Audit Management, Action Tracker
Check Icon Use Case: Structured RCA + audit-to-action automation across plants
Check Icon Outcome: Better investigation closure quality + fewer repeat + faster audit closure

Executive Summary

The Problem

  • Investigations lacked structured root cause workflows
  • Training tracking was manual and fragmented
  • External audit findings were tracked manually

What Changed

  • Digital incident investigations with structured RCA
  • Digital audits with automatic action creation from audit
  • Training dashboards with manual + bulk upload capability

What Improved

  • 55% improvement in investigation closure quality scores
  • 42% reduction in repeat minor incidents
  • 60% reduction in manual audit action tracking effort

The Challenge

1
Repeat incidents: Investigations didn’t force a clean RCA path, so the same patterns resurfaced.
2
Closure uncertainty: Evidence quality varied by plant and investigator, leading to inconsistent closure.
3
Audit friction: External audit findings needed manual tracking and action creation.
4
Training proof gaps: Compliance visibility was split across HR and plants, with no single truth.

Context & Constraints

Number of Sites Multiple automated facilities
Contractor Intensity High
SOP Alignment Strict Requirement
Offline Mode Enabled for low-signal areas

What We Implemented

Deploying a standardized, integrated safety environment across all active operational sites.

cs-what-we-implemented-icon

Incident Investigations (RCA)

Configured for: Structured investigations that prevent repeat incidents.

Key Workflow Controls

  • Check Icon Guided RCA flow (Why-Why) with required fields
  • Check Icon Mandatory evidence attachments for closure
  • Check Icon Root cause + corrective/preventive action linking

Audit Proof Captured

  • Audit Proof Icon Full investigation timeline + ownership
  • Audit Proof Icon Evidence stored inside the record
cs-what-we-implemented-icon

Audits + Training Compliance

Configured for: Audit findings → actions → closure, plus training visibility across plants.

Key Workflow Controls

  • Check Icon Digital audits with automatic action creation from findings
  • Check Icon Action ownership + due dates + escalation (overdue control)
  • Check Icon Training compliance dashboards (manual + bulk upload)

Audit Proof Captured

  • Audit Proof Icon Audit-to-action trail with timestamps
  • Audit Proof Icon Closure evidence linked to the original finding

Workflow at a Glance

1

Trigger

Incident is logged and routed into a structured investigation workflow.

2

Review

EHS assigns investigators and validates severity and required evidence.

3

Execution

Investigation runs through RCA (Why-Why), with evidence required at each stage.

4

Closure

CAPA is assigned, tracked, and validated before the case can close.

5

Visibility

CAPA is assigned, tracked, and validated before the case can close.

Field capture view UI

RCA investigation view with mandatory evidence gates

Corporate dashboard view UI

Corporate view: repeat themes + audit actions + training compliance

Measured Outcomes

Measured Outcomes Icon

Better investigations

55% improvement in investigation closure quality scores

What Enabled It Structured RCA + mandatory evidence closure
Measured Outcomes Icon

Fewer repeats

42% reduction in repeat minor incidents

What Enabled It RCA quality + linked CAPA discipline
Measured Outcomes Icon

Less audit admin

60% reduction in manual audit action tracking effort

What Enabled It Auto action creation + central tracking
Measured Outcomes Icon

Faster closure

47% faster audit action closure turnaround time

What Enabled It Ownership + deadlines + escalations
Measured Outcomes Features Icon Role-Based Access Control
Measured Outcomes Features Icon Immutable Audit Trail
Measured Outcomes Features Icon PDF/Excel Exports Available
Measured Outcomes Features Icon Offline Field Capture

Ready to standardise investigations and audits?

Download the one-pager summary, or request a security brief for your IT review.

Explore similar stories

Construction Worker

Unsafe condition reporting increased, and corrective actions stopped going overdue.

Read full story Link Arrow Blue Icon
Construction Worker

Near-miss reporting increased and audit closure improved across plants.

Read full story Link Arrow Blue Icon
Automotive Components Factory

Near-miss reporting grew and repeat equipment-related incidents reduced.

Read full story Link Arrow Blue Icon

Request a tailored demo

Tell us your workflows. We’ll show your time saved.

OQSHA Demo

See OQSHA on your data, not just ours

In a 30–45 minute session, we’ll map your current safety workflows inside OQSHA and help you estimate the payoff.

  • Map one workflow live (permits / incidents / inspections)
  • Get a quick ROI estimate
  • Take a security brief back to IT

We keep your data private and only use it to schedule your demo.

Before you ask IT or procurement…

Most teams ask these questions before rolling out OQSHA.

Typically 2–6 weeks, depending on sites, workflows, and data migration. Most teams start with a pilot, then scale site-by-site.
No special hardware. Use phones or tablets for field users and a laptop or desktop with a browser for admins. Optional: QR stickers for assets.
Core workflows need internet for real-time approvals, alerts, and audit trail. Offline support can be discussed based on site constraints.
Stored securely in the cloud with encryption in transit and at rest, plus role-based access controls. Deployment options can be shared on request.
© OQSHA. All rights reserved.