Proof Functionality Takes Files Out of Souce Format

[#1]

ISSUE: PROOF FUNCTIONALITY TAKES FILES OUT OF SOURCE FORMAT

When using the proofing functionality, anything besides a PDF (e.g., Word DOC, Figma FIG, Powerpoint PPT) all get converted to a PDF therefore losing the working file so the agency must continually take feedback from a PDF and go back to the source document (Word DOC, Powerpoint PPT, etc). and reincorporate the feedback, creating room for error and missed feedback versus accepting, declining changes etc. 

• Conversations about the document are essentially happening outside of the working file when we use proofs, creating additional work for the agency team.
• This creates a scenario where the agency is 
• Referencing to “printed” PDFs to manually cross-transfer comment input back into source document creating risk because the team is working in multiple files
• Impact: High impact for all projects, high risk for errors, creating additional work for project management and creative

Ideal solve: documents uploaded as a proof would remain in their native source file format and could be downloaded and shared as such, removing the need for multiple versions of essentially the same document just in different formats

[#2]

We generate PDFs for proofing in Workfront.  When we release working files to vendor we do it through a different external process.

[#3]

We do the same thing that Richard Carlson mentioned. For example, we would not want to upload the InDesign files and have our users be able to change the files. In addition, the people we are sending these to for review do not have the InDesign software to be able to open it. Same with our video files. If this gets implemented, there needs to be an option choose when uploading a document to keep the native source or not.