Questions plants ask us.
Product
Does Raven Incident work as a standalone system?
Yes. It is a complete system of record for near-miss and incident management: reporting, classification, investigation, recommendations, and closure, with its own dashboards and exports. It doesn't require any other Raven product.
We already have an EHS system. Does this replace it?
Not necessarily. Some plants run Raven Incident as their full incident system; others run it alongside an existing suite for capture quality, investigation drafting, and closure tracking. We'll scope the right fit in the demo. (Plants using Raven's wider product line can connect incident data to it later, but nothing here depends on that.)
Does it handle unsafe act / unsafe condition reporting and observation rounds, or only near-misses?
Both. Unsafe acts and conditions are captured in the same conversational flow as near-misses. Structured observation rounds, checklist-based with safe/unsafe marking and coaching-level closure, run on mobile as part of the same system.
Can the action tracker hold actions that don't come from incidents, such as audits, committee meetings, and walkthroughs?
Yes. The action tracker is one register across every safety source, including categories your admin defines. Every action carries an owner, a due date, evidence requirements, and aging alerts.
Who reviews what the AI suggests?
People do, at every step. Classification is a suggestion with reasoning and confidence shown; reviewers verify or override in one click, and the system learns from corrections. Investigation drafts are starting points the investigation team reviews, refines, and owns. Nothing is auto-approved.
How does the AI know anything about my plant?
It works from your plant's procedures, taxonomy, formats, and roles, and it is grounded in publicly available incident investigations and guidance from bodies such as the CSB, CCPS, OSHA, and OISD. Every output stays a draft your team reviews.
Can it use our taxonomy and our report formats?
Yes, that's the default, not a customization. Classification follows your plant's taxonomy and tiers. Investigation reports are drafted in your plant's format. Approval chains follow your role structure.
Is there a mobile app?
Yes. Raven Incident ships with Android and iOS apps alongside the web app, all included in the plant price.
What does the mobile app cover vs the web app?
Mobile is built for frontline reporting: describe, photograph, submit, even offline. The web workspace is where review, classification, investigation, workflow, dashboards, and closure live.
Data & security
Where does our data go? Is it used to train AI models?
No. Zero data retention: your data is not used to train AI models. Full customer data ownership and control, with configurable retention and deletion policies. Customer data is logically isolated per tenant.
Can this run in our own cloud?
Yes. Raven Incident runs in our cloud or deployed in your own cloud, and on-premise deployment options are available. Cloud deployments run on enterprise infrastructure (AWS/Azure).
Does it work offline?
Yes. Reports can be filed offline on mobile and sync when a connection returns, built for plant areas with poor connectivity.
Deployment
How long does implementation take?
Days, not months. We configure the system around your taxonomy, formats, and approval roles and go live at a single plant quickly, then expand scope as your team pulls for more.
Commercial
How is it priced?
One flat annual price per plant, with unlimited reporters and everything included. See pricing for the numbers.
What happens to our data if we leave?
It leaves with you. Full export of your records, registers, and reports; your data is yours throughout, and that doesn't change at the end of a contract.
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.