Project RAMS

A project RAMS is a source: a full risk assessment and method statement that jobs on this project copy rather than start blank. It is editable for as long as you like and it is never reviewed, issued or exported. That last point is the one people get wrong, so it has its own section below.

Before you start

Nothing here is permission-gated — any member of the organisation can create and edit project RAMS sources. Capturing geo evidence works best once the project has a flight area, ideally a starred one, because the evidence is taken from its geometry.

Steps

1. Open the project RAMS tab

   Open the project and select the RAMS tab. The readouts across the top count Sources and Hazards, and will read No Hazards Yet or No Geo Evidence while the project is empty. The panel below is RAMS Sources, and its meta line states the point of the thing: Reusable — jobs copy a source rather than starting blank.

2. Create a source

   Select New source. Give it a Name, then choose Start from — Blank RAMS, one of your Organisation templates, or Copy an existing source. Copying takes the method statement, scope and every hazard, and the copy is independent from that moment on.

3. Pin the authorisation route

   Set Authorisation route to Open category, PDRA01 or UK SORA / legacy OSC OA. This sets the regulatory baseline that controls are checked against, and you can change it later.

4. Capture geo evidence, or not

   Capture geo evidence offers Not now or Starred flight area. Capturing on create means the editor opens with hazard suggestions drawn from the site, which you accept or dismiss one at a time. Select Create source.

5. Write the method statement and hazards

   The editor has four sections: Details, Method statement, Hazards and Scoring reference. Complete Purpose and scope and the method statement, then use Add hazard for each risk. A hazard needs Hazard, Causes / unmitigated failures, Potential consequences, Initial likelihood, Initial severity, Mitigations, Residual likelihood and Residual severity, plus a Risk owner and the ALARP and Tolerable switches under Decision. Editing autosaves — the pill by the title reads Saving then Saved.

Options

Refresh the site evidence

The Geo control at the top of the editor picks which geometry the evidence comes from — Starred flight area, or a named area, with the starred one suffixed (primary). Recapture re-reads the site and offers fresh suggestions; the readout beside it shows the last capture date or Never captured.

Read the register

The RAMS Sources list shows Source, Authorisation, Origin, Hazards, Geo evidence and Updated. Origin tells you where a source came from: Blank, Org template, or From job RAMS. Retire one with Archive on its row menu.

Promote a good job RAMS back to the project

The flow runs both ways. If a job RAMS turns out to be the version you want to reuse, select Save as project RAMS on the job RAMS panel. The new source appears here with Origin reading From job RAMS.

What happens next

A job picks this source up in its own Create RAMS dialog: the RAMS source list shows each project source as Project RAMS · <name>, and choosing one snapshots its method statement and hazards into the job. Picking a project source also pins the job’s authorisation route to match.

Copy the source into the job, finish it there and put it through review — see Job RAMS.

Troubleshooting

Geo evidence says Not captured. No geometry was captured, usually because the project had no flight area at the time. Add one, then use Geo and Recapture in the editor.

The Send for review button is missing. You are looking at a project source. That button only exists on a job RAMS.

A hazard will not let the document be ready. The Readiness rail lists exactly what is missing, one line per problem — a hazard needing its causes and controls, a missing ALARP confirmation, a missing tolerability confirmation, or an unacceptable residual risk score.