Set your RAMS up from scratch, packages and all
Category: Safety
Reads your documents for the packages, screens each for whether it needs a RAMS, and creates them with a due date and a contractor.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Project Documents | Document Picker | Yes | Select the project drawings, specifications and scope documents to analyse. These are the primary... |
| Additional Information (Optional) | Text | No | Optional information to guide package identification and RAMS screening (e.g. project type, known... |
| Always Identify Packages | Boolean | No | If enabled, the package identification stage runs even when the job already has packages. Leave o... |
| Baseline RAMS Lead Time (days) | Number | No | How many days before a package starts on site a routine RAMS should be approved. The screening ad... |
| Create Summary Reports | Boolean | No | If enabled, each stage creates a markdown report summarising its results. |
Outputs
Summary
Type: Text/Markdown
Summary
Outputs
Type: Array
Outputs
Packages Created
Type: Number
Packages Created
Packages Screened
Type: Number
Packages Screened
Packages Needing Rams
Type: Number
Packages Needing a RAMS
Rams Created
Type: Number
RAMS Created
Rams Skipped
Type: Number
Packages Already Covered
Completion Time
Type: Text/Markdown
Completion Time
Example Use Cases
Populate RAMS from scratch
Fresh job with no packages - identify the packages, then screen them and create the RAMS records.
Configuration:
- Force Package Creation:
False - Default Lead Time Days:
14 - Create Report:
True
Create RAMS against existing packages
Packages already exist - skip identification and go straight to RAMS screening and creation.
Configuration:
- Force Package Creation:
False - Default Lead Time Days:
14 - Create Report:
True
Tags: rams · packages · cdm · empty-state · composite
Last updated: 2026-08-31