Skip down to the research record

Due date checks for sales follow-ups: 8 rules

Quota Forecast Editorial Team · Published · 12 min read

Eight date checks keep sales follow-up dates and expected close dates from drifting apart.

Key takeaways for how to set due dates for sales follow-up tasks in crm tools

  • Atlassian sets the due time for a checklist item to 6pm local time of the person who set the date, as stated in "Set due dates for checklist items | Trello | Atlassian Support" according to Atlassian.
  • Doist calculates the next date for a recurring task as 3 months from the task's original date when completing a task dated every 3 months, in "Introduction to recurring dates" according to Doist.
  • Close automatically changes the estimated Close date to a future date when you snooze an opportunity notification to that date, without using the date picker, as described in "Inbox | Close Help Center" according to Close.
  • Close automatically changes the Estimated Close Date to today’s date when you mark an opportunity notification as Done, without using a date picker, in "Inbox | Close Help Center" according to Close.
  • Microsoft allows a maximum of 20 checklist items on a task, as noted in "Use task checklists in Microsoft Project for the web | Microsoft Support" according to Microsoft.

How due dates work across sales tools

The eight date checks in this guide address specific behaviors where task timing can drift from your forecast. These checks cover default time rules, recurring logic, snooze behavior, completion impact, item limits, sync gaps, calendar views, and start dates. Each rule belongs to a specific tool, and applying one publisher's logic to another creates errors in your pipeline visibility.

Your CSV must include one lead-matching column, the task text, and optionally a due date and assignee, according to Close. They help your team track follow-ups, callbacks, or any activity that needs to happen by a specific date, according to Close. See Sales data imports: 5 field checks before upload before you import. If the due date is omitted, the task lacks a specific temporal anchor for forecasting purposes.

The distinction between a task date and a deal close date is critical for accurate reporting. A task due date tracks when an activity must occur, while the close date tracks when revenue is expected. Conflating these two dates leads to misaligned forecast periods. For example, a follow-up call scheduled for next week does not change the expected close date of the deal, even if the call is a prerequisite for the next stage. Read Close date change log: why the date moved when a close date shifts.

Check the default due time setting in your primary CRM and verify how your team's recurring follow-up tasks are scheduled to ensure they align with your forecast period.

Default times and recurring logic

When a rep sets a due date on a checklist item, the system applies a specific time rule. According to Atlassian, when setting a due date in a checklist item, the due time is automatically set to 6pm local time of whoever set the due date. This fixed time applies to the user who creates the date, not the recipient of the task. If your team spans time zones, the 6pm local time of the setter may differ from the 6pm local time of the viewer. Check your team’s time zone settings to understand how this 6pm rule impacts your daily pipeline review.

Recurring tasks follow a different logic for calculating future dates. According to Doist, completing a task that has a date of every 3 months will set the task’s date to 3 months from the task's original date. This rule ties the next occurrence to the initial creation date, not the completion date. For example, if a task is created on January 10th with a date of every 3 months, it will recur on Jan 10, Apr 10, and July 10 regardless of when you complete the task, according to Doist. This ensures the recurring schedule remains anchored to the original calendar date. If a rep completes the task late, the next date does not shift to reflect the delay. The forecast date remains tied to the original interval.

According to Doist, if you create a task with the date every Monday, Friday at 8pm, both the Monday and Friday recurrence will be scheduled for 8pm. When managing a team with distributed reps, verify that the 8pm setting aligns with your forecast period.

A filled reference table for date rules

The following table lists the 8 date checks with publisher-specific rules. Each row names the publisher and states the rule exactly as documented.

CheckPublisherRule
Default time ruleAtlassianWhen setting a Due date in a checklist item, the Due time is automatically set to 6pm local time of whoever set the Due date, according to Atlassian.
Recurring logicDoistCompleting a task that has a date of every 3 months will set the task’s date to 3 months from the task's original date, according to Doist.
Snooze behaviorCloseIf you snooze the opportunity notification (set it to a later date), the estimated Close date of the opportunity will automatically change to that future date without getting to the date picker, according to Close.
Completion impactCloseIf you mark the opportunity notification as Done, we’ll automatically change the Estimated Close Date to today’s date without getting to a date picker at all, according to Close.
Item limitMicrosoftYou can create a maximum of 20 checklist items on a task, according to Microsoft.
Sync gapGoogleIf a checklist item is deleted in the doc, but the task isn’t deleted first, it'll still appear in the assignee's personal Tasks list, according to Google.
Calendar viewGoogleThey can view the task in their personal Tasks list and on their Google Calendar if the task has a set date, according to Google.
Start date settingDoistTo start the first occurrence on a later date, add a start date, like every 2 weeks starting 3 January, according to Doist.

Review each row against your current tool settings to confirm alignment with your forecast period.

Illustrative example

Picture 8 open follow-ups on one deal. The next call is due in 3 days, and the expected close is 30 days out. Moving the call to day 10 leaves the close on day 30. One follow-up repeats every 3 months from its original date, so finishing it 2 weeks late leaves the next date on that same interval. The activity list holds 20 steps, and steps past that count go on a second list. Keep the call date and the close date in two separate fields.

