Turn a site manager message into RAMS
Site managers write short. 'Lift in Tuesday', 'second fix on Block C', 'scaff coming down Friday'. Riskora reads the actual instruction and structures it into a RAMS with hazards, controls, method steps and a 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
Preview first. No card needed. Download when you're happy.
- Free to start
- No signup to preview
- Done in ~60 seconds
Site manager messages are dense — every word is a signal. Riskora pulls the signals out and writes them into the document the contractor needs 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
- Site manager's WhatsApp says the job's on Tuesday and you've got no paperwork.
- The instruction is three lines long but the job needs a full RAMS.
- You want to reply 'RAMS attached', not 'I'll send it tomorrow'.
- The contractor has asked for documents before the lift slot.
- “Lifting steels south elevation Tuesday AM, banksman needed”
- “Second fix Block C, lone worker, weekend access”
- “Scaff coming down Friday — confirm method”
- “Site induction at 7am — bring RAMS”
- “Install containment and remove old ductwork”
- A short voice-note transcript
What Riskora extracts from a site manager message
Short messages carry the most signal per word. Riskora pulls each one out and writes it into the right section of the document.
Task
The actual instruction — lift, install, strip, second fix, survey.
Location / context
Block, elevation, access route, time slot or day.
Hazards
Inferred from task and site context — lifting, lone working, traffic, weather.
Controls
Matched to each hazard — exclusion zones, banksman, traffic mgmt, supervision.
PPE
Task-specific PPE — hi-vis, boots, hard hat, gloves, eye and harness where needed.
Method steps
Numbered sequence with the responsible person per step.
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 message stored
The pasted instruction is kept against the document — full provenance.
From a three-line message to a site-ready RAMS
'Lift Tuesday AM, banksman needed' becomes a structured RAMS with hazards, controls, method steps and a sign-off block. Edit anything before issue.
Not a paragraph generator pretending to be a RAMS
Generic AI tools turn three lines into three paragraphs that pass nothing. Riskora reads the message the way a supervisor would — what's the task, what changes today, what stops the work — and writes the structured sections a reviewer signs off.
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 message and build the document
Drop in the site manager's WhatsApp, text or voice note. Riskora builds the document around it.
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.