How to Remind Your Team About Overdue Tasks

Make the task clear enough to act on

“Website” is too vague for a useful reminder. “Check the contact form on a phone and record the result” gives the owner something they can finish. Add a due date and the person responsible.

Agree what Done means. A task can look finished in a chat message while remaining open in the task tool. Choose one record as the source for its status.

If a task has no owner or due date, put it on a short list for the team lead to fix. Guessing a recipient or deadline creates messages that people learn to ignore.

Choose a reminder rule the team understands

Write the rule in ordinary words: each working morning, remind the owner about open tasks whose due date has passed. Decide which timezone defines the morning and the due date.

Choose a frequency that fits the work. A daily summary may suit a small office. A single reminder followed by a review may suit a longer project. Agree the rule with the people receiving it.

Keep urgent alerts separate. A normal overdue task should not look like a system outage or a customer emergency.

Work through an example reminder

Example: a studio needs a brochure checked by Tuesday afternoon. The task belongs to Sam. On Wednesday morning, the workflow finds that it is still open and sends Sam a reminder with the task link.

The message could say: “The brochure check was due Tuesday. Please update the task when it is finished, or mark it blocked and add what you need.” This tells Sam what to do next.

Sam is waiting for the customer’s final text and marks the task Blocked. The next check puts it in a blocked-work summary for the project owner. It does not keep asking Sam to complete work that depends on someone else.

Use the rules already available in your task tool

Start by checking your current app’s notification settings and automation rules. Asana, for example, documents due-date and overdue triggers. The available rules and limits depend on the plan and task type; some due-date triggers do not apply to subtasks.

Confirm the rule applies to the actual tasks you use. Test a normal task and a subtask if both are part of your work. Review any existing email reminders before adding a separate message workflow.

If several tools hold the same task, choose which one owns the due date and completion state. Copying a reminder into another system should not create another version of the work.

Stop messages as soon as the task changes

Read the current task status before each send. A completed or cancelled task should leave the reminder list. A changed due date should use the new date rather than the date captured when the task was first created.

Record the task and the reminder period already sent. This helps prevent the same daily reminder from going out twice if a run restarts. If the sending result is uncertain, check the message record before retrying.

If ownership changes, the next reminder should reach the current owner. Avoid carrying the previous person’s address forward in a long-lived queue.

Give stuck work a useful next step

Choose when a team lead should review a late task. That might be after an agreed number of working days, or immediately when the task is blocked. Include the reason and task link so the lead can help.

Keep the notification in the smallest appropriate group. A task about a private customer issue does not belong in a general channel. Share the task link with people who already have access.

If the connection fails, leave a visible run record and tell the person responsible for the workflow. A quiet failure can make a team believe reminders are being sent when they are not.

Test a small set before turning it on

Use test tasks covering a normal overdue item, a completed item, a moved due date, a changed owner and blocked work. Include a weekend and tasks near midnight if timing matters to your team.

Check the message on a phone. The owner should be able to identify the task and next step without opening several apps. After the trial, ask whether reminders helped people act or merely repeated information they already knew.

Use the worksheet below to agree the rule. To discuss a setup for your team, contact Automations For Business on WhatsApp with your task tool, the reminder you want and one example with private details removed.

Your ready-to-use checklist

Make the next step clear.

Sources and notes

Sources checked on October 21, 2026.

• Asana: rules

  Rule triggers, limitations and failed-rule visibility.

• Asana: notification settings

  Review existing task notifications before adding another channel.