What a General Contractor Actually Checks in Your Safety Program

On a mid sized commercial job the reviewer is usually the GC's safety manager or a project engineer who has been handed safety document intake as part of their role. On larger jobs it may be a corporate EHS coordinator who never sets foot on your site. In many cases the first pass is not a person at all: it is a prequalification network such as ISNetworld, Avetta, or Veriforce, where a reviewer grades your uploaded program against a standard question set and returns a score.

None of these reviewers are trying to find a reason to fail you. They are trying to close out a file. The faster your document lets them check their boxes, the faster you get an approval. That is the whole game. Everything below is about making the boxes easy to check.

The very first thing a reviewer looks at is whether your company name is on the cover, whether there is a date, and whether an owner or officer has signed a policy statement committing the company to the program. It sounds trivial. It is the single most common reason a document gets bounced back the same day it arrives.

A safety policy statement signed by the owner tells the reviewer that a real person at your company owns this document. An unsigned statement, or one that still carries a template publisher's placeholder text, tells them the opposite. Put the company name, the date, and the signature block on the front, and half of the reviewer's suspicion disappears before they turn the page.

This is the check that decides most rejections. The reviewer knows what you were hired to do because it is written into the subcontract in front of them. They then flip to your table of contents and see whether the program addresses that work.

A roofing subcontractor whose program has no fall protection section is rejected on sight. An electrical sub with no lockout or tagout content, an excavation contractor with no trenching and protective systems section, a concrete contractor with nothing on silica: all of these are immediate returns. The reviewer does not need to read the section to know it should exist.

The opposite problem is just as damaging. If you are a drywall contractor and your program contains chapters on crane operations, marine terminals, and underground mining, the reviewer knows you bought a generic manual and never edited it. That undermines everything else in the file.

The reviewer wants a name and a phone number. Many OSHA construction standards assign duties to a competent person, meaning someone capable of identifying hazards and authorized to correct them. Your program should identify who holds that role for your company, or at minimum name a safety contact who the GC can call when something happens on site.

Naming a person also matters for the GC's own paperwork. When they build the site safety roster, they copy your contact into it. If your document does not give them a name, they have to email you and wait, and your file sits in the pending pile while they do.

Reviewers look for a stated cadence, not a philosophy. They want to see that new hires get an orientation before they work, that toolbox talks happen on a defined schedule such as weekly, and that attendance is documented with sign in sheets.

The regulatory backing here is 29 CFR 1926.21(b)(2), which requires the employer to instruct each employee in the recognition and avoidance of unsafe conditions. A program that says training happens as needed does not satisfy the reviewer, because as needed is not a cadence and cannot be audited. Write the frequency down and keep the sign in sheets.

Hazard Communication under 29 CFR 1910.1200 is one of the few programs OSHA requires in writing whenever hazardous chemicals are present, and construction adopts it through 1926.59. Nearly every trade has chemicals on the truck, including adhesives, solvents, fuels, sealants, and concrete admixtures.

The reviewer checks for three things: a written hazard communication section, a statement of how employees reach safety data sheets in the field, and container labeling practice. Saying that sheets are in a binder in the office fails the field access test if your crews are an hour away. Naming a binder in each truck, or a phone accessible digital library, passes it.

A PPE list is not a hazard assessment. The reviewer is looking for evidence that you assessed the hazards of your work and then selected protective equipment based on that assessment, which is the structure of 29 CFR 1926.95 and 1926.96 and the requirements that follow for eye, head, hearing, and hand protection.

In practice, a short table linking a task to its hazard and to the required equipment satisfies this instantly. A bulleted list of gear with no link to any task usually draws a comment asking for the assessment.

Every GC wants to know that an injury on their jobsite gets reported to them promptly, so your program needs a stated reporting chain and a timeframe. Reviewers also look for the fatality and hospitalization reporting duties under 29 CFR 1904.39, which require reporting a work related fatality within 8 hours and an inpatient hospitalization, amputation, or loss of an eye within 24 hours.

If you had 11 or more employees at any point in the prior calendar year, Part 1904 recordkeeping applies and your program should say that you maintain the OSHA 300 log, the 301 incident reports, and post the 300A summary from February 1 to April 30. If you stayed at 10 or fewer, you are partially exempt from routine recordkeeping but still have to report the serious events above. Say which case applies to you, because a reviewer who cannot tell will ask.

A disciplinary policy tells the reviewer that your safety rules have consequences. It does not need to be harsh. A progressive structure, moving from verbal warning to written warning to removal from the site for repeat or willful violations, is what they expect to see.

The employee acknowledgment form is the last box and the easiest one to lose. The reviewer wants a signature page where each employee acknowledges that they received the program and agree to follow it. Some GCs ask you to upload signed copies before mobilization. Having the form built into the back of the program means you can collect signatures the same day.

If you hold subcontracts of your own, the reviewer adds a few questions. They want to see how you qualify lower tier subs, how you handle a sub whose work creates hazards for your crews, and how site coordination and orientation are handled when multiple employers share the same work area.

This is also where multi employer worksite expectations show up. Even a small general contractor should have a paragraph describing how they coordinate with other trades and how they respond when they observe another company's unsafe condition.

ISNetworld, Avetta, and Veriforce use structured review services where a grader compares your uploaded program against a question set covering written program elements. The questions map almost exactly to the checklist above: is there a written program, is it signed, does it cover the applicable hazard, does it define training, does it define enforcement.

The difference is that a network reviewer will not phone you for clarification. They score what is on the page and return the deficiencies. Every missing element is a resubmission cycle, and cycles take days. Getting it right the first time is worth more here than anywhere else.

Across all of these reviewers, the rejection reasons cluster into a short list. If you avoid these five, most files clear on the first pass.

Open the file and search for any company name that is not yours. Confirm the date is current. Check that every hazard listed in your subcontract scope has a matching section. Confirm a named safety contact appears near the front. Then send it as a single PDF with a filename that includes your company name and the year, because reviewers manage dozens of files and a clear filename genuinely speeds up your approval.

If your trade page describes hazards you recognize, that is a good preview of the sections a reviewer expects from a company like yours.