I’ve got work we do monthly, such as sending emails, social media content, creating reports, etc.
For the project management jobs - tracking where these are at - we currently use a single task for each monthly task with subtasks to track, with a repeater on this task, so once it’s finally ticked off, it regenerates for the NEXT month.
One problem is that I’ve had staff accidentally remove the repeater when adjusting the task date, and then we lose the whole task, making us miss work.
Is there a way to protect the repeater tasks in some way to prevent this from happening? Or, failing that, is there a better way to handle this sort of thing in Asana?
I get why this is frustrating. It’s super easy to lose the repeat setting when someone moves the due date, and then the chain breaks. There isn’t a way to lock this setting right now, but here are a few setups I’ve seen work well to prevent accidents:
Use a “generator” task: Create one parent task that repeats monthly and keep it as the only place where the recurrence lives. Make that task comment only for most folks or keep it in a separate project, only you can edit, then multi‑home it into the working project so the team still sees and works on it. This keeps people from changing the repeat by mistake.
Pair it with a task template and a rule: When the new monthly instance appears, have a rule apply a task template that adds your standard subtasks with relative due dates tied to the parent. That way, your team works on the checklist without ever needing to touch the parent’s due date or repeat.
Low-tech alternative: Pre‑create the next 12 monthly tasks, so you’re not relying on recurrence at all. It’s simple and avoids the risk of losing the chain.
Add a quick guardrail: Put a note at the top of the description like “Owner updates date and repeat only” so people know not to edit those fields.
Happy to help you sketch the rule or template if you share how your subtasks are scheduled today. In the meantime, have a great weekend and enjoy your Asana experience!
For completeness sake, with an Enterprise plan, you can set restrictions on some fields including Due date, but it would apply to all tasks and uses of the Due date field, not just recurring dates:
None of these quite work as well for the setup I want to have, but that’s okay.
What I’ll do is keep a screenshot of the project of its repeater tasks as a reference point, and then I’ll just have my own task to double-check these are all preserved correctly each month when we’re doing a full run through of all the active work (WIP).
I’ll log a feature request for a more locked repeat function.
