15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Automation

Progress update task two weeks before delivery

A progress update automation covers when the check-in goes out, what happens if nothing gets updated, and who gets reminded next.

Progress update task two weeks before delivery template preview

Language:

en

Trigger:

Project

Steps:

4

Last updated:

September 2026

Share template

A project heads toward delivery, and somewhere in the last stretch the client wants to know where things stand without a manual chase for updates. The Progress update task two weeks before delivery automation handles that check-in on a fixed timer, so the message goes out 14 days before the project due date and the follow-up doesn’t depend on someone remembering.

The automation runs as a four-step sequence: it sends the client a progress update, waits two days, checks whether anything got updated, and then reminds the owner if the project still hasn’t moved. The whole thing stays inside automations that do the next step for you, so the timing and the nudges keep running even when the workday gets busy.

  • Trigger Starts 14 days before the project due date, so the check-in lands at the same point in every delivery cycle.
  • Progress update Sends the client a status email tied to the project, with wording you can change before it goes live.
  • Wait 2 days Holds the sequence for two days, then continues automatically without anyone reopening the project.
  • Updated? Checks whether the project has been updated, which decides whether the next reminder step runs.
  • Remind the owner Notifies the owner when the project still hasn’t been updated after the two-day wait.

Once the automation is in your workspace, you connect it to projects that already have a due date and an email address on the project. From there, the trigger watches the due date and the steps fire in order, leaving you to adjust the message content and the internal reminder to match how you want updates handled.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

Every step, in order

Plutio runs these 4 steps top to bottom, from the trigger through each action and condition. Every one arrives configured and stays editable. The automation is added as a draft, so it sends nothing until you turn it on.

Starts: 14 days before Project due date

  1. Send the client a progress update
  2. Wait 2 days
  3. Updated?
  4. Remind the owner (Updated? → No)

What happens when you install it

  • This automation is copied into your workspace with all 4 steps already configured.
  • It arrives as a draft, so nothing runs until you turn it on.
  • Every step stays editable, so the wording, the timing and the conditions all change before or after you activate it.

Who it is for

Studios, freelancers, and service teams delivering client projects on a deadline who want progress updates to go out and escalate automatically.

Questions about this automation template

How do you send an automatic progress update email two weeks before a due date?

Set up an automation that triggers 14 days before a project due date, then add a step that sends the client a progress update email. The trigger only works when the project has a due date set and an email address attached to it.

What do you need for an automation that runs before a project due date?

The setup needs projects with a due date set and an email address on the project. The steps run inside Plutio, so you don’t need any third-party account.

What happens if the client doesn’t reply to the progress update?

This automation waits two days after sending the update, then checks whether anything has been updated. If nothing changed, the last step reminds the owner so someone can follow up.

Can an automation check for updates before sending a reminder?

Yes, the sequence includes a check step that looks for an update after the wait. That check decides whether the reminder step runs.

Why isn’t the progress update going out on time?

The most common causes are a missing project due date or no email address on the project. The trigger depends on both, because it fires relative to the due date and sends to the address saved on the project.

Does this kind of progress update automation require Zapier or another tool?

No, every step in this template runs inside Plutio. The trigger and the email steps don’t require any third-party account to work.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away