Scheduling
Plan orders on a timeline and allocate workers and assets to them — a forward planner that feeds directly into timesheets and payroll.
Scheduling
The Scheduling module is a forward planner for your orders: a timeline board where each row is an order and each column is a day, and you allocate workers and assets to the days each order needs them. Allocations flow directly into the worker loop — a scheduled worker sees their shift in My Shifts and files a timesheet against it, which then feeds payroll and invoicing.
How it fits together
- Orders define demand. When you build an order, its resource requirements (e.g. "2 Carpenters, Mon–Fri, 07:00–15:00") describe what the order needs each day across its date range.
- The scheduler fills demand. The board shows each order's demand day by day, and you allocate specific workers and assets against it — by drag and drop or click-to-add.
- Workers see their shifts. An allocated worker sees the shift in My Shifts (date, order, role, planned times) and files a timesheet against it, recording the activities and breaks they actually worked.
- Payroll prices the actuals. The timesheet — not the allocation — is what payroll and invoicing use. The schedule is the plan; the timesheet is the record.
Key concepts
| Concept | What it is |
|---|---|
| Order | The job being scheduled. Every order with days in the visible window appears on the board. |
| Resource requirement | A demand line on the order: a role or asset, a quantity per day, working days, and times. |
| Allocation | One worker or one asset committed to one order on one day, with start and end times. |
| Role-less allocation | A worker or asset allocated to an order's day without a specific requirement — useful when you just need someone on site. |
| Operator pair | A worker and an asset allocated together — "this operator needs this asset with them." |
| Signals | Non-blocking warnings on allocations, such as a double-booking. The scheduler flags conflicts; it doesn't stop you — sometimes double-booking is intentional. |
The forward-planning model
The scheduler deliberately treats time in three tiers:
- The future is fully editable — that's what planning is.
- Today is fully editable — sick calls, swaps, and extensions happen on the day, and the board must keep up.
- The past is read-only. Days before today are visible for review but cannot be edited: no adding, no removing, no dragging into the past. Yesterday's schedule is a historical fact.
If something about a past day is wrong, the correction belongs on the timesheet — the record of what actually happened — not on the plan. Timesheets remain editable (with a full audit trail) until they're processed. See Forward-Only Planning for the reasoning and the practical workflows.
Guides in this section
- The Board — navigating the timeline, reading demand and fill states, and the day-to-day controls
- Allocating Workers & Assets — drag-and-drop, click-to-add, operator pairs, role-less allocations, and signals
- Forward-Only Planning — why the past is read-only and how corrections work
- My Shifts — the Worker View — how allocated workers see their shifts and file timesheets