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

# Plant-to-Plant Hauls

> Cement, RAP, and other plant-feed flows where the customer and the supplier are both in your network.

## When to use this

Use plant-to-plant when both ends of the haul are companies on Tread. Common with cement, RAP (reclaimed asphalt pavement), and other plant-feed materials — an upstream plant supplies an aggregate, you haul, and a downstream plant receives. Both plants are your customers, your vendors, or both.

## How it works

Plant-to-plant runs through the [Connected Ecosystem](/concepts/connected-ecosystem) — the Customer, Tread Customer, Vendor, and Driver connect. The downstream plant is a [Connected Customer](/concepts/connected-ecosystem) — they place orders. The upstream plant is also a Connected Customer or Vendor — they confirm the load left their site.

Because both ends are on Tread, the dispatcher doesn't chase paper. The upstream scale ticket and the downstream receiving ticket both flow to the same load. You bill the downstream plant for the haul and pay the upstream plant for the material.

The dispatcher coordinates the handoff between the upstream load-out window and the downstream receiving window.

## Setup

<Steps>
  <Step title="Connect both plants">
    Each plant must be a [Connected Customer](/concepts/connected-ecosystem) or Connected Vendor on your account. Send a connection invite from Settings → Customers or Settings → Vendors.
  </Step>

  <Step title="Create the order">
    Set the upstream plant as the **pickup site** and the downstream plant as the **delivery site**. Pick the right material for the load. See [Create Project, Order & Dispatch](/workflows/create-a-project).
  </Step>

  <Step title="Coordinate the handoff">
    Confirm the upstream plant's load-out window and the downstream plant's receiving hours. Mismatched windows are the most common cause of trucks waiting at gates.
  </Step>
</Steps>

## Common pitfalls

<Warning>
  **Treating one plant as Connected and the other as a manual entry.** If only one end is on Tread, you lose half the automatic ticket flow. Connect both plants before running the haul.
</Warning>

<Warning>
  **Skipping the handoff window check.** Plants run on tight schedules. A truck arriving thirty minutes after the receiving window closes wastes hours. Confirm both windows on the order.
</Warning>

## Related

* [Connected Ecosystem](/concepts/connected-ecosystem) — the stakeholders that connect to power plant-to-plant
* [Create Project, Order & Dispatch](/workflows/create-a-project) — order setup
* [Sites & Geofences](/concepts/sites-geofences) — geofences at each plant
* [Materials](/concepts/materials) — flagging plant-feed materials