Set Default Dates for New Tasks

When new tasks are created, automatically set their due dates based on the project start date or creation date. Perfect for project templates where tasks should start at specific intervals.

Choose Your Automation (click on the link):

Automation Name
What It Does
When to Use
Actual Recipe Text (in monday.com)
 Dynamic Offset (Numbers Column)⁠ 
New task created → Due date = Parent date + offset from Numbers column. Each task can have different offset (Design: +3 days, QA: +14 days).
• You need different offsets for each task type• Project templates with varied timelines• Maximum flexibility to change offsets without editing automation
When subitem is created, set its due date to match its parent item due date + offset by this number column of days/weeks/months
 Fixed Offset by Task Name⁠ 
Different offset per task name (without Numbers column). When a task with specific name is generated, it gets the same offset every time (from the parent item due date).
Standardized task names. Template-based workflows.
When subitem is created and if the subitem's name is [name] → then set its date to match parent item date + X Days/Weeks/Months
Based on Creation Date
New task created → Due date = Today + X days (not based on parent date).
• SLA-based workflows (task due in 5 business days from creation)• Due dates relative to when task was added, not project start• Support tickets, requests
When subitem is created → set subitem's [date] to creation date + [X] days/weeks/months
Creation Date + Task Name
Due = Today + X days, but only for specific task names
SLA workflows with different timings per task type
When subitem is created and if the subitem's name is [name] → then set due date to creation date + X days/weeks/months
Light Bulb Pro Tip: Use negative numbers for dates BEFORE parent dateExample: Event planning → Venue Booking = Event date -90 days

Open Book Want more details? See full article with additional examples and video walkthroughs: