Automatic task dates
Let task dates follow the work: "due 3 business days after Kickoff call is completed" instead of a date someone has to keep retyping.
Draft help article. Written for the OnRamp help center. It describes the feature behind the dynamic_task_dates flag, which is off for every organization until it is turned on. The engineering design is in Dynamic Task Dates.
In short
A date can follow something. Another task finishing, the project start or end date, or a date field from your CRM. When that changes, the date moves on its own.
Every date says why. Next to each date you see what it follows, whether it is an estimate, and what it is waiting on.
People stay in charge. A date you set by hand stays where you put it. Customers only ever see the date itself.
What the words on a date mean
Every task date in a project that uses automatic dates, start dates and due dates alike, says what decides it, right next to the date: in the project's task list after a dot ("Sep 9, 2026 · after Kickoff call"), and in a task's details under the date. Hover a date in the list to read the full sentence. Click the date, in the list or in the task, to change it.
| Label | What it means |
|---|---|
| after Kickoff call (or before end date, after project start, after its start, before its due date) | The date follows a rule, and what it follows is settled. It moves only if that changes. A start or due date with no rule of its own follows its task's other date. Open the task to read the full sentence. |
| estimate · waiting on Data import | The date follows a task that is not finished yet, so it is worked out from that task's due date, or from today if that task is already late (it can't finish in the past). An estimate is never shown as overdue. If the task it waits on is late, the text turns amber and says how late. |
| set by hand | Someone picked this date. It stays put and no longer follows its rule until someone chooses Follow the rule again under the date, or Follows other work then Follow again in the date's editor. |
| moved by Aero | Aero moved this date to when it expects the task to finish, based on how long the same task took in earlier projects. |
| Aero move undone | Someone undid Aero's move. Aero will not move this date again until a person changes it. |
| set date | The date has no rule. It changes only when someone edits it. |
| waiting | The date has a rule, but what it follows isn't known yet, such as a form question nobody has answered or an empty date field. It stays where it is until it is. |
Projects that do not use automatic dates show their dates exactly as before, with no labels.
Set it up
1 · Turn on automatic dates for a playbook
Open the playbook, go to Settings, and find Automatic dates. New playbooks have it on already. For an older playbook, select Turn on.
Turning it on changes nothing you can see yet. Every task keeps its current date, and a task with a set number of days from the start gets a rule that lands on exactly the same day. Projects already running don't change. If the playbook is a draft, deleting the draft undoes it.
Two settings sit under it:
- Move dates earlier when work finishes early (on by default). When a task finishes ahead of time, the dates that follow it move earlier too. Turn it off if dates should only ever move later.
- Exclude Weekends applies only to tasks with a set date. A task that follows a rule counts business days or calendar days, whichever its rule says.
Worked examples
A chain of tasks
| Task | Rule |
|---|---|
| Kickoff call | Set date: 2 days after the project starts |
| Data import | 3 business days after Kickoff call is completed |
| Admin training | 5 business days after Data import is completed |
The project starts on Monday, October 5. Kickoff call is due Wednesday the 7th. Until it is finished, Data import shows estimate · waiting on Kickoff call for Monday the 12th, and Admin training shows estimate · waiting on Kickoff call for Monday the 19th.
Kickoff call is completed on Thursday the 8th. Data import becomes Tuesday the 13th (3 business days later), labelled after Kickoff call. Admin training is still an estimate, now waiting on Data import, and moves to Tuesday the 20th.
More things a date can follow
- When a task is started. "Send the welcome kit 1 business day after Kickoff call is started." A task counts as started when someone moves it to In Progress or answers its first question. If it is reset, the date goes back to being an estimate.
- When a module is completed. "Launch prep is due 2 business days after Build is completed." Build counts as completed when every task in it is finished or skipped. Until then the date is an estimate from the latest due date in Build. A task cannot follow its own module.
- A date someone answers in a form. "Admin training is due on the answer to 'When would you like admin training?' in Scheduling." When the customer or your team answers, the date moves, and it moves again if the answer changes. Until it is answered the date shows waiting and stays where it is.
When a date has more than one rule
Select Add another rule to give one date several rules. The date is the latest of them:
Admin training is due the latest of: 2 business days after Data import is completed; 10 calendar days after the project starts.
That is the "and" case: the task cannot be due until all of those have passed. There is no "or", meaning "whichever comes first". For that, give the task one rule (the one that should win) and adjust the date by hand when the other matters.
Rules cannot depend on a condition, such as "only if the deal is enterprise". To give different customers different schedules, use separate modules or playbooks and add them with a workflow.
In what order dates are worked out
The order of rules on a task makes no difference, and neither does the order of tasks in the list. OnRamp works out each date only after every date it follows. So in a chain A → B → C, C always sees B's final date.
If rules point at each other in a loop (A follows B and B follows A), those tasks keep the dates they have, and nothing in the loop moves until the loop is removed.
Details that are easy to miss
- Weekends. Business days skip Saturday and Sunday. A rule of "0 business days" that lands on a weekend moves to the next weekday (or the weekday before, for a "before" rule). Public holidays are not skipped.
- Before the project starts. A date a rule puts before the project start moves to the project start instead.
- Modules added later. When a workflow or a person adds a module partway through a project, its tasks never start before the day it was added.
- Modules a workflow adds. In a workflow's Add modules step, each module's Starts line can count business days before or after:
- the project's start or end date: "SSO setup starts 10 business days before the project end date";
- a project date field, including one the workflow fills from your CRM, which the picker marks "(from HubSpot)" or "(from Salesforce)": "Training starts 5 business days after Contract signed date". When the CRM changes that field later, the module moves with it;
- a playbook module being completed: "Phase 2 starts when Build is completed";
- a module listed earlier in the same step being completed: "Advanced reporting starts when SSO setup is completed". If that module wasn't added because its conditions didn't match, the module starts the day it is added;
- a playbook task being completed, or its due date.
- Completion day. A task completed at 7pm in your organization's time zone counts as completed that day, not the next.
- What counts as setting a date by hand. Changing a date in the task panel or the project list, dragging it on the timeline, a bulk edit, an automation, OnRamp's API and OnRamp's MCP server all set it by hand. Updating a project to a new version of its playbook does not: the project's tasks take the new version's rules, as if the project had been created from it, and dates someone set by hand stay where they are. A rule changed inside the project is not replaced by the update.
- Original dates. Every task keeps its original due date. Insights can show tasks finished by their original due date next to tasks finished by their current one.
Aero and automatic dates
When Aero's Move dates action is on, Aero looks at tasks that are overdue and forecasts when they will really finish, from how late the same task ran in earlier projects. It then follows your autonomy setting for that action:
- Ask: Aero suggests the new date and someone accepts it.
- Conditional: Aero moves the date unless one of your rules says to ask first, for example when the move is more than 10 days, when it would push the project end date out (including through the dates that follow), or when Aero moved the same task in the last 7 days. You can add Someone set this task's date by hand to always ask before moving those.
- Autonomous: Aero moves the date.
Aero never moves a date that:
- someone set by hand and that has not passed yet,
- someone already undid,
- waits on another task (Aero moves the task it waits on instead), or
- belongs to a task that is finished or skipped.
Who is told when dates move
Your team members on a project (never customers) get one Dates Summary email each morning at 8am in their time zone. It lists every project of theirs where dates moved automatically since their last summary, each date once with where it started and where it ended up, and projects whose end date moved first. The person whose change caused a move is not told about it, but everyone is told about what Aero does on its own.
When a change moves a project's end date, the team also gets an email right away, as before.
Admins can switch the summary off, or edit its subject and intro, under Email templates → Dates Summary. The list of moved dates always appears.
Every move is also in the project's Activity tab, with the reason: "Due date moved because Kickoff call was completed (Oct 12 → Oct 13)". When Aero moves a date on its own, the activity credits Aero, including the dates that moved because of it, and names the person whose autonomy settings it acted for.
What customers see in the portal
Customers see the current date and nothing about how it was worked out: no rules, no "set by hand", nothing about Aero.
When a date is an estimate, the portal says what keeps it. If it waits on a task the customer owns: Due Oct 14 · if Upload your logo is done by Oct 9 (never a day before today). If it waits on your team's work: depends on <your company name>'s progress. Your internal task names are never shown. An estimated date is never shown as overdue to a customer.
Troubleshooting
Look at the date. If it says set by hand, someone picked the date, so select Follow the rule again. If the task finished early, check Move dates earlier when work finishes early in the project's settings.
The task it waits on is late and nothing has changed in the project since the estimate was worked out. The amber text next to the date names the late task and says how many days late it is. Finish or re-date that task and the estimate follows.
A date that follows a rule, or a date Aero moved, landed after it. The Activity tab shows which task moved it. The project still remembers its original end date.
It follows the task's due date: it starts when the thing the due date waits for happens, or keeps the task's length. Click the date to see which. To stop it, give it a rule of its own or choose Set a date.
The project or playbook does not use automatic dates yet. Turn it on under Settings → Automatic dates.