Safety workflow

RAMS in PlanOps

A RAMS starts as an activity on the programme and it ends as an accepted record. PlanOps keeps that whole journey together.

The complete run

From programme activity to current record

Checking the document is one part of the job. PlanOps keeps the request, decision and latest revision connected.

  1. 1

    Identify

    PlanOps reads the programme and work packages to identify activities that need a RAMS.

  2. 2

    Request

    Ask the subcontractor for it with a due date, then let automatic chasing keep the request moving.

  3. 3

    Submit

    The subcontractor uploads the document through a simple submission page. They do not need an account.

  4. 4

    Assess

    The RAMS is assessed against all 20 tests, including those that depend on the project’s own requirement.

  5. 5

    Decide

    Accept it or send it back. Each gap lands in the risk register against a named person, not in an email trail.

  6. 6

    Keep current

    Each revision is read against the previous one, while the register stays aligned with the work it covers.

Two ways to review

Check one RAMS free. Manage every RAMS in PlanOps.

The free RAMS Review is a document-only first pass. It shows what is present, what is missing and where a competent person should look more closely. PlanOps adds the project requirement and manages the complete RAMS workflow.

Free · one document

The free RAMS Review

Go to ramsreview.co.uk and upload a PDF or Word RAMS document. No account is needed. It is checked against the 13 document-only criteria in the published standard.

  1. 1

    Upload

    Add your RAMS securely.

  2. 2

    Review

    See the marks and gaps.

  3. 3

    Use

    Download or share the result.

It is not an approval: the competent person still decides whether the RAMS is suitable for the work and the site.

Full workflow · every RAMS

RAMS in PlanOps

PlanOps starts before the document arrives and keeps the accepted record tied to the activity, work package and subcontractor afterwards.

  • Identify which activities need a RAMS, then request and chase each submission.
  • Run all 20 tests using both the document and the project’s own requirement.
  • Accept or return it, assign the gaps, and keep the register and revisions current.