Scheduling

Scheduling lives at /schedule (breadcrumb Availability): one calendar for team schedules, time off, and meetings. The calendar answers availability; the records of what happened in meetings live at Meetings.

• The header states the contract: “View and manage team schedules, time off, and meetings.” Month, Week, and Day toggle the view; Add Event creates; Today jumps back to the current date.
• The legend chips split event kinds: Maintenance, Off-site Event, Paid Holiday, Paid Time Off, Personal Day, Sick, Meetings, Tasks. Time off and work share one surface — coverage reads both at once.
• An empty grid is information: no blocks means no commitments, not a broken calendar.

• Availability rules come from configuration. Work calendars, capacity, and schedule defaults live under Work Schedules — fix recurring conflicts there, not per event.
• Scheduled work still needs an owner. A block on the calendar with no responsible member is a gap wearing a date; ownership resolves on Team first.
• Due-date pressure on Tasks is a scheduling signal. When everything is urgent, the schedule is overcommitted, not the team underperforming.

What next

• Events: calendar-synced entries per CRM record.
• Meetings: the records of scheduled contact.
• Work Schedules: the calendars and capacity rules behind the view.
• Team: who owns the scheduled work.
• Tasks: the dated work the schedule must absorb.