OSHA HazCom Written Program Template for Cleaning Companies

A written hazard communication program is the one HazCom document OSHA compliance officers ask for first during a walkaround. Not the SDS binder, not the training log: the program itself. Under 29 CFR 1910.1200(e)(1), every employer using hazardous chemicals must develop, implement, and maintain a written plan describing how labels, SDSs, and training are handled at each facility. For a cleaning company running crews across a dozen client sites, this is not paperwork for its own sake. It is the document that tells a new hire, a temp agency worker, or a night-shift lead where the SDS binder lives and what to do if a jug of degreaser splits open on a loading dock.

Citation officers under OSHA's General Industry program frequently write 1910.1200(e) violations as "other-than-serious" when the program exists but is stale, and "serious" when no written program exists at all. The gap between those two outcomes is usually a two-hour drafting session, not a compliance department.

What 1910.1200(e)(1) actually requires

The written program has three mandatory components spelled out in the standard, plus a fourth that OSHA's compliance directive treats as de facto mandatory for multi-employer worksites. A janitorial company operating on client property counts as a multi-employer situation almost every time.

29 CFR 1910.1200(e) element	What it must contain	Cleaning-company application
(e)(1)(i): Chemical list	List of every hazardous chemical known to be present, using a product identifier that matches the SDS and label	One master list per branch plus a site-specific sub-list for accounts with client-supplied chemicals
(e)(1)(ii): Labels/SDS methods	Methods the employer will use to inform employees of hazards of non-routine tasks and unlabeled pipes	Procedure for floor-stripping jobs, one-off carpet extraction chemicals, or client chemicals stored in unmarked spray bottles
(e)(1)(iii): Multi-employer sites	Methods for informing other employers' workers of hazards when chemicals are used on a shared site	Covers night crews working alongside a tenant's own staff or a GC's trade contractors during a build-out clean
(e)(2)	Program must be available to employees and their representatives upon request	Keep a copy in the same binder or app as the SDS library, not filed separately at a corporate office

Source: OSHA 29 CFR 1910.1200(e).

Building the chemical inventory section

Start the list with the product name exactly as it appears on the label and the SDS, not an internal nickname. If a crew calls a product "the pink stuff," the written program and the SDS still need the manufacturer's product identifier, because that is the term OSHA inspectors cross-reference during a records review. A mid-size BSC running 15 to 25 active SKUs across floor care, restroom care, and glass care typically ends up with a chemical list of 30 to 60 line items once dilutable concentrates, ready-to-use sprays, and client-supplied products are all counted separately.

Update the list on a defined cadence rather than only when someone remembers. Quarterly review works for most operations; monthly review makes sense for accounts that rotate chemistries seasonally, such as ice-melt tracking removers in winter markets.

Non-routine task language: the section inspectors read closely

Paragraph (e)(1)(ii) requires the program to describe how employees will be informed of hazards tied to non-routine tasks. In commercial cleaning, this covers anything outside the normal chemical set: a one-time graffiti removal job using a solvent the crew has never touched, a biohazard cleanup after a medical incident, or entering a mechanical room to service equipment that carries unlabeled process piping. The written program should name who authorizes non-routine chemical use, what additional PPE gets issued, and how the supervisor briefs the crew before work starts, not just a pointer to "as needed" training.

Multi-employer worksite language

Most commercial accounts are multi-employer sites once you count the property manager, other trade contractors, and sometimes a second cleaning vendor on a different shift. The written program needs a stated method for exchanging hazard information. Usually that means requiring the site supervisor to obtain SDSs for any client-supplied or GC-supplied chemical before a crew member handles it, plus a commitment to make the cleaning company's own SDS library available to other employers' workers on request. This clause is the one most templates downloaded from generic HR sites skip entirely, because it is specific to contract labor operating on someone else's property.

Assigning ownership and setting review dates

• Name a single person by title (not just "management") responsible for maintaining the chemical list and the SDS library
• Set a documented review interval. Most programs use annual, with a trigger review whenever a new chemical class is added
• Record training completion dates tied to the written program, not as a separate untracked activity
• Keep the written program for as long as the operation exists. OSHA does not set a fixed retention period for the program document the way it does for SDSs, but inspectors expect the current version on file

Common gaps found in cleaning-company HazCom programs

Three recurring problems show up when Opora's editorial team reviews templates submitted by subscribers: the chemical list references SKUs no longer in service, the multi-employer clause is missing entirely, and the "responsible person" field names a job title that was eliminated in a reorg two years earlier. Any of these three gaps is enough to turn a routine records check into a citation, because the inspector is testing whether the document reflects the actual current operation rather than a boilerplate download.

Frequently asked questions

Does a single-location cleaning company with under 10 employees still need a written program? Yes. 1910.1200(e) applies to any employer with employees exposed to hazardous chemicals, regardless of headcount. There is no small-employer exemption in the HazCom standard.

Can one written program cover multiple branch locations? It can, provided each branch's specific chemical list and site conditions are addressed as sub-sections. A single generic program that does not reflect branch-specific chemical inventories will not hold up under a records review at an individual site.

Who signs off on the written program? OSHA does not require a specific signatory, but naming an accountable owner (safety director, operations manager, or owner-operator) closes the most common citation gap: a program with no named responsible party.