Pre-upload control
How to Avoid Uploading the Wrong COI or Endorsement
The most dangerous file in a submission folder is often the plausible-looking stale copy. Control the source, filename, manifest, and submitted snapshot before clicking Upload.
Reviewed September 2026 · Educational information, not insurance, legal, or cybersecurity advice
Why the wrong file gets uploaded
- The Downloads folder contains several files named COI.pdf.
- An email draft retains the attachment from the prior attempt.
- A replacement certificate arrives while an older endorsement remains in the package.
- Two projects use similar client names.
- The submitter trusts “final” without opening the file.
- A portal category is confused with the document type.
- The certificate issue date is mistaken for a policy expiration date.
- A file was renamed correctly but its contents belong to another project.
A filename reduces ambiguity but cannot prove content. The control must join the visible name to an opened document and a manifest row.
The two-minute pre-upload check
- Clear the staging area. Put only candidate files for this project in the upload folder.
- Open each file. Confirm contractor, project relevance, document type, policy period, and requested parties.
- Compare with the requirement. Use separate rows for certificate, endorsements, and other evidence.
- Apply the package version. Do not mix V01 and V02 unless the manifest explains why.
- Resolve generated warnings. Check duplicates, blank components, length, and possible sensitive patterns.
- Match portal categories. A correct file in the wrong category can still delay review.
- Create the submitted snapshot. Preserve the exact set delivered.
- Record the receipt and status. Submitted is not the same as accepted.
Stage the package
Generate filenames, detect duplicates, and review one manifest.
No files are uploaded to COI Workbench; only the administrative labels you enter are processed in the browser.
Who resolves each kind of mismatch?
| Mismatch | Primary owner | Contractor action |
|---|---|---|
| Wrong client entity or holder address | Client | Request exact written clarification |
| Wrong named insured or policy data | Agent or issuer | Request accurate replacement evidence |
| Wrong local filename or package version | Contractor | Correct the organizational copy and manifest without altering content |
| Wrong portal category or receipt | Client process + contractor | Follow portal instructions and record the delivery event |
| Unclear endorsement meaning | Agent or qualified professional | Keep it as an open question |
Checks immediately after upload
- Confirm the portal lists the expected number of files.
- Open or download the submitted view when the authorized system permits it.
- Record the portal receipt or neutral submission reference.
- Preserve the exact submitted snapshot and manifest.
- Do not delete source files required by the records policy.
- Track received, under review, correction requested, and accepted separately.
If the wrong file was delivered, use the portal’s approved replacement or withdrawal process and notify the appropriate reviewer. Do not assume that uploading a second file automatically removes the first.
Useful warning rules
| Warning | Why it deserves review |
|---|---|
| Duplicate filename | Two manifest rows may overwrite or become indistinguishable |
| Missing date or version | The package may be hard to reconstruct later |
| Long digit sequence | Could be an unnecessary policy or account identifier |
| Email address | May expose personal or operational data in portal logs |
| Very long name | Can contribute to path or portal length problems |
| Approval words | May imply a review outcome that has not occurred |
Frequently asked questions
Can the tool inspect my PDFs?
No. It intentionally accepts only administrative labels. The user must open and verify the actual files in the authorized local system.
Should I merge the certificate and endorsements?
Follow the client and issuer instructions. Separate files often make the manifest clearer, but some portals specify a package format.
What if the portal changes the filename?
Record the portal’s resulting label or receipt if relevant. Preserve the original submitted snapshot according to your records policy.
Does a duplicate warning mean the documents are identical?
No. It means the generated names collide. The contents could be different, which is exactly why the collision needs review.
Sources and scope
- U.S. National Archives: File and folder naming
- NARA Records Express: File naming practices
- CSU Stanislaus: Certificate and endorsement guidance
The warning rules are conservative prompts, not security or compliance determinations. Adapt the workflow to the portal and organizational records policy.