Create the RAMS each package needs, with a due date
Category: Safety
Screens every package for whether it needs a RAMS and works back from its start date, so high-risk work is approved well in advance.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Additional Review Information | Text | No | Optional context, assumptions or focus areas for the screening (e.g. known high-risk works, site ... |
| Packages to Include | Multiple Selection | No | Optional. Limit the screening to these packages only, for example the batch you have just importe... |
| Baseline RAMS Lead Time (days) | Number | No | How many days before a package starts on site a routine RAMS should be approved. The task adjusts... |
| Create RAMS Records | Boolean | No | If enabled, creates a RAMS record for each package identified as needing one — linked to its pack... |
| Create Summary Report | Boolean | No | If enabled, creates a markdown report summarising the RAMS screening and the records created. |
Outputs
Summary
Type: Text/Markdown
Summary
Outputs
Type: Array
Outputs
Completion Time
Type: Text/Markdown
Completion Time
Report Id
Type: Text/Markdown
Report ID
Rams Created
Type: Number
RAMS Created
Packages Reviewed
Type: Number
Packages Reviewed
Disclaimer
Type: Array
Disclaimer
Example Use Cases
Create RAMS for all packages needing one
Screen every work package and create the RAMS records that are required.
Configuration:
- Create Rams Records:
True - Create Report:
True - Default Lead Time Days:
14
Preview without creating records
Screen the packages and produce the report only — no RAMS records are created.
Configuration:
- Create Rams Records:
False - Create Report:
True
Tags: rams · packages · cdm · risk-screening · workspace-items · planops-report
Last updated: 2026-09-09