CASE STUDY / FOOD PROCESSING & FMCG

Investigation closures became predictableacross 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.

Download PDF case study

Client highlights

  • 01
    Modules

    Incident Investigation, Audit Management, Action Tracker

  • 02
    Use case

    Structured RCA and audit-to-action automation across plants

  • 03
    Outcome

    Better investigation closure quality, fewer repeats, faster audit closure

Quality and safety lead reviewing an investigation on an automated food line
Audit action closure47% faster
Repeat minor incidents−42%
6 min read
Multi-plantAudit-heavy compliance

Measured outcomes

The shift from ad-hoc investigations to structured root-cause work with predictable closure.

55%

Better investigations

Improvement in investigation closure quality scores.

What enabled itStructured RCA and mandatory evidence closure

42%

Fewer repeats

Reduction in repeat minor incidents.

What enabled itRCA quality and linked CAPA discipline

60%

Less audit admin

Reduction in manual audit action tracking effort.

What enabled itAuto action creation and central tracking

47%

Faster closure

Faster audit action closure turnaround time.

What enabled itOwnership, deadlines and escalations

WORKFLOW AT A GLANCE

From the incident to the verified root cause.

03

Execution

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

Explore this solution
05

Visibility

Corporate dashboards surface repeat themes, audit actions and training compliance.

Explore this solution

The challenge

Why the same patterns kept resurfacing across automated facilities.

01

Repeat incidents

Investigations didn’t force a clean RCA path, so the same patterns resurfaced.

02

Closure uncertainty

Evidence quality varied by plant and investigator, leading to inconsistent closure.

03

Audit friction

External audit findings needed manual tracking and action creation.

04

Training proof gaps

Compliance visibility was split across HR and plants, with no single truth.

What we implemented

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

RCA investigation view with mandatory evidence gates

Incident Investigations (RCA)

Configured for structured investigations that prevent repeat incidents.

Key workflow controls

  • Guided RCA flow (Why-Why) with required fields
  • Mandatory evidence attachments for closure
  • Root cause linked to corrective and preventive actions

Audit proof captured

  • Full investigation timeline and ownership
  • Evidence stored inside the record
Explore
Corporate view of repeat themes, audit actions and training compliance

Audits + Training Compliance

Configured so audit findings become actions and close, with training visibility across plants.

Key workflow controls

  • Digital audits with automatic action creation from findings
  • Action ownership, due dates and escalation for overdue control
  • Training compliance dashboards with manual and bulk upload

Audit proof captured

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

Governance and proof, inside the record

Less chasing. More traceability.

Role-based access control

Fine-grained permissions by site, role or module.

Immutable audit trail

Full history of all data changes and access.

PDF and Excel exports

One-click audit pack exports for regulators.

Offline field capture

Capture keeps working in low-signal areas, then syncs when the device reconnects.

See how the evidence adds up

Executive summary

What the safety team started with, what changed, and what improved.

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 and 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

Context & constraints

Number of sites
Multiple automated facilities
Contractor intensity
High
SOP alignment
Strict requirement
Offline mode
Enabled for low-signal areas

Ready to standardise investigations and audits?

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

PDF case study

Before you ask IT or procurement…

Most teams ask these questions before rolling out OQSHA.

Typically 2–6 weeks, depending on the number of sites, the modules you enable (Permit to Work, Inspections, Safety Alerts, HIRA, Visitor Management), and how much historical data you're bringing over. Most customers start with a pilot site, then roll out site by site.

Nothing special. Field teams use the OQSHA mobile app on Android or iOS phones and tablets; admins and managers use the web portal in any modern browser.

Yes. OQSHA is built for sites where connectivity is patchy: basements, towers under construction, plant floors. Field users can raise permits, safety alerts and inspections with no signal, including photos and attachments. Everything syncs automatically once the device reconnects.

Data is encrypted in transit and at rest, hosted on AWS in your chosen region. For organizations that need full control, OQSHA can also be deployed on-premise within your own infrastructure.

No. OQO runs as a captive AI. It works on your safety data within the OQSHA environment and never sends it to a public model or the open internet.

Yes. We support Single Sign-On and integration with common HRIS, ERP, and directory systems. Custom integrations are scoped with our implementation team during onboarding.

Yes. Historical permits, inspections, and incident records can be imported during onboarding, usually alongside the pilot, so your analytics and audit history are complete from day one.

Yes. Each organization runs in its own isolated tenant. Your templates, records, users, and dashboards are never visible to or shared with any other customer.

Built-in dashboards across permits, incidents, and inspections, filterable by site, zone, and time period. They're scoped automatically to what each user is allowed to see.

A named implementation contact through rollout, then standard support with response-time SLAs based on your plan. App updates are delivered over the air, so field users always have the latest version without reinstalling.

SAFER OPERATIONS START WITH A CONVERSATION

See what connected safety looks like.

Your workflows. Your sites. A tailored OQSHA walkthrough.

OQO welcomes you to explore OQSHA