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

# Phase Codes

> Tag Jobs, Loads, and hours with your customer's cost codes so your reports match their cost coding.

Track hauled work against the cost codes your customer already uses.

## What it is

A Phase is a Name and a Code you attach to work — your customer's cost code, bid item, or task number. Phases are optional. An [Order](/concepts/orders-projects) with no phases works normally.

## How Tread models it

* **Phase** — a Name and a Code. Defined on the Project, then copied to every Order under it.
* **Setup** — on the Project, click **View / Bulk Add Phases**. Add phases one at a time, or paste two spreadsheet columns: Name first, then Code.
* **Primary Phase** — one phase per Order is Primary. New [Jobs and Loads](/concepts/orders-projects) start with it.
* **Per Job and per Load** — change the phase on a single Job or Load. One truck-day can carry more than one code.
* **In the driver app** — drivers pick a phase when they edit a load. Foremen must pick one whenever the Order has phases. With only one phase, Tread fills it in for them.
* **On hours** — if your account tracks hours by phase, split a shift's hours across phases when you approve driver time.
* **Downstream** — the code follows the Load onto its [Ticket](/concepts/tickets-timesheets), then into exports and [OmniReports](/concepts/omni-reports).
* **Permissions** — changing the phase on a Job or a Load is permission-controlled. See [Roles & Permissions](/concepts/roles-permissions).

<img src="https://mintcdn.com/treadtechnologiesinc/JVbImJ5byyHI1bcD/images/Project---Setup-Phase-Codes.png?fit=max&auto=format&n=JVbImJ5byyHI1bcD&q=85&s=36ea047c48647fdb05802c6312b2ce58" alt="Project setup showing the bulk add phases panel with name and code columns" width="827" height="468" data-path="images/Project---Setup-Phase-Codes.png" />

## Common pitfalls

<Warning>
  **Renames and deletes stop at the Project.** Adding a phase to a Project pushes it down to that Project's existing Orders. Renaming or deleting one does not. Live Orders keep the old phase, so fix those by hand.
</Warning>

<Warning>
  **Codes match as exact text.** `1` and `1.0` count as two different phases. Copy the customer's schedule of values character for character.
</Warning>

<Note>
  Phase codes tag work for reporting and cost coding. [Settlements](/concepts/settlements-driver-pay) do not split by phase code.
</Note>

## Related

* [Orders & Projects](/concepts/orders-projects) — where phases are defined
* [Create a Project](/workflows/create-a-project) — project setup, step by step
* [Foreman](/workflows/foreman) — the foreman workflow
* [Exports & Reports](/workflows/exports-reports) — pulling phase codes out of Tread
* [Importer APIs](/api-reference/importer-apis) — syncing phases from another system