How to Understand Trip Processing Statuses

When you look at trips you may see different status levels instead of scores and events.

Within our solution, we may not be able to process your full trip for one of many reasons. Below is an overview of each processing status and the scenarios that could fall into play.

Trips can be shown with one of the following labels:

  1. “insufficient data”
  2. “not scorable”
  3. “awaiting motion data”
  4. “processing score”

The labels above show according to the logic below:

Insufficient data prompts occur when:

  • A trip has a “scoring error” AND shorter than 3 miles
  • A trip is in progress AND is shorter than 3 miles
  • A trip is done AND we still wait for motion data AND is shorter than 3 miles
  • A trip is done AND we have all the motion data AND trip is not scores yet AND is shorter than 3 miles

Not scorable prompts occur when:

  • A trip has a “scoring error” AND is longer than 3 miles
  • A trip is in progress AND is longer than 3 miles AND the start time is more than 24 hours ago
  • A trip is done AND we still wait for motion data AND is longer than 3 miles AND start time is more than 24 hours ago
  • A trip is done AND we have all motion data AND the trip is not scored yet AND is longer than 3 miles AND the start time is more than 24 hours ago

Awaiting motion data prompts occur when:

  • A trip is in progress AND is longer than 3 miles AND the start time is less than 24 hours ago
  • A trip is done AND we still wait for motion data AND is longer than 3 miles AND the start time is less than 24 hours ago

Processing score prompts occur when:

  • A trip is done AND we have all motion data AND the trip is not scored yet AND is longer than 3 miles AND start time is less than 24 hours ago