AWRA OpsHub Search

The Task That Comes Back When It Is Done

A recurring task in AWRA does not appear on a calendar. It comes back when the current one is finished, carrying its original rhythm forward. That one decision explains why a series never piles up behind a busy team, why a late month arrives already overdue, and why a series nobody finishes simply stops.

Projects & Job Costing Washingtone Aura 7 min read

The short version

Finishing a recurring task creates the next one, dated one interval after the one you finished was due, not after the day you finished it. Assign every recurring task to a person, give it dates, and treat an overdue occurrence as the series asking to be caught up. A series ends when you give it an end date or cancel an occurrence, and only then.

An accounts office in Upper Hill keeps a short list of things that happen every month whether anyone remembers them or not. PAYE and the housing levy are filed by the ninth. The bank reconciliation for the main KES account is done by the fifth. The petty cash float is counted every Friday. Each is one task, set to recur, and assigned to Achieng, Otieno or Mercy.

How a recurring task comes back

A task can repeat daily, weekly or monthly, every one to three hundred and sixty-five of those, so every second week and every third month are both possible. When an occurrence is moved to done, on the web or from the AWRA mobile app, the next one is created at that moment as a fresh open task. A pass at 07:35 each morning catches any finished occurrence whose successor was somehow not created, and it is marked once created, so the same occurrence cannot produce two successors.

On the next occurrence What happens
Title, description, project, assignee, priority, estimate Copied from the finished task
Status Open again
Start and due dates Each moved forward one interval from the finished task’s own dates
Series Every occurrence points at the first, so the series stays together
Checklist items, labels, watchers, subtasks Not carried; the new task starts without them
Comments, attachments, time logged Stay on the occurrence they belong to

Write the procedure in the description

Because checklist items do not come back with the next occurrence, a recurring routine with steps is best written into the description, which does. Carrying the checklist forward, reset to not done, is something we can add to your workspace.

Why it waits for “done”

The alternative is a calendar: create the March filing on the first of March whether February’s was done or not. That sounds safer and behaves worse. If the team falls behind, a calendar keeps producing copies, and by June there are four open bank reconciliations for one account, each looking as urgent as the last. People close the extras to clear the list, and the one that mattered goes with them.

Completion-driven recurrence keeps exactly one open occurrence per series at any time. The series never runs ahead of the work, so the task in front of Otieno is always the next one he actually owes. The cost is real and worth naming: if nobody ever finishes an occurrence, nothing new appears. That is why the open one has to be loud, and the next section is about how it is.

A recurring task chases you until you do it, and then rolls forward. It never queues up the months you missed.

Late does not move the rhythm

The next dates are worked out from the finished task’s own dates, not from the day it was ticked off. Suppose January’s reconciliation, due on the fifth, is finished on the twentieth. The February one is still due on 5 February, not on the twentieth. The schedule holds its shape however late the work is done.

Taken further, that has a useful consequence. If Mercy is away for two months and the Friday float count sits unfinished, finishing it creates the next Friday’s count, which is already in the past and so arrives overdue. Finish that one and the next arrives, also overdue, until the series catches up with today. Each missed week is worked through as a real task rather than silently skipped, and the overdue ones are impossible to miss.

Every morning at 07:30, each open task with an assignee that is due within three days, or overdue, puts a reminder in that person’s bell, and they get one email listing all of theirs rather than one email per task. That bell copy beside the email is how every workspace alert reaches people who rarely read email at work, as we explained in the alert that waits in the bell. That is the loud part. It only works when the task has an assignee with a login, which is why the probe below starts there.

How a series ends

  • An end date. Give the series an until date, on or after its current due date, and the occurrence whose next due date would fall past it creates nothing more.
  • Cancelling an occurrence. A cancelled task is resolved but not done, so it creates no successor and the series stops there. Use cancel to end a series on purpose, not to skip one month.
  • Never finishing. The series stays on the open occurrence, reminding its assignee every morning, and goes no further.

Projects with their own board columns are read on their own terms: whichever columns that project counts as done or cancelled decide whether an occurrence continues the series. For the same behaviour on a building site, where a weekly scaffold check that stops recurring is a safety matter, see the inspection that stopped recurring.

Four checks for your recurring tasks this week

Does every recurring task have an assignee with a login?

If you find

Some are unassigned or assigned to someone who left.

Then

Their reminders reach nobody. Reassign them today.

Does every recurring task have a due date?

If you find

A few were created without one.

Then

The next due date is then counted from the day it was finished. Set the dates you mean.

Which recurring tasks are overdue by more than one interval?

If you find

A series that stalled.

Then

Finish or cancel it on purpose. Leaving it open stops the series as surely as cancelling.

Do any recurring routines rely on a checklist?

If you find

Steps kept as checklist items.

Then

Copy them into the description so the next occurrence has them.

More we can add

A series shaped to your routine

Completion-driven recurrence, the morning reminders and the end date are in place. These extensions come up most often.

The checklist comes back

Each occurrence starts with the same checklist items, all reset to not done.

Labels and watchers carried

The next occurrence keeps the labels and the people watching the series.

A calendar-anchored series

For the few routines that must exist on their date whether or not the last one was done.

A notice when a series ends

Telling the assignee and the project owner that the last occurrence has passed.

The straight answer

What AWRA OpsHub does today

  • Daily, weekly or monthly recurrence, every 1 to 365 intervals, with an optional end date.
  • The next occurrence created on completion, on the web or in the mobile app, with a morning pass that catches any missed.
  • Dates carried from the finished task’s own dates, so a late finish does not shift the schedule.
  • One series, with every occurrence linked to the first.
  • A morning reminder to the assignee for tasks due within three days or overdue, plus one email digest per person.
  • A series that ends at its until date or when an occurrence is cancelled.

More we can add to your workspace

  • Checklist items carried onto each occurrence, reset to not done. Commission it
  • Labels and watchers carried onto each occurrence. Commission it
  • A calendar-anchored recurrence mode, for routines that must exist on their date regardless of the last one. Commission it
  • A notice to the assignee and project owner when a series reaches its end date. Commission it

Where we point you to a specialist

  • We will not create a new occurrence while the previous one is still open. A series that ran ahead of the work would bury the occurrence that matters under copies of itself.

Carrying the checklist forward is the first extension most teams ask for, and the checklist items are already stored against each task.

See task management in AWRA

Tasks, checklists, recurrence, due reminders and the mobile app.

Explore task management

Frequently asked questions

When does the next occurrence of a recurring task appear?

When the current one is moved to done, on the web or in the mobile app. A pass at 07:35 each morning creates any that were missed. It does not appear on a calendar date by itself.

If we finish a task late, does the schedule shift?

No. The next start and due dates are one interval after the finished task’s own dates, not after the day it was finished. A very late finish can therefore produce a next occurrence that is already overdue.

What is copied to the next occurrence?

The title, description, project, assignee, priority and estimate, with the dates moved forward and the status open. Checklist items, labels, watchers and subtasks are not carried today.

How do we stop a recurring task?

Set an end date for the series, or cancel the current occurrence. A cancelled occurrence creates no successor.

Who is reminded about a recurring task?

Its assignee, every morning while it is due within three days or overdue, in the AWRA bell and in one daily email listing all their due tasks.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center