Digital Tools & Software
Client Deliverable File Naming: A Version System That Works

A client opens a folder and sees Homepage-final.fig, Homepage-final2.fig, and Homepage-FINAL-use-this-one.fig. The file itself may be excellent; the handoff still feels uncertain. A practical client deliverable file naming convention solves a small but costly problem: it tells a client what a file is, which project it belongs to, and whether it is a draft, approved version, or final export, without asking them to remember your internal workflow.
This guide gives freelancers and small studios a repeatable file-naming system for client deliverables, version control, and project handoffs. It is designed for work that moves between email, Google Drive, OneDrive, Dropbox, design apps, and a client’s own archive. The goal is not to impose a complicated document-management scheme. It is to make the right file easy to identify months later.
On this page
The file-name problem is really a decision problem
Most version confusion is not caused by a lack of folders. It happens because the name does not answer the client’s next question: “Which one should I review?” or “Is this the approved file?” A name like Landing-Page-v03-2026-11-04-APPROVED.pdf carries more useful information than final-new.pdf, but only if each part has a consistent meaning.
Use names to identify the project, the deliverable, and its state. Use the folder structure to group related work. Use the cloud service’s version history or your source application’s history for incremental edits. These are different jobs: putting every save number in the filename creates clutter, while relying on hidden version history makes a downloaded attachment hard to interpret.
A naming convention clients can scan
For most project files, start with the client or project identifier, then the deliverable, then an optional round or date, and finish with a state only when the state matters to the recipient.
Project-Deliverable-Round-YYYY-MM-DD-Status.ext
For example: Northstar-Homepage-Copy-R02-2026-11-04-Review.docx. Keep the date in year-month-day order so files sort chronologically in common file browsers. Avoid punctuation that behaves differently across systems, client names that expose confidential information, and ambiguous words such as “new,” “latest,” or “final-final.” Use a short agreed project code if the client’s name is sensitive.
| Part | Example | Include it when |
|---|---|---|
| Project | Northstar or NS-24 | The file might leave its folder or be downloaded |
| Deliverable | Homepage-Copy | Always; make it recognizable to the client |
| Round | R02 | When the client is reviewing a defined revision round |
| Date | 2026-11-04 | For dated exports, recurring reports, or snapshots |
| Status | Review, Approved, Final | Only when the recipient needs to distinguish the state |
Choose one separator, usually a hyphen, and use it everywhere. Preserve the real extension, such as .pdf, .docx, .fig, or .xlsx. Do not rename a file extension to make an app open it; export to the correct format instead.
When to use versions, dates, and status labels
Version numbers and review rounds are not interchangeable. A review round records a client-facing cycle: R01 is the first review package, R02 is the next. A working version number can track internal iterations, but it should stay inside the design app or project system unless the client needs it. A date distinguishes a snapshot, not an approval.
Use status words sparingly. “Review” means the client is being asked to check it. “Approved” should mean the client actually approved that deliverable, not that you believe it is ready. “Final” should be reserved for the agreed final package. If the approval is limited, say so in the delivery note, for example, “Approved for web use; print export still pending.”
| Situation | Filename cue | What not to imply |
|---|---|---|
| First client review | R01-Review |
Do not call it final |
| Revised review package | R02-Review |
Do not silently overwrite R01 if the client may need to compare |
| Signed-off output | Approved or Final |
Do not use approval language before written sign-off |
| Monthly report or dated snapshot | 2026-11 or 2026-11-04 |
A date alone is not an approval status |

