Creating a feedback loop

Hi all,

I'm setting up blueprints and workflows for my department and am stumped on the best way to set up a feedback loop for a peer review situation. I set up a workflow with an approval built in, which is pretty clear-cut as long as the peer reviewer approves the document after one review. What's stumping me is how to efficiently set up a loop for cases where the document goes back and forth between the writer and the reviewer more than once, e.g., Editor 1 writes article > Editor 2 reviews and rejects article > Editor 1 revises article > Editor 2 reviews and approves article?

I've tried using the workflow/approval, but I feel like it's becoming convoluted. Would it be better to just have users attach the document and request an approval and forget about the workflow (keep the status In Progress until completed)? Or use the comments box and change the assignee back and forth? Please let me know what's worked for you! 

Thanks in advance!

 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
2 comentarios

Hi Jen Loomis

we use two statuses "Writing in Progress" and "Under Review" and when the editor finishes the article he attaches it and uses Wrike's internal approvals. If the editor approves the task it goes to "Approved to publish" status otherwise it goes back to "Writing in progress".

No loops, just common sense =)

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

☝ This. We also use a back and forth like this, with the addition that the users passing the task back and forth will often @mention each other with the status change to keep the communication thread attached to the task. 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Creating a feedback loop
[this list is visible for admins and agents only]

Arriba
Didn’t find what you were looking for? Write new post