Determine the OSHA hexavalent chromium (Cr(VI)) exposure requirements that apply to a welding operation, citing the correct standard for the work setting.
domain: ecfr.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify which standard applies to your setting: 29 CFR 1910.1026 (general industry), 1915.1026 (shipyards), or 1926.1126 (construction) — welding/cutting/brazing on chrome-containing alloys (e.g., stainless) can generate hexavalent chromium fume in any of these settings depending on the worksite.
Pull the current regulatory text from eCFR (ecfr.gov, Title 29) rather than a summary blog — confirm the permissible exposure limit (5 µg/m³ 8-hr TWA) and action level (2.5 µg/m³ 8-hr TWA) directly from the current rule text.
Check the standard's requirements for exposure monitoring, medical surveillance triggers, respiratory protection, and employee training — these differ somewhat between the general-industry and construction versions.
Cross-reference OSHA's own compliance page (osha.gov/hexavalent-chromium) for a plain-English explanation, but treat the eCFR text as the binding source for compliance decisions.
Confirm whether OSHA's National Emphasis Program for hexavalent chromium affects inspection likelihood for your industry/process.
Known gotchas
Don't cite only the general-industry standard (1910.1026) for a construction-site welding job — 1926.1126 is a distinct, separately numbered construction standard with its own text.
PEL/action-level figures can move between rule amendments — always confirm against the current eCFR text rather than a cached number from an older article.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?