COI Dates vs Limits vs Endorsements: What GCs Need to Check

An expiration date is only one part of a COI review.

A certificate can show a policy running through next spring and still leave open questions about the insured entity, the limits required for the job, the policy language, or endorsements called for by the agreement. Identity, dates, limits, policy terms, and endorsement evidence answer different questions. Keep them separate in the review record.

Identify the record first

Confirm that the named insured matches the entity performing the work and the party named in the applicable agreement. Confirm the project and scope tied to the request. An otherwise current certificate may belong to the wrong entity or job.

Dates answer a timing question

Read the policy periods displayed on the certificate and compare them with the subcontractor’s planned work. Check every coverage row the agreement requires, not only general liability. Auto liability, workers compensation, umbrella or excess, and other listed policies can have different dates.

A practical date review asks:

• Is the policy period in effect on the certificate’s issue date?
• Is any required policy already expired or not yet effective?
• Is the work expected to continue beyond a listed expiration?
• Who owns the renewal follow-up?

Set reminders according to the contract, project, and your approved process. A future date does not prove that the insurance satisfies the agreement. It tells the reviewer when the certificate says the listed policy period ends.

The current ACORD 25 also cautions that listed limits may have been reduced by paid claims. That is another reason not to turn a date check into a broad coverage conclusion.

Limits answer a comparison question

Next, compare each listed limit with the requirement that applies to that subcontractor and project. Do not compare the general liability row with every requirement on the page. Read the rows separately.

Common items can include:

• general liability each occurrence and aggregate
• products and completed operations
• auto liability
• workers compensation and employer liability
• umbrella or excess liability

The list for a particular job may be different. Requirements vary by contract, owner, public-work program, trade, and risk program. Keep the applicable written requirements close to the review so the reviewer is not working from memory.

When a limit does not match, record the exact row and the requirement used. “Limits wrong” sends the next person back to the beginning. “Auto combined single limit shown as X; agreement requests Y” gives the broker, subcontractor, or internal reviewer something specific to address.

Do not make a coverage decision from the displayed number. The certificate is informational.

Policy terms answer coverage questions

A COI does not reproduce the policy. The insuring agreement, definitions, exclusions, conditions, and amendments determine what the policy covers. A listed policy and limit do not establish coverage for a particular person, activity, place, or loss. Send those questions to the broker, carrier, coverage counsel, or insurance team responsible for the judgment.

Endorsements are part of the policy, but the document workflow should track requested endorsements separately. A note on the certificate is not a substitute for policy language.

Endorsements answer an evidence question

A certificate description may say “additional insured,” “primary and noncontributory,” or “waiver of subrogation.” That note is not the same thing as reviewing the applicable policy provision or endorsement.

If the governing agreement requires additional-insured status, request the relevant endorsement and compare the named parties, scope, and wording with the requirement. Being listed as a certificate holder is different from being an additional insured. A COI does not create additional-insured status.

Handle each endorsement requirement as its own review item. A useful status set might be:

• not required for this agreement
• requested
• received, pending review
• reviewed under the company process
• correction requested
• exception approved by the authorized person

Avoid a single “endorsements yes/no” field when several distinct provisions are in play. The reviewer should be able to see what was requested and what evidence was actually received.

The COI is information, not the policy

The ACORD certificates FAQ makes the boundary clear: a certificate is issued as a matter of information and does not amend, extend, or alter coverage. The policy and endorsements remain the controlling documents.

That boundary should shape the language in your tracker. “Certificate received” is factual. “Dates reviewed against agreement” describes a process. “Coverage guaranteed” or “endorsement verified automatically” goes beyond what the COI can establish.

Send unclear policy language, contract conflicts, and coverage questions to the broker, attorney, coverage counsel, or insurance team responsible for that judgment.

Use a review sequence that survives handoffs

A fixed order helps different reviewers reach the same work product:

1. Confirm the subcontractor entity and project.
2. Check required policy dates.
3. Compare listed limits with the applicable agreement.
4. Route policy-language and coverage questions to the qualified reviewer.
5. Request and review required endorsements as separate evidence items.
6. Record open items, owner, due date, and any approved exception.

Keep date status separate from the full review status. A row can be “current through March” and “endorsement correction requested” at the same time. Both statuses describe the file accurately.

Work and payment consequences should follow the contract and your company’s approved process. They can also be affected by law, owner requirements, and public-work programs. Do not let a red or green tracker field invent an automatic decision.

Make the record reconstructable

A reviewer months from now should be able to see the certificate received, any supporting endorsements, the requirement used, the result, the follow-up sent, and the person who approved an exception. Preserve replacement documents and history instead of overwriting the old file.

COI Compass can import a roster, draft ACORD 25 fields with AI for human review, send renewal reminders, accept no-login document uploads, and keep record history. It organizes the evidence and next action. It does not interpret policy language, decide compliance with a contract, or make coverage decisions.

Test one active file

Open one subcontractor record and review it in this order: entity, dates, limits, policy-language questions, required endorsements, then open actions.

Can you identify which facts came from the certificate, which requirement came from the agreement, and which conclusion came from a qualified human reviewer?

If those three things blur together, the record is not finished, even when the expiration cell is green.