Customer story · Fertilizer & petrochemicals · Nigeria

Every report tracked to closure at Indorama Eleme.

Indorama Eleme is a major fertilizer and petrochemical complex. Its safety team wanted more of what happens on the ground to be reported, investigated, and closed, without the paper chase that had grown around the old process. Raven Incident now runs that workflow every day, on mobile and web, online and offline.

Registered users: 1,000+
Plants & units live: 8
Reports processed: 1,000+
Investigations closed: 500+

The starting point

Friction every paper-based program knows.

Forms filled in after shift, often incomplete. Classification that varied by reporter. Full analysis reserved for the serious events. Action registers split across departments and spreadsheets. Reports compiled by hand before every review meeting.

What changed

The same workflow, without the drag.

Capture Paper forms filled after shift, often incomplete A two-minute guided conversation on any phone, online or offline

Classification Varied by who was reporting, so trends blurred Suggested from the plant taxonomy, the same way every time

Investigation Full analysis reserved for the serious events Every event arrives with the investigation drafted for review

Actions Registers split across departments and spreadsheets One register: owner, due date, evidence to close, or it escalates

Visibility Manual compilation before every review meeting Live dashboards by plant and department, repeat patterns flagged

Results

The chain, measured.

more events reported

Reporting that takes two minutes gets used. Events that went unreported start showing up. Measured against the pre-rollout baseline.

500+

investigations closed

With the analysis drafted on arrival, the events that used to be skipped get investigated.

85%

actions closed on time

Owner, due date, and evidence required, with escalation before items go overdue.

40%

fewer repeat events

Patterns surface early, so the fix lands before the third similar event. In covered areas.

Expansion

Deployed for one workflow. Expanded three times on customer pull.

01
Near-miss reporting

The first workflow: two-minute capture, AI-drafted investigation, closure tracking.
02
Unsafe acts & conditions

The daily, highest-volume signals joined the same flow on customer pull.
03
Safety observation rounds

Structured coaching rounds with injury-potential ratings and area trends.
04
Incident investigation

Formal reporting, full analysis, and lessons released plant-wide.

All six core modules are live today, with one login, one action register, and dashboards matched to the plant's management routines.

For your evaluation

What another plant can take from this.

Frontline adoption is the constraint that matters: capture has to be easier than not reporting
Start with one workflow and expand on pull, rather than deploying everything at once
Map plants, departments, units, and role groups as they exist; the workflow should follow the plant
One action register across sources is where the operating change becomes visible
Live in days, not months: the first usable release should not wait for the full program

See the same workflow on your plant's terms.

Bring your current process to the demo. We will show how capture, investigation, actions, and dashboards map to it.

Schedule a demo