Proof HQ Reject Workflow

[ChristineZhu]

None of the training videos and articles go over what happens when a proof is rejected in ProofHQ. Are we able to specify who or to what stage the proof gets kicked back to if a Review/Approver rejects it? Christine Zhu

[SamanthaWi1]

Initially there are 4 options on the approval on a proof. I had help, and I took two of them off. I believe this can be done on the PHQ side. Darren Patterson helped me do this when they first bought out PHQ. We did discuss what each button did behind the scenes and no one could tell us if it routed differently based on the button pushed. So I opted to just have 2 buttons and changed the words on them to matched what we used. Keep it simple, is what I say. Samantha Senior Specialist, Creative Services 817-424-2186

[BarryBu2]

In the workflow, there is an owner of the proof. It defaults to the person creating the proof, but you can change that to someone else. Out of the box, there are four decisions you can make - Not Relevant, Changes Required, Approved with Changes, Approved. The idea behind approved with changes is that the proof still goes to the next person in the workflow, and they see the mark-ups made. When a proof is completed, it's status matches the decision. When you say rejected, it may be 'Changes Required' or even 'Approved with Changes'. The owner is informed of this. They should then upload a new version (based on the feedback). After all, if I approve the workflow and someone else changes the discount from 10% to 25% shouldn't that affect my previous approval? The new version will by default follow the approval flow of the previous version from start to finish. When setting up the new version, the creator can modify the workflow. So you might have different workflows (first draft, final approval) or they may simply remove people/stages that don't need to see the revised version. Barry Buchanan Work Management Australia

[ChristineZhu]

Hi Barry, Thanks for the explanation. To clarify, for our workflow, we would want the routing process to be halted when someone makes a "rejects with changes" decision, not continue onto the next stage. I actually noticed a discrepancy between the Proofing Details and the Create New Proof views. Only the Proofing Details view has the option to Activate the following stage once "All decisions are Approved on parent stage," which is what we're looking for as opposed to "When all required decision are made for a previous stage." Does that make sense? We want to be able to go back, upload a new version and then start the routing process all over again. Christine Zhu