I’m setting up a workflow for planning events and want to automatically populate suggested due dates for each task based on the final event date. I’ve tried using strict dependencies, which does correctly auto‑fill the dates with the right lead/lag times.
However, the issue is that if a task is completed early or late, all of the downstream dates shift — and we don’t want that. These dates are meant to be suggested target dates to help keep the project on track, not actual dynamic due dates that should change.
Ideally, we’d like to use strict dependencies once to generate the initial dates, and then “lock” those dates so they no longer update based on task completion.
Hello @Nikki.Jesiel
Totally get what you’re trying to do and you’ve found the tradeoff with strict dependencies. In strict mode, dates will always keep shifting as items move, because it’s built to preserve the timing chain. There isn’t currently a native “lock dates after first calculation” option.
A good workaround is to keep 2 columns
One dependency driven timeline/date column for the initial suggested schedule
One separate “Locked target date” column where you copy the suggested dates once, then manage them independently
You can also build the suggested dates with formulas based on the final event date, then copy them over when ready
If you’d like hands-on help or want us to walk through this live, you can book a 1:1 paid 60-minute strategy session with our team here: Calendly
