A rejected certificate rarely means you’re actually uninsured — usually it means something small on the paperwork doesn’t match what was requested. These are the mistakes we see most often, and they’re almost all avoidable.
The Usual Suspects
An outdated certificate still on file after a policy renewal — GCs often require a fresh certificate at renewal, not just at project start.
A business name that doesn’t exactly match your contract — a DBA versus a legal entity name mismatch is a common, easily fixed rejection reason.
Missing endorsements the GC specifically requested — Additional Insured, Waiver of Subrogation, or Primary & Non-Contributory language left off because the request wasn’t fully read.
A certificate holder listed incorrectly — the wrong entity, or a project name that doesn’t match the contract.
Coverage limits that technically meet the GC’s minimum on paper but don’t match the specific wording of their request.
Why Turnaround Speed Matters As Much As Accuracy
Even a correctly issued certificate that takes days instead of minutes can hold up a start date or a payment application. The fix isn’t just getting it right — it’s getting it right fast enough that it never becomes the bottleneck.
How We Handle This
We turn around correct certificates fast — most within 30 minutes — and check them against the specific GC requirement before sending, not after it’s rejected once.
Have a GC requirement that keeps getting your certificates bounced back? Contact us and we’ll get it resolved.