Crews

A crew is a saved set of resources, each pre-assigned to a role — the gang that works together. Instead of allocating six people one at a time, you drop the crew on a day and the scheduler places every member into the matching role.

Crews live in the Crews tab of the Resources drawer.

Building a crew

Build a crew opens the builder:

• Name and colour — pick one of the presets or a custom colour. The colour is how the crew is recognised on the board.
• Members and roles — add workers and assets. Each worker member carries the role it fills; each asset member carries its asset class. A member without a role (or an asset without a class) can't be matched, so the builder asks for one.
• Machine links — link a worker member to an asset member to say "these two go out together". A linked pair deploys as an operator pair and stays paired on the board.

Crews are editable and deletable from the same tab.

Deploying a crew

Drag a crew onto any order×day cell and the deploy dialog shows what will happen before anything is written: the quantity going out, the start and end times for the day, and where each member lands.

The matcher walks the day's requirements and places each member into a requirement matching their role or asset class, honouring the links so operator pairs land together. Members it can't place are listed with the reason:

Deploying reports how many members were placed and how many were skipped.

Roles the day is full on

When a role the crew carries is already filled to its quantity, the dialog offers to expand this day rather than stranding the members: it names the role and how many don't fit (Carpenter — 1 member doesn't fit at 1), with a quantity control defaulted to what the crew needs. Expanding writes demand onto the order, so it's always confirmed and never automatic — decline it and those members are reported as skipped, exactly as before.

The expansion applies to that day only, at the requirement's own shift window, so adding a seat can't silently retime the day. A linked operator pair takes one operator seat, not a labour role plus a plant class.

Roles the order doesn't have

When the crew carries roles the order doesn't have on that day, you're offered Add roles and deploy: the scheduler adds those requirements to that day and fills them in one step, with the shift times you confirm. The order's usual pattern isn't changed — these are day exceptions, like any other single-day role addition. You can also choose to skip the missing roles and deploy only what matches.

Crew provenance on the board

An allocation created by a crew deploy remembers which crew placed it. On a collapsed card in Card layout, that crew's members show as a single chip in the crew's colour, so you read "this crew is on this job" rather than six separate names — and the name slots it frees go to people who do need naming. Anyone booked individually still appears by name; they aren't part of the crew and don't inherit its label. Expand the card to see the members.

Live crew chips use the crew's current name and colour — renaming or recolouring a crew updates chips already on the board. Click a chip to open its menu:

• Edit {name} opens the crew builder.
• Remove {name} from this day (Card layout, single-day window) drops every allocation that crew placed on that order-day in one action. Past days show the action disabled with Can't remove — this day has passed.

If a crew was deleted after it was deployed, the chip disappears and those members fall back to individual names.

The crew label only reflects what the deploy actually did: an allocation that already existed, or one you place by hand, is not retro-labelled, and removing a member from a crew doesn't rewrite shifts already scheduled. Deleting a crew outright leaves its shifts standing, unlabelled — the bookings are real work, not part of the template.