SentinelSafetyman International
Client sign in ↗Explore the demo ↗

New · Operational modules

Learn the complete Sentinel workflow.

Start with a fictional case, practise one module, then follow the evidence into the next. Guidance explains the decisions, permissions and limits at each step.

Sentinel Change

Approve the change before exposure

Review operational changes, affected barriers, readiness and temporary-change expiry. Retain a named owner, independent decision and post-implementation review.

Explore Change →Read the Change guide ↗

Sentinel Audit

Test what happens in practice

Plan audits, reuse approved checklists, sample evidence and record findings. Link actions and management reviews. These capabilities are also included within Assure.

Explore Audit →Read the Audit guide ↗

Sentinel Observe

Make early concerns visible

Capture hazards, positive control observations and improvement suggestions. Record the response, triage potential harm and propose linked changes.

Explore Observe →Read the Observe guide ↗

Sentinel Competence

Authorise against demonstrated ability

Define task requirements, retain training and practical assessment evidence, and record scoped authorisations with restrictions and validity dates.

Explore Competence →Read the Competence guide ↗

Beginner to confident user

  1. Read the module guide and select a company assessment.
  2. Practise with an unassigned fictional Draft.
  3. Assign an owner and independent reviewer with assessment access.
  4. Upload evidence, record decisions and allocate actions.
  5. Review the outcome in Assure and retain the history.
Open the full operational guide ↗

Use the guide’s Print or save as PDF button for offline reading.

Sentinel learning centre

Learn the whole response.
One practical step at a time.

From a factual incident report to a reviewed investigation, stronger barriers and evidence of effective action. Start with the public example, then practise in a separate company training assessment.

See the connected example

Start with the Northbank report and follow its evidence, barrier review and later assurance records. The separate map exercise lets you try body and vehicle selections without saving data.

Start guided tour →
Sentinel Incident

Capture a report that can be investigated.

  1. Sign in, select the correct company and create or choose an assessment. Open Incident → Report an incident.
  2. Enter the event title, date, time if known, location and every relevant category. Record observed actual impact and explain credible potential impact against your site criteria.
  3. Describe what happened and the immediate response. Keep observed facts separate from assumptions. Do not enter confidential clinical notes.
  4. For injury or vehicle events, click the affected areas or use their labelled checkboxes. Select multiple areas where needed. Body left/right refers to the person; vehicle left/right faces the direction of travel.
  5. Apply and save. Assign a review owner and due date, record the triage decision, then link an existing investigation or choose Start investigation.

The source report remains a distinct record. Revisit both the report and investigation when new evidence changes the account.

Explore this module in the example →
Sentinel Investigate

Build the factual account before the conclusion.

  1. Open the investigation linked from the incident. Confirm the event statement, scope and responsible investigator.
  2. Add evidence to the Evidence register. Retain available uploads, identify their sources and record what each item can and cannot establish.
  3. Build the event timeline. Use a focused 5 Whys chain or branch a Why Tree where conditions interact; five is a guide, not a required number of answers.
  4. Record findings with evidence and an explicit status. Keep hypotheses and open questions visible. Create corrective actions against supported findings.
  5. Use Investigate Pro for more complex testing. Review supported findings before proposing a transfer into the Bowtie.

Evidence, findings and actions stay within the authorised assessment. A link does not prove a cause or approve a barrier.

Explore this module in the example →
Sentinel Investigate Pro

Test competing explanations and barrier performance.

  1. Open Pro from the top row. Confirm the investigation brief, team, scope, review arrangements and known limitations.
  2. For each hypothesis, record a test method, observations and supporting or contradicting evidence. Keep refuted and unresolved explanations visible.
  3. Use the cause canvas to arrange and connect findings. Explain the causal relationship; position on a diagram alone does not establish causation.
  4. Open Barrier Failure Analysis → Review a barrier. Select the investigation and an existing barrier, or describe an unmodelled/missing barrier. Preserve what existed at the time of the event.
  5. Compare expected function with observed performance. Record failure mechanism, conditions, organisational influences, evidence and a recommendation. Do not assume every barrier failed.
  6. Compare solution options, define measurable success criteria and prepare the investigation for independent review. Readiness checks identify gaps; they do not approve the conclusion.

