Not all work is perfect the first time around. Seeking feedback from team members and stakeholders often brings forth suggestions, changes, and even questions that prompt conversations between reviewers.
Once the proof has traveled through its workflow, the final approver confirms which comments need action by marking them as to-dos. As the proof owner, you’ll be notified of this to-do list when it’s ready.
How to action changes requested on the proof
As you would normally do with your work when receiving feedback, you make changes to your file and at the same time mark off the to-dos in PageProof as done – the red pins will change to green. This is made even easier through the use of the PageProof plugin for Adobe Creative Cloud.
When you’ve finished, upload a new version of your work to start the feedback cycle again. We’ve made it simple by suggesting you use the same workflow as before, but you can change this if this new version of your work needs to be reviewed by fewer reviewers, or a different group of reviewers altogether. In fact, you can easily skip reviewers who have previously approved, or start the workflow at a certain step in this new proofing round.
A full version history is kept
When a proof involves more than one version, you can switch between versions and see all related comments, whether they were marked by the final approver as a to-do for action, and whether the proof owner marked them as done. See proof versions side-by-side. Even use Smart Compare – which automatically highlights the differences between versions for you.
This clarity and history that PageProof provides reduces your feedback cycles, saving you and your proofing team valuable time.