Date + offset — full reference
TL;DR: "Date + Offset" is a family of Subitem Automations recipes that set or adjust subitem dates relative to another date — parent date, creation date, or another subitem date — shifted by a fixed or dynamic offset. This article is the comprehensive reference. Pick the right variant for your workflow from the catalog below.
What is a "date + offset" automation?
It's a recipe pattern: set a subitem's date by taking another date and shifting it by a defined amount.
Example:
- Project starts November 1
- Task 1 = Start + 5 days → Nov 6
- Task 2 = Start + 15 days → Nov 16
- Task 3 = Start + 25 days → Nov 26
If the project delays to Nov 5, all tasks shift automatically.
The three offset types
- Fixed offset — same number of days every time (e.g. +5 days)
- Dynamic offset — read from a Numbers column on the subitem (each task has its own offset)
- Relative offset — shift by the same amount as the trigger date moved (e.g. parent moved +3 days → subitem moves +3 days)
When to use this approach
- You run the same project type repeatedly
- Task dates are always relative to a project start, due date, or creation date
- You're tired of manually updating dates when timelines shift
- You need different timing per task type or status
Common use cases
- Project templates with relative task timelines (consulting engagements, client onboarding, sprint kickoffs)
- Automatically rescheduling tasks when project dates change
- Setting default due dates when subitems are created
- Status-driven deadlines (e.g. "when a task starts → due in 3 days")
- Sequential or dependent tasks where one task's date drives the next
- Event planning with negative offsets — venue booking is event date −90 days, invitations −45 days, final headcount −7 days
The Date + Offset catalog
Each of the date+offset patterns has its own dedicated article. Pick the closest match to your workflow:
Set initial dates when subitems are created
Each task has its own offset stored in a Numbers column. Best for varied per-task timing.
Each named task gets a fixed offset (Design +3, QA +14). One automation per task name.
Due date = creation date + X. Useful for SLA workflows where parent date is irrelevant.
SLA workflow with different timings per task type (Triage +1 day, Resolution +14 days).
Adjust dates when something changes
Parent date changes → ALL subitem dates shift by the same amount.
Parent date changes → each subitem shifts by its own per-task Numbers-column offset.
Parent date changes → only subitems matching a Status filter shift.
One subitem date changes → all subitems with the same name across the board update to match.
Status-triggered date variants
Deadline anchored to project date, set when work starts (e.g. status moves to "In Progress").
SLA-style — "due in 5 days from when work started." Time-sensitive handoffs.
Common mistakes
- Setting the same offset for every task. Result: every task gets the same date. Fix: use different offsets per task to space them properly.
- Creating multiple automations for the same date column. Result: automations conflict and dates update incorrectly. Fix: use one automation with a Numbers column to handle all tasks.
- Forgetting to enter offset values. Result: some tasks don't update. Fix: every subitem must have a number in the Offset column.
- Confusing parent-date-triggered with creation-date-triggered. Result: the wrong dates change at the wrong time. Fix: pick the trigger that matches when you want the date set.
Use negative numbers for dates BEFORE the reference date
Most date + offset variants accept negative numbers. This is useful for event planning, where prep tasks happen before the main event:
Venue Booking
−90 days
Send Invitations
−45 days
Confirm Catering
−30 days
Final Headcount
−7 days
Event Setup
−1 day
If the event is March 15, Venue Booking is automatically December 15.
Troubleshooting
- Dates aren't updating — check that the automation is active (not paused), the trigger column matches, and offset values are filled in for every subitem.
- Wrong dates calculated — verify offset values (5 not 50), check positive vs negative direction, confirm the offset column is Numbers type (not Text).
- Some subitems update, others don't — every subitem needs an offset value entered. Empty cells = no update.
- The wrong dates are changing — you may have picked the wrong trigger (creation vs status vs parent change). Each variant fires on a different event.
Next up
Related
- Date & timeline automations (parent landing for all date automations)
- Main Use Cases
Still stuck?
Email hello@fantasymedia.io and we'll help you pick the right date + offset variant for your workflow.