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, ranked by availability. Same result as dragging, better on smaller screens or long resource lists.

Several resources at once. Multi-select in the drawer and drop the selection onto a card to allocate them all. The bulk add dialogs do the same from a dialog, including an operator flow that queues worker + asset pairs.

Several days at once. Select a range of days (shift-click a second day, or double-click a role to take the whole window) and one drop fans the allocation across every day in the range. Days that can't take it — past days, days outside the order's dates, days already full — are skipped and reported rather than silently dropped.

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, swapping and removing

• Drag a placed chip to another day or another order to move it.
• Click a chip to open its popover: the resource's detail, its signals, Remove from this day, and Replace.
• Replace swaps one resource for another in place, keeping the role, day and times. You can replace on this shift only, or across a wider scope — see Bulk Changes.
• Removing is undoable straight from the toast.
• Once removed, the worker stops seeing the shift in My Shifts.

When a timesheet has already been filed, the board warns before it acts rather than refusing: moving the shift leaves the timesheet recorded where it is, and replacing or removing the resource detaches the timesheet from the shift without deleting it. You confirm with that spelled out.

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, retime and remove together — the pair is treated as one unit throughout — and the worker's My Shifts card shows the asset they're paired with ("you need this asset with you"). The pair chip previews the change before it commits, and each half has its own menu for editing the time or replacing just that half.

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 account's default shift times. They appear in their own lane under the requirement cards — and in their own band at day scale — 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 overlapping shifts gets a conflict badge. Click it to see the competing allocations. Overlap is time-aware, including overnight shifts, so two non-overlapping shifts on the same day read as "booked today", not as a clash.
• Over-allocation beyond a day's demand shows as a red fill count (3/2), not an error.
• Shift-time drift — when an allocation's actual times no longer match the plan, the chip shows both and offers to bring the plan back in line.
• Orphaned allocation — the requirement this chip was filling has been removed from the order. The allocation is shown in the role-less lane rather than hidden, so you can deal with it.

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 on the same requirement (same person, same order, same day and times — usually an accidental double-click), the scheduler quietly rejects the duplicate. The check is per requirement, so the same person can legitimately be booked twice on a day across different roles or split shifts.