> ## Documentation Index
> Fetch the complete documentation index at: https://docs.saphion.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# RAMS overview

> RAMS writes each risk assessment and method statement as one Document from your own Word templates and Hazard library, and downloads it as your own two Word files, filled in.

RAMS is the product for risk assessments and method statements. You describe the job, and Saphion writes one Document with two tabs, **Risk assessment** and **Method statement**, from your company's own Word templates, your Hazard library and the facts Saphion already holds. You check and edit it like any Document, then download your own two Word files, or their PDFs, with everything filled in.

> [!NOTE]
>
> RAMS is a product your Organisation holds. Admins give people a RAMS author seat; only an author can write a RAMS. Writing one uses your Organisation's RAMS AI allowance, never a person's own. See [Concepts](https://docs.saphion.co.uk/concepts.md#product-seat).

## Open RAMS

Choose **RAMS** from the product switcher. The RAMS page lists the RAMS you may open: each one's name, its Project, who can see it, who it is shared with and when it was saved. Anyone with access to the product can read the list; only a RAMS author can write one. Open one to read or edit it. Beside RAMS in the sidebar are the **Hazard library** and **Templates**.

## What a RAMS is made from

* **Your two Word templates.** Your own risk assessment and method statement forms, uploaded once in Templates and checked by an Admin. Nothing about your form's look changes: your logo, fonts, tables and footers stay as they are.
* **Your Hazard library.** A board of the hazards your company has already assessed, each with who is at risk, its controls and its ratings. RAMS uses them word for word where they fit the job.
* **The job.** What you describe, and the Project you choose, if any.
* **Facts Saphion holds.** Your name and role, today's date, your Organisation, the Project, the site, the client and the nearest NHS A\&E. Anything Saphion does not know is highlighted "to confirm".

## Your template's own wording is locked

The parts of your template that are your company's standing wording, or that are completed by hand on site (signatures, sign-on sheets), stay exactly as your template has them. In the Document they show a lock when you point at them, and they cannot be edited, moved or deleted. You can add your own words around them. To change them, change the template in **Templates**.

## Ask Beacon

Beacon helps you word a job before you press **New RAMS**, and edits a RAMS that exists like any Document ("add a permit-to-work step to the method statement"). Beacon never starts a RAMS itself: only you do, with **New RAMS**.

## FAQ

> [accordion] Can I use Saphion's own RAMS form?
>
> No. A RAMS is always written into your company's own forms. Upload them in Templates first; see [Set up RAMS](https://docs.saphion.co.uk/products/rams/set-up-rams.md).

> [accordion] Where do people sign?
>
> On the downloaded Word files' own sign-on lines. Saphion has no in-app signing or status.

## Related

* [Set up RAMS](https://docs.saphion.co.uk/products/rams/set-up-rams.md)
* [Make a RAMS](https://docs.saphion.co.uk/products/rams/make-a-rams.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.