Business Enquiry

Sheet 02 / 01 — RAMS

RAMS where the work is happening.

A method statement only does its job when the people carrying out the task have actually seen it. Built Still supports getting it to them, recording that they acknowledged it, and keeping that record.

Start a Business Enquiry
  • Issue
  • Review
  • Acknowledge
  • Sign
  • Record

Sheet 02 / 01 — A

What the RAMS workflow covers.

Everything below concerns distribution, acknowledgement and record keeping. None of it concerns writing, approving or validating the document itself.

  1. 01

    Document distribution

    Prepared RAMS documents issued to the people who need them, rather than left in a folder nobody on site opens.

  2. 02

    Relevant worker access

    The right document reaching the right working party for the task in front of them.

  3. 03

    Acknowledgement

    A recorded confirmation that a person was issued with the document and acknowledged it.

  4. 04

    Signatures where configured

    Where digital sign-off forms part of the agreed workflow, the signing step is captured against the same record.

  5. 05

    Records

    The issue, the acknowledgements and the outcome retained together in a consistent structure.

  6. 06

    Supporting evidence

    Notes and photographs that relate to the work can be associated with the record.

  7. 07

    Reissue and update

    When a document is revised, the revision can be issued again so acknowledgement is against the current version.

  8. 08

    Outstanding visibility

    Who has not yet acknowledged, shown plainly rather than buried in a report.

RAMS workflow

  1. 01 Upload / prepare
  2. 02 Issue
  3. 03 Review
  4. 04 Acknowledge
  5. 05 Sign
  6. 06 Record

Sheet 02 / 01 — B

Get the RAMS to the people doing the work.

A method statement sitting in an office folder is not reaching the operative on Level 2. Built Still is designed to move that document to the people carrying out the task, and to keep a record of who acknowledged it.

RAMS workflow

  1. 01 Upload / prepare
  2. 02 Issue
  3. 03 Review
  4. 04 Acknowledge
  5. 05 Sign
  6. 06 Record
RAMS management
RMS-0412

Steel erection — Level 2

Issued

Illustrative interface — example data

Revision
03
Issued
07:31
Issued to
4 people
  • Operative A Steel fixer Signed 07:46
  • Operative B Steel fixer Acknowledged 07:52
  • Operative C Banksman Viewed 08:04
  • Operative D Plant operator Issued 07:31

2 acknowledgements outstanding

Supervisor reviewing documents on a construction projectConstruction site context

Sheet 02 / 01 — C

Where the platform stops.

This matters more than any feature list. RAMS carry real legal weight, and software cannot take that on.

  1. A

    Built Still does not write RAMS

    There is no document generation. A RAMS document must be prepared by a competent person before it is issued through the platform.

  2. B

    Built Still does not validate RAMS

    The platform makes no assessment of whether a document is suitable, sufficient or legally adequate for the work.

  3. C

    Built Still does not replace competence

    Preparation, review, approval and supervision remain with appropriately competent people in the business.

Built Still can support the RAMS process but cannot determine whether a RAMS document is suitable, sufficient, legally compliant or appropriate to the specific work without competent professional review.

Site safety briefing with a construction teamSite briefing context
Contractors planning work before starting on siteContractor planning context

Next step

How does your business get RAMS to site today?

Tell us how method statements are currently prepared, issued and acknowledged in your business, and where that process tends to break down.

Start a Business Enquiry Toolbox talks