Scaffolding RAMS for Cardiff contractors

Scaffolding RAMS cover erection, alteration, dismantling and inspection — work that combines working at height with manual handling and significant interface risk to the public and other site users. Riskora builds a Scaffolding RAMS that names the Cardiff site, respects South Wales building stock and hits the sections principal contractors reject you for missing — first time. 100+ industries supported.

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

  • Free to start
  • No signup to preview
  • Done in ~60 seconds

Riskora helps structure your RAMS — CDM 2015 aware, with the sections a Cardiff principal contractor actually asks for. A competent person must review it before use.

  • 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…
  • Cardiff principal contractor won't grant site access until the Scaffolding RAMS is in.
  • Last scaffolding submission came back: "not site-specific for Cardiff".
  • Generic scaffold design references without naming the specific design used (TG20:21 compliant, or bespoke design by a named designer).
  • Welsh-language site signage and bilingual induction material on public-funded projects.
What to add for a Cardiff Scaffolding RAMS
  • Scaffolding scope of works for the Cardiff site
  • A Cardiff client email or PC pack
  • A site manager's WhatsApp or text message
  • Pre-start meeting notes or programme
  • A previous Scaffolding RAMS to update or improve
  • Drawings, permits or Cardiff Council Building Control conditions
Inside the document

Inside a Riskora Scaffolding RAMS for Cardiff

Each section is built around the actual scaffolding task on your Cardiff site — the hazards scaffolding teams share nationally, plus the South Wales context needed for an informed PC review.

Scaffolding hazards

Falls from incomplete scaffolds · Dropped components struck against operatives below · Public interface (pedestrians, vehicles) · Electrical contact with overhead lines · Collapse from incorrect tie pattern · Manual handling of components

Controls matched to each hazard

Collective controls before personal, sequenced permits, rescue plans and hold points — mapped to every hazard in the Scaffolding RAMS.

Scaffolding RAMS sections

Project details and scaffold design reference · Erection sequence · Tie pattern and load class · Public protection (fans, hoardings, pedestrian routes) · Inspection regime (TG20:21 / Reg 12) · Dismantling sequence

Cardiff local context

Cardiff construction concentrates around Cardiff Bay regeneration, the central retail and office core, and the rapidly expanding Cardiff Capital Region housing programme. Welsh-language signage on certain public-funded sites is often a contract requirement and should be addressed in site rules referenced by the RAMS.

PPE & permits

Task-appropriate PPE for scaffolding plus the permit-to-work sequence Riskora prompts for on every Cardiff job.

Emergency arrangements

Named first-aider, Cardiff A&E route, muster point and escalation to the principal contractor.

Example output

A site-ready Scaffolding RAMS for Cardiff

See how Riskora shapes scaffolding hazards, controls, PPE, permits and method into a document designed for PC review — edit anything before you issue it.

Not a blank template

Not a generic Scaffolding template

Most "Scaffolding RAMS Cardiff" downloads are blank docs 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 specifically for scaffolding on the actual Cardiff 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.

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

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.

  • 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 Cardiff Scaffolding RAMS now

Describe the scaffolding scope or the site message. Riskora builds the rest around the Cardiff task.

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

FAQ

Questions for this exact situation

Named site, sequenced scaffolding hazards with matched controls, a method statement, PPE, permits, emergency arrangements and sign-off. The most common reason for rejection specifically for scaffolding work is: Generic scaffold design references without naming the specific design used (TG20:21 compliant, or bespoke design by a named designer). RAMS that say 'scaffold to standard' are routinely rejected.

Yes — Pennant sandstone Victorian terraces in Cathays, Roath and Canton; modern apartment stock in Cardiff Bay; and significant 1960s/70s office buildings across the central core. Ground conditions include reclaimed dock land in the Bay area and Triassic mudstones across the centre. Riskora prompts you to record the building context so the Scaffolding RAMS reflects the actual Cardiff site.

Only as a starting point — every submission must be site-specific. Riskora lets you clone a previous Scaffolding document and change what's different for the new Cardiff address, which is the sensible middle ground between starting from scratch and submitting an unedited copy.

Riskora prompts you to add Cardiff Council Building Control permits (highway licences, hoardings, skip permits, out-of-hours consent) under the permits section where they apply to scaffolding work.

Yes — the free plan includes one lifetime safety document with no card. Paid plans add higher limits; projects and team sign-off begin on the Team tier.

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.

Local notes for scaffolding work in Cardiff

Cardiff Council licenses scaffolding on the adopted highway under section 169 of the Highways Act 1980. The highway includes the pavement: this is not a separate carriageway-only permission. The council requires scaffolding companies to register before applying for a permit. For your Cardiff RAMS, record the actual licence reference, authorised location and dates, and relevant conditions from the council's decision. Check current application arrangements directly with Cardiff Council rather than relying on a fixed lead time. For Welsh and English signage, check the client's contract and the requirements applying to the project; public funding alone does not establish the same signage specification or cost for every site. Include the scaffold design reference and any site-specific wind, access or heritage constraints supplied by the competent designer and project team. A generic Cardiff Bay or listed-building description cannot establish the design for an individual scaffold.

Most common scaffolding rejection reason

Generic scaffold design references without naming the specific design used (TG20:21 compliant, or bespoke design by a named designer). RAMS that say 'scaffold to standard' are routinely rejected.

Same trade in other UK cities

Where to go next