Plan, review and brief the work

Safetyman Sentinel Suite 1.9.0 · RAMS / JSA / SWMS

Use this guide with the saved company revision and your organisation’s controls. Software approval records a named decision; it does not establish site safety, worker competence or permission to start work. The included example is fictional training material.

Choose the document purpose

RAMS, JSA and SWMS are separate document purposes. Selecting a label does not establish that the document meets local requirements. Record the jurisdiction, applicable requirements, work scope and reasons for any high-risk construction classification. Use competent people to assess the actual site.

HSE describes method statements as a practical way to explain how work will be managed, drawing on risk assessment. Australian SWMS requirements concern high-risk construction work and depend on the applicable jurisdiction. WorkSafe Victoria explicitly distinguishes a SWMS from a risk assessment or JSA. Consult the relevant regulator and your organisation's requirements.

Prepare the first revision

1. Open Sentinel RAMS / JSA / SWMS and select New work plan revision. Use a meaningful document reference and revision 1.
2. Describe the location, scope, exclusions, organisation, consultation, interfaces, resources, competence, permits, emergency arrangements, risk criteria and how controls will be monitored.
3. Assign a named author and a different reviewer who have company and assessment editing access. Save these assignments before submitting.
4. Add ordered work steps. Use a positive, unique step number within this revision. Record the activity, hazards, people exposed, initial risk rationale, controls, residual risk rationale, responsibility and monitoring triggers. Steps inherit the plan's responsibility.
5. Link preparatory actions to the plan or its steps using Add action. Use the existing Action allocations workflow for named delivery and independent verification. Every linked action must have a Closed allocation and Closed action status before approval or use.
6. Attach supporting files before submission. Reviewed plan and step attachments cannot be changed. Evidence is retained privately with the assessment.

Follow the review workflow

Record personal briefings

Use Record briefing against the exact saved Approved or In use revision. Each named account may acknowledge only its own briefing, dated today in UTC. Describe the controls discussed, questions and limitations. Save any attachments while the briefing is Draft. Once acknowledged, the record and its attachments are retained unchanged.

This release supports acknowledgements by users with assessment editing access. It does not provide an external-worker signature portal. Keep external worker briefing evidence separately and reference it in the pre-start readiness record. The system checks the author's acknowledgement; it does not independently confirm that every worker was briefed, is competent or is authorised to start.

Change the work safely

Select Prepare next revision. This copies the planning content and steps into a new Draft, retaining the previous revision. Assign people again and review every control. Previous decisions, readiness assertions, attachments, briefing acknowledgements and action allocations are not copied. Add the current evidence and preparatory actions needed for the changed work. Suspend the previous revision where conditions make it unsuitable, then review and brief the new revision before use.

Export a revision

Export this revision downloads an HTML snapshot containing the plan, ordered steps, linked actions and revision briefings. Open it and choose Print / Save as PDF. The export clearly identifies its document reference, revision, status and export time. It may contain unsaved edits and is not a digitally signed issue. Check it against the saved company revision before distribution or use.

Worked example

Add fictional RAMS / JSA / SWMS example adds an unassigned Draft RAMS for inspecting a segregated pedestrian route at a fictional dispatch bay. Three steps cover confirming segregation, inspecting the route and handing back the area. It is a training exercise, not a ready-to-use site assessment or a high-risk construction SWMS.

Desktop and data compatibility

Desktop 2.1.3 does not support RAMS-focused workspaces. Use the web workspace or the matched Desktop 2.1.4 RC1 supplied by your administrator. Staging checks covered edited uploads, conflict resolution, revision downloads, evidence and existing Safety Case data. The desktop package is a portable release candidate, not a signed installer. The new server rejects saves that drop retained planning records, including Drafts. Older workspaces migrate with empty planning registers. Import reviewed content only after converting it into unassigned Draft material without approval or personal acknowledgement assertions.

Authoritative background

• HSE: construction administration and method statements
• HSE: assessing work at height and communicating precautions
• Safe Work Australia: high-risk construction work requiring a SWMS
• WorkSafe Victoria: safe work method statements

Sources checked 31 October 2026. This guide describes the software and does not replace jurisdiction-specific advice or competent assessment.