A week, built by dragging

Move a shift to another person or another day by dragging it. Hold Alt and it copies instead of moving. The change shows on screen first and reaches the server after, so the board never waits on the network — and if the server refuses, it goes back and tells you why.

Most weeks are not built from nothing. Copy last week, apply a template you saved, or clear the week and start over. When you create a shift, day chips in the dialog put the same shift on five days at once — on creation only, because applying an edit to five days is a different and far more dangerous verb.

A colored block on the left carries the role's initial, so a card at 132 pixels still tells you it is a Server and not a Bartender. Each column carries a headcount as well as a shift count — nine shifts and eight people is a different Thursday from nine shifts and nine people. Warnings carry a count in the header, because finding them by looking is fine on a roster of eight and useless on one of two hundred.

A shift can be scheduled until close, or until business declines. The team is told exactly that; you keep a private end time underneath so the budget still computes. The card reads 6pm – Close, and it is marked as an estimate so you know which part of the budget is one. Common shift times come as presets that carry both facts: 1pm – BD (9pm).

Every change lands in a draft. The bar at the bottom counts what is waiting and publishes the week in one press. An approved hand-over on a published week does not send the week back to draft — somebody swapping a Saturday is a real change, not an edit in progress.

The board is built for a roster that grew. Grouping by role, a sticky name column, a cost bar that sits outside the board's scroller so it does not scroll away, and a week that renders on a phone as a day at a time rather than as a squeezed grid.