> ## Documentation Index > Fetch the complete documentation index at: https://docs.tryoto.com/llms.txt > Use this file to discover all available pages before exploring further. # Driver and fleet management > Register your drivers, set their areas, capacity, teams and shifts, track them live, settle the cash they collect, and review their performance. > [!NOTE] > > **Where to find it:** OTO FLEX → Configuration — [Open in OTO ↗](https://app.tryoto.com/drivers-page) Everything the assignment engine needs to know about your drivers: who they are, where they work, what they can carry, when they are on shift, and how much of your money they are holding. ## The driver register **OTO FLEX → Configuration → Drivers** lists the fleet. **Add Driver** registers one; **Driver Upload** imports a batch from a spreadsheet, which is how a fleet of any size gets set up. **Map View** shows where everyone is right now, and **OTO Flex App** is the download link to hand a new driver. ![The OTO FLEX Drivers list](https://mintcdn.com/oto/ft-bRlLvOnJkbVoC/images/flex-1-drivers.png?fit=max\&auto=format\&n=ft-bRlLvOnJkbVoC\&q=85\&s=03f0c6a843fd2d1e04955ec84bae12b8) Fig. 1 — Three drivers, all Active but none On Duty — which is exactly the state in which an operator reports that “assignment is broken”. | Column | What it tells you | | - | - | | **Driver ID · User ID** | The fleet identifier, and the platform login behind it. | | **Driver Name · Email · Phone** | Identity and contact. The mobile number is also the app login. | | **Vehicle Type** | Motorcycle, car, van — which is what makes a heavy or bulky order infeasible for some of the fleet. | | **Capacity** | How many orders this driver can hold at once. The planner will not exceed it. | | **Balance** | Cash collected on COD deliveries and not yet settled. Filterable by range, because the question is usually *who is holding more than they should*. | | **Status** | Whether the driver record is active. | | **On Duty** | Whether they are on shift right now — a separate column, and a separate idea. | | **Active Orders** | What they are carrying at this moment, against their capacity. | > [!TIP] > > **Status and On Duty are not the same thing** > > Status is an employment fact; On Duty is a shift fact. An Active driver who is off duty receives nothing. Dispatch problems that look like “the rules are broken” are often a fleet where everyone is Active and nobody is On Duty — and the two columns sit side by side precisely so you can see it. ### Registering a driver **Add Driver** takes rather more than a name and a phone number, and each field earns its place in the assignment engine: ![The Add Driver form](https://mintcdn.com/oto/YkJay8Y-1RDv8ciw/images/flex-2-add-driver.png?fit=max\&auto=format\&n=YkJay8Y-1RDv8ciw\&q=85\&s=96bcec9e2361e14d6ec0bdd6fb1bc847) Fig. 2 — Name, Email and Assigned Warehouses are required; branches are optional, which tells you the warehouse is the anchor. | Field | Why it matters | | - | - | | **Name · Email** | Required. The email is the account. | | **Mobile Number** | With a country selector. This is what the driver logs into the app with. | | **Assigned Warehouses** | Required — where this driver collects from. A driver with no warehouse has nothing to pick up. | | **Assigned Branches** | Optional, for a fleet that also collects from stores. | | **Capacity** | Concurrent orders. The planner respects it when building routes. | | **Shipment Target** | A per-driver delivery target — the number performance is measured against. | | **Vehicle Type** | Feeds vehicle-type feasibility, so bulky orders stay away from the wrong part of the fleet. | | **Image** | A photo. Customers following a live delivery see a person, not an initial. | > [!TIP] > > **Shipment Target is the incentive hook** > > A target set per driver is what turns “driver performance” from an impression into a number. It is the difference between an incentive scheme you can defend in a conversation with a driver and one you cannot. ## Unlimited drivers There is no cap on the number of drivers a fleet can hold, which matters for two cases the platform is explicitly built for: seasonal peaks, where a fleet doubles for a month, and gig models, where the roster turns over continuously. ## Areas, capacity and priority A driver is tied to geography through **Areas**, at **Settings → Advanced → Areas**. The **Area Form** has two tabs — **Area Info** and **Location** — and three of its fields belong to this module. ![Assigning drivers to an area](https://mintcdn.com/oto/ft-bRlLvOnJkbVoC/images/flex-3-area-drivers.png?fit=max\&auto=format\&n=ft-bRlLvOnJkbVoC\&q=85\&s=19ffa3a30c6d9e92672ea7926e2cf6ed) Fig. 3 — The driver picker is a multi-select with a search box and an Add New Driver User link — a driver can be created without leaving the area you are defining. | Field | What it does | | - | - | | **OTO Flex Drivers** | Which drivers serve this area. Multi-select, searchable, with **Add New Driver User** inline. | | **Capacity** | Shipments per driver per day within the area, in **pcs** — a ceiling on what the area can absorb, separate from the per-driver order capacity. | | **Priority** | Resolves overlapping polygons. Two areas covering the same street is normal; priority decides which one wins. | The **Location** tab is where the polygon itself is drawn on a map, or pasted in as coordinate pairs. Because areas are also used by [delivery-area tagging](https://docs.tryoto.com/modules/omnichannel-oms/prefulfillment.md) and by [shipping automation](https://docs.tryoto.com/modules/shipping-management/shipping-automation.md)’s *If destination is in these Areas* condition, one polygon can serve the fleet and the rules at once — draw it once, use it everywhere. > [!NOTE] > > **Three capacities, three questions** > > They stack, and they answer different questions. **Driver capacity**: how many orders can this person hold at once? **Area capacity**: how many can this geography absorb in a day? **Slot capacity**: how many can this time window take? A delivery can be blocked by any one of them. ## Driver teams Drivers can be grouped into teams and the team used as the unit of assignment, rather than naming individuals in every rule. A team survives people joining and leaving; a rule listing five drivers by name does not. ## Shifts and working hours Shifts determine when a driver is available, and pair with the delivery slots configured in [Order fulfillment](https://docs.tryoto.com/modules/omnichannel-oms/order-fulfillment.md): a slot the fleet is meant to serve needs someone on shift to serve it. The **On Duty** column on the driver list is the live expression of this. ## Live tracking **Map View** shows the fleet in real time, and tracking continues **when the app is closed** using background location. That is the difference between knowing where the fleet is and knowing where the fleet last opened the app. > [!NOTE] > > **Tell your drivers** > > Background location tracking is a privacy matter and, in several markets, a disclosure requirement. It should be in the driver’s contract and set up in the app’s permissions when they are onboarded, not discovered later. ## Vehicle capacity Capacity is defined per vehicle, and the planner respects it when building routes — a motorcycle is not given a route it cannot physically carry. Combined with **Vehicle Type** as a feasibility condition, this is how bulky orders are kept away from the wrong part of the fleet. ## Cash settlement Each driver carries a **Balance**: COD cash collected and not yet handed in. Settling reduces it. Read as a column across the fleet, it is a live picture of how much of your revenue is currently in vehicles rather than in a bank. > [!TIP] > > **The number to watch** > > A balance that climbs steadily for one driver while others stay flat is usually a settlement process nobody is enforcing, not a collection problem. The Min/Max filter on that column exists for exactly this check. ## Custom fleet naming The **Fleet Name**, set in fleet settings, is what the customer sees instead of a carrier name — on the tracking page and in notifications. A merchant delivering with their own riders can present it as their own service rather than as a third party, which for many brands is the reason they run a fleet at all. ## Performance and incentives Driver performance is measured over the same dimensions the platform uses for carriers — completion, timeliness, customer rating — against each driver’s **Shipment Target**. That combination is what makes an incentive scheme possible to run on evidence rather than impression. ## Route history Completed routes are retained, so a delivery can be reconstructed after the fact: where the driver went, in what order, and when. This is the answer to a customer disputing a delivery and to a driver disputing a route. ## Related * [Planning](https://docs.tryoto.com/modules/oto-flex/planning.md) — what the platform does with everything configured here. * [Shipping automation](https://docs.tryoto.com/modules/shipping-management/shipping-automation.md) — where the fleet wins or loses an order against a carrier. * Billing, Payments & COD — where driver-collected cash ends up. ## Related topics - [Delivery planning and driver assignment](https://docs.tryoto.com/modules/oto-flex/planning.md) - [OTO FLEX: delivery with your own drivers](https://docs.tryoto.com/modules/oto-flex/overview.md) - [Plans, pricing and add-ons](https://docs.tryoto.com/pricing/plans-and-packaging.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.