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.
A successful upload can still disclose the wrong driver's evidence.
Operations wants every incident submitted today, while legal will not release disputed driver histories.
Who you’d be doing this for
“I opened the second package and saw a different driver for the same crash. The adjuster already asked which one to use.”
Jaya Khanna · Fleet Claims Coordinator · a character in this brief
Prepares incident evidence for the customer's external claims administrator and answers driver attribution questions.
What is at stake
A fleet's claims integration has 48 disputed driver matches among 180 incidents due today. You must weigh complete submission against disclosures that cannot be recalled once adjusters receive them.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- complete claims coverage vs. verified driver attribution
- incident-time evidence vs. current assignment convenience
- integration acceptance vs. direct operational handoff
- one submission window vs. unresolved identity collisions
Why Motive
Dashcam evidence must survive the customer's historical driver mappings before a technically successful integration demonstrates operational value.
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. The lines under a posting are its own words, where it meets this brief.
- Senior Solutions Engineer, Enterprise (Central/Eastern Regions) (opens in a new tab)
- Sales Engineer (opens in a new tab)
- Partner with Commercial Account Executives to shape deal strategy, drive discovery conversations, and deliver high-impact demonstrations that support customer decision-making
- 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)
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 turns on crossing a deadline that can't be undone.
An audit found 3.1% of sampled severe-event packages carry no verifiable record of privileged access or changes, and the date is fixed.
You have to decide how far the control reaches before customers start relying on it.
Seventeen of 24,000 concurrent claim sequences show possible out-of-order updates before Monday’s cutover.
You must weigh a deadline-bound migration against evidence that has to stand up in a claim dispute.
For 11% of active drivers, the legacy logs and the vehicle data disagree on duty status, and the launch date is fixed.
You have to weigh a cutover you cannot unwind against parallel work through peak season.
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?
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn a tangle of confusing financial records into a clean, verifiable story people can trust.
Partial returns are producing different net Pay in 4 totals in merchant reports and merchant records.
You must weigh a durable published definition against the cost of changing historical reporting.
Completed direct deposits are showing a 1.6% duplicate-event rate in daily reporting.
You have to weigh a quick repair against preserving reliable historical payment records.
Florida renewals with two pricing changes are appearing differently across financial and scoring records.
You have to weigh a fast committed file against proof that every premium change can be explained.
