For concrete contractors
Concrete safety file
Formwork that has to hold, silica when you cut it, and cement that burns skin quietly.
Generate your safety file — R500What the law requires
There is no separate safety file law for concrete contractors. The Occupational Health and Safety Act 85 of 1993 and the Construction Regulations 2014 are national and trade-neutral — they apply to concrete 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 concrete file are driven by the hazards concrete contractors actually create.
Why a concrete file is different
Concrete work carries one catastrophic risk and two slow ones. Formwork and falsework failure during a pour is the catastrophic one and is squarely a design and inspection issue. The slow ones — respirable silica from cutting and grinding, and cement burns — do their damage over months and are the ones commonly left out of a file.
What to get right in a concrete 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.
Formwork and falsework collapse
Regulation 12 of the Construction Regulations 2014 requires formwork and support work to be designed and inspected by a competent person, and inspected again immediately before the pour. Wet concrete loads change fast, and the pre-pour inspection record is the document that shows someone actually checked rather than assumed.
Respirable crystalline silica
Cutting, grinding, chasing and scabbling cured concrete releases respirable silica. This is a long-latency health risk, so it needs an exposure control approach — water suppression or extraction first, respiratory protection after — and a record showing which was used.
Cement burns and dermatitis
Wet cement is strongly alkaline and causes chemical burns through prolonged skin contact, often without immediate pain to warn the person. Kneeling in a pour is the classic mechanism. Barrier protection, washing facilities and a health and safety induction that actually mentions it belong in the file.
Documents a concrete scope typically triggers
On top of the core compliance pack every construction file carries, concrete contractors should expect to need these. The exact set depends on your scope.
- —Form-support work supervisor appointment (CR 12)
- —Formwork method statement (SWMS) and risk assessment
- —Concrete mixer checklist and risk assessment; batch plant appointments (CR 20)
- —Daily risk assessment, toolbox talk and site diary register
- —PPE issue register — waterproof gloves, knee protection, RPE
- —Formwork and support work design from the temporary works designer
*Items marked * are records you obtain from third parties and file alongside the documents MySafetyFile generates.
Which document is most often missing from a concrete contractor's file?
In practice, the pre-pour formwork inspection record. Formwork designs are usually present because they are produced up front and filed once, but the inspection immediately before the pour — the check that the thing built on site matches the design and is still sound — is the one that gets done verbally and never written down.
More background: what a construction safety file is and what a compliant template must contain.
Get your concrete 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.