Most project risk registers have a line for weather delays, a line for material shortages, maybe one for labour availability. Spill containment rarely makes the list. That’s the gap worth closing. Across manufacturing, energy, logistics and heavy commercial builds, hazardous liquid handling has quietly become one of the more expensive things a project team can get wrong. Not because the chemistry is complicated. Because the fallout almost never stays contained to the spill itself.
Three shifts explain why this now belongs on a GC’s or facility owner’s radar instead of buried in a subcontractor’s method statement.
Regulation has stopped being background noise
Handling fuels, flammable liquids or other hazardous substances on a job site used to mean a spill kit in a cabinet and a line item in the safety plan. That’s a thinner cover than it used to be. Regulators in most jurisdictions now expect a facility to show, before anything goes wrong, what happens if a drum splits or a decanting line fails: where the liquid travels, whether it reaches a drain or open soil before anyone notices. That expectation looks different depending on where the project sits.
In the US, it mostly plays out through EPA Spill Prevention, Control and Countermeasure requirements plus state fire and environmental codes, increasingly checked at permitting stage rather than after the fact. Projects with an Australian footprint carry a separate obligation on top: AS 1940, the Australian standard for storage and handling of flammable and combustible liquids, which shapes bunding capacity, separation distances and containment layout from the design stage.
Well-specified, purpose-built bunding does more than satisfy that requirement on paper: it’s the difference between a contained incident that never leaves the site and one that reaches a drain or the local water table. A US contractor picking up a project with AU operations, or specifying gear for a client running both markets, needs containment built to whichever standard actually governs the site, not a generic spec that happens to satisfy neither.
A small incident rarely stays small
Here’s what tends to get underweighted on the estimating side: a modest contamination event, a few litres reaching soil, doesn’t behave like a modest problem. It can trigger remediation obligations, invite regulatory scrutiny well past the immediate footprint, and cost the project something harder to put a number on: the client relationship. Owners and developers increasingly weigh environmental compliance into who they’ll rebid with. The cleanup invoice lands fast. The reputational cost shows up three bids later, quietly, in a shortlist you didn’t make.
The spill was never the expensive part. Everything downstream of it is.
More contact points than the schedule usually accounts for
A typical site carries more spill points than most non-specialists assume. Fuel drums staged near equipment. Intermediate bulk containers waiting on a delivery window. Decanting and dispensing stations set up for the day’s pour or fabrication run. Picture a mid-size commercial build running three trades in parallel: a generator refuelling station near the site office, a fabrication bay running solvent-based coatings, and a delivery zone where IBCs sit for a day or two before they’re moved into storage. Three spill points, three different liquid types, and on most sites, one spill kit covering all of it by default rather than by design.
Each of those is a distinct exposure, and lumping them all under one generic bund or a shared spill kit is exactly where gaps open up. Acids, fuels and solvents behave differently against different containment materials; a solution rated for one chemical class can degrade against another well before anyone expects it to, sometimes within a single season. Matching the containment to the actual liquid, rather than defaulting to whatever’s on hand, is the one decision that consistently prevents a manageable spill from becoming a reportable one.
Containment is increasingly specified alongside racking, drum storage and access planning at the design stage rather than added after an audit finding. Teams are moving from spill kits as the main response toward permanent, purpose-built bunding specified from day one, and the sites that make that shift early tend to spend far less time explaining incidents to regulators later.
Why this earns a place in the risk register
None of these calls for anything dramatic. It calls for treating hazardous liquid storage the way project teams already treat schedule risk or supply chain risk: reviewed at planning stage, funded as part of the build rather than the punch list, specified against the actual liquids, volumes and layout on site rather than whatever happened to be lying around.
The teams managing this well aren’t doing anything unusual. They’ve stopped treating containment as an afterthought and started treating it as infrastructure, planned for rather than reacted to, wherever the project sits and whatever standard governs it. It costs less to settle this on next quarter’s risk register than to explain it to a client after the fact. Worth doing before an incident forces the conversation instead of after.




