The incident-to-learning system for process plants.
Report near misses and incidents, keep investigations moving, turn findings into actions, and carry the learning into the next decision. Raven can run the complete workflow or work alongside your EHS system.
Scanning by module? See the capability index.
The person who noticed it can report it.
A quick guided conversation helps the person who saw the event report it while the details are still fresh.
- Describe it in plain language; the system asks what an investigator would ask
- Photos, timestamp, and location captured automatically; any device, offline
- Contractors and shared devices supported, so reporting is not limited to people with desks
- Structured observation rounds for the scheduled walk-downs, with safe and unsafe trends by area
- The AI suggests a classification on capture, with reasoning shown and one-click override
Hydraulic hose weeping at press 2, small puddle under it
Is the press still running?
No, stopped it and tagged the isolation valve
Anyone exposed or injured?
No, area is clear, told my supervisor
Photo attached
More useful events make it into the system.
Decide what happened and how seriously to treat it.
Turn the first report into a clear event and send it down the right path.
- Structured record with your taxonomy: event type, area, activity, equipment
- The AI suggests actual and potential severity, with process-safety relevance and its reasoning shown
- High-potential events route to a formal, sponsored investigation lane
- A human confirms or changes the classification and lane in one click; every override is recorded
Trends you can trust, because classification stops drifting.
Keep the investigation moving without lowering the standard.
Raven prepares the evidence, chronology, questions, and possible paths in one workspace, so the investigation does not lose momentum.
- FIR
Formal incident reporting
The event is reported formally, severity assessed, and an investigation sponsor and team assigned by severity.
- FAR
Full analysis report
Structured analysis through standard methods, evidence folded in, findings under dual approval before release.
- LFI
Lessons from incidents
Lessons prepared from the closed investigation and released plant-wide through the system, not by email.
- Chronology, evidence in hand, and evidence still missing, visible from the start
- The AI prepares witness questions and applicable procedures for the team
- The AI retrieves similar past events alongside the case, with why they match
- More than one root-cause path proposed, run through standard methods: 5-Why, Fishbone, Contributing Factors, Bow-Tie
- System, physical, and human factors analysed with the reasoning written out
- Completion targets with reminders, and dual approval before release
- An incident closes only when every action from it closes
Could the gasket have passed inspection and still failed?
Possible. If the torque record is current, consider thermal cycling on the transfer line. Added as an alternative line under Hypothesis B.
based on 2 similar past events + public incident learningsWhat are the most likely causes of heat exchanger tube ruptures?
Most documented cases trace to tube-side corrosion, vibration-induced fatigue, or overpressure during transient operation. Inspection intervals are the common gap.
sources: public investigation reports · industry guidance- 1 Oil on walkway
- 2 Flange leak, T-105 transfer line
- 3 Gasket condition at last service?
- Torque sequence in SOP not followed
- Thermal cycling on transfer line
Your formats, digitised: FIR, FAR, and LFI as your plant writes them.
Findings become accountable work.
Findings become owned work. Actions from incidents, observations, audits, committees, and other plant work stay together in one place.
- The AI checks recommendations for specificity to the event and its accepted causes before they become actions
- Every action carries its source, rationale, owner, due date, expected result, and the evidence needed to close
- One action can go to multiple departments, with closure tracked department by department
- Aging alerts before items go overdue, and escalation when something sits too long
- Audit Due in 9d
Restore fire-water ring main pressure test records
- Near-miss Due in 4d
Replace gasket and re-torque flange, T-105 transfer line
- Observation Due in 2d
Mark safe standing zones at bagging conveyor
- Committee Overdue 11d
Update permit-to-work display boards, all units
Every report tracked to closure.
Prove the response, not just the checkbox.
A completed task does not always mean the risk is resolved. Raven keeps the response visible until there is a clear outcome.
- Completed with evidence: photos, records, and remarks reviewed at closure
- Accepted alternate mitigation, with the decision and its basis recorded
- Deferral with a named risk owner, and capital-project or management-decision routes where the fix is bigger than an action
- Rejected recommendations keep their technical basis on the record
- Effectiveness review and recurrence watch stay open after the physical work is done
The difference between done and resolved stays visible.
The event changes future work.
Lessons leave the investigation and reach the people and documents they should change.
- Lessons from incidents (LFI) prepared from closed investigations and released plant-wide through the system
- Procedure and training follow-through: the lesson routes to the documents and sessions it should update
- Toolbox-talk and contractor communication from the same record
- Learning shared across plants running Raven, so a lesson paid for once is not paid for twice
Safety knowledge moves through the system, not by email.
See the repeat before the next event becomes serious.
- Similar past events, automatically. When a new report arrives, related events from your plant's history appear alongside it
- Repeats get flagged, not filed. The third similar event in ninety days reads very differently from three unrelated entries
- Equipment and area hotspots, visible without anyone building the analysis by hand
- Classification anomalies. When the same kind of event starts getting classified differently across shifts, the dashboard flags it
- Role-based dashboards for executives, HSE ops, area managers, and sponsors, plant by plant
- Ask questions in plain language, like "which areas had the most repeated near-misses this quarter?"
Flange leak, transfer line · Area 3
Flange seep, transfer bay
same equipment typeOil sheen below pipe rack
same area · similar causeDrip at pump P-22 coupling
same category, night shift3rd similar event in this area in 90 days
The repeat shows up before it becomes the serious one.
Six modules. One product. One action register.
If your shortlist is written by module, everything is here, and it all ships together with one login. Each capability links to its place in the loop above.
Near-miss reporting
A two-minute guided conversation instead of a form, with photos, location, and follow-up questions. Any device, offline.
Unsafe act & unsafe condition reporting
The same two-minute capture for the daily, highest-volume signals, classified on capture with one-click override.
Incident reporting & investigation
Formal incident reporting (FIR), full analysis reports (FAR), and lessons from incidents (LFI), released plant-wide.
Safety observation rounds
Checklist rounds run as coaching, not policing: injury-potential ratings, on-the-spot closure, trends by area.
CAPA & action tracking
One register for actions from every source. Owner, due date, evidence, or it escalates.
Dashboards & insights
Plant-wise rollups, repeat patterns, and program health, with plain-language questions over the data.
-
PPE: gloves and eye protection in use
Safe -
Tools: right tool for the job, good condition
Safe -
Body position: line of fire, beneath suspended bag
Injury potential MediumAction taken Coached on the spot: repositioned, discussed safe standing zonephoto attached -
Reactions of people: adjusting work when observed
N.A.
Plus the Employee Suggestion Scheme as an optional add-on module. See the suggestion scheme →
AI does the groundwork inside every incident.
It asks the next questions, structures the report, finds missing evidence and earlier events, prepares the investigation, and checks whether the actions address what happened.
- 01
Raven starts with your plant's way of working.
Your procedures, event taxonomy, report formats, and role structure shape the work. Past incident records can add more plant context over time.
- 02
The investigation arrives ready to work.
The chronology is organized. Missing evidence is visible. Witness questions, similar events, possible causal paths, and recommendation checks are ready for the team.
- 03
Your team makes the accountable calls.
People decide classification, severity, accepted causes, recommendations, residual risk, and closure. The supporting evidence and the changes made along the way stay with the case.
awaiting investigator review
HSE assistant
Safety knowledge your workers can actually reach: ask in plain language, get an answer in plain language, on mobile and web.
- Any worker can ask, any time: procedures, permits, precautions, what applies to the job in front of them
- Answers draw on your plant's procedures and public safety guidance, with the source shown
- No hunting through PDFs for the one paragraph that applies
- Separate from the investigation workspace; this one is for every worker
What do I need before grinding work near the transfer line?
That counts as hot work near a live line. Before you start:
- Hot work permit signed by the area owner
- Gas test before and during the job
- Fire watch posted through the work
Who approves the permit on night shift?
The on-duty shift in-charge for that area.
Your workflow keeps the work moving.
Raven follows your approval chains, roles, and routing, with a clear next step at every handoff.
Your own approval workflows.
Add and change approval chains: who creates, reviews, approves, assigns, and closes, per plant and department. The application follows your company's workflow.
A notification at every handoff.
Assignment alerts, review requests, due-date reminders, aging alerts, and escalation when something sits too long.
Releases carry the report.
Approved reports and lessons go out through the system with the PDF attached, not by someone circulating files.
Closure needs evidence.
Nothing closes on a checkbox: actions close with evidence and remarks, and every step is on the audit trail.
Your admin runs it, not a vendor queue.
Your team can change users, taxonomy, workflows, and reports without turning every update into a vendor project.
Users, roles, and structure.
Plants, departments, units, role groups, and permissions, managed by your admin.
Taxonomy and sources.
Event types, severity routes, action sources, and recipient lists: changes your admin makes the same day, not a vendor ticket.
Workflows and formats.
Approval chains, report formats, and dashboards configured to your management routines.
Every change on the record.
Configuration changes are attributable and auditable, like everything else in the system.
Complete workflow, or overlay on your EHS system.
Raven runs the complete workflow
Bring reporting, investigation, actions, and learning into one mobile and web workflow built around how your plant works.
- Reporting, review, investigation, actions, dashboards, and audit history in one place
- Your formats, approval chains, and notifications
- Your admin runs the configuration
Best when reporting lives in paper, Excel, email, or a rigid internal portal today.
Schedule a demo →Raven adds intelligence alongside your EHS system
Keep your current EHS system. Raven helps your team investigate each event, improve the actions that follow, and learn from repeats.
- Your system of record stays in place
- Raven prepares the investigation work around each event
- Actions and recurring patterns stay visible
Best when your EHS system is staying put, or you want operating evidence in hand before its next renewal.
Schedule a demo →Built for how plants actually run.
Android, iOS, and web apps.
Mobile apps for frontline reporting, even offline. The web workspace for review, investigation, dashboards, and administration.
Our cloud or yours.
Runs as a cloud service on enterprise infrastructure (AWS/Azure), or deployed in your own cloud. On-premise deployment options available.
Roles & permissions.
Role-based access with configurable role groups: who can create, review, approve, assign, and close, defined per plant and department.
Single sign-on.
Single sign-on with your identity provider.
Serious events get a formal track.
Higher severity routes to a formal investigation with a sponsored team and dual review before release.
Multi-plant, multi-department.
One system across plants and departments, with department-wise views of what's reported, open, and closed. One login across units.
Audit trail throughout.
Every action attributable: who reported, who classified, who approved, who closed, and when.
Security.
SOC 2 Type 2 certified, encryption in transit and at rest, tenant isolation. Security & data →
Corporate governance.
Controlled core taxonomy with local extensions, cross-plant visibility, and shared learning. Enterprise & multi-plant →
Spill-related events in Tank farm classified Tier 3 on night shift, Tier 2 elsewhere. Review suggested.
The system compounds.
Every event should improve how the plant understands the next one, responds to it, and shares what it learned.
Report from wherever the work happens
Voice notes, phone calls, and messages become useful reports without asking the worker to change how they communicate.
Bring the whole case together
The chronology, missing evidence, relevant procedures, and earlier events stay together as the investigation develops.
Turn findings into better actions
Raven checks whether a recommendation addresses this event, then keeps the effectiveness question open after the work is done.
Let the learning change the next job
Lessons reach procedures, training, toolbox talks, and the risk work that should change because of the event.
Connect the event to the plant
Equipment, lines, areas, and safeguards become part of the incident record, so related risks are easier to see.
See the pattern across plants
Recurring events and weak responses stop looking isolated when the same risk appears in another place.
Process-safety indicator mapping
Events classified to API RP 754 tiers, with plant-level Tier 3/4 leading-indicator rollups for conformance reporting.
Employee Suggestion Scheme
Raven Incident can also run your plant's suggestion scheme: workers submit ideas from the same app they report near-misses in, your committees evaluate on your own marks format, rewards follow from the marks, and a suggestion closes only after the implementation is verified. Priced as a one-time module fee per plant, never per user.
Ready to close the loop on safety?
See how Raven Incident captures complete reports, drafts investigations, and tracks every action to closure at your plant.