How do you use "Approved with Changes" and "Reject" for proofs?

[CarolynFi]

For proofs, how does your organization use “Approved With Changes” and “Reject”?

In my organization we only use “Reject” when the proof is completely off the mark from what was requested. An example is that the request was for a brochure about widgets, but the proof is a flyer about apples. For “Approved with Changes” we still give the client the option to review the revised proof after the changes have been made.

Recently, a colleague questioned whether we should allow clients to review the revised proof after approving with changes, citing that by approving with changes, they are implying that the proof is approved and need not be reviewed again.

What does everyone else do?

[Sheri_Whitten]

Hi Carolyn,

If the user selects "Approved with Changes" we don't route another proof. If they approve with changes, they trust the changes are made and don't want to see it again. We only have one proofreader, who gets inundated with proofs, so that may affect our process. 😊

If someone wants to see it again, they have to select "Changes Required"

[CarolynFi]

Thanks Sheri! We don't use "Changes Required", but maybe we should.

[Heather_Kulbacki]

We do the same as Sheri with all of our business partners, if they select "Approved with Changes" they trust us to make the changes and move forward. Unless, we feel the changes are extensive or weren't clear and we want them to review another time.

[CarolynFi]

Thanks Heather!

[AnthonyIm]

We actually removed Approved with Changes from our system. We ran into too many issues where an executive said Approved with Changes but then got mad when something was sent without them looking at it again. So now our people only have Approve or Changes Required.