Reference · built on requestOperator by FibricFleet, routes & field

Unassigned Driving

Lists driving segments recorded with no driver logged in and proposes the driver to assign, from dispatch, roster, and vehicle records.

Request accessPricing ↗

About

Unassigned Driving is an operator job for the segments an ELD records while nobody is logged in. It reads those segments from your telematics platform each day, then looks at who was dispatched to that vehicle, who was on the roster at that hour, and which driver the vehicle record names. Where those agree, it names a candidate.

The candidate goes to the safety or compliance manager with the evidence side by side: the segment's start, end, and distance, the dispatch, the shift, and the assignment. The manager approves the assignment, picks another driver, or leaves the segment unassigned. For drivers who must claim their own time in the driver app, the proposal is a message to the driver instead of an edit.

This is a reference listing. It documents what Fibric would read from Unassigned Driving and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Motive driving periods from GET /v1/driving_periods filtered by assigned_to_driver and annotation_status, where source 3 marks a period assumed from the unidentified driver profile
  • Geotab Trip records whose driver is UnknownDriver, DriverChange records with their DriverChangeType, and DutyStatusLog entries with eventType 5 for login and logout activity
  • Samsara alert configurations with the Unassigned Driving trigger type and their AlertIncident subscriptions, plus HOS sign-in and sign-out logs per driver
  • Verizon Connect Reveal Unassigned Miles and Unassigned Vehicles alert webhook messages, keyed by Vehicle Number
  • Dispatch records for the vehicle and hour: Motive dispatches with driver and vehicle, Samsara routes assigned to a driverId or vehicleId, Route4Me route members
  • Rosters for the same hour: Deputy Roster records by date and employee, When I Work shifts from GET /2/shifts by user, start, and end
  • Vehicle assignments: the static assigned driver on Samsara GET /fleet/vehicles, and Fleetio GET /vehicles/{id}/current_assignment

Proposed actions

  • Target capability: propose assigning a Motive driving period through PUT /v1/driving_periods/{id} with driver_id and notes
  • Target capability: propose a Geotab DriverChange through Add, with device, driver, a dateTime not in the future, and type TripDriver for a single trip
  • Target capability: propose a message asking the named driver to claim the segment, through Samsara POST /v1/fleet/messages, Motive POST v1/messages, or a Twilio SMS
  • Target capability: propose a daily list per vehicle of unassigned segments with the candidate and evidence for each, in Slack or Microsoft Teams

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Assign Motive periods from Deputy rosters

    Driving periods with assigned_to_driver false are matched to Deputy Roster records for the vehicle's depot and hour. Where one employee was rostered, the operator proposes PUT /v1/driving_periods/{id} with driver_id and notes naming the shift.

    With Motive, Deputy

  • Explain Geotab UnknownDriver trips from When I Work shifts

    Trip records with driver UnknownDriver are set beside When I Work shifts for the same hours. The operator proposes a DriverChange of type TripDriver for the matching user, for the manager to approve in Slack.

    With Geotab, When I Work, Slack

  • Ask a Samsara driver to claim a segment

    An AlertIncident from the Unassigned Driving trigger is paired with the route assigned to that vehicle for the day. The operator proposes a message through POST /v1/fleet/messages asking the route's driver to claim the time in the Driver App.

    With Samsara, Microsoft Teams

  • Follow Verizon Connect Reveal Unassigned Miles

    Unassigned Miles alert messages name the Vehicle Number. Fleetio's current_assignment for that vehicle gives the candidate, and the operator lists the segment with that candidate in Slack for the manager to record in Reveal.

    With Verizon Connect Reveal, Fleetio, Slack

Requirements

  • An ELD or telematics connector that exposes unidentified driving: Motive, Geotab, Samsara, or Verizon Connect Reveal
  • At least one record of who should have been driving: a dispatch or route source, a roster connector, or the vehicle's assigned driver
  • A matching rule: how many of dispatch, roster, and vehicle assignment must agree before a candidate is named
  • Slack or Microsoft Teams, where the safety or compliance manager approves each item
Authentication
Holds no credentials. Driving segments, dispatches, and rosters are read, and assignments proposed, through the connectors you bind, under the access each carries.

Limits

  • Motive's assignment endpoint accepts only exempt drivers; assigning a logbook or HOS driver returns a 400 error, so for them the proposal is a message
  • For Samsara this listing reads unassigned driving as an alert trigger and its incidents, not as a segment list
  • A Geotab DriverChange added through the API cannot carry a future dateTime, and a system ResetDriver to UnknownDriver is shown, not reversed
  • The candidate is an inference from records. A segment with no dispatch, no shift, and no assignment stays unassigned with that finding

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Unassigned Driving ↗

Questions and answers

What does the manager approve?
One item per segment: the vehicle, start, end, distance, the candidate driver, and the records that pointed to them. The manager approves the assignment, chooses a different driver, or marks the segment as staying unassigned. For HOS drivers the item is a message, not an edit.
What record does it leave?
Per segment: the driving record read, the dispatch, roster, and assignment records compared, the rule applied, the candidate, the manager's decision and time, and the write as the ELD platform accepted it, with the notes sent.
Does it edit hours-of-service logs on its own?
No. Nothing is written until a manager approves it, and an approved assignment is written once. It never edits duty status, certifies a log, or assigns time to a driver who must claim it themselves; those drivers get a message.
Ask about Unassigned Driving

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy