Which of the following best describes recommended naming conventions and file organization for large catalog shoots?

• A. Use inconsistent file naming and random folders.
• B. Use consistent file naming (project_date_client_product_revision), structured folders (RAW, PROOFS, FINAL), include metadata, track version history, and maintain offsite backups.
• C. Store all files in a single folder without backups.
• D. Rename files per client contract.

Answer: (B)

In catalog photography, a clear, scalable system for naming and organizing files is essential because you’re often juggling thousands of assets across many shoots. The best approach uses a consistent file naming scheme that encodes key details for quick identification—something like project_date_client_product_revision. This means each file carries its own context: which project it belongs to, when it was shot, who the client is, what product appears, and which revision it represents. That self-describing name makes searching, sorting, and cross-referencing assets fast and reliable, even after years of work.

Pair that with a structured folder hierarchy that keeps different stages separate—RAW for untouched captures, PROOFS for proofs or previews, and FINAL for approved deliverables. Keeping these stages in distinct folders prevents mixing files at different processing levels and helps protect the integrity of the final deliverables. Adding metadata (keywords, shoot date, client, product, location, equipment) makes assets even more searchable in a digital asset management system, so you can find exactly what you need without opening dozens of folders. Tracking version history gives you visibility into what changed between revisions and lets you revert if a decision gets overturned. Finally, maintaining offsite backups guards against data loss from hardware failure or emergencies, which is crucial for large catalogs.

In contrast, inconsistent naming and random folders create confusion, slow down collaboration, and raise the risk of misfiling or losing assets. Storing everything in a single folder without backups makes retrieval inefficient and endangers the archive. Renaming files only per client contract fragments the naming system and undermines the ability to trace assets across projects.