How we write about safety and regulation
We publish guidance on OSHA recordkeeping, hazard analysis and incident classification. Those are subjects where being confidently wrong causes real harm, so here is exactly how the content is produced, checked and corrected.
We cite primary sources
Regulatory statements cite the regulation, not a summary of it. Where a guide states what OSHA requires, it links to the relevant section of 29 CFR Part 1904 or to OSHA's own published guidance, and every guide carries a Sources section listing what it drew on.
We do not cite competing software vendors as authorities on what the law requires. We explain concepts in our own words and link to the authority rather than reproducing regulatory text at length.
Review by a named practitioner
Our safety and regulatory guides are reviewed for technical accuracy by John McWade, CSP, a Certified Safety Professional with experience across general industry and construction, who also designed and built EHSTEC.
Two things that means, stated plainly. This is internal review by the practitioner behind the company — it is not independent third-party review, and it is not legal, medical or regulatory advice. And a credential behind a reviewer does not make every sentence authoritative: it means a qualified person checked the content against the source material.
We separate what the product does from what the law requires
A guide teaching a practice does not imply EHSTEC automates that practice. Where a guide describes what EHSTEC does, it says so in a visually distinct callout, kept deliberately separate from the instructional content around it.
Our OSHA recordkeeping page carries an explicit section on what the software does not do — it does not decide whether a case is recordable, does not submit anything to OSHA, and does not guarantee compliance. We would rather state limits clearly than let a reader assume more.
We do not claim guarantees
No software makes an organization compliant, and we do not say otherwise. EHSTEC is described as helping teams manage inspections, incidents, training and records — supporting compliance work, not guaranteeing its outcome. Compliance depends on what an organization actually does, and determinations under the regulations remain professional judgements made by qualified people.
Neither OSHA, ASSP nor the National Safety Council endorses, certifies or is affiliated with EHSTEC.
Dates mean something
Every guide shows its publication date, and an updated date only when one exists.
- Publication dates are never back-dated to make content look newer or older than it is.
- An updated date records a substantive editorial revision — corrected facts, changed guidance, materially new or removed content.
- Template, styling and byline changes do not count. Re-deploying a page, restyling it, or adding a reviewer credit changes nothing a reader relies on, so it does not touch the updated date.
The same rule governs our sitemap: a page's last-modified date comes from when the page genuinely changed, not from when it was last uploaded.
We correct errors rather than quietly reprint them
If we get something wrong on a regulatory topic, the fix is to correct the guide and update its revision date — not to leave it standing. If you find an error, tell us at our contact page; a specific correction with a source is genuinely useful and we would rather hear it than not.
Scope
Everything in our guides is general educational information about safety practice and United States federal OSHA requirements. It is not legal advice, and it does not account for state-plan requirements, industry-specific standards or the particular circumstances of your workplace. For decisions with legal or regulatory consequence, consult a qualified professional who knows your situation.