Proofing best practices - How do you post the final document?

we have integrated workfront and proof (not standalone proof) and for us the project or task/issue object drives everything. So if you have uploaded the final, you would complete the task or issue and the requestor would be notified through this action. Several teams also have a system of marking the final file, whether that's by naming convention or document custom form, and reports are provided that list all the finals. (e.g. our planogrammers have a report showing final files by display date, which is basically a task report filtered on a task status that provides a collection column reading the documents in each task for ones that are final).

Similar to Skye's process, the project and task/issue drives everything for us as well. Once the new file is uploaded, the user marks their "revisions" task complete, then the project manager gets a task to "Provide final files" to our internal business partner. However, rather than uploading files to the task itself, every project template has a folder labeled "Final Files" that those files are uploaded to.

Another thing to consider is do you need to maintain a full version history of the proof in Workfront? Does every version of the proof, and the final, need to be "bundled" together? Or is it OK if the final version is separate from the proofs of the work in progress?

Our finals are only recorded as an upload to a digital asset manager (not Workfront's). We only use WF for change cycles and approvals…the "final" never ends-up there. Well, except as an accidental byproduct of a round of approvals where no changes are requested. The DAM is the system of record for final artwork.

I wish there were a button in WF that would allow for download/delivery of the final, approved, clean file to the original requestor.