by

Contract-to-certificate workflow

How to Compare Contract Insurance Requirements With a COI

A reliable comparison maps each written requirement to one certificate field or supporting document. It does not rely on a single “insured” label, a total coverage number, or a statement that the certificate meets the contract.

By COI Workbench Editorial Team · Reviewed September 2026 · General U.S. guidance

Use the final written requirement. Public agencies and private clients tailor insurance requirements to the work. A sample, old onboarding packet, or another contractor’s certificate is not a substitute for the controlling contract.
Line-by-line comparison modelCompare like with like; a total, note, or checked box should not silently stand in for a different requested field.
1Source rowCopy one current written requirement.
2Matching fieldLocate the corresponding certificate or evidence field.
3Observed stateRecord match, shortfall, missing, or unclear.
4AuthorityRoute policy questions to the issuer and requirement questions to the client.
5Evidence trailPreserve the answer, corrected file, delivery, and review state.

Build a requirement matrix

Create one row for each coverage and limit. Then add separate rows for legal names, policy dates, certificate holder, additional insureds, waiver, primary wording, completed operations, cancellation requirements, and attachments. This prevents a matching limit from hiding a missing endorsement.

Requirement Evidence to locate Comparison outcome
General liability each occurrence Matching GL limit field Meets, shortfall, missing, or unclear
General aggregate Matching GL aggregate field Compare separately from occurrence
Auto combined single limit Auto liability row Check covered-auto indicators separately
Employer’s liability Each accident and disease fields Do not replace with “statutory” workers’ comp
Additional insured Policy provision or executed endorsement Agent confirmation/document review
Certificate holder Recipient block Exact name and address match

Step 1: identify the controlling document

Ask which contract version or portal instruction is current. Record its revision date. If an email changes a limit or entity, retain the written clarification with the contract. When two documents conflict, return the inconsistency to the requester instead of choosing the lower requirement.

List the named insured, contracting client, certificate holder, project owner, property manager, general contractor, and every requested additional insured. One company may occupy several roles, but each role has a different purpose. King County’s public guidance, for example, distinguishes its certificate-holder address from the separate additional-insured endorsement requirement.

Step 3: transcribe coverage lines and limits

Copy each label and amount exactly. Avoid converting “general aggregate” into “total liability” or combining three employer’s-liability fields. If the requirement says “statutory workers’ compensation,” preserve that text as a policy question rather than assigning an invented dollar amount.

Use the COI Coverage Limit Comparator for the numeric rows. It calculates only simple differences between the values you enter and intentionally does not combine umbrella and underlying limits.

Step 4: compare dates with the work schedule

Map the project start and expected end against the effective and expiration date of every required policy. If a policy renews during the project, ask how the client wants updated evidence delivered and who will track it. A future renewal is not automatically a deficiency, but ignoring it can stop access later.

Step 5: create a separate endorsement checklist

Contracts may request additional insured status, ongoing and completed operations, primary and noncontributory wording, waiver of subrogation, or a project-specific aggregate. These are not limit fields. Ask the agent which policy wording or endorsement responds and whether the requester needs an executed copy.

The Texas Department of Insurance states that certificate information may not exceed the policy and that certificate indicators for additional insured and waiver provisions should correspond to applicable endorsements. This is why typing contract language into a description is not a reliable solution.

Step 6: classify every result

Meets Displayed value is at least the entered requirement.
Shortfall Displayed value is numerically lower.
Missing The requirement has no entered certificate value.
Review The fields do not align or require policy interpretation.

“Meets” is a numeric workflow label, not a coverage or compliance opinion. Keep that distinction visible in saved reports and messages.

Step 7: send a focused correction request

Group the result into clerical corrections, numeric gaps, and policy questions. A useful message identifies the exact contract row, current certificate value, requested amount, entity, project, deadline, and required attachment. The COI Agent Request Builder turns that information into a copy-ready draft.

Worked administrative example

A client requests $1 million general-liability each occurrence, $2 million general aggregate, $1 million auto combined single limit, statutory workers’ compensation, $1 million employer’s liability each accident, and additional-insured endorsements for two named entities.

The certificate displays $1 million each occurrence, $1 million aggregate, $1 million auto, and $500,000 employer’s liability each accident. The package has no endorsement copies. The comparison should produce:

  • Numeric match: GL each occurrence and auto combined single limit.
  • Numeric shortfall: GL aggregate and employer’s liability each accident.
  • Policy/document question: statutory workers’ compensation and requested additional-insured endorsements.
  • No conclusion: whether a policy change is available, whether an umbrella can help, or whether the client will accept an alternative.

Common comparison mistakes

  1. Comparing the requirement with the largest number anywhere on the certificate.
  2. Adding umbrella and primary limits without contract and agent confirmation.
  3. Treating certificate holder and additional insured as synonyms.
  4. Ignoring an expiration that falls during the project.
  5. Marking a row “not applicable” without written client clarification.
  6. Calling the whole certificate noncompliant when only one field needs review.

Frequently asked questions

Can the comparator tell me whether my insurance complies with the contract?

No. It reports arithmetic matches and differences between user-entered values. Coverage, wording, contract interpretation, and acceptance remain outside the tool.

What if the certificate uses a different field label?

Do not force a comparison. Mark it unclear and ask the agent which field corresponds to the requirement.

Should I upload the contract or certificate?

No upload is required. Transcribe only non-confidential labels and values. Keep sensitive documents in approved systems.

Who resolves a shortfall?

The agent explains available insurance options; the client decides whether a contract alternative is acceptable; qualified counsel addresses legal interpretation when needed.

Sources and limits

Public contract examples illustrate how requirements can be structured; they are not universal minimums or recommendations.