Home · Insights · Safety

Lessons from the George building collapse: what a safety system is meant to catch

The investigation found the collapse entirely preventable. Read against ISO 45001, every documented failure corresponds to something a management system is designed to catch.

Key takeaways

  • On 6 May 2024 a building under construction in George collapsed, killing 34 people and injuring 28.
  • The government-led investigation concluded the collapse was entirely preventable.
  • Structural warnings were raised in 2023. Site managers directed temporary patching rather than stopping work for inspection.
  • The appointed structural engineer did not hold the qualifications required for a multi-storey development.
  • Concrete in the floor slabs measured 13 MPa against a required range of 19 to 25 MPa.
  • Every one of those findings corresponds to a clause of ISO 45001. None of them required specialist knowledge to catch.

On 6 May 2024, a five-storey apartment building under construction in George collapsed. Thirty-four people died. Twenty-eight were injured. Most of those killed were construction workers on shift.

A government-led investigation later concluded that the collapse was entirely preventable.

Writing about a disaster carries an obligation, so let us be clear about the purpose. Investigations exist so that what was learned is used. Every documented finding in this one describes something that a functioning occupational health and safety management system is specifically designed to catch, and there are sites across South Africa where the same conditions exist today. Setting the findings against ISO 45001 is not an academic exercise. It is the reason the investigation was conducted.

Nothing here suggests a certificate would have saved anyone. It would not have. What follows is about the obligations a system creates, and what happens when they are absent.

What the investigation found

The failures were multiple rather than singular, which is almost always the case. A structure does not fall because of one mistake. It falls because several controls that should have been independent all failed together.

Documented findingISO 45001 clauseWhat the system requires
Cracks in columns, wall perforations and noticeable vibrations raised as early as 20236.1.2 Hazard identificationHazards must be identified and assessed on an ongoing basis, not only at design stage
Site managers directed temporary patching with sand and mortar instead of halting work for inspection5.4 Consultation and participation
8.1.1 Operational control
Workers must be able to report hazards and remove themselves from danger without reprisal. Work must stop when a control is in doubt
Appointed structural engineer did not hold the qualifications required for a multi-storey development7.2 CompetenceCompetence must be determined against the actual work and evidence retained. Not assumed from a title
The framework permits engineers to self-declare competency8.1.4 Procurement and contractorsWhere a control depends on an external party, the organisation remains responsible for verifying it
Concrete in floor slabs at 13 MPa against a required 19 to 25 MPa9.1 Monitoring and measurementCritical parameters must be measured, and results acted on when they fall outside specification
Inadequate supervision and protocols not followed5.1 Leadership
10.2 Nonconformity
Leadership is accountable for the system actually operating, and departures must be corrected

Read the middle column. There is nothing exotic in it. These are the ordinary clauses of a standard that has been in use since 2018, and the obligations they create are the ones every certified organisation is audited against.

The finding that matters most

Of everything in the investigation, one finding is more transferable than the rest, and it is not the concrete strength.

Structural warning signs were raised in 2023, and the instruction was to patch them. Cracks in columns. Perforations in walls. Vibrations that people could feel. These were reported. Somebody looked at them, and the decision was to make the symptom disappear using sand and mortar rather than to stop and find out what was causing it.

That is not a technical failure. It is a decision about what a warning means.

We have written before about the near-miss process, and about the fact that a rising number of reported near-misses is usually a sign of a healthy system rather than a failing one. This is the inverse case, and it is the more common one. A warning was raised, and the organisational response was to remove the evidence of it.

The reason the ISO 45001 health and safety standard puts worker consultation at clause 5.4, near the front rather than buried in the operational detail, is precisely this. The people on the site saw the cracks. The standard requires that they can report a hazard, that reporting is acted upon, and that they can remove themselves from a situation they believe is dangerous without fear of reprisal. That requirement is not administrative. It exists because the people closest to the work see the first evidence, and because organisational pressure to keep going is the normal condition on any site running to a deadline.

Competence, and the danger of assuming it

