# Solo / Team / Combined Setup

## Solo / Team / Combined Setup

This page defines how your company's **fleet setup** determines whether a unit requires a solo driver, a team (driver + co-driver), or allows for either.

This configuration is set when assigning a **driver to a truck unit** and controls how driver assignment behaves in the Dispatch Board.

***

### Fleet Assignment Types

When setting up a unit with a driver, you must choose one of the following fleet modes:

| Mode         | Description                                                                  |
| ------------ | ---------------------------------------------------------------------------- |
| **Solo**     | Only one driver can be assigned to the unit. No co-driver field will appear. |
| **Team**     | Both a driver and co-driver are always required for dispatch.                |
| **Combined** | One driver is required; co-driver is optional. Two fields will be visible.   |

> 💡 This selection controls what driver fields are shown on the Dispatch Board and how validation behaves during dispatch.

<figure><img src="/files/1anjVz91JTwll6RiL4fk" alt=""><figcaption><p><em>Figure 1: Selecting Solo, Team, or Combined during unit setup.</em></p></figcaption></figure>

***

### Required Fields

* A **fleet type** must be selected for each unit during setup.
* In **Team** mode: Both driver and co-driver are required before dispatch.
* In **Solo** mode: Only one driver can be assigned.
* In **Combined** mode: One driver is required, co-driver is optional.

> ⚠️ If a required driver or co-driver is missing based on the selected mode, the load cannot be dispatched.

***

### Behavior in the UI

* On the **Dispatch Board**, the number of driver fields shown is based on the unit’s fleet type:
  * Solo → 1 driver field
  * Team → 2 required fields
  * Combined → 1 required + 1 optional
* The system enforces required assignments during load dispatch.
* Load cards reflect the configured mode with tags (Solo, Team, Combined).

***

### Example Scenarios

#### Solo Unit

* Unit is assigned to Driver A only
* Dispatch board shows only one driver field

<figure><img src="/files/e8ldtnZSQWKR7cYDOsrT" alt=""><figcaption><p><em>Figure 2: Solo load assigned to one driver.</em></p></figcaption></figure>

***

#### Team Unit

* Unit setup requires two drivers: Driver A and Driver B
* Both must be assigned before dispatch

<figure><img src="/files/iv65VDPqLIMqdKW8GzCk" alt=""><figcaption><p><em>Figure 3: Team load with both driver and co-driver assigned.</em></p></figcaption></figure>

***

#### Combined Unit

* Unit allows assignment of either one driver or both a driver and co-driver
* Dispatch has flexibility depending on operational needs

<figure><img src="/files/aDrgYgVc5pfZbCqxt4K6" alt=""><figcaption><p><em>Figure 4: Combined load showing optional co-driver.</em></p></figcaption></figure>

***

### Notes

* This configuration is part of **unit setup**, not payroll.
* The number of required driver fields on the Dispatch Board is directly tied to this setting.
* Only Admins or users with unit edit permissions can change fleet type.

> ✅ Use Combined mode for operational flexibility when loads may vary between solo and team assignments.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rute.gitbook.io/carrier/company/settings/payroll-setup/solo-team-combined-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
