DELIVERY DATES
Put task dates and milestones into one planning conversation
Review when work is intended to start and finish, then open the underlying task to discuss the people and decisions behind the dates.
A deadline only helps when its context is visible
A list of due dates cannot show the whole delivery plan. The timeline places dated project tasks in a time-oriented view, helping a team examine the order and overlap of planned work. Dated milestones provide additional checkpoints. The view uses the project task records, so a planning discussion stays connected to the descriptions, assignees and states that explain what still has to happen.
Plan from explicit start and due dates
Tasks can carry a start date and a due date; the project also has its own start and target end. These are intentionally chosen planning dates, not a prediction of actual completion. Compare work periods, find a task whose dates are missing and decide whether the plan is realistic before presenting a delivery commitment to the customer.
- Task start and due dates
- Project start and target end
- A common view of dated work
Keep checkpoints and task detail connected
The project timeline includes a list of milestones that have due dates. A milestone gives the team a named checkpoint, while the related tasks retain the concrete work. Open a task to inspect its assignees, description and any recorded predecessors. This helps explain an ordering constraint without claiming that the timeline automatically recalculates an entire dependency network.
- Named dated milestones
- Access to the underlying task details
- Predecessor context available on the task
Use the right view for the decision
A time-oriented layout answers a different question from a status board. Switch to calendar, board, table or list while keeping the same task records. Authorized date edits use the normal task update flow and current-record checks. Reading a date does not grant the ability to change a restricted project, and a shifted date does not imply that every dependent task has been rescheduled.
- Shared task data across project layouts
- Date changes follow task write authority
- Manual planning decisions remain explicit
A concrete workflow
Add realistic dates
Give the work a start and due date where the team has enough information to plan it.
Inspect the timeline
Compare the sequence of tasks with the project target and the named milestones.
Clarify constraints
Open tasks that appear out of order and discuss predecessors, ownership or missing information.
Update the agreed plan
Save authorized changes and communicate a revised delivery expectation through the project update process.
An illustrative working example
Example: coordinating a training launch
A training provider plans preparation, participant materials and a rehearsal before a launch milestone. The timeline reveals that materials are due before the content review has finished. The coordinator opens the relevant tasks, checks the recorded prerequisite and agrees revised dates with their owners. A project update explains the effect on the launch. The dates are consciously maintained rather than silently treated as an automatically optimized schedule.
Questions about this topic
Is this an automatic critical-path scheduler?
No. The supported timeline presents planned work dates and milestone checkpoints. Do not assume critical-path calculation or automatic propagation of every dependency.
Are milestones visible without a date?
The timeline milestone list uses milestones that have a due date. Undated milestones can still belong to the project and be managed through their own record.
Do task dates represent recorded working time?
No. Planned dates describe a schedule. Actual duration and approved effort come from Time entries rather than the width of a timeline item.
Can I switch back to the board?
Yes. The project supports several layouts of the same task set. Choose the board for status flow and the timeline when dates are the subject.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Microsoft Excel
Workflow concept: Review task start and due dates in a checked planning workbook.
Asana
Workflow concept: Compare planned work periods without assuming automatic dependency rescheduling.
Google Calendar
Workflow concept: Check milestone dates against known team commitments before confirming the plan.