# Division Company

Division Company allows you to define subdivisions within your organization under a single Carrier account. Divisions are used to group loads, assign drivers, and organize reports without creating a separate company profile.

***

### When to Use Divisions

* To split operations across internal teams, terminals, or geographic areas
* To assign loads and assets to different billing/reporting groups
* To control visibility in reporting, payroll, and driver assignment

> 💡 Use divisions when you operate as a single legal entity with multiple internal business units.

***

### Required Fields

<table><thead><tr><th width="200">Field</th><th width="90" align="center">Required</th><th>Description</th></tr></thead><tbody><tr><td>Division Name</td><td align="center">✅</td><td>Display name used in filters and records</td></tr><tr><td>Code</td><td align="center">✅</td><td>Unique short identifier (e.g. WEST, ATL)</td></tr><tr><td>Location</td><td align="center">Optional</td><td>Associated terminal or city (for context)</td></tr><tr><td>Notes</td><td align="center">Optional</td><td>Internal reference only</td></tr></tbody></table>

***

### Behavior in the UI

* Division appears in filters across:
  * Load List
  * Payroll
  * Dispatch Board
  * Reporting Views
* Drivers, assets, and loads can be assigned to a specific division
* Divisions do not affect billing, company-wide settings, or permissions

***

**Insert image showing Division selector or list view in Load/Dispatch screen(../assets/division-company-selector.png)**\
\&#xNAN;*Figure: Division selector visible during load creation and filtering.*

***

### Notes

* You can edit or delete divisions at any time
* Each driver, truck, trailer, and load can belong to only **one** division at a time
* If no division is selected, the record defaults to your global company scope

> ✅ Tip: Use consistent naming (e.g. WEST, MIDWEST, NE) to simplify reporting across teams and units.


---

# 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/division-company.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.