Best Practices for Recurrent Tasks

Hi Tony, 

Are you saying that each task would have a duration of 2-3 months? If so, I would utilize the recurrent task, but also take advantage of sub-tasks within there. I am guessing these tasks might have multiple parts moving during those months. 

Wrike labs has a fun new feature: https://help.wrike.com/hc/en-us/community/posts/6798100243351--Wrike-Labs-Release-AI-Subtask-Creation-

It allows you to highlight a checklist in the description of the task to easily make subtasks out of them. You could put that list in the recurrent part of the task, then use this feature to create subtasks with a simple click!

If you are instead saying that each subtask would recur every day/week/month but only last a couple months, you can have the recurrence end at a certain date:

Hope this helps!

We do not create a task that recurs frequently but instead highlight the task is occurring over a long period of time. I do like the suggestions that Devree Czupinski highlighted.

I agree with Devree Czupinski and Kevin Thalacker - nothing wrong with using a recurring task, but definitely consider who is it assigned to, how many recurrences you will need to establish (& how many upfront) as well as any subtasks if they are required.  IF you truly have repeatable and consistent work - the recurring tasks will truly help save time for set up!

I, personally, haven't utilized recurrent task but can think of a few instances where I could. I like Devree's suggestions and agree with the subtask list as well.

We use recurrent task not very often, but if so we normaly make a sub folder in which recurrent task are generated to have them in one position even so it becomes a huge number. Subtasks as suggested above could be also a solution to keep overview.

Like Sven was saying, your recuring task will pile up, you have to be sure this is what you want.  If it is for a long span of time between tasks, I prefer to copy them.  For weekly meeting tasks, it make sense,,,

Do you mean that the task recurs every 2-3 months? If so - I'd use a non-recurrent blueprint and just trigger it when needed

Or tasks that will recur for 2-3 months and then stop recurring? Then use the "Limit to" number of occurrences so you don't have to remember to turn off the task

Our directors like to see projects/tasks completed on a month-to-month basis, so we duplicate them.

I think Devree Czupinski gave a great tip in the sub-task creation to help remind the task owner(s) to make sure this recurring task is being completed. Or some sort of notification from Wrike bot to remind the owners.

Haven't utilize recurring tasks yet but I agree with Devree Czupinski.

I think automation can you help you when the status doesn't change to the desired status?