Stop filling in a blank UK method statement template
A PDF template gives you the headings. Riskora structures the document from your scope — sequenced method, responsibilities, PPE, hold points and emergency arrangements — so a competent person can review and sign off. 100+ industries supported.
Preview first. No card needed. Download when you're happy.
- Free to start
- No signup to preview
- Done in ~60 seconds
Covers the same sections a proper UK method statement template covers — scope, sequence, plant, PPE, permits, hold points, emergency arrangements and briefing — except Riskora actually fills them in for your job.
- 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 downloaded a method statement template and didn't get past page 1.
- The principal contractor wants a method statement before site access.
- Your last one got knocked back as 'a paragraph, not a method'.
- You need a template that understands UK contractor expectations.
- Client email asking for a method statement
- Scope of works or quote
- Site manager WhatsApp or message
- An existing template to fill in properly
- A risk assessment to pair the MS with
Every section a UK method statement template should cover — filled in
Scope & site info
Activity, location, dates and team — populated at the top of the document.
Roles & responsibilities
Supervisor, lead, first-aider, banksman — who does what on the day.
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 audit trail inside your workspace.
Cross-reference to risk assessment
Hazards from the RA referenced inside the method steps.
What a finished method statement from this template looks like
Numbered steps in order, responsible person per step, equipment, PPE and hold points — not paragraphs. Built so a UK principal contractor can sign off on the first read.
Why this beats a PDF template — and a generic AI chatbot
Word templates leave every step blank. Chatbots produce paragraphs that don't survive review. Riskora is part of an end-to-end safety document and site safety management system — the method statement lands in your workspace alongside risk assessments, RAMS, COSHH, toolbox talks and sign-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.
Describe the job — get a populated method statement
Drop in the scope, the client email or a site manager's message. 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.