Calendar View vs Timeline View

Calendar and timeline are both date views. They are not the same picture, and neither of them is a Gantt chart. The calendar answers "which tasks are due on this day?" The timeline answers "which tasks sit with this person this month?" If you open one expecting the other, the screen looks empty or pointless.

A schedule with blocking arrows is the Gantt chart, covered in how to plan a project on a Gantt chart and compared with the board in Kanban vs Gantt charts. This page stays on the two date views.

Calendar view

The calendar is a month grid. A task with a due date appears on that due date. You can move through months. Tasks with no due date do not land on a day. They stay in the undated list beside the grid, so you can see what the calendar cannot place.

Use the calendar when the question is the day:

• What is due Thursday?
• What is due next week?
• Which tasks have never been given a day?

The calendar does not draw dependency arrows. Two tasks on the same day are simply due the same day. One does not block the other unless you set that link and look at the Gantt.

The calendar is also not the company holiday calendar. Holidays and weekly offs belong with attendance and leave, in HR. A project calendar will not grey out a public holiday for you. If a task is due on a holiday, the date is the date you typed. Change it yourself if the team does not work that day.

Priority is still a separate field. The calendar does not sort a day by Urgent versus Low. It shows what is due. You read priority on the task.

Timeline view

The timeline is labeled as a resource swimlane. Each row is a person who has at least one assigned task in the set you are viewing. Across the row is the current month, day by day. Each of that person's tasks appears as a chip on the row, with the due day number when the due date falls in that month.

Read it as "this person's tasks," not as a bar that runs from the start date to the due date. The chip does not measure duration. It names the task and the due day. People with no assigned tasks in the current set are not given a row.

Use the timeline when the question is the person:

• What is on Priya's list this month?
• Who has several tasks due in the same few days?
• Did we assign this task to anyone? Unassigned work will not appear on a person's row.

It is not a capacity plan. It does not convert tasks into hours, and it does not know a person's available time. The workload view is the count of tasks due per day. The timeline is the list of those tasks by person. Neither one is a billable forecast.

Side by side

	Calendar	Timeline
Organized by	Day of the month	Person
What places a task	Due date	Assignee, with the due day on the chip
Undated tasks	Shown as unscheduled	Not placed on a day
Unassigned tasks	Can appear on their due date	Do not get a person row
Dependency arrows	No	No
Duration from start to due	No	No
Company holidays	No	No

If you need the span of a task from start to due, and you need to see what blocks it, open the Gantt. If you need the due day on a wall-calendar grid, open the calendar. If you need each person's tasks for this month, open the timeline.

A Tuesday standup

The group looks at the calendar first. Three tasks are due today. One has no owner, which the calendar still shows, because a due date does not require an assignee. They assign it before the meeting ends.

They switch to the timeline to see whether those three sit with the same person. Two are on Sam's row, and Sam's row also shows a task due Friday that is easy to forget because Friday is quiet on the calendar when you only stare at today. The timeline made Friday visible without turning the meeting into a schedule review.

They do not open the Gantt. Nothing in the standup is about a block. Using the timeline as a Gantt would be the wrong tool, and it would not draw the arrow anyway.

Mistakes that make the views look broken

No due dates. The calendar's month is empty and the undated list is long. The timeline can still show the tasks on a person, but it cannot point at a due day. Add dates if the date is the question.

No assignees. The timeline has no rows for that work. The calendar can still show it. Assign someone if the person is the question.

Expecting holidays. Someone asks why the office closure is missing. It is missing because this is not the HR calendar. Do not recreate the holiday list as fake tasks unless you truly want those tasks in the project.

Expecting bars. Someone asks why a two-week task is not a long bar. That shape is the Gantt, and only when start and due are both set. The timeline chip is not that bar.

Which one to teach a new teammate

Teach the calendar if their job is "what is due." Teach the timeline if their job is "what each person is carrying." Teach the Gantt only if their job is order and overlap. Teaching all three in one hour produces people who open the wrong tab and decide the product has no dates.

The views are on the same tasks. Saving a personal preference for which tab you open is a separate habit. The dates and the assignees are the data. The view is only the picture.

Choosing for a specific role

A producer who is asked "are we clear this week?" should live in the calendar. Their follow-up is a day with too many due dates, or a due date that slipped and was not moved. They will be tempted to paste the month into a slide. The calendar is the slide. If someone cannot open the project, fix access rather than copying days into a document that will be stale on Thursday.

A lead who is asked "is anyone overloaded?" should open the timeline and then the workload view if they need the count. The timeline shows the names of the tasks. It does not show that a task takes six hours. If the conversation becomes "Sam has eight chips, so Sam is over capacity," stop. Eight due dates are eight due dates. They might be eight small reviews or two large builds plus six chips that should have been a checklist. Open the tasks before you move work off the person.

A client who can open the project may open either view. A due date you set as a private target will read as a promise on the calendar. Move internal-only tasks out of the shared project, or do not share it. The timeline also shows team names on the rows. Check who appears before you treat that view as something a guest should open.

None of these roles needs a holiday overlay. If a day is a closure, do not put due dates on it. The product will not import the HR calendar into the project month.

Conclusion

Calendar view puts tasks on the due date in a month, and keeps undated tasks beside the grid. Timeline view puts each person's assigned tasks on a row for the current month and marks the due day. Neither shows Blocks arrows, neither draws a duration bar, and neither is the holiday calendar. Pick the calendar for the day, the timeline for the person, and the Gantt when the schedule itself is the question. Those views are part of /pms.