Workflow
A practical file-naming system for print projects
Build a naming and folder system that makes the approved artwork obvious, prevents version mistakes and speeds up every print reorder.
A print error often begins before a file reaches production. Someone attaches an older logo, exports the wrong size, or mistakes “final-2” for the approved version. A clear file name turns those decisions into information the whole team can see.
The best system is not the longest or most technical one. It is a small set of rules that a client, designer, account manager and production partner can all follow without explanation.
01
What a useful file name should tell you
A good name answers the questions that matter at handoff: which project is this, what item does it belong to, which version is it, and is it ready to produce? Include only fields that help someone choose the correct file.
- Project or client code: a short, consistent identifier such as ACME or PB1042.
- Product: for example business-card, banner, pouch or staff-shirt.
- Variant: size, language, location, colour or employee name only when variants exist.
- Date: use YYYY-MM-DD when the date is useful for approvals or archives.
- Version: use v01, v02 and v03 so files sort in the correct order.
- Status: use a controlled term such as DRAFT, REVIEW or APPROVED.
02
Use one readable pattern
Choose a single order and keep it everywhere. Separating fields with hyphens makes names readable across common systems and avoids problems created by spaces or unusual characters.
- Simple job: PB1042-business-card-v03-APPROVED.pdf
- Multiple languages: PB1042-menu-EN-v04-APPROVED.pdf and PB1042-menu-FR-v04-APPROVED.pdf
- Multiple sizes: PB1042-banner-33x81in-v02-REVIEW.pdf
- Personalized items: PB1042-name-badge-Alex-Chen-v01-APPROVED.pdf
03
Separate working files from production files
Editable design files, linked images, fonts, proofs and approved PDFs serve different purposes. Keeping them in dedicated folders reduces the chance that an unfinished source file is uploaded for production.
- 01-Brief: requirements, dimensions, copy and reference material.
- 02-Working: editable layouts and linked assets used by the designer.
- 03-Proofs: dated review PDFs and client comments.
- 04-Approved: the signed-off artwork and approval record.
- 05-Production: only the exact files intended for upload or manufacturing.
- 06-Archive: completed source package, licences and final documentation.
04
Version numbers prevent “final-final” confusion
Increase the version every time artwork is sent for review. Do not overwrite an approved proof with new changes, and do not reset the version number when the file moves between team members.
- Use v01 for the first review, then v02, v03 and so on.
- Keep APPROVED for the one version the client has accepted.
- If approved artwork changes, create the next version and request a new approval.
- Record the approver and approval date outside the filename when a formal audit trail is needed.
05
Make names safe for teams, uploads and archives
A file may move between macOS, Windows, cloud storage, email, an upload portal and an archive. Simple names survive those transfers more reliably and are easier to search.
- Avoid slashes, colons, quotation marks, question marks and emoji.
- Do not distinguish files only by uppercase and lowercase letters.
- Keep extensions intact and visible during final checks.
- Use concise names so important fields are not hidden when a screen truncates them.
- Remove personal or confidential information unless it is required for controlled personalization.
06
Run a 60-second handoff check
Before uploading, compare the filename with the order: product, finished size, language, quantity-dependent artwork, sides and version. Then open the PDF itself—an excellent filename cannot prove that the artwork inside is correct.
- Confirm that the APPROVED file matches the latest approval message.
- Open every page and verify orientation, size, bleed and safe margins.
- Check that front and back files cannot be confused.
- Remove obsolete production files from the upload folder.
- Archive the delivered package so the next reorder starts from a known source.
A naming rule your team can adopt today
- Choose one field order and separator
- Use a short project or client code
- Add item and variant only when useful
- Number versions with two digits
- Reserve APPROVED for signed-off artwork
- Keep production files in a dedicated folder
- Open and inspect the PDF before upload
- Archive the approved source for reorders