fleetbase · roncodes · Sep 3, 2026
diff --git a/content/docs/fleet-ops/connectivity/devices/overview.mdx b/content/docs/fleet-ops/connectivity/devices/overview.mdx
@@ -1,11 +1,11 @@
 ---
 title: Devices
-description: Manage GPS trackers, OBD-II scanners, dash cameras, and other IoT devices connected to your fleet vehicles.
+description: Manage GPS trackers, OBD-II scanners, dash cameras, and other IoT devices connected to Vehicles and Trailers.
 ---
 
 # Devices
 
-**Devices** are the physical hardware units connected to your fleet vehicles — GPS trackers, OBD-II scanners, dash cameras, and IoT sensors. While telematics modems are managed in the Telematics section (they bridge to a provider's cloud), Devices tracks the individual hardware installed in or on vehicles.
+**Devices** are physical hardware units connected to fleet assets — GPS trackers, OBD-II scanners, dash cameras, and IoT sensors. While telematics modems are managed in the Telematics section (they bridge to a provider's cloud), Devices tracks the individual hardware installed in or on Vehicles and Trailers.
 
 Navigate to **Fleet-Ops → Connectivity → Devices**.
 
@@ -57,17 +57,17 @@ Navigate to **Fleet-Ops → Connectivity → Devices**.
   </Step>
 </Steps>
 
-## Linking Devices to Vehicles
+## Linking Devices to Assets
 
-Devices are linked to vehicles through the vehicle record:
+Attach a device to the asset it physically measures. A Trailer tracker remains attached to that Trailer when its towing Vehicle changes.
 
-1. Open **Fleet-Ops → Resources → Vehicles → [Vehicle]**
+1. Open the target **Vehicle** or **Trailer** detail view
 2. Click the **Devices** tab
 3. Click **+ Add Device** and select from the devices list
 4. Set the **Mounting Location** (e.g., dashboard, cargo area, wheel well)
 5. Save
 
-A vehicle can have multiple devices — e.g., one GPS tracker, one OBD-II scanner, and one temperature sensor.
+An asset can have multiple devices. For example, a Vehicle might have GPS and OBD-II devices while its connected reefer Trailer has an independent tracker and temperature sensor.
 
 ## Device Events
 

diff --git a/content/docs/fleet-ops/connectivity/telematics/overview.mdx b/content/docs/fleet-ops/connectivity/telematics/overview.mdx
@@ -1,11 +1,11 @@
 ---
 title: Telematics
-description: Connect telematics providers to Fleet-Ops — enter API credentials, discover devices, link them to vehicles, and start receiving live telemetry data.
+description: Connect telematics providers to Fleet-Ops, map devices to Vehicles or Trailers, and receive live telemetry data.
 ---
 
 # Telematics
 
-**Telematics** devices are modems installed in vehicles that continuously transmit GPS position, engine diagnostics, and sensor data to a telematics provider's cloud platform. Fleet-Ops connects to supported providers via API to ingest this data in real time.
+**Telematics** devices are modems or asset trackers that transmit GPS position, diagnostics, and sensor data to a provider's cloud platform. Fleet-Ops connects to supported providers via API and maps each device to the Vehicle or Trailer it physically measures.
 
 Navigate to **Fleet-Ops → Connectivity → Telematics**.
 
@@ -58,10 +58,10 @@ Once the telematics integration is connected, Fleet-Ops can discover the devices
     Click **Discover Devices** — Fleet-Ops fetches the list of registered devices from the provider.
   </Step>
   <Step>
-    For each discovered device, click **Link to Vehicle** and select the vehicle it is installed in.
+    For each discovered device, choose **Attach to Asset**, select Vehicle or Trailer, and then select the asset where it is installed.
   </Step>
   <Step>
-    Save. Fleet-Ops now associates telemetry data from this device with the selected vehicle.
+    Save. Fleet-Ops now associates telemetry data from this device with the selected asset.
   </Step>
 </Steps>
 
@@ -82,10 +82,10 @@ Each telematics integration includes device records:
 
 ## Live Data Flow
 
-Once a device is linked to a vehicle:
+Once a device is linked to a Vehicle or Trailer:
 
 1. The provider sends position updates to Fleet-Ops (via webhook or API polling)
-2. Fleet-Ops stores the position as a `Position` record for the vehicle
+2. Fleet-Ops stores the position as a `Position` record for the attached asset
 3. The position is broadcast to the live map via SocketCluster
 4. OBD-II and sensor data is stored as `DeviceEvent` records
 5. Alerts (engine fault codes, geofence crossings) can trigger Issues or notifications

diff --git a/content/docs/fleet-ops/getting-started/core-concepts.mdx b/content/docs/fleet-ops/getting-started/core-concepts.mdx
@@ -85,6 +85,10 @@ A **Vehicle** is a fleet asset assigned to carry out orders. Vehicle records sto
 
 Vehicles can have connected devices (GPS trackers, OBD-II scanners, cameras, sensors) through the Connectivity module, and maintenance schedules tracked through the Maintenance module.
 
+## Trailers
+
+A **Trailer** is an independently managed towed asset. Dry vans, reefers, flatbeds, tankers, chassis, dollies, and similar units retain their own identity, specifications, equipment, maintenance, device, telemetry, and connection history. Tractor heads and prime movers remain Vehicles. Connecting or disconnecting a Trailer changes the effective-dated towing relationship; it does not transfer ownership of the Trailer's records to the Vehicle.
+
 ## Fleets
 
 A **Fleet** is a logical grouping of drivers and vehicles. Fleets help you organize resources by:

diff --git a/content/docs/fleet-ops/index.mdx b/content/docs/fleet-ops/index.mdx
@@ -5,7 +5,7 @@ description: Fleet-Ops is the flagship fleet and transport management extension
 
 # Fleet-Ops
 
-Fleet-Ops is the core logistics and fleet management extension for the Fleetbase platform. It gives operations teams a full dispatch console for managing orders, drivers, vehicles, and routes — plus a mobile driver app (Navigator) that handles real-time GPS tracking, turn-by-turn navigation, and proof of delivery capture.
+Fleet-Ops is the core logistics and fleet management extension for the Fleetbase platform. It gives operations teams a full dispatch console for managing orders, drivers, Vehicles, first-class Trailers, and routes — plus a mobile driver app (Navigator) that handles real-time GPS tracking, turn-by-turn navigation, and proof of delivery capture.
 
 ![Fleet-Ops multi-waypoint order showing optimized route across multiple stops with driver assignment and live status timeline](/images/screenshots/fleet-ops/fleet-ops-multi-waypoint-order.webp)
 
@@ -19,6 +19,7 @@ Fleet-Ops covers the full delivery and fleet operations lifecycle in one place:
 | **Live Map** | Real-time driver and vehicle positions with route overlays |
 | **Driver App (Navigator)** | Mobile app for drivers — navigation, status updates, POD capture |
 | **Fleet & Driver Management** | Organize drivers and vehicles into fleets, track availability and status |
+| **Trailer Management** | Manage towed assets, Vehicle connections, equipment, maintenance, devices, and telemetry |
 | **Orchestrator** | Multi-phase planner — stack vehicle allocation, driver allocation, and route optimization phases in sequence |
 | **Scheduler** | Driver shift scheduling and order timeline management |
 | **Order Configurations** | Custom order types with configurable workflows and entity fields |
@@ -34,6 +35,7 @@ Fleet-Ops is organized around a few core entities:
 - **Order** — a delivery or service task with a pickup location, a destination, and items (entities). Orders move through a configurable status lifecycle and are captured with proof of delivery.
 - **Driver** — a person who executes orders using the Navigator app. Drivers have real-time location, shift schedules, and skill constraints that the Orchestrator uses for assignment.
 - **Vehicle** — a fleet asset with capacity, location tracking, and maintenance history.
+- **Trailer** — an independently managed towed asset with effective-dated Vehicle connections, equipment, maintenance, and telematics.
 - **Fleet** — a logical group of drivers and vehicles, typically scoped to a route, region, or service type.
 - **Order Configuration** — a template that defines a custom order type: its activity flow, the entity fields required, and the proof of delivery method.
 

diff --git a/content/docs/fleet-ops/maintenance/equipment/overview.mdx b/content/docs/fleet-ops/maintenance/equipment/overview.mdx
@@ -1,21 +1,19 @@
 ---
 title: Equipment
-description: Track fleet equipment assets — tools, trailers, containers — with maintenance schedules, work orders, and warranty coverage.
+description: Track auxiliary equipment attached to Vehicles or Trailers, with maintenance schedules, work orders, and warranty coverage.
 ---
 
 # Equipment
 
-**Equipment** tracks fleet assets beyond vehicles — tools, trailers, containers, attachments, and other hardware that require their own maintenance schedules and work orders. Equipment records are linked to vehicles or drivers and participate in the same maintenance workflow as vehicles.
+**Equipment** tracks auxiliary tools, mounted components, and issued hardware that require their own maintenance schedules and work orders. Equipment can be linked to a Vehicle, Trailer, or Driver and participates in the same maintenance workflow as those resources. Towable units such as dry vans, reefers, flatbeds, tankers, and chassis are first-class [Trailers](/docs/fleet-ops/resources/trailers/overview), not Equipment.
 
 ![Equipment list — name, category, assigned vehicle, status, next maintenance date](/images/screenshots/fleet-ops/fleet-ops-equipment-list.webp)
 
 ## What Equipment Covers
 
 Equipment in Fleet-Ops includes:
 
-- **Trailers** — flatbed, refrigerated, curtainsider, tanker
-- **Containers** — shipping containers, ISO containers
-- **Attachments** — forklifts, tail lifts, cranes
+- **Attachments** — tail lifts, liftgates, cranes, pumps, and ramps
 - **Tools** — delivery trolleys, pallet jacks, scanners
 - **Powered equipment** — generators, refrigeration units
 
@@ -28,12 +26,12 @@ Anything that:
 
 | Field | Description |
 | :--- | :--- |
-| **Name** | Equipment identifier (e.g., "Trailer 003", "Pallet Jack 12") |
+| **Name** | Equipment identifier (e.g., "Pallet Jack 12") |
 | **Category** | Type of equipment |
 | **Description** | Detailed description |
 | **Serial Number** | Manufacturer serial number |
 | **Status** | active, inactive, maintenance, retired |
-| **Assigned Vehicle** | Vehicle this equipment is currently assigned to |
+| **Attached Resource** | Vehicle, Trailer, or Driver this equipment is currently attached or issued to |
 
 ## Creating Equipment
 
@@ -51,7 +49,7 @@ Anything that:
     Set the **Serial Number** for identification.
   </Step>
   <Step>
-    Assign to a **Vehicle** if this equipment is currently attached.
+    Assign to a **Vehicle**, **Trailer**, or **Driver** if this equipment is currently attached or issued.
   </Step>
   <Step>
     Click **Save**.

diff --git a/content/docs/fleet-ops/meta.json b/content/docs/fleet-ops/meta.json
@@ -21,6 +21,7 @@
     "resources/overview",
     "resources/drivers",
     "resources/vehicles",
+    "resources/trailers",
     "resources/fleets",
     "resources/vendors",
     "resources/contacts",

diff --git a/content/docs/fleet-ops/resources/overview.mdx b/content/docs/fleet-ops/resources/overview.mdx
@@ -13,6 +13,7 @@ The **Resources** section of Fleet-Ops is where you manage the assets and entiti
 | :--- | :--- |
 | [**Drivers**](/docs/fleet-ops/resources/drivers/overview) | People who execute orders using the Navigator app |
 | [**Vehicles**](/docs/fleet-ops/resources/vehicles/overview) | Fleet assets assigned to carry out deliveries |
+| [**Trailers**](/docs/fleet-ops/resources/trailers/overview) | Independently managed towed assets with connections, maintenance, and telematics |
 | [**Fleets**](/docs/fleet-ops/resources/fleets/overview) | Logical groupings of drivers and vehicles |
 | [**Vendors**](/docs/fleet-ops/resources/vendors/overview) | Third-party carriers and integrated service partners |
 | [**Contacts**](/docs/fleet-ops/resources/contacts/overview) | Customers, suppliers, and facilitators |

diff --git a/content/docs/fleet-ops/resources/trailers/connections-and-equipment.mdx b/content/docs/fleet-ops/resources/trailers/connections-and-equipment.mdx
@@ -0,0 +1,41 @@
+---
+title: Connections and equipment
+description: Connect trailers to vehicles, preserve towing history, and manage equipment attached to vehicles or trailers.
+---
+
+# Trailer connections and equipment
+
+Fleet-Ops treats a towing relationship as an effective-dated **connection**, not as a permanent field on either asset. Each connection records the Vehicle, Trailer, towing position, start time, optional end time, source, notes, and audit data.
+
+## Connection rules
+
+- A Trailer can have only one active Vehicle connection at a time.
+- A towing position on a Vehicle can contain only one active Trailer.
+- Repeating the same attach or detach request is safe and does not create duplicate active connections.
+- Moving a Trailer to another Vehicle requires detaching the current connection first.
+- Detaching closes the active record; it does not erase it.
+- Tenant boundaries are enforced for both assets.
+
+These rules also allow multi-trailer combinations: connect each Trailer to the same Vehicle with a distinct towing position.
+
+## From a Vehicle
+
+Open a Vehicle and choose **Trailers** to see its active Trailer connections. Use **Attach Trailer** to select an unattached Trailer, or **Detach** to end a connection. The Vehicle's **Equipment** tab separately lists auxiliary equipment assigned directly to that Vehicle.
+
+## From a Trailer
+
+Open a Trailer and use:
+
+- **Connection history** to review current and completed towing relationships;
+- **Equipment** to attach, open, or detach auxiliary equipment;
+- **Devices** to review trackers and sensors attached directly to the Trailer.
+
+## Equipment assignment
+
+Equipment has a polymorphic assignment. It can be attached directly to a Vehicle or Trailer and reassigned atomically. Examples include a liftgate fixed to a Trailer, a pallet jack carried on a Vehicle, or a refrigeration unit mounted on a reefer.
+
+The Equipment create and edit forms let you choose the asset type and asset. The public API also exposes explicit attach and detach operations. Assignment responses include the asset type, public ID, and display name; private UUIDs are not accepted by public endpoints.
+
+## Operational guidance
+
+Record the physical relationship that exists in the yard or on the road. Equipment mounted on a Trailer should remain attached to that Trailer when the Trailer moves between Vehicles. Only attach it to the Vehicle when the equipment belongs operationally to the powered unit.
diff --git a/content/docs/fleet-ops/resources/trailers/meta.json b/content/docs/fleet-ops/resources/trailers/meta.json
@@ -0,0 +1,4 @@
+{
+  "title": "Trailers",
+  "pages": ["overview", "connections-and-equipment", "telematics"]
+}
diff --git a/content/docs/fleet-ops/resources/trailers/overview.mdx b/content/docs/fleet-ops/resources/trailers/overview.mdx
@@ -0,0 +1,51 @@
+---
+title: Trailers
+description: Register and operate trailers as first-class towed fleet assets with connections, equipment, maintenance, and telematics.
+---
+
+# Trailers
+
+Fleet-Ops models a **Trailer** as a first-class fleet resource. A trailer has its own identity, lifecycle, dimensions, maintenance history, equipment, devices, and location even though it cannot move under its own power. This keeps semitrailers, flatbeds, tankers, chassis, reefers, dollies, and other towed assets separate from both powered **Vehicles** and auxiliary **Equipment**.
+
+Choose **Resources → Trailers**, directly below Vehicles, to create and manage trailers.
+
+## When to use each resource
+
+| Resource | Use it for | Examples |
+| :--- | :--- | :--- |
+| **Vehicle** | A powered road unit that can perform transport work | tractor head, truck, van |
+| **Trailer** | A towable asset with an independent identity and operational lifecycle | dry van, reefer, flatbed, tanker, chassis |
+| **Equipment** | Auxiliary gear that can be mounted, carried, or reassigned | liftgate, pallet jack, refrigeration unit, tool kit |
+
+Do not create a tractor head as a Trailer. A head or tractor is a Vehicle, and its current towing relationship points to one or more Trailer records.
+
+## Trailer data
+
+Trailer records support:
+
+- identity and registration: name, code, VIN, plate and serial number;
+- classification: dry van, reefer, flatbed, step deck, lowboy, tanker, bulk, dump, chassis, curtain side, car carrier, livestock, logging, dolly, specialty, or other;
+- physical specifications: length, width, height, tare, gross vehicle weight rating, payload, volume, axles, tires, doors, brakes, ABS/EBS, and coupling;
+- reefer details: temperature range and engine hours;
+- ownership, acquisition, lease, valuation, vendor, warranty, photo, notes, and custom fields;
+- current vehicle connection and complete connection history;
+- attached devices and equipment;
+- location, connectivity, maintenance schedules, work orders, and maintenance history.
+
+## Lifecycle
+
+1. Create or import the Trailer.
+2. Attach equipment and a telematics device when applicable.
+3. Connect the Trailer to a Vehicle when a towing movement starts.
+4. Track it directly through its device or the Trailer tracking API.
+5. Detach it when the movement ends. Fleet-Ops preserves the completed connection in history.
+6. Schedule inspections and maintenance against the Trailer itself.
+
+A Trailer cannot be deleted while it has an active vehicle connection. Detach it first so the operational history remains accurate.
+
+## Related pages
+
+- [Connections and equipment](/docs/fleet-ops/resources/trailers/connections-and-equipment)
+- [Trailer telematics](/docs/fleet-ops/resources/trailers/telematics)
+- [Vehicles](/docs/fleet-ops/resources/vehicles/overview)
+- [Maintenance](/docs/fleet-ops/maintenance/overview)
diff --git a/content/docs/fleet-ops/resources/trailers/telematics.mdx b/content/docs/fleet-ops/resources/trailers/telematics.mdx
@@ -0,0 +1,28 @@
+---
+title: Trailer telematics
+description: Attach IoT devices to trailers and ingest current and historical telemetry independently of the towing vehicle.
+---
+
+# Trailer telematics
+
+A Trailer can have one or more directly attached Devices. This is useful for battery-powered GPS trackers, reefer controllers, door and cargo sensors, tire-pressure systems, and other IoT hardware that continues reporting when the Trailer is detached from a Vehicle.
+
+## Attach a device
+
+From a Trailer, choose **Attach Device** and select an unattached device. From Connectivity, the same device attachment workspace can target either a Vehicle or a Trailer. Reassigning a device closes its previous installation record and creates a new one; detaching preserves that history.
+
+## Ingested state
+
+Location events from an attached device update the Trailer's current projection and position history, including available speed, heading, altitude, odometer, reefer engine hours, online state, provider, and observation time. Older out-of-order events remain in event history but do not overwrite a newer current position.
+
+Trailer updates broadcast `trailer.location_changed` on company, public Trailer ID, and internal Trailer channels. Public tracking endpoints use Trailer public IDs and reject private UUID fields.
+
+## Direct API tracking
+
+Use the Trailer tracking endpoint when the source does not arrive through a configured telematics provider. Supply latitude and longitude plus an optional observation time and motion values. Fleet-Ops stores a historical position and updates the Trailer snapshot only when the observation is not stale.
+
+## Vehicle versus Trailer telemetry
+
+Attach each device to the asset it physically measures. A tracker installed on a Trailer belongs to the Trailer even while it is being towed. The current connection tells you which Vehicle is moving it; it should not be used to rewrite device ownership or duplicate positions onto the Vehicle.
+
+See [Devices](/docs/fleet-ops/connectivity/devices/overview) and [Telematics](/docs/fleet-ops/connectivity/telematics/overview) for provider setup and event ingestion.