Editing File Management Procedures (section)

==Production Process==

After a project is approved for production, no more work should be saved or completed in the Creative folder. All retired concepts and previous layouts should be moved to Old Layouts. 

The approved file should be Packaged or copied to the Build folder, collecting all assets and fonts if the source files will be released to vendor. This ensures that all linked files are collected for release. This step can happen after all final production on the file is complete, if there is more photo production to complete, but the work should be completed on a file resaved to Build with our typical file naming conventions.

In many cases, there are images to purchase at this stage, and updated in the packaged files. Remember to copy any purchased images to the Photos – Logos library in the appropriate folder. Additional Photoshop work that occurs on a stock photo for a particular concept can remain in the Build folder for that job unless it is being used across multiple projects.

All final edits during production should take place in the Build folder by iterating the file names forward with our alphabetical codes (eg c1'''b'''-XXXXX-v3 becomes c1'''c'''…). Because of conflicts in synching across Box and the servers, we must always give these files a new name and move the older version into an Old Layouts folder. 

When final production is complete, designer will fill out QA worksheet and let proofer know via timestamp that the files are ready for review. Proofer completes QA checklist and alerts designer if any changes are required. When QA is finished, proofer will move whatever files are being released to the Final folder. If only a PDF is being released, the source files remain in Build. If all files are being released, the Build folder should be empty to avoid confusion about which files are final.

Client share files are created by copying the contents of Final to a shared folder on Box. There is no need to compress files into a zip file unless requested. A link to the shared folder should be posted to Seeker.

''Quest Template exceptions''

The one exception to this process is in template jobs, such as map pads, which have different locations for the shared assets and aren’t recollected for release as InDesign packages. If the final deliverable is a print-ready PDF, there is no need to recollect all assets in Build.