After a delivery-driver collision, start with the work actually happening

Reconstruct the activity, not a platform label

Start with the crash time and work outward through the records already available. A dated assignment, pickup message, receipt, cancellation or completion notice may help identify what was happening. Record the time shown, the source and any uncertainty. Your recollection and an app display may not answer exactly the same question.

An app being open is different information from a particular order being accepted. An accepted order is different information from goods being collected or delivered. Those distinctions help identify what to investigate; they do not, by themselves, determine coverage.

If you were the delivery driver, keep existing records from your own account and messages. If you were another road user, you may have only a report, a photograph or what the driver said. Label that source rather than attempting to fill in the driver's private account history.

A useful short sequence might be: order reference shown; pickup message received; crash time recorded; later cancellation notice received. Leave a missing step missing. Do not infer that a later cancellation proves whether the driver was working when the crash occurred.

An example: a cancelled order leaves a question, not an answer

Imagine a driver remembers heading toward a pickup. A saved message shows an order was accepted before the crash, while a cancellation notice is dated afterward. This is a fictional illustration.

The records give a sequence to examine. They do not establish who cancelled, why it happened, whether another assignment was active or which policy governed the trip. The next useful question is which available record describes the driver's activity at the crash time, rather than whether the app eventually labeled the order cancelled.

Keep the original messages and exact times together. If someone gives a different account, preserve that statement and its source too. A discrepancy calls for examination; it is not automatic proof of dishonesty.

Separate the businesses before assigning responsibility

A restaurant may have prepared food, a platform may have connected an order, a driver may have used a personally owned vehicle, and a different company may be handling a claim. That is a set of possible relationships to verify, not a finding that each relationship existed.

For the particular crash, identify:

One organization may occupy several roles. A restaurant's name on a receipt does not establish that it employed the driver. A platform's brand does not establish vehicle ownership. An agreement calling someone a contractor does not, on its own, resolve every legal issue.

• The driver and vehicle owner: names, registration or other ownership information already available, and the vehicle used.
• The source of the work: an identified employer, delivery company, restaurant, platform or customer assignment, with the record connecting it to the trip.
• The activity: what was accepted, collected, transported, completed or cancelled, and when.
• The stated relationship: any employment or contractor description and the actual agreement if available. Keep a label separate from a legal conclusion.
• The claim contact: who contacted you, which person or business it represents and what claim it is discussing.

Delivery is not simply a passenger ride with a package instead

Oklahoma's Courier Application Services Act addresses a limited category of app-connected, on-demand transportation of property, with definitions, vehicle conditions and exclusions. Section 1071 does not turn every restaurant, fleet, freight or non-app delivery into the same legal arrangement.

Its service-timeline definition distinguishes a start based on accepting a courier request from a start tied to pickup in a specified fixed-block arrangement, and addresses active transportation and completion. That is one reason acceptance, pickup, crash-time and completion records can matter. It is not a universal insurance clock: matching a statutory definition does not decide crash-date coverage or responsibility. The actual activity, applicable definitions and agreements still need to be examined together.

If a company offers several services, identify the service and actual activity involved rather than applying information from its passenger-ride pages to a delivery trip.

A person carrying an order may have no passenger trip receipt. An occupant of another vehicle may have no app record at all. A restaurant employee driving an assigned vehicle may present different records from an app-connected driver using a personal car. The same general word, “delivery,” is not a substitute for those facts.

Use the rideshare guide when passenger transportation and app-trip status are the actual issue. This page supplies no passenger-rideshare insurance limit or rule for goods delivery.

A statement about insurance needs a policy and a subject

Keep the personal, vehicle-owner, employer, delivery-company or platform policy materials that have actually been identified. Do not assume every category exists. For each available document, note the named person or business, vehicle, effective period and any delivery or business-use wording.

When a contact says “delivery isn't covered” or “the platform handles it,” identify which policy, claim and activity that statement concerns. Preserve the written position and the policy provisions it identifies. A general website description or certificate should not be mistaken for the complete crash-date policy.

Coverage, responsibility and the cost of the damaged vehicle are different questions. The coverage guide, insurance-call guide and vehicle guide address their own parts of the problem. This guide does not rank policies, promise a minimum fund or decide whether an exclusion applies.

Take the unresolved connection into the conversation

A useful starting summary says what activity is known, who supplied that information, which businesses and vehicle are identified, and what an insurer or other person has asked you to do. Bring an actual proposed date or document to attention without waiting to obtain every agreement or app record.

You can request review using the closest broad subject and safe contact details. The initial form does not accept a written account or uploads. Keep app history, contracts, policy papers and private crash details for a later conversation if one is arranged. A request does not create representation or promise acceptance of a delivery matter.