Period 2 coverage

What is Period 2 coverage?

Period 2 is the intermediate coverage level under New Jersey's transportation network company insurance framework, applying when a rideshare driver has the app on and is actively available for ride requests, but has not yet accepted a specific one.

It requires a specific minimum coverage level, lower than the substantially higher requirement applying once a ride is actually accepted under Period 3, but higher than the driver's own personal coverage that applies with the app entirely off.

This intermediate tier reflects a policy judgment that a driver actively available for rides, even without a specific accepted request yet, carries meaningfully more risk exposure than an ordinary personal driving trip.

Precisely identifying which of these three specific periods actually applied at the time of a crash is generally the first and most important question in any rideshare injury case.

What specifically characterizes this coverage period?

Several factors distinguish this period from both the app off status and the higher Period 3 coverage that follows ride acceptance.

• The driver's app is on and actively signaling availability for rides
• No specific ride request has yet been accepted by the driver
• Coverage requirements are higher than app off status, but lower than Period 3
• The driver may be driving anywhere while awaiting a ride request
• This period ends the moment a specific ride request is actually accepted

Why does this specific intermediate tier exist?

Because a driver actively signaling availability for rides genuinely carries more risk exposure than an ordinary personal trip, but meaningfully less than one where a passenger is actually involved or a specific pickup is already underway.

The insurance framework reflects this graduated risk by establishing three genuinely distinct coverage tiers rather than only a simple binary distinction between app on and app off.

Understanding which specific tier applied at the moment of a crash directly determines what coverage level is actually available to respond to any resulting claim.

How is the exact timing of this period established in a claim?

Through the rideshare platform's own trip and app status data, which records precisely when the app was activated and when, if ever, a specific ride request was actually accepted.

This data generally requires a formal legal request to obtain, since it is not something an injured party can typically access informally on their own.

Establishing this precise timing accurately is essential to correctly identifying which of the three coverage tiers genuinely applied at the specific moment of the crash.

Common questions

How is this different from the coverage that applies once a ride is accepted?

This period requires a lower minimum coverage level than applies once a specific ride is actually accepted, reflecting the somewhat lower risk exposure before a passenger becomes directly involved.

What if the driver had just turned on the app moments before the crash?

The app's specific activation status at the precise moment of the crash generally governs, which is why the platform's own trip data timing matters so significantly to the analysis.

Can I obtain this specific trip and app status data myself?

This typically requires a formal legal request, since rideshare platforms do not generally provide this detailed data informally to injured parties on request alone.