Sentinel Suite 1.10 · RAMS / JSA / SWMS
Plan the work.
Review the revision. Brief the team.
Bring the work scope, ordered steps, hazards, controls and personal briefings into one controlled assessment. Keep the named author and independent reviewer clear, and retain the previous revision when the work changes.
Make the plan specific
Record the location, scope, exclusions, interfaces, resources and emergency arrangements. Add ordered steps with hazards, controls, responsibility and monitoring triggers.
Keep decisions independent
The named author submits the plan. A different named reviewer records the approval decision. Linked preparatory actions and their allocations must be closed before approval or use.
Connect people to a revision
Each authorised account acknowledges its own briefing against the exact saved revision. Retain external worker briefing evidence and record pre-start readiness.
What are RAMS, JSA and SWMS in Sentinel?
RAMS means risk assessment and method statement; JSA means job safety analysis; SWMS means safe work method statement. Sentinel offers these as distinct document purposes, supported by shared planning, review and briefing records.
Choosing a document label does not establish compliance. Use competent people to assess the actual task, location and applicable requirements. Software approval records a decision; it does not issue a permit or establish that work is safe to start.
A clear route through each revision
- Draft: develop the plan and ordered steps, assign the author and a different reviewer, add evidence and close preparatory actions.
- Submitted: ask for independent review. Scope and steps are frozen; return to Draft with a reason before making changes.
- Approved: retain the reviewer’s decision and review date. Reviewed content cannot be silently overwritten.
- In use: the author records pre-start checks and evidence of required briefings, including their own acknowledgement. Only one revision of the same document can be In use.
- Suspended: record why reliance has stopped. Prepare a new revision for changed work; a suspended revision cannot return directly to In use.
- Superseded or Closed: retain the earlier content, steps and history. Supersession requires an approved or in-use successor.
Keep follow-up work connected
Use Add action on a plan or work step to retain its source. Use named Action allocations for delivery and independent verification. The Shared work queue helps users find outstanding work within the selected assessment.
Explore shared actions and workflow →
How to access the module
- Sign in to the client portal and select your authorised company.
- Open or create an assessment and choose Sentinel RAMS / JSA / SWMS.
- If the product is not visible, ask your administrator to check Module settings and Company products.
- Assign different named author and reviewer accounts with existing company and assessment editing access.
Practise with the included example
The fictional dispatch-bay example starts as an unassigned Draft and contains three ordered steps. Use a separate training assessment, assign your own test users and work through review and briefing. It is not a completed operational assessment.
Common questions
Does approval confirm that every worker has been briefed?
No. Each account acknowledges only its own briefing. The author records readiness and evidence of the required briefings. Sentinel does not independently establish every worker’s competence or authorisation. There is no external-worker signature portal in this release.
What happens when the plan changes?
Prepare the next revision as a Draft. Planning content and steps are copied; approval decisions, readiness assertions, attachments, acknowledgements and action allocations are not. Review and brief the new revision before use.
Can I export the plan?
Export this revision downloads an HTML snapshot of the plan, steps, linked actions and briefings. Print it or save it as PDF. Check the export against the saved company revision before distributing it; an export may contain unsaved edits and is not a digitally signed issue.
Which desktop version supports RAMS?
Use the web workspace or the matched Desktop 2.1.4 RC1 supplied by your administrator. Desktop 2.1.3 and earlier do not support RAMS-focused workspaces. The 2.1.4 package is a portable release candidate; back up your local workspace before changing versions.
Connect contractor work to the suite
Review contractor evidence, link engagement plans and check every compulsory worker qualification. Keep follow-up actions connected to their source.
Explore Contractor management → · Follow the fictional contractor example →