Overview
Clear due dates keep retirement plan work on schedule. In Stax.ai CX, you can set a due date on the project itself and on each task inside it. Due dates create accountability for your team and your clients, and they power automated reminders. This guide covers when to use fixed dates versus relative dates, and how to track key milestones.
Fixed dates vs. relative dates
Fixed date — A specific calendar date, like April 15. Use it for regulatory deadlines or one-off tasks.
Relative date — A number of days after the project launches. Use it in templates so deadlines adjust automatically each time you launch.
Important: Project due dates and manually created tasks always use a fixed calendar date. Relative dates are only available for tasks when you launch a project from a template.
Set the project due date
Open the project you want to update.
Select the due date field.
Pick a calendar date.
Set task due dates when launching from a template
While launching a project from a template, review the list of included tasks.
For each task, find the Due Date field.
Choose one of the following: a. A specific calendar date. b. A number of days after the project launch date.
Enter the date or the number of days.
Complete the launch.
Verify that each task shows the correct due date.
Note: Tasks set to "days after launch" calculate their deadlines automatically from the project launch date.
Set a due date on a manually created task
Open the project where you want to add the task.
Create a new task and enter the details.
Assign the responsible person.
Select a calendar date in the Due Date field.
Save the task.
Confirm assignments and reminders
Open each task and verify it is assigned to the right internal user or client contact.
Make sure every task you want to track has a due date.
Confirm reminder notifications are enabled for assigned users.
Important: Reminders send only when a task has both an assigned owner and a due date. Client tasks are the exception — clients may still receive reminders based on the due date alone.
Track milestones
For longer workflows, you can add project data fields that log key milestone dates — for example, when census data was received or when final approval came in. These fields let you report on timelines across all your plans. See Census Data Collection Projects for a worked example.
Best practices
Review the full timeline before launch. Make sure the project due date matches any regulatory or client deadline.
Scan task dates to confirm they are realistic and in the right order.
Adjust any dates that create conflicts or bottlenecks, then save.
Related articles
Projects Overview
Creating and Launching Projects
Census Data Collection Projects
Client Task Reminders