Build RAMS for archaeology fieldwork

Archaeology RAMS need to align with the WSI, recognise plant-interface and deep-excavation risks and address human-remains handling and lone working. Riskora structures all of it — without losing the academic tone. 100+ industries supported.

Preview first. No card needed. Download when you're happy.

Already have a RAMS? Upload and rebuild it
  • Free to start
  • No signup to preview
  • Done in ~60 seconds

Riskora structures your brief into a site-specific RAMS for archaeology fieldwork — 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
You're probably here because…
  • Main contractor needs RAMS aligned to the WSI before access.
  • Local planning archaeologist asked for a documented method.
  • Linear scheme — lone-working / driving documentation required.
  • Possible human remains / scheduled feature — escalation plan needed.
What to paste into the box
  • Scope of works for the archaeology fieldwork
  • 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 the document

Inside a Riskora RAMS for archaeology fieldwork

Every section is built around the actual task — not boilerplate. These are the task-specific items Riskora drops in by default for archaeology fieldwork, ready for you to refine and sign off.

Task-specific hazards

Trench / sondage collapse in deeper interventions · Plant strike during machine watching brief · Lone working on remote watching briefs · Manual handling of finds and equipment · Slips, trips and falls into open features · Discovery of human remains or unexploded ordnance · Weather exposure on open / linear sites

Controls matched to each hazard

WSI alignment with stop / escalation triggers in the RAMS · Battering or shoring for any sondage > 1.2m · Pedestrian banksman during machine watching with agreed signals · Lone-working check-in protocol, mobile / satellite comms · Manual handling assessment for spoil / finds bags · Trench edges flagged, covered or fenced when unattended · Stop-work procedure for human remains (police + coroner) and ordnance (EOD)

Likely PPE

Hi-vis Class 2 · Safety boots with mid-sole · Hard hat in shared areas · Cut-resistant gloves · Weather PPE (waterproofs, sun protection, hi-vis warm layer)

Permits & hold points

Main contractor site permit / induction · Excavation permit · Scheduled Monument Consent (where applicable) · Lone-worker authorisation

Emergency arrangements

Lone-worker emergency procedure with escalation contact · Trench rescue plan with ladder access at intervals · Casualty extraction in remote location (grid reference, vehicle access) · Discovery escalation: human remains → police, UXO → EOD · First aid kit + nearest A&E and grid reference

Method steps & sign-off

Numbered method sequence with responsible person, briefing register, and competent reviewer sign-off before work starts.

Example output

A site-ready RAMS for archaeology fieldwork

See how Riskora structures hazards, controls, PPE, permits and method steps into a single document specifically for archaeology fieldwork — edit anything before you issue it.

Build this RAMS free
Not a blank template

Not a generic Archaeology Fieldwork template

Most "RAMS for archaeology fieldwork" 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.

Inside the document

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.

Build this RAMS free
Before & after

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.

Before

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.
After

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.
Build this RAMS free
How it works

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.

  1. 1
    Paste 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.

  2. 2
    Riskora structures the document

    Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.

  3. 3
    Review, edit and download

    You stay in control of every section. Tweak anything, then download a clean PDF or share a link.

  4. 4
    Brief the team and record sign-off

    Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.

Build this RAMS free
Built for site reality

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.

Build this RAMS free
  • 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 in seconds

Start your archaeology fieldwork 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.

Already have a RAMS? Upload and rebuild it
FAQ

Questions for this exact situation

Yes — Riskora records the WSI reference and pulls stop / escalation triggers directly from it into the RAMS.

Banksman, exclusion zone, signal protocol, communication with operator, and a stop-work trigger for archaeological discovery.

Defined as a stop-work event with police notification, coroner involvement and a documented welfare process for the team.

Mandatory check-in protocol with escalation contact, communications (mobile / satellite) and a fall-back rendezvous point recorded.

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.

Keep exploring

Related Riskora pages