Why one ANSI Z10 or ISO 45001 program often fails when it’s applied identically to fabrication and field crews
Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.
One Safety Management System. Two Completely Different Jobs.
You have OSHA compliance. You may already own several of the individual ANSI/ASSP and ANSI/ISEA titles that fill in the detail OSHA leaves out. What you don’t have — yet — is a safety management system that ties hazard identification, training, incident investigation, and continual improvement into one structure instead of a pile of separate documents.
If your operation runs only a shop, or only field crews, building that system is mostly a matter of picking a framework and writing it around one environment. If you run both, it gets harder — and this is the part many guides skip.
From the Floor: I’ve seen a corporate safety team try to run one safety management system across both a fabrication shop and a field crew, using the same procedures for both. It didn’t hold up. A shop environment is fixed, controlled, and repetitive — the hazards are largely the same from one day to the next. A field crew works a different site every few weeks, with hazards that change with the scope, the weather, and who else is on site. The company had one system built around one set of assumptions, and it fit neither environment well. The fix wasn’t more procedure — it was recognizing the two operations needed a shared framework with separate execution, not one identical set of documents.
👉 If you run both a shop and a field crew, the fastest way to see where a single system would break is to run both compliance checklists and compare the gaps side by side. Start with the Manufacturing Compliance Checklist for the shop and the Construction Compliance Checklist for the field — the differences between the two results are exactly where a shared system needs separate execution →
Quick Answer: What Should You Actually Build?
| If your situation is… | Do this |
|---|---|
| One site, shop only | Build your framework and procedures around the shop environment — the two layers described below can be integrated more closely |
| One site, field crews only | Build the framework once, but expect site-specific procedures to change with every job |
| Both a shop and field crews under one company | Build one shared framework (hazard ID, investigation, training records), then require a separate site-specific procedure set for each environment |
| Deciding between ANSI Z10 and ISO 45001 | See our ISO 45001 vs ANSI Z10 guide first — this article assumes you’ve picked a direction |
| Not sure if you need a formal system at all | Run a compliance checklist first and see how many gaps trace back to “no system,” not just missing paperwork |
In This Guide
- What a safety management system actually is (and what it isn’t)
- ANSI Z10 or ISO 45001 — which framework, briefly
- Why the shop and the field need different execution, not different rules
- Building one framework with two layers
- “We already follow OSHA — why do we need a management system on top of that?”
- Getting started: gap assessment before you build anything
- Quick readiness checklist
- FAQ and free resources
Table of Contents
👉 Start Here (Top Resources)
If you’re ready to formalize a safety management system, BSI Group’s ISO 45001 training and ISOQAR’s ISO 45001 courses are the two providers we recommend for teams building the framework for the first time — both offer implementation and internal auditor training.
If you want to read the standard itself before committing to a training provider, [ANSI/ASSP Z10.0-2019 — ANSI Webstore] is the U.S. voluntary consensus framework, and [ISO 45001:2018 — ANSI Webstore] is the internationally certifiable one. Use code CC2026 for an additional 5% off at checkout through December 31, 2026 — apply the coupon here.
What a Safety Management System Actually Is
OSHA regulations set the legal floor. Individual ANSI titles — Z87.1, Z359, Z244.1, and the rest — supply the equipment and hazard-specific detail OSHA doesn’t spell out. Our guide to buying ANSI safety standards covers that layer.
A safety management system is the layer above both of those. OSHA establishes the regulatory requirements. Individual ANSI/ASSP and ANSI/ISEA standards provide technical requirements for particular hazards, equipment, or activities. A safety management system connects those requirements to the way your organization identifies hazards, assigns responsibility, trains people, investigates incidents, tracks corrective action, and reviews performance — instead of a compliance binder and a stack of individually purchased standards that don’t talk to each other. Without it, you can be fully OSHA-compliant, own every relevant ANSI title, and still have no way to see that the same near-miss is happening at three sites for three different documented reasons.
Two prominent frameworks in the U.S. are ANSI/ASSP Z10.0, the voluntary domestic standard, and ISO 45001, the internationally recognized management-system standard that can be certified by an accredited third-party certification body.
ANSI Z10 or ISO 45001?
Both frameworks cover the same ground — policy, planning, hazard identification, implementation, evaluation, and management review — using a structure similar to ISO 9001 and ISO 14001. The difference that actually matters is certification: ISO 45001 can be certified through an accredited third-party certification body, and ANSI Z10 cannot. If a customer prequalification packet or an insurance application asks whether you hold ISO 45001 certification by name, a Z10-aligned program — however well it runs internally — doesn’t check that box.
ASSP describes Z10 as a systems-based standard organizations can customize to their own needs — the flexibility that makes the shop/field split in this article possible in the first place. This article assumes you’ve made the Z10-or-45001 call, or don’t need to yet. Our full ISO 45001 vs ANSI Z10 comparison walks through certification, cost, and global recognition in depth if you haven’t, and our ISO 45001 Certification Guide covers the certification path itself once you’re ready to move.
Why the Shop and the Field Need Different Execution
A framework document doesn’t know the difference between a fabrication shop and a jobsite. The people running it have to build that difference in.
| Category | Fabrication / Shop | Field / Jobsite |
|---|---|---|
| Hazard profile | Largely fixed — the same machines, materials, and processes day to day | Changes with every job — new site, new scope, new neighbors |
| Site control | Controlled access, consistent layout | Multi-employer sites, public exposure, layout changes weekly |
| Environmental conditions | Climate-controlled, consistent lighting and footing | Weather, terrain, and lighting vary by site and season |
| Procedure cadence | Written once, reviewed periodically | A new pre-task plan or JSA for each activity, sometimes each day |
| Training delivery | On-site, recurring, same instructors and equipment | Mobile — delivered by crew leads, often across subcontractor personnel |
| Emergency response | One fixed plan, one facility | A different rescue and evacuation plan for every site |
If you are running only one of these environments → your system-level framework and your site-specific procedures can be integrated more closely, because the environment doesn’t change under you. If you are running both → treating them as one document is what breaks first, usually during the next incident investigation or the next customer audit, whichever comes first.
Building One Framework With Two Execution Layers
The fix from the From the Floor story wasn’t writing more procedure. It was splitting the system into two layers that stay connected but don’t try to be the same document.
Layer 1 — Shared framework (write once, apply everywhere):
- Hazard identification and risk assessment methodology
- Worker participation and communication
- Incident investigation and root cause process
- Training record system and competency requirements
- Corrective action and management review process
- Leading and lagging indicators tracked the same way at every site
Layer 2 — Site-specific execution (write separately, per environment):
- Job safety analyses or pre-task plans (field) vs. standard operating procedures (shop)
- PPE selection matrices, matched to the actual hazards present
- Emergency response and evacuation plans specific to the location
- Subcontractor and multi-employer coordination (field only)
- Housekeeping, machine guarding, and layout-specific controls (shop only)
If you already have OSHA-compliant procedures for both environments → much of Layer 2 likely already exists in some form. The work is auditing it against a common Layer 1 methodology, not starting over — our guide to ISO 45001 documentation requirements covers what that audit should actually look for. If you are building both layers from scratch → build Layer 1 first. A site-specific procedure written before the shared framework exists usually has to be rewritten once the framework defines how hazards get identified and ranked.
Common finding in practice: an operation with both a shop and a field crew builds strong site-specific procedures in both places, independently, with no shared incident investigation or training-record structure connecting them. Each environment looks compliant on its own. Neither one feeds the other, and the company has no way to see a pattern until it repeats at a third site.
“We Already Follow OSHA — Why Do We Need a Management System on Top of That?”
This is the same objection covered in our ISO 45001 vs OSHA guide, and it deserves a straight answer here too.
OSHA requirements apply to the workplaces, operations, and activities covered by the applicable standards, and OSHA’s own recordkeeping rules distinguish between establishments while allowing certain records to be maintained centrally. What OSHA requirements do not provide by themselves is your company’s management-system architecture for aggregating hazards, investigations, corrective actions, and improvement activities across different operating environments, or the structure your organization may need to demonstrate continual improvement to customers, insurers, leadership, or other interested parties. A formal management system does that — and in practice, that gap is often the difference between a safety program that satisfies your own team and one that satisfies someone else’s prequalification checklist.
The better question is not whether OSHA compliance is enough on its own. It’s whether you can currently answer, in writing, why the same type of incident happened at two different sites for two different documented reasons — and whether anyone would catch that before a third one happens.
Getting Started: Run a Gap Assessment Before You Build Anything
Don’t draft a management system from a blank page. Find out what you already have first.
If your safety program lives mostly on the jobsite → start with the Construction Compliance Checklist. If it lives mostly in the shop → start with the Manufacturing Compliance Checklist. If you are running both → run both, then compare the two results side by side. The gaps that show up in one checklist but not the other are exactly where Layer 2 needs separate execution. The gaps that show up in both — usually around documentation, training records, or incident tracking — are your Layer 1 candidates.
Once you know where the gaps actually are, BSI and ISOQAR both offer ISO 45001 implementation and internal auditor training built around closing exactly that kind of gap.
✅ Quick Readiness Checklist
✅ You can name which framework you’re building to — ANSI Z10 or ISO 45001 — and why
✅ You know whether your operation is shop-only, field-only, or both ✅ A gap assessment has been run against current procedures, not assumed from memory
✅ Hazard identification, incident investigation, and training records use one methodology across every site
✅ Site-specific procedures exist separately for each distinct operating environment
✅ Leading and lagging indicators are tracked the same way everywhere, so patterns across sites are visible
✅ Someone outside the safety team (ops, quality, or leadership) has reviewed the system, not just the site procedures
FAQ
What is a safety management system?
A safety management system is a structured approach for managing occupational health and safety through connected processes — hazard identification, worker participation, training, incident investigation, corrective action, and management review — rather than relying on OSHA compliance and individual equipment standards alone. ANSI Z10 and ISO 45001 are two established frameworks that can be used to structure that approach, though an organization can run an effective system without formally adopting either.
Is ANSI Z10 or ISO 45001 required by OSHA?
Neither is required by OSHA directly. Both are voluntary consensus frameworks. OSHA regulations remain the legal floor; a management system sits above that floor and is typically adopted for internal governance, customer requirements, or certification, not because a regulation mandates it.
Can one safety management system cover both a fabrication shop and field crews?
The overall framework — hazard identification methodology, incident investigation, training records, management review — can and should be shared across both. The site-specific procedures underneath it, such as job safety analyses, PPE selection, and emergency response plans, need to be built separately for each environment because the hazards and conditions are genuinely different.
Do I need to be certified to have a safety management system?
No. You can build and run an ANSI Z10-aligned system without any third-party certification, since Z10 isn’t certifiable. ISO 45001 can be run the same way internally, or certified through an accredited body if a customer, insurer, or your own strategy requires it.
How is a safety management system different from just following OSHA regulations?
OSHA regulations establish requirements for the workplaces, operations, and activities covered by the applicable standards. A management system aggregates what happens across those environments into one structure, so patterns in incidents, near-misses, and corrective actions can be identified instead of remaining separated in individual site records.
How long does it take to build a safety management system?
It depends heavily on how much of Layer 2 — your site-specific procedures — already exists in some usable form, and how many sites or operating environments you’re consolidating. Building the shared framework from scratch can take longer than expected if a gap assessment hasn’t been run first; skipping that step is a common source of a longer timeline.
Does a safety management system replace individual ANSI safety standards like Z87.1 or Z359?
No. Individual ANSI/ISEA and ANSI/ASSP titles supply equipment and hazard-specific requirements — what PPE to select, how to inspect fall protection equipment. A management system is the structure that governs how those requirements get identified, trained on, and tracked across your operation. You need both.
Can a small company build a safety management system without hiring a consultant?
Many do, particularly for an ANSI Z10-aligned system with no certification goal. A gap assessment, a clear framework choice, and structured training — through BSI or ISOQAR — cover much of what a consultant would otherwise be hired to do. Certification to ISO 45001 through an accredited body is a separate step and typically involves an external audit regardless.
📥 Free Resources
Construction Compliance Checklist — 81-item jobsite self-assessment covering OSHA 1926, ANSI/ASSP consensus standards, quality flow-downs, environmental permits, and subcontractor management, for contractors and fabrication crews working in the field
ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system
Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments
Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts
Not Sure What to Do Next?
🔹 Still deciding which framework fits? Read the ISO 45001 vs ANSI Z10 guide and the ISO 45001 vs OSHA guide before you commit to a direction.
🔹 Ready to formalize, and you run only one environment? Run the Construction Compliance Checklist if you’re field-based, or the Manufacturing Compliance Checklist if you’re shop-based, then build your framework around what it finds.
🔹 Running both a shop and field crews, and ready to build the shared framework? Run both checklists, compare the results, and use BSI or ISOQAR training to formalize the shared layer once you know where it needs to hold both environments together.
A safety management system earns its name by working the same way everywhere it’s checked — not by being the same document everywhere it’s read. The Standards Navigator covers exactly this space: which framework, how to structure it across more than one kind of operation, and where the line is between a shared system and a document that only looks like one.
The Safety Program Built to Look Compliant, Not to Actually Connect
Operations that struggle here build strong procedures at each site independently and never connect them — every location passes its own audit, and nobody can see the pattern repeating across all three.
Operations that get it right build one hazard identification and investigation methodology first, then let the site-specific procedures underneath it differ by environment. When an auditor or a customer asks how a shop incident and a field incident get tracked, the answer is the same system, not two different binders.
The Standards Navigator covers exactly this space — ANSI Z10, ISO 45001, and the structure that holds a safety management system together across fabrication and field operations.
👉 Get updates on ANSI Z10 and ISO 45001 management system requirements as they change
👉 Be first to access new compliance checklists and safety management system tools
Industrial Compliance. Clearly Explained.