How to Prepare for an OSHA HazCom Inspection: Be Audit-Ready

An OSHA inspection can happen anytime. For Hazard Communication (HazCom), inspectors focus on four things: a written program, SDS access, container labeling, and employee training. If you can show all four in minutes, you're audit-ready. If not, you're at risk of citations and fines.

This guide explains what inspectors look for, the most common HazCom citations, and how to use free tools and a clear workflow to be inspection-ready.

What OSHA inspectors look for (29 CFR 1910.1200)

Under the Hazard Communication Standard, employers must:

1. Have a written HazCom program that describes how you meet the standard (labels, SDS, training, inventory) (29 CFR 1910.1200(e)(1)).
2. Keep Safety Data Sheets readily accessible to employees during their work shift (29 CFR 1910.1200(g)(8)).
3. Ensure containers are labeled: labels on incoming containers are not removed or defaced (29 CFR 1910.1200(f)(9); the supplier labels them under (f)(1)), and workplace containers are labeled under (f)(6) (product identifier and hazard information).
4. Train employees (29 CFR 1910.1200(h)). The standard does not require a training record, but a record of who was trained, on what, and when is how you show it.

Inspectors will ask to see each of these. "We have it somewhere" or "the safety person has it" is not enough. Workers must be able to access SDSs, and you must be able to produce the written program. Training records are not required by (h), but they back up what workers tell the inspector.

Penalties (29 CFR 1903.15(d), unchanged for 2026): Serious violations can be up to $16,550 per violation; willful or repeated up to $165,514 per violation. If you receive a citation, you have 15 working days to contest (29 CFR 1903.17(a)). Missing it makes the citation a final order; only in extraordinary circumstances can the Review Commission relieve an employer under Federal Rule of Civil Procedure 60 (note 1 to 29 CFR 2200.33). Use that window to correct gaps and, if needed, request an informal conference.

How the inspector actually tests each of the four

Having the four elements isn't the same as passing. Inspectors don't just glance at a binder. They probe each one, and knowing how they probe tells you what "audit-ready" really means:

• Written program → is it site-specific? The CSHO reads it looking for your actual chemicals (the list in 29 CFR 1910.1200(e)(1)(i)), locations, and procedures, including how you inform employees of non-routine tasks and unlabeled pipes ((e)(1)(ii)). A generic template with no site detail fails even though a document exists.
• SDS access → they ask a worker. OSHA's HazCom directive (CPL 02-02-079, reissued in 2026) tells inspectors to check that workers know how to access SDSs (section X.H.2); expect a request to pull the sheet for a chemical in use. "It's on the office server" fails if the worker can't retrieve it in their work area during the shift, including in a low-signal spot.
• Labels → they open the cabinets. The CSHO inspects the secondary containers (spray bottles, safety cans, mixing buckets in gang boxes and storage cabinets), not just the manufacturer's drums. An unlabeled transfer container is an (f)(6) citation unless the immediate-use exception of (f)(8) applies.
• Training → they interview a worker. CPL 02-02-079 tells inspectors to interview employees to determine whether they have an adequate understanding of workplace chemical hazards. A signed sign-in sheet is evidence, but the real test is whether the employee can explain the hazards of what they use and demonstrate finding an SDS. If interviews show a trend that training is not happening or is cursory, the inspector looks harder at the training program, and paperwork on file does not settle the question; the directive also notes that workers cannot be expected to recall everything from training (section X.H.2.a).

Prepare for the probe, not just the paperwork: a self-audit that only checks "do we have it?" misses the way an inspector checks "does it actually work?"

No rule asks you to log who opened an SDS. It still helps to know. In HazComFast, opening a product's page and opening its SDS from the app leave two separate entries in the audit log, "product page viewed" and "SDS viewed", which an administrator can read. On a phone, the product page shows the manufacturer, the CAS numbers and the hazards, as it does on a computer.

Which version will the inspector read?

The one in effect on the day of the inspection, and if the inspection follows an incident, the one in effect that day too. 1910.1200(e)(1) asks you to "develop, implement, and maintain" the program; paragraph (e) says nothing about how long to keep the versions you replaced. Keeping them is still how you answer "what did the program say in March?"

In HazComFast, each saved version of the program is kept. An earlier version opens read only, two versions can be compared with the added and removed text highlighted, and restoring an old one creates a new version, "Restored the content of version N", without overwriting anything. When nothing has changed since the version in effect, the screen says so and offers "Attest review without changes" instead of another version.

Can I hand OSHA a spreadsheet?

Yes, if it's the right list. 1910.1200(e)(1)(i) asks for "a list of the hazardous chemicals known to be present using a product identifier that is referenced on the appropriate safety data sheet (the list may be compiled for the workplace as a whole or for individual work areas)." It names no template and no file format. An Excel file does the job.

What fails is a file that covers less than you think. An export run from a search box, a filter left on one jobsite, a list cut off partway: the inspector gets a list missing the product the crew is spraying that afternoon. Before you hand it over, read what the file says it covers, compare its row count with the inventory, and look for any line saying it was cut. The spreadsheet carries the list. The rest of the written program under (e)(1) and SDS access under (g)(8) still have to be there.

