The cell drill-down

Every cell on Capacity by project is a number that came from somewhere. Select one and a panel opens on the right saying where — the sum written out, not the total repeated in a bigger font.

Select a cell to open it, or press Enter or Space while it has focus. Close, Escape or a click outside dismisses it.

The panel reads the plan; it does not change it in place. Where it offers an action, the action opens a dialog or makes the same change the grid makes. An empty cell offers Declare a need, which opens the usual dialog. A person's cell offers Move bookings, which opens a dialog that shows every change before anything is saved (see below).

This is the Projects view. Cells on Capacity by person do not open a panel.

What every panel shows

At the top: what the cell is about, the same meter the cell drew — redrawn rather than replaced with a different kind of chart — its value, and the period the column covers.

Under that sit three figures, and they differ by the kind of row you opened. Each one gives the percentage and the hours behind it.

Then the sum itself, headed Where 50% comes from, followed by the rows it is made of.

A role's cell: is this covered, and by whom

The three figures are Confirmed, Draft and Gap.

Gap is not the same as the open hatch on the grid, and the difference is the useful part. The hatch is demand that is not confirmed. The gap is demand that nobody has even been proposed for. A role asking for 100% with nothing confirmed and one person proposed at 50% shows a full hatch on the grid — a proposal is not coverage — and a Gap of 50% in the panel. The hatch says this is not staffed. The gap says this is what nobody has so much as suggested a name for, which is the half you can act on today.

Who is in this role lists everyone contributing, each marked Confirmed or Draft with their share as a percentage and in hours. Where a gap remains, it gets a line of its own — Nobody · the remaining demand on this role — so an outstanding gap is shown rather than only counted.

A project's cell: which role is the problem

A project row is the total of its roles, and a total is precisely the number you cannot take apart by looking at it. 50% is equally two roles half-staffed and one role full, one role empty, and those two need opposite decisions.

The figures are Demand, Staffed and Coverage, and the sum is written out in hours: (40 + 0) h staffed of (40 + 40) h demanded = 40 of 80 h, 50% covered. Each role's demand is what it declares, so a small role weighs little and a large one a lot. Where the roles are not uniform the panel says so and counts them — 2 of the 3 roles are covered and 1 is not — and Roles that make up the total lists each one with its own bar.

Drafts stay outside the total, and the panel names the figure it is declining to use: what the coverage would read if proposals counted. A project should not look better staffed on the strength of a proposal.

Only roles carrying demand that period are in the total. A role not running yet does not dilute it, and does not appear as an empty term.

A person's cell: what else is on them

Expand a role and each person booked on it gets a row. That cell shows their share of this project — and because the grid is organised by work, everything else they are on is on another row, or hidden by the project filter, or off screen entirely. The panel is where it comes back.

The figures are Share here, Available and All commitments.

Everything Anna Kowalska is on in W35 lists every project and role they hold that period — the one you opened first, then the rest heaviest first, each confirmed or draft. The sum is written out across all of them and compared with what their week is actually worth after leave, so a person quietly at 130% across four projects reads as that rather than as four reasonable-looking cells.

Colours match the project bands on the grid. Beyond four projects at once, colour can no longer tell them apart reliably, so further lines carry a dashed empty square instead of a repeated colour and the panel says why. A recycled colour would claim the wrong project; a name never does.

Moving a person's bookings to other weeks

A person's cell offers Move bookings…. It moves that person's bookings on that project and role to other weeks, so you do not have to recreate them cell by cell.

The dialog opens on the period of the cell you selected. You can change it:

Days from and Until choose which days to move. Only days this person is booked on this project and role inside those dates move. Other people, other projects and other roles stay where they are, at every zoom.
Move by (weeks) is a whole number of weeks. A positive number moves the bookings later, a negative number earlier.

Before anything is saved, the dialog lists every run of days it will move and where each one lands, with the weekday, and whether it is confirmed or a draft. Press Move bookings to save it. Nothing changes until you do.

