The situation you've described seems relatively up-in-the-air when I think about our process.Projects are defined by their deliverables, deliverables are chosen in custom forms in request queues.  As much as possible we aim to have as much information as possible present in the request when it's ope...

Instead of mailing out the report once a day have you considered adding the report to their dashboard so that they can see it updated throughout the day?

As difficult as it might be, I think that step 1 would be for everyone to only generate proofs in Workfront

I was just curious if this report would be able to report on proofs generated outside of Workfront, like described in the original post.My guess is that the answer is no?

My concern would be relating to the difficulty of tracking proofs made outside of Workfront.  Is there any way to stop this practice in order to introduce more consistency?   I'm just curious how these users are accessing the proofing backend, can you simply remove the proof button from their Workfr...

In my experience each proof link is individualized and if I were to share my personal proof link with someone else it effectively mean that they're doing the commenting as me. In our environment we make sure that each user or reviewer has their own individual accounts, so sharing proofs is done via ...

We have it set so that proofs automatically generate when someone uploads a document to the documents folder - can you help me understand the benefit of your process where proofs are generated some time after file upload?

If you are creating a user report it should be fairly straightforward to pull up a field that will display the user name. If you are creating a different type of report it can be difficult to report on certain objects which reside more than 2 levels away from the object without text mode.

I'm not sure exactly what you're looking for but we use the Status Update column in project reports to show the last comment in the project