The Site EHS Lead owns the program, which keeps EHS from spreading across the operation.

Earlier today, I came across an EHS Manager job posting for a Hillsborough, NJ site.

This was part of the responsibilities section:

“Review and update…”

“Design and deliver…”

“Monitor…”

“Implement and manage…”

“Develops and implements…”

Most sites handle this the same way.

A site EHS lead owns the program, sometimes with corporate support.

It puts responsibility on one role at the site, which keeps EHS from spreading across the operation.

There’s another way to set it up.

A team that drives execution across sites and builds EHS into the operation over time.

That leads to a different outcome.

If EHS sits with one role at your site, what’s the first thing that slips?

Cheers!

Brian