How a move treats the calendar:

Every day keeps its weekday and its hours. A booking on Tuesday and Wednesday arrives on the Tuesday and Wednesday of the new week, with the same hours, and nothing lands on a weekend.
Gaps stay gaps. If a person is booked Tuesday and Wednesday of two weeks in a row, moving both weeks keeps the empty Thursday to Monday between them empty. It does not fill in the days that were free.
Crossing a month is fine. A move from the last week of one month to the first week of the next works the same way.
A public holiday in the new week is not worked, as for any booking. Its hours are not moved to another day.

It is all or nothing. If any part of the move cannot be saved, nothing is moved, and the dialog says why:

The new dates already hold this booking, or the move would overbook the person. Choose other weeks, or change the booking that is already there.
The bookings changed after the dialog read them, for example because a colleague edited them. Check the grid and try again. Trying again never moves the same bookings twice.

Moving confirmed bookings needs the Resourcing approver role. With only the Resourcing manager role you can move drafts, and the dialog tells you before you save if the dates you chose include confirmed bookings.

Extending a person's booking

A person's cell also offers Extend Anna's booking… (or Extend Anna's draft… for a proposal). It closes the panel and opens that person's day planner for the same project and role, already filled in:

From is the day after the last planned day on the role, and a hint names that day.
Weekdays and Hours per day are taken from the last run of planned days, each with the hint As in the last run while the field still holds that value. Where the days of that run carry different hours, the hours field is left empty for you to fill in.
To is empty and has the focus. Until you choose it, the preview reads Choose the To date and Apply stays disabled.

Once you choose the end date, the planner shows the days and hours it will add, and saves them the way any planned run is saved. Extending needs the Resourcing manager role.

A Draft mark in the panel explains itself when you point at it or move the keyboard focus onto it: a draft is a proposal, it shows on the grid and on People but not in leave, and it does not count as staffed until someone with the Resourcing approver role confirms it.

Leave

Every panel ends with Leave in this period: how many of the period's working days are approved leave, and the planned-against-available reading that follows from it. Leave removes capacity rather than shading over it, so the overlap between leave and a booking is the conflict, stated in words.

Where nobody is away, the section says so instead of being absent — Nobody here is on leave in W35 is an answer, and a missing section is not.

An empty cell opens too

A cell with nothing in it is not a dead click. It opens on Nothing declared here and says which fact that is: no demand declared and nobody booked on this project, or on this role, or simply that this person is not booked on this project that week.

An empty cell is also the one place the panel offers an action: Declare a need, which hands off to the same dialog as everywhere else. See Setting a role's demand. It needs the Resourcing approver role.

Hours beside percentages

The plan is held in percentages; the hours beside them are derived, to make a share of a week concrete — 43% = 17.2 h/wk. They are worked out against a full-time 40-hour week.

On the day zoom, a project cell's panel shows that day's hours, so they read per day: 100% = 8 h/day, with demand and staffing as 12 h/day and 8 h/day. A role or person cell keeps its weekly figure, 100% = 40 h/wk, because that figure is the share of a full-time week whatever zoom you opened it from.

A project's Coverage is shown as the hours it divides — 8 of 12 h — staffed hours over demanded hours.

Working with the keyboard

Cells are part of the grid's own keyboard order, so the arrow keys reach them and Enter or Space opens the panel on the focused one. Each cell announces what opening it will show — the row, the period and the current value — and an empty cell announces that there is nothing declared, rather than passing as an unlabelled cell.

Example use cases

Open a role reading 0% and find that someone is already proposed for half of it, so the real gap is smaller than the grid's hatch suggests.
Open a project at 50% and see in one line whether that is two half-staffed roles or one unfilled one.
Open a person's cell and find the three other projects that add up to the week they appear to have room in.
Check what a cell's percentage is in hours before promising a delivery date on it.
Move a person's Tuesday and Wednesday bookings one week later when the project slips, keeping the days between them free.