SIGNALS Docs
Reader View

Scheduling

Facilities, services, resource assignments, conflicts, timeline UI, iCal, and the connector hook catalogue.

Overview

Signals scheduling is the system of record for demand and assignments. Crew capability matching and external crewing tools sit outside core — they integrate via the Plugin SDK hook catalogue, webhooks, and the resource-assignment API.

Surfaces

Surface Path / name Permission / ability
Labour (services) UI /services services.view
Resource Timeline UI /scheduling/timeline resource-assignments.access
Fleet diary UI /fleet/diary vehicles.view + resource-assignments.access
iCal feeds /calendar/feed.ics and /calendar/feed/{user}.ics Explicitly created per scope; private credential and signature expire after 90 days; revocable/rotatable, with current access rechecked on every request

The facilities, services, resource-assignment and conflicts APIs, assignment concurrency and the plugin hook catalogue are in Scheduling API contracts.

Feed subscriptions require a managed link. See calendar feed controls for creating, rotating and revoking links.

Labour services

The Labour page (/services) lists the labour services in the catalogue: the service's catalogue item, its resource type, and the minimum and maximum number of resources it needs. It is a read-only list with sortable, filterable columns; it needs services.view.

The Resource Timeline runs in one timezone

The timeline draws every lane on a single grid timezone, and that zone is always the viewer's own — the timezone on their profile, falling back to the company clock, then UTC. Day boundaries, the today marker, bar positions, assignment resolution, and conflict resolution are all computed in that one zone, so a bar can never disagree with the column it sits under.

Unlike the rental diary, the timeline has no Grid time toggle — there is no way to switch it to a warehouse's local zone. Assignments across warehouses in different zones are drawn on the viewer's clock; the warehouse filter narrows which lanes appear, not what time they are drawn in.

Assignment and route-stop inputs are read in the viewer's timezone and stored as UTC instants. Rental booking windows are also UTC instants, converted to the viewer's timezone for display — see Rentals.

Reading the timeline

The Resources switch sits in the one toolbar with the warehouse filter; the shared date controls (‹ Today ›, date picker, span) are right-aligned and the key is below the grid. The switch picks the layout. Everything is view-only; changes happen on the rental. The timeline uses the same warehouse union and inherited vehicle dates as the REST assignment list.

  • All and Facilities — resources down, days across. Rows are grouped Crew, Facilities and Vehicles, each with a per-day load meter. Bars show the rental, the status as a word and a glyph, the time window and one dot per route stop; scheduled bookings are dashed tints. Each bar spans the whole local days it touches (the row data behind the grid keeps exact positions); bars that carry on past the window have a square edge. A resource name opens a side panel of its bookings in the window (?resource=account:{id}).
  • Crew — a utilisation heatmap: hours booked per person per local day (or jobs, with Metric), with an over-10-hour flag and a conflict flag on each cell, a Total column and Crew on / Free counts per day. A cell opens that day on an hour axis with the rest of the crew beneath (?panel=cell:account:{id}:{date}); a Free count opens the day summary (?panel=day:{date}). Only crew with a booking in the window appear. Cancelled bookings never count as booked time.
  • Vehicles — a route day: hours across one local day (?day=; ‹ Today › step a day), one lane per vehicle booking from depot out to back with its assignment role and travel time between stops, route stops at their arrival time with their dwell, the rental's delivery / collection window shaded behind delivery and collection stops (arriving after it closes is a late risk), crew booked on the same rental that day beneath (over 10 hours flagged; none booked is flagged "No crew booked"), idle vehicles listed, and a read-only Unscheduled transport tray of orders delivered or collected that day by the company with no vehicle booked (orders for privacy-restricted accounts are left out unless you hold accounts.privacy.case). A vehicle opens its run sheet (?panel=run:{assignment}), a stop its details (?panel=stop:{id}). Signals records no mileage or driver role, so leg miles and a no-driver callout are not drawn.

The Fleet diary is the vehicle route day on its own page. Today is drawn in tenant branding: the now line is Settings › Branding › Schedule's now-line colour, and the today marks use the brand primary colour.

Rental phase timing

Scheduling reads rental phase definitions by operational role, independent of their labels or keys. The delivery and collection roles supply customer windows for the route day and timeline only when both endpoints form a positive interval. The event role supplies day-phase indicators; without event dates, hire days default to In Use unless a delivery or collection window matches. A renamed or hidden definition keeps its role; archived definitions still serve attached rental phases.

Unscheduled service demand counts only rentals in warehouses you can access, and cached results are never shared between callers with different warehouse access. For unscheduled service demand, each explicit line endpoint has priority. Otherwise a line following delivery or collection uses that role's window only when both endpoints exist; an absent or partial window falls back to hire. Hire-period lines use hire dates. Dispatch and scan-out planning use the outbound_loading start with hire-start fallback. Return briefings use the collection start with hire-end fallback.

Phase edits and definition impact rebuilds retain booked assignment dates. An undated vehicle booking continues to inherit the rental hire window in assignment list/timeline reads. Moving a customer window can change a route stop's late-risk indication without moving the vehicle booking. Charge dates remain independent of these operational windows.

Phases do not create calendar events or timed workflow triggers. Calendar feeds continue to publish assignments using their own effective dates. To react to a phase edit, use event-based phase conditions.

Resource types

Live polymorphic resource_type values are account (crew), facility, vehicle, and dispatch_group.

Rental and project attachments

Every resource assignment belongs to exactly one rental or rental project. A linked rental_line_id is valid only on a rental assignment and must identify a line on that same rental. Project assignments use the warehouse union of their linked rentals: access to any linked rental warehouse makes the project row visible, while no matching linked rental warehouse hides it. Route stops and scheduling conflicts inherit the same visibility through their assignment links.

An editable rental assignment backed by a linked crew service or fleet catalogue item can create a normally priced rental charge line. The new line uses the existing rental add-line flow and is linked through rental_line_id; removing the line leaves the assignment in place and clears that nullable link. Assignment and charge-line windows remain independent unless an operator explicitly copies one to the other from the Resource Timeline. Invoiced lines, immutable rentals, externally managed assignments, and resources without a supported catalogue link are rejected.

The project Crew form requires a Labour service for person/account and dispatch-group assignments. It creates a one-time Labour cost calculated from that service's rate over the assignment window in company base currency; catalogue-linked project vehicles create Fleet costs through the same bridge. The cost is an independent, editable project record after creation and is not re-priced when the assignment or catalogue price later changes. API assignments without a supported catalogue link remain logistical and do not create a cost.

Assignment creation rechecks the rental window, line and resource under locks; refusals and their responses are listed in Scheduling API contracts.

Dashboard

The Scheduling conflicts widget (scheduling-overview) shows open conflict counts, unmet demand, and top items linking to the Resource Timeline.

Additional form guidance

The timeline shows a starting prompt before any resource booking exists, or before any vehicle exists on the fleet surface. Deleted records still count for this first-run check. The empty Services list links to creating a catalogue item of type Service.