Upload your existing RAMS — get a properly structured one back
Been sent a template someone else wrote? Got a RAMS the principal contractor rejected? Drop the PDF or Word file in. Riskora reads the whole document, keeps your company, project and scope, and rebuilds it as a CDM 2015-aligned RAMS — hazards mapped to controls, numbered method steps, PPE, emergency arrangements and sign-off block. 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
Drop in a PDF, Word doc or old RAMS
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready RAMS around it.
- PDF · Word · TXT
- Company + scope kept
- Free to start
- No signup to preview
- Done in ~60 seconds
Riskora reads the document the way an experienced SHEQ coordinator would — extracts the real task and site context, discards the filler, and rebuilds the sections a principal contractor expects to see.
- 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
- You inherited a generic RAMS template that doesn't match your job.
- The principal contractor rejected the RAMS and asked for a proper one.
- The document you were given is missing hazards, controls or a method.
- You need CDM 2015 language without rewriting the whole thing by hand.
What Riskora extracts from the file you upload
The uploaded document usually contains the right raw material — company, site, scope, some hazards. Riskora keeps what's yours and rebuilds the rest into a structured RAMS.
Company + contractor details
Company name, address, contact — kept verbatim from the uploaded file.
Project + site context
Project name, location, client, access window and deadline pulled from the document.
Scope of works
The actual task — extracted from method paragraphs, scopes and bullet lists.
Hazards (kept + inferred)
Your listed hazards are kept; missing ones are inferred from the task (height, hot work, COSHH, public interface).
Controls mapped to hazards
Each hazard gets a specific control — permits, exclusion zones, RPE, supervision, edge protection.
Task-specific PPE
Hi-vis, boots, harness, gloves, eye, RPE — matched to the extracted task, not a generic list.
Numbered method steps
Sequenced steps with the responsible person per step — the section principal contractors actually check.
Emergency + sign-off
First aid, rescue, escalation route and the preparer / reviewer / approver block set up for signature.
Gap prompts
Riskora flags anything the uploaded file was missing — supervisor, plant, emergency arrangements — before issue.
From uploaded PDF to a CDM-aligned RAMS
A generic RAMS template becomes a site-specific, structured document with hazards, controls, method steps and a sign-off block ready for the principal contractor.
Not a paragraph rewrite. Not a filename change.
Generic AI tools paraphrase your file into long prose. Riskora reads the uploaded document, extracts the underlying task and site context, and rebuilds the sections the HSE and CDM 2015 expect — hazards, controls, method, emergency arrangements, sign-off — with your company details kept intact.
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.
Upload the file — get a proper RAMS back
Drop in the PDF or Word file. Riskora rebuilds it as a structured RAMS with hazards, controls, method steps and sign-off.
Drop in a PDF, Word doc or old RAMS
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready RAMS around it.
- PDF · Word · TXT
- Company + scope kept
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.