Approved with Changes option in ProofHQ

[StephanieHa3]

Hi, We have run into a roadblock with the "Approved with Changes" option within ProofHQ. We currently have our schedules/tasks set up for each person to approve the proof and we have also created automated workflows within ProofHQ to follow the same workflow. Our challenge is when a user makes a comment and selects "Approved with Changes" in ProofHQ and marks off their task within the schedule, the next person's task is activated and Workfront shows it's "Ready to Start". The challenge is the proof is not ready for the next stage in the schedule because the Designer has not updated it yet with the respective changes. Has anyone else run into this challenge? We've brainstormed removing the tasks from the schedule but that would be hard to track where we are in a project and would make our teams very reactionary rather than proactively planning out their day/week. Thanks! Stephanie Haslbeck Navy Federal Credit Union

[Richard__Carlson]

Approved with changes has to be very minor changes which would not require further review. Perhaps a situation where all of the layout and art on a page was correct but a single punctuation mark needed to be added. My first thought is that maybe systematically you could map 'Approved with Changes' to a status that does not equate with being 'complete', but instead a status that reflects that more work needs to be done. Richard Carlson Behr Paint Company Santa Ana, CA

[Heather_Kulbacki]

Stephanie, Sounds like your reviewers are marking off the task...? We have our automated workflows set up to go from the reviewer to a project manager and the PM manages the task. When the proof is sent to the reviewer, the task is marked to 50% complete so we know at a glance that it is out for review. Then when the proof comes to the PM, the review the decision to see if it is ready to move to the next stage in the process.

[StephanieHa3]

Thank you so much for your replies! I discussed the options with our team and it looks like using "Issues" for the edits might be the best option for us. Stephanie Haslbeck

[CalvinFold]

In our case, if changes are required, then the project manager filters the information to the designer, who makes the change, then the PM starts a new routing. We prefer to keep change cycles/rounds as distinct from each other. Primarily this is because when one person requests a change, everyone else has to re-review as if it was new artwork anyway. Kevin Quosig