> ## 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.

# Dispatching to Drivers and Vendors

> The three ways to send a dispatch — an internal driver, a shared driver, or a vendor.

## What it is

* **Internal Driver User** — your own driver, in your company.
* **Driver** - an owner operator driver who has their own entity
* **Shared Driver** — a driver another company shares to you, so you assign them like your own.
* **Vendor** — a hauling company you dispatch to. Their dispatcher assigns the driver.

Each routes through a different link in the [Connected Ecosystem](/concepts/connected-ecosystem) — your own company, a vendor who shares a driver, or an owner operator.

## Why it matters

The driver configuration primarily determines who is responsible for assigning a driver to a dispatch.

## How Tread models it

| Assign to                | Who it is                               | In the Assign panel | Billing path                                               | When to use                                                          | Setup required                         |
| ------------------------ | --------------------------------------- | ------------------- | ---------------------------------------------------------- | -------------------------------------------------------------------- | -------------------------------------- |
| **Internal User Driver** | Your own driver                         | **Driver** tab      | Customer pays you, <br />you pay your driver               | Your own drivers and trucks                                          | Internal User added under your company |
| **Driver**               | Owner Operator / Driver with own Entity | **Driver** tab      | Customer pays you, <br />you pay the Owner Operator Entity | An owner operator who contracts with you through their own entity    | Driver added under your company        |
| **Shared Driver**        | A driver a partner shares to you        | **Driver** tab      | Customer pays you, <br />you pay the partner               | A partner whose specific driver you assign yourself                  | Partner shares the driver to you       |
| **Vendor**               | A hauling company that sub-dispatches   | **Vendor** tab      | Customer pays you, <br />you pay the vendor                | You hired a hauling company and let their dispatcher pick the driver | Vendor invited and connected           |

An Owner-Operator (O\&O) — a single-truck hauler who owns and drives — is the most common Shared Driver. For a Vendor, the driver's name appears on your board only after their dispatcher accepts and assigns one.

## Common pitfalls

<Warning>
  **Vendor jobs need an active connection.** If the vendor has not accepted the connection, your dispatch will not send. Check **Settings → Vendors** first.
</Warning>

<Warning>
  **A Shared Driver must be shared to you first.** Without the share, the driver does not appear in your Assign list. The partner shares from their side under **Settings → Drivers**.
</Warning>

## Related

* [Connected Ecosystem](/concepts/connected-ecosystem) — the Customer → Primary Co → Vendor → Driver chain
* [Driver Lifecycle](/concepts/driver-lifecycle) — invite, vendor moves, deactivation
* [Create a Project, Order & Dispatch](/workflows/create-a-project) — where you assign the job
* [Roles & Permissions](/concepts/roles-permissions) — who can dispatch