Wiki/Core Operations/Collections: Schedule → Confirm → Drive → Deliver → Inbound
12Core Operations3 min read

Collections: Schedule → Confirm → Drive → Deliver → Inbound

The pickup workflow that ends with an inbound order creating itself, with the client and contract already filled in.

A collection in ITAD is the act of going to the client’s site and picking up the equipment. It’s also the part of the workflow where, in most operations, the most retyping happens — client name, contract reference, contact info, all entered three times into three systems.

The status flow

A collection starts as requested (either from /request-collection on the marketing site or created by the operator). Moves to confirmed when the slot is locked and the client is notified. To scheduled when a driver and vehicle are assigned. To in_progress when the driver checks in at the client site. To collected when the equipment is loaded. To delivered when it arrives at the warehouse — and at that moment, the inbound order auto-creates itself with the client, the contract, the contact, and the vehicle reference all already filled in.

Multi-trip pickups

Some collections don’t fit in one truck. A collection can carry multiple trips, each with its own driver, vehicle, scheduled-date, and items-loaded sub-record. The collection itself stays one logical pickup against the client; trips track the physical reality. The inbound order created at the end consolidates all trips into one inbound — manifest reconciles against the union, not against trip-1-only.

Driver and fleet

Drivers and vehicles live in their own catalogs (/settings/core/drivers, /settings/core/fleet) so they can be assigned without typing. A driver has license-class and certification-level (some sites require a security-cleared driver). A vehicle has capacity and access constraints (a 3.5T van fits where a 7.5T truck doesn’t).

Tracking and revert

The collection detail page (/core/collections/[slug]) shows status, driver, vehicle, scheduled-date, items-expected. If a status needs to be reverted (the driver was assigned to the wrong slot, the collection didn’t actually happen), the revert-preview shows what side-effects will reverse before the change is committed. Database triggers guard transitions: you can’t mark "delivered" without a "collected" record before it.

Public request form

/request-collection on the marketing site is the public-facing version: a five-step form for prospects to request a pickup themselves. The submission lands as a draft collection with the data structured, ready for the operator to confirm or adjust.