The Schedule board: workload, capacity, rebalancing

Schedule (in the left sidebar) is the one workspace-level view that isn't project-first. It puts every staff member on a row and every day in a column, and fills each cell with the work they're due to finish that day — so "is anyone drowning next week?" is a question you answer by looking, not by adding up hours in your head. The page header reads "Resource schedule".

Each person's row shows a load bar — hours committed versus hours available for the visible window, spelled out underneath as "32h of 40h · 6 tasks". It goes red when they're over. Click the row to expand an hour-by-hour detail strip.

A task's whole estimate lands on its due date, in a single bucket — it is not spread across its start-to-end span. A 12-hour task that runs Monday to Friday shows up as one 12-hour chip on Friday, not 2.4 hours a day. That keeps long tasks from smearing across the grid, and it means dragging a chip visibly moves it. The load bar, the over-capacity tint and the rebalance suggestions all use the same rule, so the numbers always agree.

• ＋Week / Day toggle, with Previous · Today · Next to move the window. Week view shows Monday to Friday.
• ＋Weekends — turn the toggle on to add Saturday and Sunday columns (they carry zero capacity either way).
• ＋Team filter — Everyone, My teams (if you're on one), or a specific team.
• ＋Microsoft 365 — overlays real calendar busy time on top of Current work. It's on by default, and turning it off sticks in that browser. Your own events keep their subjects; everyone else's arrive as an unlabelled "Busy" band, so nobody's calendar is exposed. A multi-day or all-day event blocks every day it covers, so a week of vacation booked in Outlook shows up as busy all week.
• ＋The legend stays short. Billable task and Internal task always appear; Milestone, Microsoft 365 busy, PTO/out and Holiday/weekend show up only when something on screen actually uses them.

Only staff appear as rows. External partner viewers and deactivated members are excluded from the grid, the head count, the capacity math and the drop targets — so you cannot drag internal work onto a partner. Partners don't get the Schedule link at all.

"To dispatch" holds every open task that can't be placed on the grid — no assignee, or no due date, or neither. Dated ones sort first, earliest due at the top. Drag one onto a person × day cell to schedule it; the cell tints when the drop would push that person over capacity, so you see the cost before you let go.

1. 1
   Open Schedule and land on the right week

   Use Week/Day and the arrows. "Today" jumps back to the current week.
2. 2
   Drag a chip onto someone's day

   Dropping on a different person reassigns it; dropping on a different day reschedules it. Both at once works too.
3. 3
   Duration is preserved

   If the task already had a start and an end, both dates shift by the same number of days. If it only had one date (or none), it becomes a single-day task on the day you dropped it.
4. 4
   Answer the service-call prompt (Autotask-synced tasks only)

   Current offers to book an Autotask service call — Autotask's own calendar booking, which Autotask then puts on the technician's Outlook calendar — when the drop actually changes the DATE of an Autotask-synced task whose project is linked to Autotask. Moving such a task to a different person on the day it is already due reassigns it without prompting. The reschedule is already saved either way; saying no just skips the booking. (Service-call booking is an Autotask feature — ConnectWise workspaces simply don't see this prompt in this release.)
5. 5
   Drag back to the tray to unschedule

   This clears the task's dates in Current so it leaves the grid. It deliberately does not push to your PSA, so it can never wipe the PSA's dates.

The Rebalance suggestions tile answers "who's drowning, and who could take something off their plate?" It looks ten days ahead and proposes concrete moves: "Move 'Migrate mailboxes' (~3h) from Alex → Jordan on Thu Jul 16." Only project managers and admins see the tile. Apply is a task write, and the database (RLS) independently enforces who may reassign a task — but the tile's visibility itself is a UI gate.

Apply reassigns the task (and, on a PSA-synced task, pushes the new owner as the PSA's primary resource). The X dismisses a row for the rest of your session. If nobody is over, the tile says so. The three tiles on this page can also be dragged into any order and resized, and the arrangement saves to your account.

Days a person is out carry zero capacity, so any work sitting there reads as over capacity — exactly the signal you want. People add their own time off from the account menu in the top right → My availability (PTO or Blocked, over a date range). Company holidays come from your tenant's holiday list. For how the scheduling engine pushes work off those days, see "PTO and availability-aware scheduling in the Timeline" and "Holidays and employee costs: where the numbers come from".