Copywriter in Proof Workflow

[JamesMa4]

Hi everyone, we finally have a copywriter on our team and are trying to figure out the best way to incorporate her into our proof workflows.

Basically, we’d like her to view the first proof/version and the last, without all the in-between.

We currently have a “Creative Review” stage where the designer sends the first proof to the Design Manager for review, and we can add her to that.

We’d also like her to look at an “almost final” version just to make sure it looks good before going to production.

As mentioned, we’d like her to not have to see all the versions and comments in between, or at least know she can ignore those, but also be notified exactly when to come back in and see the “almost final” version, which seems to be the tricky part.

An option is to ask the project leads tag her at that point, but are hoping for something more reliable from a process/workflow standpoint.

Any suggestions? Thank you!

[OliviaCl · Accepted solution]

Have you considered taking it into a task and creating an approval route on a task with her being the approver? It would be a little more effort on someone's end but once the first version is ready, it could get dropped into the task an attachment and set up the routing rule to go straight to her. Could do a secondary task down the road for the final approval. It takes her out of the proof aspect and she doesn't get notifications, but she'd be automatically getting things for review if the tasks were created with an approval route. Assuming not all of your projects need a copywriter, you could just copy an existing template to give this option. 

You could also play around with her 'role' on the proof and dictate her settings - for example, adjust the proof settings during setup to only notify her of the 'final decision' - she would only get an email that a final decision has been made (aka Draft 1 is done) and view it at that point.

[JamesMa4]

Thanks for the suggestions @OliviaCl! 

I didn't think about the task options. We'll explore that, but will likely lean on proof settings/notifications/workflow stages so we don't need to rely on someone to drop it into a task and route it to her. The 'final decision' notification setting may work well.