Free pre-upload file-control tool

COI Submission Filename and Package Manifest Builder

Create consistent names for the files in one outgoing COI package, detect common organizational risks, and export a document-by-document manifest.

Labels stay in your browserNo document upload, account, policy number, server storage, or automatic renaming. Downloads are created locally.

Organization only. The builder cannot open, rename, authenticate, or verify a file. Always inspect the actual issued evidence and follow the client portal and your records policy.

Define one package convention

Use a neutral project reference. Avoid policy numbers, personal data, email addresses, and confidential contract wording.

Project or vendor reference * Package date * Package version * Component separator Maximum filename length Date meaning

I understand that generated names and statuses do not verify a document, policy, coverage, or client acceptance, and I will open every actual file before delivery.

Private package-control result

Your filename and manifest review

0Manifest rows

0Ready after review

0Warnings

0Duplicate names

Generated filename	Document type	Scope	Status	Warnings

Copy-ready package brief

Use the manifest as a check, not as evidence. Open every actual file, match it to one row, follow portal naming rules, and preserve the exact submitted snapshot and permitted receipt.

A filename is one control in a larger check

Name

Use consistent components without unnecessary sensitive identifiers.

Open

Verify that the actual document matches the manifest row and project.

Snapshot

Preserve the delivered set, permitted receipt, and observable review status.

Read: How to name COI files · Package manifest checklist · Avoid the wrong upload