Civil safety file

Excavations, heavy plant and everything already buried under the site.

Generate your safety file — R500

What the law requires

There is no separate safety file law for civil contractors. The Occupational Health and Safety Act 85 of 1993 and the Construction Regulations 2014 are national and trade-neutral — they apply to civil work exactly as they apply to every other trade on a South African site, with no minimum project size exemption.

What changes with the trade is the content. The regulations require the file to reflect the work actually being carried out, so the risk assessments, method statements, appointments and registers in a civil file are driven by the hazards civil contractors actually create.

Why a civil file is different

Civil work concentrates the hazards that kill people on South African sites: ground that collapses, machines that cannot see a person standing beside them, and services buried where nobody expected them. The file is heavier on excavation and plant documentation than almost any other trade.

What to get right in a civil safety file

These are the hazards that should be reflected properly in the risk assessments and method statements — the parts of the file that are easiest to leave generic and hardest to defend when they are.

Excavation collapse

Regulation 13 of the Construction Regulations 2014 requires excavation work to be under the supervision of an appointed competent person, with the sides made safe by shoring, benching or battering. The excavation inspection record is a daily document, not a once-off, and inspectors treat a gap in it as a gap in the control.

Buried services

Striking a live cable, a water main or a gas line is a routine civil incident and an avoidable one. A service location exercise before breaking ground, and a record of it, is what separates a controlled dig from a lucky one.

Plant and people sharing ground

Excavators, TLBs and tippers operating where people are working on foot is the defining risk of a civil site. Your file needs a traffic management arrangement showing segregation, banksman duties and reversing controls — not just an operator's licence copy.

Documents a civil scope typically triggers

On top of the core compliance pack every construction file carries, civil contractors should expect to need these. The exact set depends on your scope.

  • Excavation supervisor appointments (CR 13, CR 13.1)
  • Excavation and trenching procedure, method statement and risk assessments
  • Underground utility scanning procedure
  • Traffic management plan and street works procedure
  • Vehicle and compaction equipment checklists; construction vehicle appointments (CR 23)
  • Operator licences and medical certificates of fitness, recorded against the training register

*Items marked * are records you obtain from third parties and file alongside the documents MySafetyFile generates.

How deep does an excavation have to be before it needs a competent person?

The Construction Regulations 2014 do not set a single depth at which supervision starts and below which nothing is required — excavation work must be carried out under the supervision of an appointed competent person, who assesses the ground and decides what support the sides need. Treating any excavation a person can enter as needing that assessment is the defensible position, and it is what your file should reflect.

More background: what a construction safety file is and what a compliant template must contain.

Get your civil safety file in 8 minutes

MySafetyFile generates a complete, site-specific construction safety file — drawn from a library of 351 documents across 9 categories — in about 8 minutes for R500. Register free, enter your project and scope, and download a file that is ready to print or submit. There is no monthly fee, and one account handles unlimited projects.

Every document is aligned with the OHS Act and Construction Regulations 2014, developed by a SAIOSH-registered practitioner, and carries a unique identification code that ties it to the account and project it was generated for.