A handoff folder that makes the final obvious
Keep the folder structure shallow enough that a client can find the output without learning your whole project-management system. A useful default is:
- 01-Review: the current package awaiting client feedback
- 02-Approved: approved deliverables, if approval is staged
- 03-Final: final exports and any source files included in scope
- Archive: superseded review packages only when there is a real reason to retain them
For a small one-off project, these can be files in one folder rather than four subfolders. The important part is a single, clearly identified current review or final location. Do not leave multiple folders named “final,” “final new,” and “final latest.” If the work includes source material, licensed stock, or assets the client cannot reuse freely, separate those from the deliverables and label the permissions accurately.
Cloud version history is helpful for recovering edits, but it is not a substitute for a client-ready handoff. Shared links may also point to a changing file. If you share a live document, state that it is a live working file and confirm what the client should download or approve. For the final package, consider an export or snapshot that will not change when you continue editing the source.
A practical naming table by deliverable
Keep the same core pattern across formats, but add only the detail that clarifies the handoff. A client should not need to decode your naming system before opening a deliverable.
| Deliverable | Example | Why it works |
|---|---|---|
| Website copy review | Northstar-Homepage-Copy-R02-Review.docx |
Project, content, round, and requested action |
| Approved design export | Northstar-Homepage-Desktop-Approved.pdf |
Identifies the screen and approved state |
| Final logo package | Northstar-Logo-Final-RGB.zip |
Separates the final bundle and color mode |
| Monthly analytics report | Northstar-Analytics-2026-10.pdf |
ISO month sorts and defines reporting period |
| Invoice or statement | Northstar-Invoice-2026-11-04.pdf |
Date helps the recipient file and retrieve it |
Use “Final” for the deliverable state, not for every export variation. If a package has distinct formats, include the format or use subfolders: RGB versus CMYK, Web versus Print, or Desktop versus Mobile. Do not put passwords, personal data, or payment information in filenames.
The review-to-final workflow
A naming convention sticks when it is connected to a simple handoff routine. Before sending a review link, make a dated or round-specific snapshot, confirm that the link opens with the intended access, and write one sentence explaining what feedback you need. When the client approves, preserve the approved review package if it is useful for the record, then export the final deliverable into the final location.
- Prepare: name the item using project, deliverable, and round; remove internal notes and comments that should not be shared.
- Share: send one review link and identify the requested decision or deadline. Avoid attaching several files that compete to be “the latest.”
- Record approval: keep the client’s actual approval in the project record. A filename is a label, not evidence of consent.
- Finalize: export the agreed formats and place them in the final location. If a scope item remains open, label that limitation in the message, not with a misleading “complete” filename.
- Close: check access, file integrity, and included formats before archiving the project.
This pairs well with a clear written approval process. See our freelance project timeline and client approval guide for setting review gates, and our deliverable provenance log for recording what was handed over and when.
Exceptions: live files, exports, and recurring work
Some work should not be frozen into a succession of attachments. A shared spreadsheet, design source, or website prototype may be intended to remain live. Name it as a source or working file, and make clear in the delivery note that updates continue in that location. If the client also needs a point-in-time record, export a dated PDF or archive snapshot separately.
For recurring deliverables, use a period rather than an arbitrary version number: Client-Report-2026-10.pdf. For a batch of assets, put the common project and campaign in the folder name and give each file a concise asset-specific name. For sensitive engagements, use an internal project code in filenames that could be forwarded outside the secure folder.
Some platforms maintain their own history, coauthoring, and recovery features. Learn the service’s behavior before relying on it: cloud history may have retention limits, and downloading a copy can detach it from that history. Keep the client’s access needs, file format, retention requirements, and your contract in view rather than assuming one storage setting fits every project.
A 10-minute cleanup before delivery

Before sending the handoff, search the package for ambiguous names and duplicate finals. Open the actual files, check that the right format and pages are present, and test the share link in a private browser window or with a non-owner account where appropriate. Confirm that the client can view or download what you intended, but do not grant broad folder access just to avoid an access question.
Then send a short index: what is included, which item is final, what remains outside scope, and where the client should ask for changes. If the client needs the editable source, include it explicitly. If it is not part of the agreed scope, do not imply that a flattened PDF is the source file.
A good file naming convention is deliberately boring. Once clients can tell a review from an approved final without asking, the convention is doing its job. Keep the names predictable, the approval claim honest, and the link to the current package unmistakable.
FAQ
What is the best file naming convention for client deliverables?
A reliable default is Project-Deliverable-Round-Date-Status.ext, with optional parts omitted when they add no clarity. Keep it consistent, readable, and free of confidential details.
Should I put “final” in a filename?
Only when the file is genuinely the agreed final deliverable. If it is waiting for client approval, use “Review” or a review round instead. Never label a file approved based only on your own readiness check.
Should version numbers go in every file name?
No. Keep routine edits in the source app’s history or cloud version history. Add a client-facing review round or date when the recipient needs to compare or identify a fixed handoff snapshot.
Are dates better than version numbers?
They answer different questions. A date identifies when a snapshot or report applies; a version or round identifies an iteration. Use ISO order, YYYY-MM-DD, when chronological sorting matters.
How do I avoid sending the wrong Google Drive or OneDrive file?
Share one clearly labeled current review or final location, check the permissions, and describe whether it is a live file or a fixed export. Cloud version history helps recover changes but does not make an unclear handoff self-explanatory.
Should I keep old client versions?
Retain only what is useful and permitted by your contract, the client’s retention policy, and applicable privacy obligations. Remove unnecessary copies securely and avoid keeping sensitive client material indefinitely by default.

