> ## Documentation Index
> Fetch the complete documentation index at: https://useidalia.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How to plan a last-mile plant delivery to site

> Send plant from a yard onto a job site. The site agrees when trucks can arrive. The transport coordinator plans each truck and records when it arrives.

## Overview

Site deliveries can be chaotic. There's a lot of people involved that all need to agree on what's coming and when. They're often from different teams and companies, and there's almost always 100 other things happening on site at the same time that could get in the way.

In this guide, we'll see how Idalia make the entire process safer, simpler, and more efficient.

As an example, we'll use a 20t excavator being delivered to a job in Sydney. The machine goes on one truck, the buckets and attachments on a second.

While we'll only use 2 trucks and a simple asset register for this example, Idalia can handle any number of trucks and much more complex assets.

## Build the workflow

Transporting plant and equipment is a high-risk activity. We can use custom forms and automations to enforce checks at the key stages so each delivery is done correctly and safely.

If you'd rather skip the workflow setup and get right to it, skip to [Plan the transport order](#plan-the-transport-order) below.

### Create transport forms

We'll create two forms

* **Transport dispatch**: filled at the yard, before the truck leaves
* **Transport receipt**: filled at the site, when the truck arrives

Create these two forms once for the workspace. Every later transport order uses the same forms. You do not create a new form for each order or each truck.

Open the Idalia AI agent and paste this, or do it manually using the [Forms](https://useidalia.com/docs/workflows/forms.md) guide:

```text wrap theme={null}
Create two forms: Transport dispatch and Transport receipt.
Publish both. Connect each one to TransportLeg.

Add a short, clear description to each form, and a short title and description to each field.

Transport dispatch, filled at the yard before the truck leaves:
- Checklist: This is the right plant for this load, and it is safely loaded
- Images: The plant on the truck
- Signature: The driver accepts the load
- Long text: Anything the office must know

Transport receipt, filled at the site when the truck arrives:
- Choice: On time, or Delayed
- Long text: The reason for a delay. Show this field only when the choice is Delayed
- Choice: No damage, or Damage
- Images: The damage. Show this field only when the choice is Damage
- Signature: The site supervisor accepts the load
```

On the day, as people submit their forms, responses come in and are stored by the transport order.

### Trigger automations

You can also trigger Idalia AI to read each response and act on the information. It can perform safety and quality checks, send notifications, update your workspace data, and more.

Let's ask the Idalia AI to run a safety check each time the Transport Dispatch form is submitted.

```text wrap theme={null}
Create an automation that runs when the Transport Dispatch form is submitted.

It should review all of the images and ensure the plant is correctly loaded and secured for transport.

If anything looks off or potentially unsafe, notify me immediately.
```

See [Automations](https://useidalia.com/docs/workflows/automations.md) for more.

## Plan the transport order

First, well before the delivery, create a transport order with 2 loads. One for the excavator, one for the buckets and attachments. Set the **owner** to whoever's running the delivery, and set the order to **Planned** once the trucks are booked with expected arrival times for each load.

| Load | Assets | From | To | Arrive by |
| - | - | - | - | - |
| 1 | Excavator | Storage yard | Sydney site | 07:00 |
| 2 | Buckets and attachments | Storage yard | Sydney site | 07:30 |

For more about creating and planning transport orders, see [Transport](https://useidalia.com/docs/logistics/transport.md).

## Agree it with the people on site

The order is only the plan. The site still has to accept both trucks, and most of the people in that conversation never open Idalia. They confirm by phone or at the gate. The **owner** writes down what they confirm.

| Who | What they agree | What the owner records |
| - | - | - |
| Site supervisor | The gate can take the excavator at 07:00, and the buckets at 07:30 | **Arrive by** on each load |
| Yard supervisor | Both trucks can be loaded in time to meet those times | The order stays **Planned** |
| Driver | They have the yard, the site, and their load | The driver on that load |
| Project coordinator | The excavator is booked to the Sydney job for those dates | The allocation |

The second truck waits until the first is clear of the gate. That is why its **Arrive by** is 07:30, not 07:00.

On the day, the yard records the loading on **Transport dispatch**, and the site records the arrival on **Transport receipt**. The **owner** still sets the load status. Those forms were created once, in **Set up the custom forms**.

## Dispatch each truck

On the load, in Idalia or the mobile app, choose **Fill form**, then **Transport dispatch**. Do this while the load is **Loading**. Submit the form before the truck leaves. Then set the load to **In Transit**.

Do the excavator first, then the buckets and attachments.

1. A truck arrives at the yard to pick up its payload. Set that load to **Loading**.
2. Fill **Transport dispatch**. The checklist confirms the right plant is on this truck and that it is safely loaded. Add photos. The driver signs to accept the load.
3. The truck leaves the yard. Set the load to **In Transit**.

**In Transit** only means the truck has left. The excavator still shows the storage yard until that load is **Completed**.

## Receive each truck

When the truck is on site, choose **Fill form** on that load, then **Transport receipt**. The site supervisor signs it. Submit the form, then set the load to **Completed**.

1. Record whether the truck is on time or delayed. If it is delayed, write the reason.
2. Record whether the plant has damage. If it has damage, add photos. Damage does not stop the delivery. The receipt holds that record, and you still complete the load.
3. The site supervisor signs. Set the load to **Completed**.

**Completed** is the status that moves the plant on that load to the Sydney site. The form is the evidence. It does not move the plant.

## Close the delivery

When both loads are **Completed**, set the transport order to **Completed**.

The project coordinator then sets the allocation to **In Progress**. That starts the excavator's time on the job. Completing a load does not do that. It only records that the plant has arrived.

**Planned**, **In Progress**, and **Completed** are the default names. A workspace can use other words for the order and the allocation. The load statuses stay **Loading**, **In Transit**, and **Completed**.

## Check the two loads

Open the order. **Forms** shows four submitted responses: a dispatch and a receipt for each load. Both loads are **Completed**. The excavator, the buckets, and the attachments show the Sydney site. The allocation is **In Progress**.

**Transport dispatch** and **Transport receipt** are unchanged. The next transport order uses them again.

If the plant also has to move by sea or through a port, that is a different job. See [Mobilise and demobilise plant](https://useidalia.com/docs/guides/mobilise-and-demobilise-plant.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.