Impact of snoozing and completing tasks

In the Inbox feature described by Close, if you snooze the opportunity notification and set it to a later date, the estimated Close date of the opportunity will automatically change to that future date without getting to the date picker. The same source notes that the Future view shows your scheduled tasks or snoozed items, allowing you to track these delayed activities separately from immediate work.

According to Close, if you mark the opportunity notification as Done, the system will automatically change the Estimated Close Date to today’s date without getting to a date picker at all. Because the date picker is bypassed during this completion action, the Estimated Close Date becomes today’s date when the opportunity notification is marked Done.

These automatic changes require careful monitoring. If a rep snoozes a Close opportunity notification, the estimated Close date moves to that future date. If they mark that notification Done, the Estimated Close Date becomes today. For accurate forecasting, you must verify that these automatic adjustments align with your actual sales expectations. Do not assume that snoozing a task in one tool updates the forecast date in another; each system handles these actions independently. Review the Future view in Close to see which items are currently snoozed and check the close date on completed items to ensure they reflect the intended timeline.

Syncing tasks with calendars and docs

When a sales rep assigns a follow-up from a shared document, the task moves into the rep's personal workflow. Google explains that a rep can view the task in their personal Tasks list and on their Google Calendar if the task has a set date, according to Google. This sync relies on the presence of a specific date; without it, the task does not appear on the calendar. For a revenue leader, this means the calendar view is only as reliable as the date discipline in the source document. If a rep leaves a follow-up task undated, it will not show up in the calendar, creating a gap in the visible pipeline activity.

The deletion process introduces a specific sync gap that can distort your activity logs. Google notes that if a checklist item is deleted in the doc, but the task isn’t deleted first, it'll still appear in the assignee's personal Tasks list, according to Google. This behavior means that removing a line item from a proposal or scope document does not automatically remove the associated follow-up task from the rep's queue. The task persists in the personal list even after the source item is gone. This leftover task can clutter the rep's view and potentially confuse the timeline of follow-up activities if the original context is no longer valid.

Common pitfalls in task date management

Date errors often stem from structural limits and blocking rules that prevent tasks from being marked complete on time. Understanding these constraints helps prevent forecast delays caused by incomplete activity logs.

Item limits create bottlenecks A common pitfall is exceeding the maximum number of checklist items allowed for each task. In Microsoft Project for the web, you can create a maximum of 20 checklist items on a task, according to Microsoft. If a sales follow-up requires more than 20 distinct steps, the task structure itself becomes a barrier to accurate tracking. Reps may struggle to log all necessary activities within a single task, leading to fragmented data or missed entries that obscure the true status of a deal.

Completion requirements block status updates Another significant issue arises when checklist requirements are enforced. In Microsoft Teams task lists, when you set a checklist requirement, task recipients must complete all items on the checklist before they can mark the task complete, according to Microsoft. This rule means that if even one sub-item is left unchecked, the parent task remains open. For revenue leaders, this creates a risk where a deal appears stalled in the pipeline because the task cannot be closed, even if the primary follow-up action was executed. The system prevents the status change until every single item is resolved.

Blocking rules enforce strict sequencing Related to the completion requirement, the blocking rule ensures that tasks cannot be marked complete until all checklist items are marked complete, according to Microsoft. This strict enforcement can lead to date discrepancies if reps do not update individual checklist items promptly. A task might have a due date that has passed, but the task remains open because a minor checklist item was overlooked. This disconnect between the actual work done and the system status can skew your forecast data, making it difficult to identify which deals are truly at risk.

Today, open one deal and write the follow-up due date on one line and the expected close date on the next. If those dates match only because an opportunity notification was snoozed or marked done, restore the close date you still expect. Then read Deal forecast months: date rules across 4 tools before you place the deal in a month.

FAQ: how to set due dates for sales follow-up tasks in crm tools

What time does Trello set for a checklist due date?

When setting a Due date in a checklist item, the Due time is automatically set to 6pm local time of whoever set the Due date, according to Atlassian. This rule applies specifically to the product named in the source title, "Set due dates for checklist items | Trello | Atlassian Support."

How does Todoist calculate the next date for a recurring task?

Completing a task that has a date of every 3 months will set the task’s date to 3 months from the task's original date, according to Doist. This logic is documented in the source titled "Introduction to recurring dates."

Does snoozing an opportunity in Close change the close date?

If you snooze the opportunity notification (set it to a later date), the estimated Close date of the opportunity will automatically change to that future date without getting to the date picker, according to Close. This behavior is described in the source titled "Inbox | Close Help Center."

What happens to a task in Google Tasks if the checklist item is deleted?

If a checklist item is deleted in the doc, but the task isn’t deleted first, it'll still appear in the assignee's personal Tasks list, according to Google. This sync gap is detailed in the source titled "Assign tasks from Google Docs - Computer - Google Docs Editors Help."

What is the maximum number of checklist items for each task in Microsoft Project?

You can create a maximum of 20 checklist items on a task, according to Microsoft. This limit applies to the product named in the source title, "Use task checklists in Microsoft Project for the web | Microsoft Support."

Sources