Turn a Client Email into a RAMS
Paste the message once. Riskora structures it into a RAMS for UK site work with hazards, controls, method steps, emergency arrangements, sign-off, review notes and export-ready structure. 100+ industries supported.
UK (RAMS) example document — Two-Storey Rear Extension — 14 Birchwood Lane, Reading. Client: Mr & Mrs A. Whitfield (Private Client). Site: 14 Birchwood Lane, Reading, RG1 5JT. Scope: Construction of a two-storey rear extension (6.4m × 4.2m) to an existing semi-detached dwelling. Works comprise breaking out of existing rear elevation, trench-fill foundations to 1.0m, traditional cavity blockwork to first floor, pre-stressed concrete lintels, timber roof structure with natural slate finish, plus alterations to existing rear wall to form structural opening with rolled steel joist (RSJ 203×102 UB23). Works programmed over 9 weeks with a peak site team of 6 operatives. Hazards assessed: Manual handling — blocks, lintels, plasterboard, Working at height — independent scaffold & roof structure, Buried services strike during excavation, Collapse of excavation / trench wall, Hand-arm vibration (HAVS) — breaking out, drilling, Silica dust — cutting blocks, brick, concrete, Vehicle/pedestrian segregation — narrow domestic street.
Full version
Preview first. No card needed. Download when you're happy.
- Free to start
- No signup to preview
- Done in ~60 seconds
Structured around HSE-recognised RAMS format — review before use and adapt to your site.
- UK · IE · US · CA · AU · NZ
- RAMS · SWMS · JHA · JSA · COSHH · Task Analysis · Toolbox Talks
- Site-specific — not a blank template
- First document free · No card required
- Client emailed asking for RAMS and COSHH before you can quote or attend.
- FM or principal contractor sent a scope email with a deadline attached.
- You want to reply with the document, not 'we'll send it tomorrow'.
- The email has the job buried in three paragraphs and a signature.
- “Client email asking for RAMS and COSHH”
- “Please return RAMS before site access Monday”
- “Quote needs RAMS, method statement and insurance attached”
- “Install containment and remove old ductwork”
- Forwarded message from the principal contractor
- Tender email with the scope inside
What Riskora extracts from your client email
Client emails carry the same signals buried in them every time. Riskora pulls them out and structures them into the document the client is asking for.
Task
The work being requested — install, strip-out, survey, repair.
Location / context
Site, building, block, access window and deadline.
Hazards
Inferred from the task and context — height, dust, hot work, live services.
Controls
Matched to each hazard — permits, exclusion zones, RPE, supervision.
PPE
Task-specific PPE — hi-vis, cut gloves, RPE, eye, harness.
Method steps
Numbered sequence with the responsible person per step.
COSHH where flagged
If the email mentions substances, dust, fuels, adhesives — Riskora prompts for COSHH.
Emergency arrangements
First aid, rescue, escalation contact and route — built around the task.
Sign-off requirements
Preparer, reviewer, approver and briefing register set up.
Original email stored
The email is kept against the document so you can show why the document was built that way.
From a client email to a document you can reply with
A scope email becomes a structured RAMS with hazards, controls, method steps, COSHH and a sign-off block. Edit anything before issuing, then reply with the PDF attached.
Not 'paste email, get paragraphs'
Generic AI tools turn your email into a wall of paragraphs that pass nothing. Riskora parses the email — task, hazards, deadline, requested documents — and writes the structured sections a reviewer expects. The email becomes the brief; the document is built around it.
What your RAMS actually contains
Riskora builds a structured, client-facing document — not a generic AI paragraph. Every section is shaped around your job, your site and your team.
Hazards
Task-specific hazards for the job, captured row by row — not a generic list pulled from an old RAMS.
Controls
Control measures mapped to each hazard with residual risk scoring after controls are applied.
PPE
PPE requirements tied to the activity and site, ready to brief to the team.
Method steps
Step-by-step method statement structured around how the work is actually sequenced on site.
Emergency arrangements
First aid, rescue plan, emergency contacts and site-specific escalation routes.
COSHH prompts
Substance prompts when the work involves chemicals, dusts, fumes or sealants — flagged early, not missed at review.
Sign-off
Operative sign-off captured against the document — names, dates and acknowledgement of the brief.
Version history
Every change tracked so you can show what was issued, when, and which version the team signed.
Approval status
Clear approval state on every document — draft, in review, approved, issued — visible across the team.
Audit trail
Who created it, who reviewed it, who signed it. A complete trail you can hand to a principal contractor or auditor.
From copied-and-pasted to site-specific
The reason RAMS get rejected is rarely the format — it's that the document is obviously generic. Riskora rebuilds it around this job, this site and this task.
Generic template copied from an old job.
- • Hazards and controls that don't match this site or task.
- • Method steps written for a different sequence of work.
- • No emergency arrangements specific to the location.
- • Client flags it as generic and asks for a rewrite.
Site-specific document structured around this job, site and task.
- • Hazards captured from the actual scope you pasted in.
- • Method steps sequenced for how the work runs on site.
- • Emergency arrangements and rescue plan tied to the location.
- • Approved internally, briefed to the team, signed off and stored.
From job details to signed-off document
A four-step workflow used by contractors, consultants and safety teams to turn informal job details into client-ready safety paperwork.
- 1Paste job details
Drop in a client email, a WhatsApp from the site manager, a scope of works or a tender note. Anything that describes the job.
- 2Riskora structures the document
Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.
- 3Review, edit and download
You stay in control of every section. Tweak anything, then download a clean PDF or share a link.
- 4Brief the team and record sign-off
Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.
Built by people who've written this paperwork on real sites
Riskora is built by a founder with hands-on site and document experience — designed for contractors, consultants and safety teams who need to issue, brief and prove safety paperwork without losing a day to admin.
- Built for contractors, consultants and teams
Solo trades, principal contractors and in-house safety teams all run on the same workflow. - Supports multiple countries
UK, Ireland, Australia, New Zealand, US and Canada — wording and document types match the local standard. - Not just documents
Sign-off, approvals, version history and an audit trail — the management workflow around the paperwork.
Add the email and build the document
Drop in the client email. Riskora builds the RAMS they're asking for.
Preview first. No card needed. Download when you're happy.
Questions for this exact situation
Riskora helps structure a site-specific safety document. It does not replace competent review, site supervision, client requirements or legal duties. Always check the final document before issue.