GC safety coordinators reject plans for specific, fixable reasons. Here's what they're looking for — and how to get approved.
If your GC's safety coordinator kicked back your Fall Protection Plan, you're not alone. It's one of the most frequently rejected pre-mobilization documents — and the rejection reasons are almost always the same.
The good news: every common rejection reason has a clear fix. The plans SafeDocs prepares include all of these elements by default, so they pass GC review the first time.
Your plan uses generic language with no reference to the actual project name, job site address, or specific work being performed. GC safety coordinators can spot a copy-paste template instantly.
How SafeDocs fixes this: SafeDocs references your company name, project name, job site address, and competent person by name throughout every section of the plan.
The plan says 'the competent person' without naming a specific individual, their title, and their qualifications. OSHA requires a named competent person with defined authority.
How SafeDocs fixes this: Your competent person's name and title appear in the designation section, signature pages, and throughout the plan wherever their responsibilities are referenced.
This is the #1 reason for rejection. OSHA 29 CFR 1926.502(d)(20) requires prompt rescue procedures. Many templates omit the rescue plan entirely, or include a single paragraph that says 'call 911.'
How SafeDocs fixes this: SafeDocs includes a detailed rescue plan with multiple rescue scenarios, step-by-step procedures, required equipment, target rescue times, and suspension trauma (orthostatic intolerance) guidance.
Citing 'OSHA regulations' generically is not the same as citing '29 CFR 1926.502(d)(16)' specifically. Safety coordinators look for specific CFR references to verify the plan is substantive.
How SafeDocs fixes this: Every applicable section cites the specific OSHA standard number — from 29 CFR 1926.500 through 1926.503 and related standards like ANSI Z359.1.
GCs need proof that workers were informed about the plan. A plan without signature pages can't demonstrate training compliance.
How SafeDocs fixes this: Every plan includes competent person certification, management approval signature blocks, and a 15-row worker training acknowledgment log.
The plan doesn't identify the specific fall hazards present on this project — leading edges, roof work, openings, skylights — or the specific control measures for each.
How SafeDocs fixes this: SafeDocs generates a hazard assessment table with each hazard type, its location on your project, risk level, and specific control measures based on the hazards you identify in the form.