Allocating Workers & Assets

An allocation commits one worker or one asset to one order on one day, with start and end times. This guide covers every way to create, move, and remove them.

Creating allocations

Drag and drop. Drag a worker or asset from the Resources drawer onto a demand card. The allocation takes the requirement's planned times. You can also drag onto the day cell's role-less lane to allocate without a requirement.

Click to add. Every demand card has a + add control — click it and pick from a searchable list. Same result as dragging, better on smaller screens or long resource lists.

Multi-day demand fills day by day. Each day is allocated on its own — allocating someone to Tuesday says nothing about Wednesday. This keeps each day independently editable and independently visible to the worker.

Moving and removing

• Drag a placed chip to another day or another order to move it.
• Click a chip to open its detail, where you can remove it.
• Once removed, the worker stops seeing the shift in My Shifts.

Operator + asset pairs

Some work needs a worker and an asset together. The scheduler handles this as a pair:

• Use + pair on an operator requirement to allocate a worker and asset together, or
• Drag a placed worker onto an asset (or vice versa) on the same day to combine them into a pair.

Paired allocations move and remove together, and the worker's My Shifts card shows the asset they're paired with ("you need this asset with you").

Role-less allocations

Not every allocation needs a requirement. Drag a resource onto the role-less lane (or use the role-less add) to put someone on an order's day without a role. Role-less allocations get the default shift times. They appear in their own lane under the requirement cards, and the worker sees the shift like any other — just without a role tag.

Signals — warned, not blocked

The scheduler deliberately signals problems instead of preventing them:

• Double-booking — a resource allocated to two places at once gets a conflict badge. Click it to see the competing allocations. Sometimes a double-booking is real (a split day, a planned handover), so the board flags it and leaves the call to you.
• Over-allocation beyond a day's demand shows as a red fill count (3/2), not an error.

The philosophy: the dispatcher has context the system doesn't. The board's job is to make sure nothing surprising is invisible.

Duplicate protection

If an identical allocation already exists (same person, same order, same day and times — usually an accidental double-click), the scheduler quietly rejects the duplicate. Legitimate near-duplicates like split shifts are unaffected.