Skip to main content

Drop Off and Collection Workflow

B
Written by Brayden Woods
Updated today

Assets move through a defined workflow linked to tasks.

Drop-off process

Job creation

  • Select assets on the job

  • Assets are assigned to:

    • One DROP_OFF task (deliver to customer)

    • One TRANSPORT_WASTE task (eventual collection)

  • Asset status becomes PLANNED_FOR_USE

Run scheduling

  • Drop-off task is added to a run

  • Task becomes SCHEDULED

Drop-off execution

  • Driver completes the drop-off

  • Task becomes COMPLETED

  • Asset status becomes IN_USE

  • Location updates to the customer address

  • Movement record created (site → customer)

Collection process

  • Transport task includes assets to collect

  • Driver confirms collected assets

  • System updates:

    • Status recalculated (usually AVAILABLE)

    • Location updated back to your site

    • Customer link cleared

    • Movement record created (customer → site)

Important rules

  • Each asset must be assigned to one drop-off task per job

  • Each asset must be assigned to one transport task per job

  • Assets cannot be deleted while assigned to active jobs/tasks

Movement history is retained permanently

Did this answer your question?