The calendar view, and what it cannot tell you

Two questions, two views

People ask a project two quite different things. The first is about occupancy: what is happening the week of the 12th, is anything landing on the Friday I am away, how full does next month look. The second is about consequence: if the API work slips three days, what else moves, and does the launch date survive.

A calendar answers the first well and the second not at all. It has no way to draw "this cannot start until that finishes", so dragging a task two days later shows you a task two days later and nothing else. The three tasks waiting on it sit exactly where they were, looking fine. A Gantt chart answers the second, because the arrows between bars are the whole point of the drawing.

This is not an argument against calendars. It is an argument against having only one of them. The mistake is using a calendar to make scheduling decisions and then being surprised in the retro.

One task, one bar

Plenty of tools draw a multi-day task by repeating its name in every day box it touches. A task running Monday to Friday becomes five labels. A moderately busy week then reads as twenty five separate things, and the two facts you actually wanted, where the work starts and where it ends, are the two the drawing hides.

GanttPulse replaced that in August 2026. A task now draws as one continuous bar across the days it spans, packed into lanes down the week the way a real calendar packs events. The fill carries the project's colour, so in a multi-project week you can see whose work is crowding whose without reading a single label.

What the bar is telling you

Every mark on a bar is there to answer a question without a click.

• Rounded end or chevron. A rounded edge is a real start or a real finish. A squared edge with a chevron means the week cut the bar and the task carries on. You never have to guess whether Monday is the beginning of something or the middle of it.
• Colour is the project. Not the status. In a week pulling from three projects, colour is the fastest way to see which one is eating the week.
• Status rides along. Done work is struck through and faded, on-hold work carries a pause glyph, and work in progress draws a thin line along the bottom at however far it has got.
• A breached deadline flags itself. A red flag on the bar, in the week you are already looking at, rather than in a report you open on Fridays.
• Off-days are tinted. Weekends and the holidays you have configured, so a bar stretching across four working days and two shaded ones is not quietly counted as six.

When a day holds more bars than fit, it says how many it is hiding rather than silently dropping them, and that count opens the day. A calendar that shows you four of seven things without admitting it is worse than no calendar.

A workable habit

Use the calendar to read the week and the Gantt to change it. Bars can be dragged to move a task and their edges dragged to resize it, which is genuinely useful for the small corrections: a task that should start a day later, a review that needs an extra afternoon. For anything with work waiting behind it, make the move on the Gantt where the dependency arrows are, see what follows it, then come back.

And if the calendar you actually read every morning is somewhere else, there is an iCal export, so the schedule can live there too.