Client file naming standard
Name client files as ClientCode_ProjectName_DocType_Date.pdf so every deliverable is traceable to a client and project without revealing confidential information.
- Lead with client code (not full name) to group all work for a client while maintaining confidentiality.
- Include project or engagement name to distinguish between multiple projects for the same client.
- Add document type (Proposal, Report, Presentation, Invoice) for quick filtering.
- Date deliverables with YYYY-MM-DD so versions sort chronologically without "final_v3" naming.
6.1k client deliverables organized with this pattern across 18 consulting firms and agencies.
Recommended patterns
Standard client file pattern
The standard pattern for agencies and consultancies. Client code first enables folder-level grouping. Date at the end eliminates version suffixes — the latest date is always the latest version.
ClientCode_Project_DocType_YYYY-MM-DD.pdfACME_BrandRefresh_Report_2025-10-15.pdfClient deliverable with version
Date-first pattern for firms that organize by timeline rather than client. Useful for consultants who need to see "what did I deliver this week" across all clients.
YYYY-MM-DD_ClientName_Deliverable_Version.pdf2025-10-15_AcmeCorp_Q4-Marketing-Plan_v2.pdfConfidential client pattern
For firms with strict confidentiality requirements (Big Four, law firms, M&A advisors). Uses opaque codes instead of client names. Only people with system access can resolve the code to a client name.
ClientCode_EngagementID_DocType_Date.pdfC-2025-042_ENG-1042_AuditReport_2025-10-15.pdfCore principles
Client code before project for top-level grouping
When browsing folders, you think "which client" before "which project." Client code first groups all work for a client together. Use the same code as your CRM or project management tool.
Use codes, not full names, for confidentiality
Client names in filenames visible on screen shares, email attachments, and cloud storage can create confidentiality issues. Codes like "ACME" or "C-042" are identifiable to your team without revealing client identity to outsiders.
Date deliverables — never use "final"
The word "final" in filenames is a lie. There is always another revision. Use dates instead: 2025-10-15 is unambiguous. The latest date is the latest version. No more "final_v3_FINAL_really-final.pdf."
Include document type for filtering
A single client project might produce proposals, reports, presentations, invoices, briefs, and contracts. Document type in the filename lets you find "all proposals for Acme" without opening files.
Match your project management system
If Asana, Monday, or Notion uses engagement IDs, use those same IDs in filenames. This eliminates translation between systems and enables automated filing.
Common mistakes
The "final_v3_FINAL.pdf" naming pattern
Every version gets called "final." After 3 rounds of feedback, you have final.pdf, final_v2.pdf, final_FINAL.pdf, and no one knows which is actually current.
Fix: Use dates: ACME_BrandRefresh_Report_2025-10-15.pdf. The latest date is always the latest version.
Using client nickname instead of official code
"Bob's project.pdf" is meaningless to anyone who joined the team after Bob left. Client nicknames are not searchable and not professional.
Fix: Use the client code from your CRM: ACME_BrandRefresh_Report_2025-10-15.pdf
No project identifier in the filename
A file named "ACME_Report.pdf" could belong to any of the 6 projects you have with Acme. Without the project name, you open the wrong file constantly.
Fix: Include project: ACME_BrandRefresh_Report_2025-10-15.pdf
Sharing files with internal naming conventions visible
Sending a client "C-042_ENG-1042_AuditReport.pdf" looks unprofessional and confusing. Internal naming is for internal use.
Fix: Rename for external delivery: "Acme-Corp_Brand-Refresh-Report_October-2025.pdf" for client-facing files. Automate the rename on export.
Inconsistent naming across team members
When Alice names files "ClientName_Date" and Bob uses "Date_ClientName," filtering and sorting become impossible across the shared drive.
Fix: Publish a team naming convention document and enforce it. Use renamed.to to automatically enforce the standard.
Frequently asked questions
Should the client code or date come first?
If you organize by client (most agencies), put client code first. If you organize by timeline (freelancers, weekly deliverables), put date first. The key is consistency across your entire firm.
How do I handle files shared between multiple clients?
Templates and internal resources should not have client codes. Use "Internal_Template_Proposal_v1.pdf." Once customized for a client, rename with the client code.
What about email attachments from clients?
Rename client-provided files to match your convention when you save them: ACME_BrandRefresh_ClientBrief_2025-10-15.pdf. This keeps incoming and outgoing documents in the same system.
How do I handle sub-contractors or white-label work?
Use the end client code (not the agency you report to) if you need to track deliverables by end client. For white-label work where you should not know the end client, use the agency as the client code.
Is there a standard for client codes?
No universal standard, but common patterns include: 3-4 letter abbreviations (ACME), sequential codes (C-042), or CRM-generated IDs. Pick one format and stick with it. Document the mapping in your CRM.
How do I name client files when the project spans multiple years?
Date individual deliverables by their delivery date, not the project start. The project name stays constant: ACME_BrandRefresh_Report_2025-10-15.pdf and ACME_BrandRefresh_FinalPresentation_2026-01-20.pdf.