by

Version comparison

How to Compare Old and New COI Requirements

A revised insurance exhibit or portal request should not quietly replace the prior version. Preserve both sources, compare one requirement at a time, and record what appears added, changed, removed, unchanged, or still unclear.

Reviewed September 2026 · Educational information, not insurance or legal advice

Absence is not automatic deletion. If an item appears in the baseline but cannot be found in the revised request, confirm the client’s intent before treating the obligation as removed.

Start by freezing both source versions

Identify the baseline and revised source by a neutral label, date, and version. A source may be a contract exhibit, bid requirement, client email, portal instruction, or documented clarification. Preserve the actual records in the approved project system; the browser tool accepts only concise administrative labels.

Do not compare a remembered summary with a current document. Confirm that the two sources concern the same project, contractor, client, and scope. If one document replaces only part of the earlier requirement, note that limited scope before classifying changes.

USGS revision guidance for public data uses a short version-history record describing changes and access to earlier versions. COI requirements are different records, but the same control principle is useful: retain prior versions and describe revisions rather than erasing history.

Build an item-by-item comparison matrix

Use one row for each independently testable item. “General liability” may require separate rows for each-occurrence limit, general aggregate, additional-insured evidence, primary-and-noncontributory wording, waiver request, policy period, and certificate-holder details.

Requirement item Baseline state Revised state Classification
GL each occurrence Stated: baseline value Stated: revised value Changed if values differ
Owner as additional insured Not found Stated for GL ongoing operations Appears added
Certificate holder address Stated Stated with same normalized text Unchanged
Waiver evidence Stated Not found Appears removed; confirm
Submission deadline Stated Wording unclear Needs clarification

Compare the versions

Preserve both values and classify each difference.

Build a private matrix for additions, changed terms, apparent removals, unchanged items, and questions.

Track requirement changes

Use classifications that preserve uncertainty

Appears added

The baseline item was marked “not found” and the revised source states a value or wording. Confirm when the new requirement takes effect and which work or vendor relationship it covers.

Changed

Both sources state the item, but the preserved wording or value differs. Do not reduce “changed” to “higher” or “lower” unless a reliable numeric comparison is appropriate for that field.

Appears removed

The baseline states the item and the revised source does not contain it. This is a review flag, not a contractual conclusion. The revised document might be supplemental, incomplete, or limited to a particular section.

Unchanged

Both source states and normalized text match. Preserve the original text in the authoritative records even if the tool ignores spacing and capitalization for classification.

Needs clarification

Either source is unclear, the item cannot be mapped confidently, or the two records use language that should not be treated as equivalent without confirmation.

Assess the workflow impact

  1. Client clarification: confirm the controlling version, effective date, changed entity, value, evidence type, deadline, and affected work.
  2. Agent review: provide the revised written request and ask what accurate policy information or issued evidence can support it.
  3. Contractor planning: update the internal checklist, owners, filenames, package version, target date, and resubmission log.
  4. Legal escalation: route questions about contract meaning, enforceability, cost allocation, or disputes to qualified counsel.
  5. Reviewer confirmation: record the observable outcome without treating client acceptance as a coverage determination.

The Texas Department of Insurance notes that certificate requests under its cited rules should be specific, clear, and reasonable, and a certificate cannot alter the underlying coverage. The jurisdiction-specific rule should not be generalized as nationwide law, but it reinforces the practical need to send precise revised requirements to the appropriate parties.

Pre-response checklist

  • Both source versions are preserved.
  • The same project and scope are being compared.
  • Compound paragraphs are divided into atomic items.
  • Original values remain visible.
  • Apparent removals are marked for confirmation.
  • Unclear wording is not forced into a match.
  • Each change has a current action owner.
  • The revised deadline and effective date are distinguished.
  • The agent receives the actual current written request through an approved channel.

Frequently asked questions

Can I paste the whole contract into the tool?

No. Enter concise labels and values without confidential language, personal information, or policy numbers. Preserve the contract in the authorized system.

Does “appears removed” release the contractor?

No. It only describes the comparison. Confirm the controlling obligation with the client and obtain professional advice when needed.

What if the wording is different but seems equivalent?

Record it as changed or unclear until the appropriate source confirms equivalence.

Should unchanged items stay in the log?

Yes when they help prove the comparison was complete and define the current package scope.

Sources and scope

The comparison model is original administrative guidance. It does not decide which source legally controls.