Sync all subitem dates with the parent
TL;DR: When the parent item's date changes, all subitem dates shift by the same offset automatically. The simplest sync — whole project moves together. The #6 most-used Subitem Automation in the app — used by 6% of all accounts.
What this does
Recipe: "When item's date changes, adjust subitem's timeline by the same offset."
When the parent item's date changes, every subitem's date shifts by the same number of days. No filters, no exceptions — the entire project moves together.
Example: a client pushes the launch date by 2 weeks → all 47 task subitem dates shift by 2 weeks automatically.
When to use it
- Whole project moves together when the deadline shifts
- You don't need to filter which subitems shift
- All tasks are equally affected by parent timeline changes
- Simple project templates where every task has a relative offset from the project date
This shifts every subitem, including completed ones. If you only want to shift pending tasks, use Sync subitem dates with the parent (only matching status) instead. For per-task offsets (each subitem shifts by its own amount), use Sync subitem dates with the parent (per-task Numbers offset) .
Before you start
- A Date or Timeline column on the parent item (the trigger)
- A Date or Timeline column on the subitem (the date that adjusts)
Set it up (2 minutes)
Create the Subitem Automation
Navigate to the automation center to find the appropriate third-party app recipe.
1. Click the Automate button in the top right corner of your board.
2. Click Create to browse the automation center.
3. Search for Subitem Automation in the search bar.Click the Subitem - All automations app card to view the available recipes.
With over a hundred automations available, filter the list to find the specific offset rule. Type offset into the search bar to narrow down the results.
5. Click Use template on the recipe that reads: "When item's date changes, adjust subitem's timeline by the same offset"
Configure Date vs. Timeline Fields
When setting up the recipe, you can mix and match column types for both the parent trigger and the target subitems depending on your board setup. Select the combination that fits your workflow.
Date Column
Date Column
Standard task deadlines shifting equally.
Date Column
Timeline Column
Parent deadline changes, pushing a subitem's multi-day span.
Timeline Column
Date Column
Parent project span shifts, moving individual subitem deadlines.
6. Click the underlined date variable to specify the parent item column that acts as the trigger.
7. Click the underlined timeline variable (or date) to select the corresponding subitem column that will adjust.
8. Click Create automation to save and activate the rule.
Test the Offset
Once the automation is active, verify that changes propagate correctly down to the subitems.
9. Click the parent item's due date cell.
10. Select a new date from the calendar to trigger the automation.
Success: Your subitem dates will automatically shift by the exact same amount of days applied to the parent item, eliminating the need for manual schedule correction.
Q: Can I use timeline columns instead of date columns for this automation?
A: Yes. The automation recipe supports both date and timeline columns for both the parent item trigger and the subitem target. You can even mix them, such as using a date column for the parent item and a timeline column for the subitems.
Q: How do I fix the schedule if I accidentally select the wrong date?
A: The automation is designed to handle corrections dynamically. Simply change the due date on the parent item to the correct date, and the subitems will automatically recalculate and adjust by the new offset.
Common gotchas
- Affects every subitem — including ones marked Done. Use the by-status variant if you want to skip completed tasks.
- Date columns must exist on both parent and subitem. Names don't need to match — you map them in the automation.
- The shift is relative, not absolute. If parent moved +3 days, every subitem moves +3 days from its own current date.
- For per-task offsets (each subitem shifts by its own amount), use the per-task Numbers-offset variant .
- Combine with weekend → workday if the shift may land subitems on weekends — see Auto-shift weekend dates to a workday .
Next up
Related
- Date & timeline automations (parent landing)
- Sync subitem dates with the parent (per-task Numbers offset) (per-task variant)
- Date + offset — full reference
Still stuck?