Professional review status
No professional domain review recorded
This bundle covers safety, regulatory subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: A qualified safety or compliance professional appropriate to the question, decision, organization, and jurisdiction.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
A warehouse manager says an employee was hospitalized after a forklift-related incident yesterday. The manager asks whether OSHA must be notified and whether the event must go on the OSHA log. The manager has not provided the state, employer size, industry classification, establishment facts, medical-treatment details, incident timing, hospitalization.
Without the bundle
You probably need to notify OSHA and record the incident because an employee was hospitalized. Fill out the OSHA log and call OSHA as soon as possible. Review forklift safety procedures and retrain the team.
Using the bundle
Direct Answer This is an OSHA recordkeeping/reporting issue, but the conclusion is provisional and blocked by missing facts. A work-related in-patient hospitalization may trigger OSHA reporting, and a recordable injury may belong on OSHA recordkeeping forms, but the answer depends on current 29 CFR Part 1904 source inspection, state-plan status, and incident-specific facts. Source Note Official source categories needed: OSHA recordkeeping/reporting resources and current eCFR 29 CFR Part 1904; OSHA state-plan sources if the workplace is in a state-plan jurisdiction. User evidence provided: a forklift-related hospitalization occurred yesterday.
Why this is better: The bundle-assisted output is stronger because it gives a direct provisional answer, names official source categories, separates user evidence from missing evidence, distinguishes reporting and recordkeeping, requires state-plan checks, and sets a professional-review and confirmation boundary. This example is illustrative only. It is not a measured baseline-vs-OKB score.
Inspect this example in the repositoryOverview
OSHA Overview
Defines the source scope, applicability framing, and safety boundaries for OSHA compliance work.
Read the fileRequirements map
OSHA Source and Standard Map
Maps common OSHA question types to official source categories and evidence needs.
Read the fileWorkflow
OSHA Obligation Triage
source-backed workflow for turning an OSHA question into an evidence-backed compliance brief.
Read the fileTemplate
source-backed OSHA Compliance Brief
Output format for OSHA answers that separate official sources, workplace evidence, assumptions, and missing verification.
Read the fileIs this bundle right for your task?
Who it is for
- Compliance, legal, risk, security, operations, and product teams assessing OSHA (Occupational Safety and Health Administration)
- Teams working in manufacturing, construction, logistics
When to use it
- An OSHA (Occupational Safety and Health Administration) question needs to be scoped to the correct rule, guidance, regulator, date, and affected entity.
- A draft conclusion needs its stated facts, missing evidence, source citations, and professional-review handoff checked.
What you need to provide
- The jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer.
- Current official sources plus the policies, contracts, records, system evidence, and missing facts relevant to the situation.
Tasks and expected outputs
Questions it helps answer
- Triage OSHA questions without inventing legal or safety conclusions.
- Separate official OSHA and eCFR sources, user-provided workplace evidence, assumptions, and missing evidence.
- Route questions to federal OSHA, state-plan, recordkeeping/reporting, poster, industry-standard, hazard-specific, or enforcement source categories.
- Produce source-backed OSHA compliance briefs for professional review.
What it helps produce
- source-backed OSHA compliance brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer. Ask the agent to assess OSHA (Occupational Safety and Health Administration) and draft source-backed OSHA compliance brief that separates stated facts, assumptions, missing evidence, relevant source sections, and actions requiring professional approval. Begin with OSHA Laws and Regulations, then confirm that the reference is current and applicable. Inspect OSHA Overview before drafting.
Context path: bundles/compliance/osha
What the bundle includes
Frameworks
- source-evidence matrix
- OSHA source-family triage
- workplace applicability check
Evaluations
- OSHA source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Final legal or compliance conclusions, filings, notices, or operational changes without current source review and accountable professional approval.
Known limitations
- This bundle is a compliance hub, not legal advice, safety engineering advice, or a complete rule-by-rule OSHA treatise.
- Scenario-specific answers require current official sources, workplace facts, hazard or incident evidence, state-plan checks when relevant, and qualified professional review.
- State-plan rules, penalties, deadlines, exemptions, exposure limits, and required controls must be inspected before reliance when relevant.
Safety notes
- Require qualified legal, safety, industrial hygiene, compliance, HR, operations, or incident-response professional review before relying on outputs for regulatory, enforcement, reporting, citation, or workplace-control decisions.
- Do not request, expose, or publish personal employee data, medical details, incident records, or employer confidential information beyond what is necessary for the user-approved analysis.
- Require explicit confirmation before submitting reports, contacting OSHA or a state-plan authority, changing workplace controls, changing policies, exporting records, or modifying live systems.