COI Submitted vs. Accepted: How to Track Delivery and Review Status

by

Status control

COI Submitted vs. Accepted: How to Track Delivery and Review Status

“Sent” is a delivery event, not a review decision. Separate preparation, submission, receipt, review, correction, and acceptance so the project team knows what has actually happened.

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

Administrative status only: a portal label or client acceptance message is not a policy interpretation, guarantee of coverage, or legal conclusion. The policy, endorsements, applicable law, and facts control.

Six states that should not be collapsed

Status Observable event What it does not prove
Prepared A candidate package is assembled and checked That it was delivered
Submitted The sender completed the approved delivery action That the recipient received or reviewed it
Received A portal, recipient, or system confirms receipt That the evidence is acceptable
Under review The reviewer or system identifies an active review That no correction will be requested
Needs correction The reviewer identifies an unresolved item That every other field was approved
Accepted The authorized reviewer or system records acceptance That the policy will respond to every future event

The exact portal terminology may differ: pending, uploaded, verified, compliant, approved, expired, rejected, or waived. Record the system’s actual label and map it cautiously to your internal workflow. Do not upgrade “uploaded” to “accepted” merely because the project deadline is close.

What to retain for each administrative state

Prepared

Retain the controlled package checklist and the version label. The working package should be compared with the reviewer’s current written request, not with an old project template.

Submitted

Record the date, time if relevant, channel, submitter, and exact version. Preserve the sent-message record or portal submission event according to the organization’s records policy.

Received

Use a receipt ID, confirmation page, system notification, or recipient acknowledgment. A log can store a neutral reference rather than the full potentially sensitive message.

Under review

Record the reviewer or system state only when observable. If there is no review confirmation, use “submitted” or “received,” then add an internal follow-up date.

Needs correction

Preserve the exact response and separate every requested change. A rejection may be administrative, but the contractor should not alter certificate or endorsement content. The authorized agent or issuer handles issued evidence.

Accepted

Retain the acceptance notice or final portal state under the applicable records policy. If acceptance is conditional, expiring, limited to a project, or subject to renewal, record those visible qualifiers without expanding them.

Official contracting guidance often distinguishes certificates from required endorsements and other documentation. For example, King County’s insurance requirements and CSU Stanislaus’s certificate guidance describe evidence beyond a bare certificate. That is why “file received” and “package accepted” can be different events.

A follow-up workflow that avoids status inflation

  1. Log immediately after delivery. Capture the version and route while the details are fresh.
  2. Check for a receipt. If none exists, do not mark “received.” Follow the permitted delivery process.
  3. Set an internal follow-up date. Base it on the project deadline and the client’s stated review process, not on an invented universal waiting period.
  4. Record every response as a new event. Never overwrite the submission event with the latest status.
  5. Open a new version when the package changes. Link it to the preceding correction request.
  6. Close the cycle with the observable result. Accepted, needs correction, withdrawn, superseded, or another accurate status.

Separate the states

Build a chronological COI delivery and review history.

Track up to eight attempts or responses, calculate the current status, and export a local CSV for your authorized project file.

Create a status log

Three common scenarios

Portal says “uploaded”

Record Submitted. If the portal also produces a receipt, record Received. Wait for an explicit review state before using Accepted.

Reviewer replies “please correct the holder address”

Record Needs correction with a concise faithful summary. Confirm the exact address with the client, route the issued-document request to the agent, and create a new version only when the outgoing package changes.

No response before mobilization

Do not treat silence as acceptance. Escalate through the project’s approved contact path and record the follow-up. Contractual decisions belong to the appropriate client, legal, insurance, or project professional.

Useful questions for the client reviewer

  • Which portal or delivery route is authoritative for this project?
  • Does the confirmation show upload only, or completed review?
  • Should a correction replace the complete package or only the requested item?
  • Which exact entity and address should appear in the certificate-holder block?
  • Which supporting endorsements or issued evidence are required?
  • Who can confirm acceptance and renewal requirements?

Useful questions for the agent or broker

  • Which current issued files answer each requested evidence item?
  • Was a replacement certificate issued, and what changed from the prior version?
  • Are separate endorsements involved for different parties, operations, or policy lines?
  • Are any requested statements unsupported or inappropriate for the certificate?

Frequently asked questions

Can the contractor mark a package accepted?

Only record acceptance when it comes from the authorized reviewer or system. An internal team may mark its own preparation complete, but that is a different status.

What if the portal changes from accepted to expired?

Record both events. Acceptance of one evidence period does not eliminate later renewal or expiration requirements.

Does an acceptance message prove coverage?

No. It records the reviewer’s administrative outcome. Certificate text does not amend the policy, and acceptance does not replace policy analysis by qualified professionals.

Should screenshots be stored?

Follow the organization’s security, privacy, and records rules. A neutral receipt reference may be enough for the working log; the authoritative record belongs in the approved system.

Sources and scope

The status model is an original administrative framework. Portal labels, legal effects, deadlines, and evidence requirements vary; follow the current written instructions for the specific project.