Asana recurring parents: prepare the next task copy

For an existing recurring Asana parent task on the web, check what must carry forward before proposing completion.

Check the next copy

Asana’s recurring-task instructions, under Recurring tasks, say completion duplicates the task for its next due date. Fields copy except comments; subtasks copy too. If the parent repeats, do not also repeat its subtasks: the source warns of exponential duplication.

The calendar shows the next due occurrence, not every future occurrence. Periodical recurrence uses the last completion date; do not generalize that anchor to other modes. The source also permits stopping recurrence through remove repeat or removing the entire due date.

Prepare the owner’s decision

Privately identify the exact parent and intended occurrence; a repeated title is insufficient. Record the repeat mode, parent/subtask settings and whether comments contain information needed next time. Resolve that retention need separately rather than relying on the next copy.

Ask whether the owner means completed work, a postponement or ending repetition. Keep the requested operation separate from work evidence and the responsible person’s acceptance. Do not propose marking complete merely to postpone work.

Return unresolved questions to the owner before any account action. Exact next-date calculations, time zones, late/missed occurrences, copied-item access and actual controls remain unverified here. Missing controls or unclear authority leave the proposal pending; no workaround is supplied.

Evidence: Full rendered English primary page read through 2026-10-05T21:15:01Z; no update date displayed. The author performed sixteen manual reader-decision checks; a distinct internal checker reread the rendered primary page through 2026-10-05T21:18:42Z, rechecked these decisions and evaluated eight additional boundaries at 2026-10-05T21:19:30.141317Z. These are shared-controller checks, not independent review or task execution. No task or recurrence settings were changed. Recheck before use, after source/control/owner-intent changes and by 2026-11-05T21:15:01Z. Follow the task standard [current article]. Report a disputed step without private task content or links.