After an Arizona crash involving a delivery driver, preserve the app activity surrounding the collision, the order or trip identifiers, and the insurance correspondence. Whether a driver was available, had accepted a delivery, or had completed it can matter to the coverage investigation. The actual platform and policy must be checked.
A delivery bag in a car does not prove an active order. A driver saying “I work for an app” does not establish which app or what the driver was doing at that moment. Keep those observations as leads and seek records that connect the activity to the collision time.
If you were the delivery driver
Save the order or trip details available in your own account. Include acceptance, pickup, completion, cancellation, and support messages when available. Capture the screen with the order identifier and date, then use the platform’s export or account-data process if it offers a fuller record.
Preserve earnings and activity records for the surrounding period. A single receipt may show that you earned money that day without showing your status at impact. Keep originals and avoid editing timestamps or deleting a canceled order because it seems unrelated.
Report the collision through the appropriate insurer and platform channels, following the applicable requirements. Tell the truth about the work you were doing. Concealing app use can create additional coverage and credibility problems; an attorney can help you understand the policy questions without changing the facts.
If the other driver was making deliveries
Write down what the driver said, who heard it, and when. Save photographs you already have of the vehicle and visible delivery equipment. Do not take the driver’s phone or demand access to a private account. Give relevant observations to the officer and your attorney.
Ask which platform or business the driver identified and preserve any insurance information provided. A restaurant delivery employee, independent courier, and app-based driver can involve different arrangements. Avoid substituting a familiar brand name for the business actually involved.
If a witness saw the driver collecting an order or discussing a delivery, preserve the witness’s contact information and account. The detail may help identify a record source, but it does not resolve fault or coverage by itself.
Contact Wood Injury Law if a delivery-related Arizona crash has produced uncertainty about the driver or insurer. Bring the app name, claim letters, and facts you can verify.
Platform guidance is a starting point, not the policy
Uber’s delivery-insurance guidance distinguishes activity phases and directs drivers to state-specific certificates. DoorDash publishes its own insurance and reporting guidance. The descriptions are platform-specific and can change.
Do not apply one company’s limits, definitions, or reporting process to another company. Obtain the documents applicable in Arizona on the collision date. Ask which insured person, vehicle, activity period, and claim type the insurer is evaluating.
Third-party liability coverage concerns harm to others under its terms. It should not be assumed to pay every expense of an injured delivery driver or damage to that driver’s vehicle. Separate those questions and review any other applicable policies or benefits with your attorney.
Build the activity sequence around the crash time
List the collision time separately from each app event. Record where the time came from: emergency call, phone photograph, police report, or witness estimate. Preserve the original time display and note whether a time zone appears.
Then add the relevant app events without forcing them to match your memory. An order could be canceled after a collision, and a completion entry could reflect a later action. A support message may explain the sequence. The exact wording and timing deserve review.
Illustrative example: a driver accepted an order, had a collision before pickup, and contacted support to cancel afterward. A screenshot showing only the cancellation might omit the accepted-order period. Preserving the surrounding history gives the investigator a more accurate sequence.
Account access can change after a crash
A broken phone, password reset, deactivated account, or replaced device can make records harder to retrieve. Preserve available information through legitimate account tools and keep the original device if it may contain evidence. Ask for technical help before wiping a damaged phone.
Do not share your password with a stranger claiming to investigate the collision. Use official support channels and your attorney’s secure document process. Save account-data requests and support replies with the date and any reference number.
If you cannot access an old account, document the issue and tell your attorney. The lack of a screenshot does not prove the activity did not occur. Platform records, messages, merchant records, and other sources may require separate requests or legal process.
Preserve merchant and delivery information with care
An order identifier may connect to a merchant pickup time, receipt, or communication. Save information already in your possession, including relevant messages and receipts. Customer addresses and personal details should remain private and be shared only through an appropriate claim or legal channel.
A restaurant may have pickup records or camera footage. An attorney can evaluate whether preservation requests are appropriate and how narrowly to identify the event. Do not contact customers to pressure them into supporting a version of the collision.
If two apps were open, tell your attorney about both. Do not choose the one that appears to offer more coverage and omit the other. Actual activity and policy language determine the analysis, and multiple app records may be needed to understand the sequence.
Organize insurer responses by company and issue
Keep separate folders for personal auto insurance, platform-associated insurance, and any other claim. Record the adjuster’s name, claim number, and role. One adjuster may address property damage while another evaluates injuries.
If an insurer denies coverage or asks another company to respond first, request the position in writing with the relevant policy language. Preserve the letter and attachments. Our insurance-communication resource addresses broader questions about those conversations.
Before signing a release or accepting settlement terms, ask how the proposed action affects other claims. A payment for one issue may come with language broader than its email description. Supply the complete proposed document to your attorney.
Questions to bring to a consultation
Does an open app prove the driver was on a delivery?
No single screen resolves the whole issue. The app’s status definitions, activity records, collision time, and policy terms need comparison. Preserve what the screen showed without drawing a coverage conclusion from it.
Can a screenshot replace the platform’s underlying records?
A screenshot is useful evidence of what appeared on your device, but it may omit surrounding events or system details. Keep it, identify its source, and ask whether a fuller export or formal request is needed.
See the Arizona car injury resource for the wider process. Call Wood Injury Law at (480) 937-2116 to discuss delivery activity, records, and the insurance decisions following an Arizona crash.
Keep the delivery activity file separate from your personal spending history when preparing copies for review, while preserving all originals. Tell your attorney what you excluded from the working copy and why. The attorney can determine the appropriate disclosure scope. Do not delete unrelated activity from the underlying account or alter an export to make the sequence appear cleaner than it was.
Sources
General information; the application of law depends on the facts and relevant policy. Featured image is an AI-generated illustration.
