Build RAMS for project managers
Project managers waste days chasing subbie RAMS, spotting the templated ones and rebuilding what's missing. Riskora structures your project's RAMS pipeline — new build, review, version and brief — so you're not the person the PC calls at 5pm the day before start. 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
Riskora structures your brief into a site-specific RAMS for project managers — hazards, controls, PPE, permits, method steps and emergency arrangements. Not a generic template.
- 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
- Programme starts Monday and half the subbie RAMS are still missing.
- PC has rejected two subbie submissions as generic.
- You need version control across a project instead of email chains.
- New crew starting — you need a briefable summary today.
- Scope of works for the project managers
- A client email, PQQ note or RFI
- A site manager's WhatsApp or text message
- Pre-start meeting notes or programme
- A previous RAMS to update or improve
- Drawings, permits or site rules to align with
Inside a Riskora RAMS for project managers
Every section is built around the actual task — not boilerplate. These are the task-specific items Riskora drops in by default for project managers, ready for you to refine and sign off.
Task-specific hazards
Subcontractor RAMS not site-specific · Overlapping activities with unmanaged interface risk · Missing rescue / emergency arrangements · Version drift between issued and briefed RAMS · Competence evidence not attached · Unbriefed operatives on site
Controls matched to each hazard
Central RAMS register per project · Structured review checklist (site, task, controls, rescue, sign-off) · Sequenced programme with interface risk called out · Version log + PDF re-issue on any change · Sign-on register captured before start · Competent-person review + PC issue trail
Likely PPE
Standard site PPE (helmet, hi-vis, boots) · Package-specific PPE per subbie RAMS
Permits & hold points
Package permits collated per activity · Hot works, height, isolation, excavation as required
Emergency arrangements
Project-wide emergency arrangements · Muster point + assembly · Named first aiders per package · Escalation matrix to PC + client
Method steps & sign-off
Numbered method sequence with responsible person, briefing register, and competent reviewer sign-off before work starts.
A site-ready RAMS for project managers
See how Riskora structures hazards, controls, PPE, permits and method steps into a single document specifically for project managers — edit anything before you issue it.
Not a generic Project Managers template
Most "RAMS for project managers" templates online are blank docs you still have to fill in, or AI prose with no structure. Riskora reads your brief and writes the right sections — hazards, controls, PPE, permits, method steps, emergency arrangements and sign-off — built for the actual task on the actual site.
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.
Start your project managers RAMS now
Describe the job details, site message or scope of works. Riskora builds the rest around the task.
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.