A certificate is evidence, not coverage. It reports what the policy says. When a general contractor’s risk manager rejects one, they have usually compared it against the subcontract and found something the policy behind it cannot actually deliver. Raising limits does not fix any of the four most common reasons.
What gets a certificate sent back:
Additional insured status that is scheduled rather than blanket. The subcontract asks for blanket AI including completed operations. A scheduled endorsement naming one entity does not satisfy it, and completed operations is the part most often missing.
No primary and non-contributory wording. Without it, your carrier can argue the GC’s policy shares the loss. Risk managers check for this specifically because it decides who pays first.
Waiver of subrogation absent. Standard subcontracts require it. It has to be endorsed onto the policy; it cannot be added to a certificate.
The wrong named insured or description of operations. A DBA on the certificate that does not match the entity on the subcontract will stop the job at the gate, and so will a description that reads “general contractor” when you are performing fire protection work.
How Liberty structures your protection:
Liberty reads the subcontract against the policy form before the certificate is issued, so the wording is confirmed rather than assumed — which is the difference between a rejected certificate and a start date that holds.