Questions plants ask us.

It means a report does not stop at recording what happened. Raven carries the event through investigation and action, then keeps the response and the learning connected to what comes next.

Not by itself. Actions close with evidence, and closure can also be an accepted alternate mitigation, a deferral with a named risk owner, or a capital-project route, each documented. An effectiveness review and a recurrence watch can stay open after the physical work is done, and an incident closes only when every action from it closes.

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.

Not necessarily. Some plants run Raven Incident as the complete workflow. Others keep their current system as the formal record and use Raven to investigate events, improve the actions that follow, and learn from repeats. We'll scope the right fit in the demo.

Run Raven alongside your current system now, starting with the free 30-day pilot. By the time the renewal decision arrives, your own plant can show whether more useful events are reported, investigations are improving, and actions reach a real conclusion. See the renewal evaluation.

Raven Incident already connects reporting, investigation, actions, dashboards, and plant administration. The product direction extends how evidence, earlier events, learning, and recurrence work across that loop. The demo shows what fits your rollout today.

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.

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.

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.

Your procedures, taxonomy, report formats, and role structure shape the work. Raven also draws on publicly available incident investigations and guidance. Your team makes the accountable decisions.

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.

Yes, as an add-on module. Employees submit improvement ideas from the same app they use for safety reporting; your working and steering committees evaluate on your own marks format; reward categories follow from the marks; and a suggestion closes only after the implementation is verified. See the Employee Suggestion Scheme module for details.

Yes. Raven Incident ships with Android and iOS apps alongside the web app, all included in the plant price.

Mobile is built for frontline reporting: describe, photograph, submit, even offline. The web workspace is where review, classification, investigation, workflow, dashboards, and closure live.

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.

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).

Yes. Reports can be filed offline on mobile and sync when a connection returns, built for plant areas with poor connectivity.

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.

Your admin does. Users, roles, taxonomy, action sources, approval chains, report formats, and dashboards are changes your admin makes the same day, without a vendor ticket. Every configuration change is attributable and auditable.

Role-based enablement during rollout, and after it, help from people who understand plant operations, not a generic ticket queue. Commercial and service specifics are agreed per deployment.

We agree what history needs to remain visible in Raven, what stays in your current system, and how the data should move before rollout. Bring a sample export to the demo so we can plan the right approach.

One flat annual price per plant, with unlimited reporters and everything included. See pricing for the numbers.

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.