Month, week and day views, filters and workload
Calendar and deadlines
The calendar brings the practice's deadlines into one view: tasks, obligations and reminders across the whole team. It's the instrument for anticipating peaks rather than absorbing them.
The three views
| View | When it helps |
|---|---|
| **Month** | Overview of the period, distribution of peaks |
| **Week** | Short-term operational planning |
| **Day** | What's happening today, in detail |
Arrows move between periods; the Today button returns to the present from anywhere.
What appears on the calendar
Each entry corresponds to a task with a date. Colour reflects priority, using the same scale as everywhere else in the product: green for low, blue for normal, violet for high, rose/red for critical.
The current day is highlighted, so the line between "already past" and "still recoverable" stays immediate.
Filters
The filter panel combines several dimensions:
- Client — one subject's deadlines.
- Case — the calendar for a single line of work.
- Status — for example, only what isn't finished.
- Priority — to isolate the higher levels.
- Assignee — one person's load.
Filtering by assignee in month view is the fastest way to see whether work is distributed or concentrated on one person. Do it before the peak, not during.
Anticipating peaks
The calendar's value isn't remembering tomorrow's deadline — that one is already known. It's making visible, weeks ahead, that a given week concentrates too many obligations, while redistributing is still possible.
The typical flow:
- Month view, no filters: identify the dense weeks.
- Filter by assignee: check who carries the load.
- Reassign or pull forward whatever can move.
Reminders
Reminders configured on tasks raise an alert before the due date. They're the safety layer that doesn't depend on someone looking at the calendar.
Recurring obligations
Deadlines that return on a fixed cadence should be set as recurrence on the task, not recreated by hand each cycle. They reduce administrative work and — more importantly — remove the possibility of forgetting a cycle.
A badly configured recurrence generates phantom deadlines the team learns to ignore, eroding trust in the whole calendar. It's worth verifying after the first cycle.
Good practice
- One source for deadlines. A parallel calendar on paper or in a spreadsheet cancels the benefit.
- Consistent priorities, so colour actually communicates something at a glance.
- A weekly look at the following month, as a fixed practice ritual.
- Reminders on obligations with external consequences, not on everything.