Loading
Because dates are set one project at a time. Each is reasonable alone; together they put four deliverables and two people's holidays in the same week, and nobody sees it until that week arrives.
The calendar view shows tasks, milestones and deliverables by date, alongside leave and holidays, for a project or across all of them.
It reads the plan and the leave calendar in Nest together, so a date is chosen against real availability rather than an empty grid.
A milestone is being placed for late July. The calendar shows two team members on leave and another project's cutover the same week, so it moves before it is promised.
It will not prevent a clash. It makes the clash visible while it is still a proposal, which is the only point at which it is cheap to fix.
Tasks and milestones from the plan, leave and holidays from Nest, and client-visible dates from the portal.
Yes, filtered by team, client or person.
No. Availability is visible; the reason stays in Nest.
Yes, as a subscribed feed per person.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.