Rail · Safety & Assurance Case
A change you can explain. Evidence you can trace.
Build an explicit argument. Connect the controls and original evidence. Record the people, limitations and decisions behind each reviewed issue.
Available for controlled evaluation. Specialist acceptance and hosting suitability must be established before operational use.
A traceable argument
Context → claims → evidence → independent review
Rail system and station interfaces; no live movement authority or signalling design is represented.
Original sector framework · human decisionsRail review must establish the applicable jurisdiction, change significance and assessment route.
Built around your review questions
Rail context, made explicit.
Change significance and proposer decision
Record the proposed change, significance assessment, criteria, justification and accountable proposer. Do not assume every railway change has the same assessment route.
Hazard record and transferred risks
Identify hazards, causes, consequences, measures, owners and accepted transfers between organisations. Retain the controlled hazard record reference.
Risk acceptance principles and demonstration
Identify the applicable acceptance approach and demonstrate why each safety requirement is satisfied. Record unresolved assumptions.
Independent assessment and competence
Record the required assessment body or other independent assessment arrangements, scope, competence and open observations. A Sentinel reviewer is not automatically an assessment body.
Interface and configuration baseline
Identify infrastructure, rolling stock, operations and maintenance interfaces, baseline configuration and evidence revisions.
Entry into service and continuing monitoring
Record authorisations, restrictions, handover and monitoring responsibilities. Issuing this record does not itself authorise entry into service.
Fictional demonstration · no live records changed
Northbank Rail – station dispatch change
A fictional station dispatch arrangement is being changed. The case considers passenger-platform interfaces, visibility, competence and the evidence needed before a controlled change.
The proposed dispatch change is justified within its defined railway context
Link applicable evidence and document why it substantiates or challenges this claim.
Passenger-platform interface hazards have effective controls
Link applicable evidence and document why it substantiates or challenges this claim.
Responsibilities and transferred risks are accepted by the appropriate parties
Link applicable evidence and document why it substantiates or challenges this claim.
The selected risk acceptance approach is supported by evidence
Link applicable evidence and document why it substantiates or challenges this claim.
Independent assessment observations are resolved or dispositioned
Link applicable evidence and document why it substantiates or challenges this claim.
Handover, competence and monitoring arrangements are established
Link applicable evidence and document why it substantiates or challenges this claim.
Explore the review scenarios
1. Establish the working baseline
Define boundaries, assign a case owner and record the relevant requirements and their current editions. The example begins in Draft; no claim is automatically supported.
2. A gap challenges the argument
An interface acceptance record is missing. Unresolved interface responsibility Record the challenge against the relevant claim. Retain the source evidence and determine who must review it.
3. A supporting record changes
Update a linked assessment or shared control, then refresh the case. The dependency version mismatch prompts review. A subsequent draft may acknowledge the new version; a previously issued snapshot remains unchanged.
4. Review and controlled issue
Resolve completeness gaps, substantiate claims and submit to the assigned reviewer. Every contributor to that revision is excluded from approving it. Separate regulatory, clinical or operational decisions remain outside this workflow.
Create an editable copy with “Create fictional Rail draft” in the client workspace. Training prompts must be replaced with actual reviewed content before any real case is issued.
Connected to the Sentinel Suite
Use the work you already do.
Learn and challenge
Incident, Investigate and Investigate Pro provide findings that can challenge assumptions. Reference the applicable finding and assessment revision.
Control and verify
Use Bowtie and Assure records, register shared barriers and retain performance evidence. A changed barrier prompts reassessment of dependent cases.
Manage continuing assurance
Change, Compliance and Audit support controlled review. Authorised copies of Observe and Competence evidence can be attached; their original permissions remain separate.
Know what the edition does.
Is this certification or regulatory approval?
No. It manages arguments, evidence, version history and accountable review. It does not decide whether the technical argument is sufficient or whether operations may proceed.
What can I retain and export?
Original PDFs, Word documents, Apple Pages files and supported images can be uploaded to a case. Export Google Docs to Word or PDF first. Download original files separately, export JSON and generate printable case reports.
What information is suitable for this launch?
Use fictional or appropriately authorised evaluation information. This deployment has not been assessed for classified defence material, nuclear-sensitive information, patient-identifiable clinical records or sensitive cyber secrets. Sector labels do not establish hosting accreditation.
Can the edition be allocated separately?
Yes. An administrator allocates each edition to a company. An active company annual licence and manager role are required to write. Existing authorised managers retain read/export access after expiry.
Does the desktop include this edition?
No. These new case editions are cloud add-ons. Desktop case synchronisation and sector-specific desktop validation are separate work.
ORR – Managing safety when investing in the rail network · Reference checked 23 October 2026. Determine applicable current requirements for each real project.