In HazComFast, the inventory export asks for its scope first, the whole organization or the jobsites you pick, and writes that scope on the PDF and in the file name. Each row carries the product name, the manufacturer, the signal word, the pictograms, whether an SDS is on file, its revision date and the jobsites the product is assigned to. A list too long for one file comes out in numbered parts, "Chemical inventory (part 1 of 3)". If a list can't load whole, the screen says the export would be incomplete and suggests narrowing it by jobsite, before anything is downloaded. Each export goes into the audit log with its scope and its row count.

Common HazCom citations (and how to avoid them)

• No written program or outdated program
  Use a written HazCom program generator and update it when chemicals or locations change. Keep it where employees can access it.

• SDS not readily accessible
  SDSs must be available during the shift, electronically or in print, without barriers. See Are Digital SDS Legal? and Offline SDS Access. Maintain a chemical inventory that ties to your SDS library.

• Unlabeled or mislabeled secondary containers
  Every workplace container needs a label with product identifier and hazard information, apart from two exceptions: portable containers for the immediate use of the employee who filled them ((f)(8)), and stationary process containers, which may use signs, placards or batch tickets instead ((f)(7)). Use the GHS Label Generator and Container Size Matcher. See Secondary Container Labels: OSHA Rules.

• Training gaps
  1910.1200(h) requires the training, not a record of it, and OSHA checks it by interviewing workers (CPL 02-02-079, section X.H.2). Document who attended and when anyway: it backs up what they say. Use a HazCom Training Record / Sign-In Sheet and keep completed sheets with your written program. See How to Run Effective Toolbox Talks.

• Missing or incomplete chemical list
  Keep an up-to-date list of hazardous chemicals at the worksite. The Chemical Inventory Template and SDS Gap Analyzer help you stay current.

The four elements and the paragraphs an inspector quotes

5-minute self-audit (inspection readiness)

Run through this before an inspection, or monthly:

1. Written program: Can you hand an inspector a current, site-specific HazCom program? If not, generate one and fill in SDS format and location.
2. SDS access: Can a worker pull the correct SDS in under a minute (including in low-signal areas)? If not, fix access and/or go offline-capable.
3. Labels: Are secondary containers labeled with product name and hazards, apart from the (f)(7) and (f)(8) exceptions? Use the HazCom Audit Checklist to verify.
4. Training: Can your workers explain the hazards of what they use and find an SDS? A training sign-in sheet for each session backs that up.
5. Chemical list: Does your inventory match what's on site? Update it when chemicals change; reconcile it container by container with the gap-analysis method.

In HazComFast, three of those checks come out as files you can hand over. A jobsite's SDS binder downloads as a ZIP with an index file that lists every product, the ones without an SDS included, and the reading confirmations export as a dated CSV or PDF. The HazCom binder comes out as one PDF: a cover page, the site's chemical inventory and its SDSs. And SDS coverage reads as a count, "5 of 6 products · 1 missing", with the date you asked the supplier for the missing sheet.

Free tools that make you audit-ready

• HazCom Audit Checklist (2026): Self-audit against written program, SDS, labels, training. Print or export for your file.
• OSHA Fine Calculator: Estimate penalty exposure so you can prioritize fixes.
• HazCom Program Generator: Produce a written program PDF; add SDS format and location.
• HazCom Training Record: Sign-in sheet that shows the training 1910.1200(h) requires took place; keep it with your program.
• GHS Label Generator: Workplace labels built from the classification you enter; check it against the SDS; use with Container Size Matcher.
• Chemical Inventory Template: CSV template for product name, CAS, hazards, storage, SDS status.
• SDS Gap Analyzer: Find gaps in program, SDS access, labeling, and training; get a prioritized report.

For chemical-level data (CAS numbers, hazards), use the Chemical Inventory Template and link to the GHS Label Generator when labeling.

Already cited? Fix it fast

If you've received a HazCom citation, you need to abate and document. Responding to an OSHA citation: abatement, certification and PMA outlines the steps and how to show compliance. Pair that with the written program, audit checklist, and training record so you can prove corrective action.

For contractors and multi-employer sites

GCs and subs share jobsite compliance risk. OSHA HazCom for Contractors covers who's responsible and how to stay audit-ready. Use the Subcontractor RFI Writer to request missing SDS and HazCom documentation in writing.

Related reading

• OSHA Penalties 2026 & HazCom Citation Risk for Construction: Penalty caps and how HazCom execution affects citation risk.
• Complete Guide to OSHA HazCom Compliance 2026: Full picture of the standard.
• OSHA Inspections hub: the full inspection process, the response clock, and penalty reductions.
• Secondary Container Labels: OSHA Rules + Workflow: Labeling rules and on-site workflow.
• Are Digital SDS Legal?: Electronic access and "readily accessible."

Summary

To be audit-ready for an OSHA HazCom inspection: maintain a current written program, ensure SDS access (including offline where needed), label secondary containers (apart from the (f)(7) and (f)(8) exceptions), and train your crews, with records that back the training up. Use the free tools above to generate and maintain each piece, and run the HazCom Audit Checklist regularly. When inspectors ask, you'll have proof, not excuses.