The second finding with broad application concerns the structural engineer, who the investigation found did not hold the qualifications required for a development of that type. The investigation also noted that the current South African framework allows engineers to self-declare their competency, a gap now under review.

For any organisation appointing specialists, that is worth sitting with. If the regulatory framework permits self-declaration, then the verification either happens inside your own management system or it does not happen at all.

ISO 45001 clause 7.2 requires an organisation to determine the competence necessary for work that affects safety performance, to ensure people are competent on the basis of education, training or experience, and to retain documented evidence of it. Clause 8.1.4 extends the same discipline to contractors and procurement: where you rely on an external party for a control, you remain responsible for confirming that the control is real.

In practice, most organisations file a CV and a professional registration number and consider the obligation discharged. The standard asks for something more deliberate: competence determined against the specific work being done, not against a job title.

Why several controls failed at once

It is tempting to treat the concrete strength as the cause. It was not. It was one of several independent controls that should have operated separately and did not.

Materials testing should have caught 13 MPa concrete. Supervision should have caught workmanship departures. Competence verification should have caught the engineer's qualifications. Hazard reporting should have caught the cracks. Any single one of those, working properly, would have created an opportunity to stop.

This is what a management system is actually for, and it is the part that is hardest to explain to somebody who sees certification as paperwork. The value is not in any individual control. It is in having several of them, operating independently, so that the failure of one is caught by another. When an organisation's controls exist only on paper, they fail together, because none of them were really running.

What to take from this onto your own site

Three questions, all answerable this week.

When someone reports a structural or safety concern, what actually happens? Not what the procedure says. What happened the last time. If the honest answer is that it was noted and work continued, that is the George pattern.

How do you verify the competence of the specialists you appoint? If the answer is that you rely on their own declaration, you are carrying a risk the framework does not carry for you.

Which of your critical parameters are actually measured, and what happens when a result comes back out of specification? A test that is performed but not acted on is worse than no test, because it creates a record that the organisation knew.

Thirty-four people died in George, and the investigation concluded it did not have to happen. The most respectful use of that conclusion is to check whether the same conditions exist where you work.

Synergy Consilium is a management-systems consultancy. We work with businesses in engineering, manufacturing and construction on ISO 45001 and integrated management systems. If anything here raises a question about your own operation, you are welcome to contact us.

Frequently asked questions

What happened at George?
On 6 May 2024, a five-storey apartment building under construction in George, Western Cape, collapsed. Thirty-four people died and twenty-eight were injured. A government-led investigation concluded that the collapse was entirely preventable.
What did the investigation find?
Multiple failures rather than a single cause: concrete in the floor slabs at roughly 13 MPa against a required 19 to 25 MPa, structural warning signs raised in 2023 and patched over rather than investigated, a structural engineer without the qualifications for a multi-storey development, inadequate supervision, and construction protocols that were not followed.
Would ISO 45001 certification have prevented it?
That is the wrong question, and it deserves an honest answer. A certificate prevents nothing. What ISO 45001 provides is a structured obligation to identify hazards, verify competence, act on warnings and record what was done. Every one of those obligations was engaged here. A system that was genuinely operating would have made several of these failures much harder to sustain.
What is the single most transferable lesson?
That visible cracks reported in 2023 were treated as a cosmetic problem and patched with sand and mortar. That decision, to make a warning sign disappear rather than investigate it, is the failure most likely to be repeated on any site.
What does the competency finding mean for other businesses?
The investigation noted the appointed engineer lacked the required qualifications, and that the South African framework allows engineers to self-declare competency. For any business appointing specialists, it establishes that accepting a self-declaration without verification is a real exposure. ISO 45001 clause 7.2 requires competence to be determined and evidence retained.
Does this apply outside construction?
Yes. The pattern of a warning being suppressed rather than investigated, and of competence being assumed rather than verified, is not specific to construction. It appears in manufacturing, mining, engineering and processing operations in the same form.

Reading up because you have a decision to make?

Skip ahead. An obligation-free consultation gives you the honest answer for your specific business.

087 150 3022