ISO 45001 vs ANSI Z10 vs ILO-OSH: Which System Fits Best?

Choosing between ISO 45001, ANSI/ASSP Z10, and ILO-OSH 2001 is not a branding exercise. The real decision is whether the organization needs a certifiable global management system, a US-centered operating standard, or a policy framework that keeps health and safety visible across countries and functions.

Across 25+ years leading EHS at multinationals, Andreza Araujo has seen leaders confuse the label with the result. In Safety Culture: From Theory to Practice and A Ilusao da Conformidade, she keeps returning to the same point: a standard matters only when it changes repeated decisions in the field, and not when it simply improves the look of the slide deck.

This article is for plant managers, EHS executives, and operations leaders who need a decision they can defend. During her tenure at PepsiCo South America, where the accident ratio fell 50% in six months, Andreza Araujo learned that standards only work when leaders keep asking what changed in the work front, who owns the barrier, and how the field proves it.

What decision are you making?

The first mistake is to treat the three options as if they were interchangeable. They are not. ISO 45001 is built for a certifiable management system with a global audit language. ANSI/ASSP Z10 is a US consensus standard for occupational health and safety management systems. ILO-OSH 2001 is guidance for designing an OHS system, which makes it useful for policy and governance even though it is not a certification path.

The better question is simpler. Do you need an external credential, a management system that travels well across sites, or a policy backbone that helps the organization define roles, participation, and review without pretending that the paper itself is control? If the company cannot answer that question, the standard will become a logo exercise instead of an operating choice.

The article Risk Management: 6 Decisions That Turn Control into Theater is a useful companion because the same failure appears here. A team can approve the framework, fill the slide, and still miss the fact that the field did not change.

ISO 45001

ISO 45001:2018 works best when the organization needs a shared language across multiple sites, suppliers, and auditors. It gives leaders a disciplined way to define context, leadership, worker participation, hazards, risks, objectives, documented information, internal audit, and management review. That structure matters when the business wants the same operating logic in more than one country.

Its strength is not only the certificate. It is the forcing function that pushes the company to connect policy, planning, support, operation, evaluation, and improvement in one loop. When leaders use it properly, the standard makes weak ownership visible, because a site cannot hide behind local habits once the management system asks for repeatable evidence.

The trap is obvious in the field. A certificate can coexist with weak contractor control, rushed permits, and a green dashboard that hides drift, which is why the article on Safety Indicators and Metrics: 5 Blind Spots That Hide Control Drift belongs in the same conversation. The standard is not the control. It only tells you what kind of control the company says it wants.

As Andreza Araujo argues in A Ilusao da Conformidade, compliance is useful only when it stays connected to the real work. If the organization uses ISO 45001 to decorate the audit room while supervisors still improvise on the floor, the system has chosen theater over discipline.

ANSI/ASSP Z10

ANSI/ASSP Z10 is strongest when the company is US-based, engineering-heavy, or already speaks in the language of management responsibility, design, and continuous improvement. It can feel closer to plant reality than a generic compliance checklist, especially when the operation wants a voluntary standard that frames safety as a management system rather than as a poster campaign.

For a manufacturing site that needs to tie leadership, design changes, and operational accountability together, Z10 can be a better conversation starter than a broad legal summary. The standard helps the organization ask how work is designed, how decisions move, and how management reviews the controls it claims to own.

The risk is adoption without context. A multinational can import ANSI/ASSP Z10 and still fail to build enough local buy-in, because the credibility of the standard outside the US is narrower and the internal team may never fully translate it into supervisor routines. The article on Safety Culture: Survey vs Maturity vs Field Evidence matters here because a name on the wall is not maturity, and a maturity label is not proof that the field changed.

ANSI/ASSP Z10 also rewards leaders who care about prevention through design, hierarchy of controls, and direct management ownership. That makes it a strong fit when the board wants the conversation to move away from recordkeeping and toward the decisions that shape the work before exposure exists.

ILO-OSH 2001

ILO-OSH 2001 is a different tool altogether. It is a guideline for occupational safety and health management systems, which makes it especially useful when the company wants a policy backbone that respects participation, social dialogue, and country-to-country consistency. It is often the right language for global groups that need an internal framework before they need a market credential.

Its strength is organizational breadth. Because it is not trying to be a certificate factory, it can help leaders build an OHS system that fits public policy, labor relations, and multinational governance without making the operation look more mature than it really is. In a company that needs a common frame across regions, that flexibility has value.

The trap is equally clear. If leaders treat ILO-OSH as if it were a finished control system, the organization can end up with good policy and weak verification. The article How to Run a Hazard Communication Review in 30 Minutes is relevant because the same gap appears whenever documentation outruns the field.

James Reason is useful in this conversation because latent conditions do not disappear when the governance model sounds respectable. A guideline can support the system, but only repeated field checks show whether the barrier really exists.

Decision matrix

The right choice becomes clearer when the criteria are laid out side by side. The table below is less about prestige and more about fit, because a standard that sounds strong can still be the wrong instrument for the decision the company actually needs to make.

The article on risk management theater fits naturally here because the same comparison applies to standards. The label only matters if the work changes after the label is adopted.

Which one fits which operation?

Choose ISO 45001 when the company needs certification, supplier assurance, or a common system that can be explained to customers and auditors across regions. Choose ANSI/ASSP Z10 when the operation is mainly US-based and leadership wants a management standard that speaks directly to design, accountability, and prevention. Use ILO-OSH 2001 when the organization needs a policy backbone that supports participation, governance, and cross-border consistency.

If the company wants maturity rather than a logo, it should pair any of the three with field evidence, decision rights, and a cadence that forces leaders to test the controls they claim to own. That is why the article on Safety Culture: Survey vs Maturity vs Field Evidence belongs beside this one. The standard can organize the system, but culture determines whether the system becomes real.

For board and executive teams, the practical filter is this. If the goal is market trust, start with ISO 45001. If the goal is sharper operating discipline in US plants, start with ANSI/ASSP Z10. If the goal is a cross-country governance frame that respects social dialogue, start with ILO-OSH 2001.

What leaders should do in 30 days

First, decide what problem the standard is supposed to solve. Certification, global alignment, and local operating discipline are not the same goal, and a company that blurs them will choose the wrong tool.

Second, map three live pain points and test each one against the candidate standard. A permit that is rushed, a contractor interface that is weak, or a supervisor routine that never reaches the field will tell you more than a presentation ever will.

Third, pair the chosen standard with one live verification routine. The article on how to run a hazard communication review in 30 minutes is a practical model because it shows how a short field check can expose whether the system still matches the work.

• Write the decision the standard must support.
• Check whether the current team can sustain the discipline it requires.
• Assign one owner for implementation and one owner for field verification.
• Define one indicator that will show whether the work changed.
• Review the result with leadership after 30 days, not after the annual audit.

Final recommendation

There is no universal winner. ISO 45001 is the best fit when the company needs a recognized certification path and a stable global management system. ANSI/ASSP Z10 is the better fit when the operation is US-centered and wants a sharper management standard for engineering and leadership decisions. ILO-OSH 2001 is the better fit when the organization needs a policy and governance backbone that can support participation across countries.

The deeper lesson is the one Andreza Araujo keeps repeating in Safety Culture: From Theory to Practice. A standard does not create safety by itself. It only works when leaders use it to change repeated decisions, test the field, and close the gap between what the system says and what the work still needs.

If your team needs help turning this choice into operating discipline, start with Andreza Araujo's books at Andreza Araujo's store and move the conversation from labels to field control.