Independent guide
File naming and version control for custom design
Clear names reduce the risk of an obsolete proof reaching production.
Updated 2026-09-10
Choose a stable structure
Use project, item, version and date in a consistent order. Avoid labels such as final-final and keep the version visible on the proof as well as in its filename.
Separate file roles
Store editable masters, linked assets, review PDFs and production exports in named folders. Keep superseded proofs in an archive outside the production handoff.
Record approval
Log the exact approved filename, approver, date and exceptions. Any later change creates a new version and requires a new approval.