The BFA is a historical review. The Bowtie is the current control model. Review changes deliberately so the original event conditions remain traceable.

Explore this module in the example →
Sentinel Bowtie

Turn supported learning into a stronger control model.

  1. Define the hazard and top event. The hazard is the source of potential harm; the top event is the point at which control is lost.
  2. Identify credible threats leading to the top event and consequences that could follow. Check that the pathways are meaningful for the work.
  3. Place preventative barriers before the top event and mitigative barriers on consequence pathways. Define their functions and responsible owners.
  4. Add degradation factors that could weaken each barrier and the degradation controls that manage them. In the example, a temporary route bypasses segregation; review and approval address that weakness.
  5. Review the transfer from Investigate/Pro, retaining its evidence and rationale. Define performance standards and the verification needed in Assure.

A proposed control is not a verified control. Avoid assigning numerical reliability or risk-reduction claims without a justified method and evidence.

Explore this module in the example →
Sentinel Assure

Check delivery, then check whether it worked.

  1. Select the relevant barrier or action. Define an inspectable performance standard, owner, review date and required evidence.
  2. Record the inspection result and its evidence, including failures and limitations. Raise corrective work where the standard is not met.
  3. Check completed action evidence independently. Completion confirms delivery; it does not establish lasting effectiveness.
  4. At the agreed review point, assess the outcome against the success criteria and record Effective, Partly effective or Ineffective as appropriate.
  5. Keep further reviews scheduled. The latest review governs managed-action closure; reopen work if new evidence shows the intended outcome has not been sustained.

For the training example, the short-term sample supports initial effectiveness only. It does not prove that all barriers work indefinitely or quantify incident reduction.

Explore this module in the example →
Shared responsibility

Allocate work. Verify the outcome.

  1. Create a linked corrective action and set a due date and required outcome.
  2. Open Action allocations. Choose the responsible organisation, a named authorised owner and a different verifier. Both need existing company and assessment access.
  3. The owner accepts the assignment, progresses the work and submits completion evidence for verification.
  4. The verifier checks the evidence and either returns the action to In progress or marks it Verified complete.
  5. Record the later effectiveness review in Assure. Close only when the latest outcome is Effective and the required evidence and review notes exist.
  6. Use the incident’s Closure review to examine linked work and record the closure rationale. Reopen when new evidence requires it.

An external organisation can be recorded, but allocation does not invite a contractor, grant permissions or allocate seats. Use an authorised accountable owner.

See the action lifecycle →

Practise without changing operational records

Open the connected training assessment.

  1. Confirm all five modules are enabled for your company. Pro is allocated separately.
  2. In the portal, choose Incident → Load connected training example. It creates a separate assessment; save any current work first.
  3. Follow the linked Northbank near miss, its evidence and Pro BFA, the segregation barrier and temporary-layout degradation control.
  4. Inspect the interim Assure review: it is partly effective, so the exercise should remain open. The public tour shows a separate later teaching snapshot.
  5. Use the separate low-speed vehicle-contact exercise for body and vehicle selections. Do not add an injury to the Northbank near miss.
  6. Practise action allocation using authorised training accounts. The example deliberately assigns no live staff.
Download connected practice file (JSON) ↓Open client portal ↗
Missing a module?

Ask your administrator to check Sentinel Suite → Module settings and Company products, then refresh the portal. Company membership, module allocation and assessment permissions all matter.

Further guidance

Work at the depth
the evidence needs.

Visual cause analysis and solution comparison →

Investigate Pro handbook (PDF) ↓

Detailed Incident, BFA, allocations and troubleshooting guide →

Configured AI offers drafting support. Forecasting needs sufficient dated observations and validation. Sensor feeds, email alerts and their recipients need separate configuration. No regulatory report is automatically submitted.