Portal status
COI Portal Status: Uploaded vs. Received vs. Accepted
Portal labels describe workflow events, not interchangeable conclusions. Preserve the exact wording and connect each later state to the package version and evidence that supports it.
Reviewed September 2026 · Educational information, not insurance or legal advice
A conservative status ladder
| State | What it can mean | What it does not establish |
|---|---|---|
| Selected locally | A file is staged in the browser or upload control | Transmission |
| Submitted | The user performed a final send or submit action | Destination receipt |
| Uploaded | The system displays a completed transfer for a file | Correct category, readable content, or review |
| Received | The destination acknowledges the package or item | Substantive acceptance |
| Processing | The system is performing an automated or queued action | Human review |
| Under review | The platform or reviewer expressly shows active review | Acceptance |
| Needs correction | A returned issue requires action or clarification | Failure of the policy or coverage |
| Accepted by reviewer | The authorized workflow communicates acceptance for its purpose | A guarantee that a policy will respond to a future claim |
Different systems use different labels. A portal may skip “received,” combine processing with review, or use “complete” for profile completion rather than document acceptance. Read nearby instructions and preserve the screen or notification according to organizational policy. The exact portal definition controls its workflow meaning.
Connect every status to observable evidence
A useful status record includes the project reference, package version, filename or package scope, category, displayed status, timestamp, time zone, and transaction or message reference when available. Record who observed the state and when, especially if the portal does not retain a visible history.
Do not backfill an earlier event from a later one. If the reviewer accepted package V03 on Friday, that does not prove when each file was uploaded on Tuesday unless a separate portal record supplies that timestamp. If a later correction replaces one file, preserve the earlier V03 record and create V04 rather than changing history.
Separate the events
Compare each expected file with its exact portal status.
Build a private matrix for filenames, categories, timestamps, references, and follow-up prompts.
Status examples and correct next actions
File selected, submit button still available
Status: selected locally. Complete the authorized final-submit step. Do not record a receipt timestamp.
Package banner says success, one row says rejected
Status: mixed result. Preserve the banner and the file-level rejection. Investigate the rejected row before describing the package as received in full.
All rows say uploaded, no reference appears
Status: uploaded with receipt reference unavailable. Preserve the final list and timestamp if allowed, then schedule acknowledgment follow-up.
Automated email says submission received
Status: receipt recorded for the scope identified by the message. Do not assume human review.
Portal says complete
Read the definition. “Complete” may mean all required profile fields exist, the upload finished, or review closed. If the meaning is unclear, retain the literal word and ask the portal owner.
Reviewer says accepted until renewal
Status: accepted by reviewer with a future evidence checkpoint. Preserve the message and create the renewal task; do not delete the acceptance qualifier.
Why acceptance still has a boundary
A client’s reviewer evaluates evidence for its own contract or onboarding workflow. The licensed agent or issuer controls what insurance evidence can accurately be issued, and the policy plus endorsements, law, and facts control coverage questions. The Texas Department of Insurance emphasizes in its jurisdiction-specific FAQ that a certificate cannot alter or extend coverage and that certain statements depend on policy or endorsement support. Therefore, “accepted by reviewer” should never become “coverage guaranteed.”
The University of California describes certificates as evidence used in contract workflows and assigns issuance responsibilities for its own program to designated offices. That illustrates distinct ownership: the contractor can prepare and submit; the portal can record a technical event; the client can review its requirement; and the issuing professional controls issued insurance evidence.
Controls for reliable status history
- Use one package version per frozen outgoing snapshot.
- Record file-level results when available rather than relying only on a banner.
- Preserve the portal’s exact status label.
- Keep actual timestamps distinct from planned dates.
- Retain the time zone or portal locale when timing matters.
- Do not use “accepted” without an authorized observable source.
- Start a new version when a corrected file is sent.
- Connect each correction to the original reviewer issue.
- Schedule follow-up for submitted or uploaded items without acknowledgment.
- Follow approved retention and access rules.
Common reporting errors
- Calling a selected file uploaded before pressing submit.
- Calling a general success message proof that every row succeeded.
- Treating an automated acknowledgment as human review.
- Combining received and accepted into one date.
- Replacing a rejected row in the historical record.
- Describing a technical upload failure as an insurance deficiency.
- Using the newest portal status without identifying the package version.
- Calling client acceptance a coverage opinion.
Frequently asked questions
Which status should I use if two labels appear?
Record the most specific file-level label and preserve the package-level label separately. Do not average them into a stronger conclusion.
What if the portal has no history?
Preserve permitted confirmation evidence at the time of submission and maintain an internal event log. Follow company and client rules.
Can “approved” be used?
Use the portal’s exact term with attribution, such as “portal status: approved,” and keep the page’s limits clear. “Accepted by reviewer” is less likely to imply insurance verification.
Does a green icon mean accepted?
Not without a label or portal definition. Record the icon only as an observation and ask what it means.
What if the portal later changes the status?
Add a dated event. Do not overwrite the earlier state.
Sources and scope
- Texas Department of Insurance: Certificate limits
- University of California: Certificate evidence roles
- U.S. National Archives: Consistent names and versions
The status ladder is original administrative guidance. Portal-specific definitions and the actual source record control.