Investigate with evidence, not email threads

Command centre for the live case

Every investigation is one workspace — Overview, Gantt, Tasks, Recommendations, Actions, Findings, D&A, Fatigue, Chat, Final report and Audit — so the file does not live in email threads and shared drives.

Open cases as manual investigations or from an incident feed when that source is configured. Capture location with coordinates, what3words and a map, set the investigation level, and assign a lead and team.

• Statuses Open, In review and Closed, with Level 1 / 2 / 3 (and Other) for severity.
• Configurable incident types for your operation (SPAD, derailment, collision, welfare escalation and more).
• Gantt and tasks so planned work sits on a timeline against the case.

Recommendations that become owned actions

Raise recommendations against the case and the evidence behind them. HSSE and DCP roles approve or reject; rejection needs a written justification. Approval creates a tracked action that moves from open through in progress to done — so close-out is visible, not assumed.

• Recommendation board with pending, approved and rejected states.
• Mandatory rejection justification so a no is auditable.
• Actions from approvals with clear ownership and status.

Evidence, RCA and the final report

Record findings against human performance factors and the ten incident factors, with an evidence reference and narrative on each item. When the investigation is ready, the final report compiles the artefacts for print or PDF, with signature pads for the Lead Investigator and Designated Competent Person — and seals when both have signed.

• RCA coding against human performance and ten-incident-factor frameworks.
• Print / Export PDF of the compiled final report.
• Dual sign-off (Lead Investigator + DCP) before the report is sealed.
• Hash-linked audit chain of who did what, and when, on the case.

Drugs & alcohol and fatigue on the critical path

D&A screening sits on the investigation when the level or incident type requires it — breath, urine, blood or saliva, with consent and results, and follow-up actions where needed. Fatigue can be assessed against the shift pattern entered for that case, with a tenant-level FRMS view structured as Plan, Do, Check and Act.

• Mandatory or recommended D&A driven by investigation level and incident type.
• Shift pattern on the case for fatigue context during the investigation.
• FRMS workspace for the tenant, separate from the individual case file.

Connected to Rail Intel CMS when you need it

Investigations and CMS stay separate products. When linked through Admin → API Management, a dual-approval token binds one Investigations company to one CMS tenant. You can then look up the employee under investigation, pull competency cycle status and recent medication declarations, and pick lead and team members from CMS team management and employee records.

Roster and shift data for fatigue stay in Investigations — CMS does not supply them.

• Dual-approval CMS connector so pairing is deliberate on both sides.
• Subject lookup with competency cycle (in date / due soon / overdue) and recent medications.
• Lead and team selectable from CMS people where the link is active.

Roles, tenants and assurance views

Workspaces are multi-tenant and entered with a company code. Roles cover System Admin, Company Admin, Lead Investigator, Investigator, HSSE and DCP, with capability overrides on top of the role baseline — the same idea as CMS permissions, tuned for investigation work.

• Reporting for open / in review / closed mix, levels, incident types, RCA counts and sealed reports.
• Recommendations and Compliance sections for assurance oversight across the workspace.
• Admin for users, email templates, incident catalogue and the CMS API link.

A product, not a CMS add-on

Rail Intel Investigations is a standalone Rail Intel app at investigations.railintel.co.uk. CMS add-on modules extend Rail Intel CMS; Investigations sits alongside it for investigation workflows, with an optional connector when you want shared people and competency context.