Build a method statement from job details, scope or a client message
A method statement isn't a wall of paragraphs — it's an operating plan. Riskora structures the sequence, responsibilities, equipment, PPE and hold points. 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
Step-by-step method, responsible person per step, hold points and emergency arrangements — built so a competent person can review and sign off.
- 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
- Principal contractor wants a method statement before site access.
- Your last one came back marked 'too vague' or 'paragraphs'.
- You need a sequenced plan, not a paragraph dump.
- The job starts tomorrow and you still need paperwork.
- Client email asking for a method statement
- Scope of works or quote
- Site manager WhatsApp or message
- A risk assessment you need an MS to pair with
- An old method statement to upgrade
What Riskora builds into every method statement
Scope & site
Activity, location, dates, team — recorded properly at the top of the document.
Roles & responsibilities
Supervisor, lead, first-aider, banksman — who is responsible for what.
Plant, tools & equipment
Equipment in use, inspection requirements and certification.
Materials & substances
Materials in use and any COSHH cross-references.
Step-by-step method
Chronological sequence with the responsible person per step.
Hold points & checks
Inspection and check points between phases of work.
Emergency arrangements
First aid, fire, spill, rescue and escalation specific to the task.
Briefing & sign-off
Briefing register, version lock and an audit trail in your workspace.
Pairs with the risk assessment
Hazards from the RA referenced inside the method steps.
See what your finished method statement will look like
Numbered steps in order, responsible person per step, equipment, PPE and hold points. Not a long paragraph — an operating plan a reviewer can sign off.
Why this isn't a generic AI method statement
Generic AI text tools produce paragraphs that read fine and pass nothing. Word templates leave the sequence empty. Riskora is part of an end-to-end safety document and site safety management system — it structures the sequence, captures the responsible person per step, pairs the document with the risk assessment, and stores it in your workspace with toolbox talks, sign-off records and audit-ready briefings.
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.
Describe the job — get a structured method statement
Drop in the scope, a client email or a WhatsApp message from your site manager. Riskora structures the sequence.
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.
Related Riskora pages
- UK method statement templateTemplate that turns into a structured doc
- Real method statement examplesWorked examples by trade
- Build a method statement from a client emailPaste the email, get a structured doc
- Method statement rejected — fix and resendRebuild after a knock-back
- Method statement for roofingTrade-specific
- Method statement for brickworkTrade-specific
- Method statement for asbestos removalTrade-specific
- Combined RAMS generatorMethod statement + risk assessment together
- Standalone risk assessment generatorRA on its own
- Urgent document helpSame-day or rejected docs
- See Riskora pricingFree start · paid from £29/mo