Agree a delivery date when a project is created without one
A delivery date automation covers the follow-up steps that confirm a delivery date after a project gets created without one.
Share template
A project gets created, but the delivery date field stays blank, which means the next update turns into a back-and-forth that somebody has to remember to send. This automation handles that follow-up, so the delivery date gets agreed instead of hanging over the project.
The steps wait a day, prompt “Agree a delivery date”, wait three more days, then check Agreed?. If the date still isn’t confirmed, the automation sends Ask when they need it delivered, so the client gets one clear question instead of a vague chase.
- Wait a day Holds the first follow-up back for one day after the project gets created.
- Agree a delivery date Starts the delivery-date conversation, so the client gets asked early rather than weeks into the work.
- Agreed? Checks whether the delivery date has been confirmed before the automation moves on.
- Ask when they need it delivered Sends a direct question when the date still hasn’t been agreed, so you can pin down a deadline.
Inside Plutio, the only setup is making sure the project has an email address. From there the automation runs entirely inside your workspace, and the follow-ups go out in the order the steps lay out.
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.
Every step, in order
Plutio runs these 5 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: When Project is created
- Wait a day
- Agree a delivery date
- Wait 3 days
- Agreed?
- Ask when they need it delivered (Agreed? → No)
What happens when you install it
- This automation is copied into your workspace with all 5 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 project-based teams who kick off client work before the delivery date has been pinned down.
Questions about this automation template
How do you follow up for a delivery date after a project is created?
A common approach is to wait briefly, ask to agree a delivery date, then check back again if you don’t get a clear answer. This automation follows that sequence, ending with a direct “when do you need it delivered?” question.
What triggers a delivery date follow-up workflow?
The trigger is the project being created. That makes the follow-up automatic for any new project that starts life without a confirmed delivery date.
How long does the workflow wait before checking again?
The steps include a one-day wait and then a three-day wait. Those waits space out the follow-ups so the client doesn’t get chased immediately after kickoff.
What happens if the delivery date still isn’t agreed?
After the second wait, the workflow checks Agreed?. If the delivery date still isn’t confirmed, it sends a message asking when they need it delivered.What do you need set up for the automation to run?
The project needs an email address so messages can be sent. The whole workflow runs inside Plutio, so no third-party account is required.
Does the automation run outside Plutio or need another tool?
No. Every step runs inside Plutio, so the workflow doesn’t depend on an external app or integration.
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
