File organization
How to Name COI Files for Client Portals
A useful filename identifies the project, document type, relevant date, and controlled version without exposing policy numbers or pretending that a file is approved.
Reviewed September 2026 · Educational information, not insurance, legal, or cybersecurity advice
Use one predictable pattern
The National Archives and Records Administration recommends descriptive, consistent, meaningful naming conventions and keeping components such as project names, dates, and versions in the same position. For a contractor evidence package, a practical pattern is:
ProjectRef_DocumentType_CoverageOrScope_Date_Version.ext
This is a working convention, not a portal standard. If the client specifies a different filename, extension, maximum length, or upload category, follow the current client instruction.
What each component contributes
| Component | Purpose | Safer example |
|---|---|---|
| Project reference | Connects the file to the correct job without a full confidential title | Riverside417 |
| Document type | Distinguishes certificate, endorsement, receipt, or requirement | Certificate |
| Coverage or scope | Separates GL, Auto, WC, Umbrella, or package-wide evidence | GL |
| Date | Supports sorting and identifies the relevant package date | 2026-09-30 |
| Version | Distinguishes controlled submission attempts | V02 |
| Extension | Preserves the actual file format |
Use the date consistently. It might represent the certificate issue date, policy expiration, package date, or submission date, but the team should decide which meaning applies and record it in the manifest. A filename cannot carry every date displayed inside the document.
Prefer stable, portal-friendly characters
NARA guidance uses letters, numbers, underscores, and hyphens and warns that complete file paths can become too long. The UK National Archives likewise recommends unique, consistently arranged filenames built from letters or numbers with limited separators. A conservative portal filename avoids spaces, repeated periods, slashes, quotation marks, and decorative symbols.
Keep versions sortable
V01, V02, and V03 sort more predictably than final, final2, and final-really. A version should identify an actual package or controlled revision. Do not label a file Approved, Accepted, Compliant, or Renewed unless the label accurately reflects an authorized, documented status.
Keep unnecessary sensitive data out of the filename
Filenames can appear in email subjects, portal notifications, browser download lists, sync logs, and search results. Do not place policy numbers, taxpayer identifiers, personal phone numbers, email addresses, birth dates, claim numbers, or confidential contract wording in a general filename. Use a neutral internal project reference.
The builder flags long digit sequences and email-like text as a prompt for human review. It cannot determine whether a value is actually sensitive, so the user remains responsible for the decision.
Build the convention
Create filenames and a package manifest without uploading documents.
Detect duplicates, missing fields, excessive length, and potential sensitive patterns before the client upload.
Examples
| Weak filename | Controlled alternative | Reason |
|---|---|---|
| new coi final.pdf | Riverside417_Certificate_Package_2026-09-30_V02.pdf | Identifies job, type, scope, date, and version |
| endorsement.pdf | Riverside417_Endorsement_GL_2026-09-30_V02.pdf | Separates endorsement and coverage line |
| COI-policy-123456789.pdf | Riverside417_Certificate_Package_2026-09-30_V02.pdf | Removes an unnecessary long numeric identifier |
| approved.pdf | Riverside417_SubmissionReceipt_Package_2026-10-01_V02.pdf | Records the actual document instead of making an approval claim |
Pre-upload filename check
- Confirm the file belongs to the correct project.
- Open it and identify the actual document type.
- Use the intended date meaning consistently.
- Apply the same version to every file in one controlled package.
- Check for duplicate generated names.
- Remove unnecessary sensitive values.
- Compare the manifest with the client’s upload categories.
- Preserve the exact submitted snapshot and receipt.
Frequently asked questions
Should I rename files received from my agent?
Follow the issuer’s, client’s, and company’s procedures. If a local filing copy is renamed, never alter its contents and retain enough provenance to identify the original.
Should the policy expiration date be in every filename?
Only if that is the defined convention and it helps the workflow. The manifest can retain the date meaning without making filenames excessively long.
Do hyphens or underscores work better?
Both are commonly portable separators. Choose one pattern and use it consistently unless the portal specifies otherwise.
Does a clean filename prove the file is correct?
No. It improves organization only. Open and compare the actual issued evidence.
Sources and scope
- U.S. National Archives: Recommended File and Folder Naming Conventions
- NARA Records Express: Best Practices for File Naming
- UK National Archives: Digitisation and filenames
The COI pattern is an original administrative convention. Client portals and organizational records policies control.