The setting
provides software and hardware for managing physical operations, mainly fleets of commercial vehicles. Its combines devices, cameras, and software so safety, operations, and finance teams can manage drivers, vehicles, equipment, and fleet spend in one system.
Job-level visibility competes with certainty about where idling belongs.
The pricing review needs useful coverage, while overlapping dispatch assignments limit what vehicle telemetry proves.
Who you’d be doing this for
“Yesterday finance asked which contract caused the idling, and I had to divide it across every job again.”
Pooja Joshi · Fleet Manager · a character in this brief
Oversees the 60 pilot vehicles and brings operating-cost evidence to the customer's contract-pricing review.
What is at stake
A fleet cannot tell which jobs account for idling across 60 vehicles. You must weigh useful coverage against defensible attribution before its pricing review.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- job coverage vs attribution certainty
- customer-specific rules vs reusable integration
- pricing urgency vs honest cost interpretation
- richer matching vs weekly exception workload
Why Motive
Vehicle telemetry must meet the fleet's dispatch records before connected operations data becomes useful in its contract-pricing review.
Written with these in mind
Not your kind of problem? 49 more at Motive, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Motive. They are listed as sources, not as openings.
- Senior Solutions Engineer, Enterprise (Central/Eastern Regions) (opens in a new tab)
- Sales Engineer (opens in a new tab)
- Solutions Engineer, Mid-Market (Canada) (opens in a new tab)
- Senior Manager, Commercial Solutions Engineering (Nashville or Austin) (opens in a new tab)
- Senior Solutions Engineer, Enterprise (Canada) (opens in a new tab)
Reporting read before this brief was written
The pieces closest to the situation in this brief.
In C.H. Robinson's October 1, 2026 truckload update, carriers describe record diesel prices as a major concern, saying fuel surcharges do not cover idle time, extended routing and temperature-controlled freight.
North America Truckload Freight Market Update | C.H. Robinson (opens in a new tab) · chrobinson.com · Oct 1, 2026
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about losing track of what's happening in the field.
Fleet managers are rebuilding fuel anomalies from separate vehicle signals instead of reviewing them in one place.
You must weigh quick explanations against evidence a manager can inspect before acting.
Vehicles with missing diagnostic coverage are being read as healthy in maintenance reporting.
You must weigh a useful fleet-status signal against the risk of labeling incomplete telemetry as normal.
Remote trailers and equipment disappear from the map after they leave cellular coverage.
You have to weigh recovered visibility against battery life, ruggedness, unit cost, and a pilot path that can scale.
The same setting, from another role
Each is set around Motive’s Motive Integrated Operations Platform, written for a different role. They’re separate briefs, not the same scenario.
Android engineers disagree on where disappearing edits originate across 36 driver reports.
You decide when AI can propose an owner from a replay and when Android or backend engineers must first settle what the replay proves.
Security engineers must judge 240 production grants, including rarely used recovery access.
Where will you require an owner’s explanation before AI can propose revoking a quiet grant?
Leaders deferred seven of twelve review items because pipeline totals lacked context.
Where would you let a threshold crossing become a proposed agenda question without an analyst first choosing its explanation?