Guide
How to Verify General Liability on a COI
By Keelstar Team · Updated July 11, 2026
The short answer
Verify general liability on a COI by confirming the commercial general liability row shows active policy dates, per-occurrence and general aggregate limits meeting your contract minimums, and the named insured matches your vendor's legal entity. Check whether coverage is occurrence-based or claims-made — claims-made policies need current retroactive dates and tail coverage at project close. Compare limits to your tier requirements: a janitorial vendor on a healthcare campus and a structural steel subcontractor should not share the same minimums. If the ACORD 25 remarks reference additional insured endorsements, request copies when your agreement requires them. Record pass/fail status and deficiency notes before authorizing work or releasing payment.
Locate the GL row on the ACORD 25
Commercial general liability appears in the standard policy table — typically letter code CGL or GL. Read policy number, effective date, expiration date, and both per-occurrence and general aggregate limits. Each field should be populated; dashes or blanks trigger a deficiency.
Compare limits to your requirements
Pull limits from your contract insurance exhibit or vendor tier matrix. Verify per-occurrence meets minimum, general aggregate meets minimum, and products-completed operations aggregate satisfies construction close-out requirements where applicable. Limits below contract minimums are a hard stop.
- Per-occurrence limit vs contract minimum
- General aggregate limit vs contract minimum
- Products-completed operations aggregate if required
- Umbrella or excess sitting above GL limits
Validate policy dates
GL must be active on the work date — not just on the certificate issue date. A certificate printed yesterday can list a GL policy that expired last month. Track expiration separately and tie it to your renewal workflow.
Check additional insured on GL
Most U.S. construction and property contracts require additional insured status on the vendor's general liability policy. The ACORD 25 may show a checkbox or remarks reference. Generic language may not satisfy ISO endorsement requirements — request the endorsement when your contract specifies CG 20 10, CG 20 37, or equivalent wording.
Named insured must match the vendor
The GL policy insures the named insured at the top of the certificate. That entity should match your subcontractor, service agreement counterparty, or DBA relationship documented in your vendor file. Mismatches between certificate insured and contract party create coverage gaps in a claim.
Document verification outcome
Record reviewer, date, pass/fail by field, and notes on deficiencies sent to the broker. GL verification should be repeatable — the same checklist for every certificate. Operations teams approving site access should see GL status without re-reading the full ACORD 25.
Frequently asked questions
- What GL limits do most U.S. contracts require?
- Low-risk vendors often need $1M per occurrence / $2M aggregate. Construction and healthcare frequently require $2M / $4M or higher, with umbrella sitting above GL. Your contract exhibit is the source — not industry habit.
- Does a blank GL row mean no coverage?
- Usually yes — or the broker omitted the line. Treat a blank commercial general liability row as a deficiency unless the vendor has a valid reason and alternative evidence. Do not authorize on-site work without confirmed GL.
- What is the difference between occurrence and claims-made GL?
- Occurrence policies cover incidents during the policy period regardless of when the claim is filed. Claims-made policies cover claims filed during the period — retroactive date and extended reporting period matter at project completion.
- Should aggregate limits include products-completed operations?
- Many construction contracts require separate or sufficient completed operations aggregate. Check whether your agreement specifies completed operations limits distinct from the general aggregate on the certificate.
Related guides
Put this into a monitored workflow
COI Tracker handles this continuously — with reminders and an audit trail.