Two identical condensate tanks stood on the same site when the cyclone came through.
One had its top stiffener ring fitted. One didn't.
Only one was still standing afterwards.
A gas project on the southern African coast. The second tank was almost complete. A long weekend was coming, and everyone was keen to get home to family.
We left site in perfect sunshine.
The tank crew were experienced, but from a different region. They weren't familiar with how quickly the weather on that coast can turn.
Other contractors on the same site were. They kept skeleton crews behind for exactly that reason. The tank crew was too small and too specialised for that. It was all on site, or none.
I had stayed local, visiting friends five hours' drive away. The storm built so quickly I barely made it back. For the last hour I drove on the wrong side of the road to dodge palm trees blowing across it, half blind in the rain, with gusts that nearly put the Land Rover on its side.
The first tank, with its ring on, came through without damage.
The second collapsed.
Same tank. Same site. Same storm. One ring.
When the site manager came back after the break, he stood there with his face in his hands. I will never forget it.
The hard part to accept is that the fix was cheap:
Tack the top ring on before leaving.
Or delay the break until it was on.
Neither was considered.
Not through carelessness.
The knowledge was on that site. It just never reached the one crew that needed it.
We worked out a plan to cut out the damaged sections, recover what we could, and replace the rest with the least disruption to the overall programme. The job kept going. But someone paid real money for knowledge that was already on site.
No system stops a cyclone.
What a system can do is turn what one team knows into a release condition for everyone doing the same work:
No tank shell is left over a break until its top stiffener ring is on.
Asked every time, by whoever is on site, wherever they're from.
That's how WorkClear treats lessons — as release conditions attached to the type of work, not paragraphs in a close-out report.
READINESS BEFORE RELEASE.
What's the most expensive thing your project ever learned from local knowledge it didn't have?
