Feedback cycles:
What happens when changes need to be made
Not all work is perfect first time round. Seeking feedback from peers often brings about suggestions, changes and even questions to prompt conversations between proofers.
Once the proof has travelled 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.
When you’ve finished you’re able to 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 less proofers, or a different group of proofers all together.
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.
This clarity and history that PageProof provides reduces your feedback cycles saving you and your proofing team valuable time.