A Cal/OSHA Subpoena Follows a Gig-Worker Fatality: Map Relevance Before Producing

When Cal/OSHA investigates a death involving work arranged through an app, the company and investigators may disagree about both employment status and the reach of an administrative subpoena. A useful response begins with an incident map, not a blanket refusal or an unfiltered data dump. Identify the event, the systems that governed it, and the records that can prove or disprove a workplace connection.

Build the incident map before debating labels

Preserve dispatch records, app status, acceptance and cancellation events, route data, communications, safety reports, insurance notices, and contracts in effect on the incident date. Record which entity controlled each system and who can authenticate the data. Employment classification may be disputed, but disappearing or fragmented evidence will make every later issue harder.

In Division of Occupational Safety & Health v. Uber Technologies, Inc., No. B340734 (Cal. Ct. App. June 18, 2026), the Court of Appeal recognized the agency’s authority to investigate and use a subpoena after an app-based delivery driver’s death. It also reversed an order enforcing the subpoena without meaningful limits and remanded for a scope analysis. Authority to investigate did not make every requested company record automatically relevant.

Connect each request to an investigatory question

For each category, state the period, custodians, data fields, and link to the incident or worker population under review. A request for the decedent’s account history has a different nexus from nationwide records covering unrelated users and years. A response chart can identify what will be produced, what does not exist, what requires clarification, and what is withheld under a stated objection.

Offer workable narrowing proposals

Propose date ranges, geographic limits, sampling, staged production, or agreed search fields where a request is broader than necessary. Preserve confidentiality issues without assuming they defeat the subpoena. Courts expect a practical explanation of burden and relevance, supported by declarations or system facts rather than adjectives.

Keep safety review separate from litigation positioning

Investigate the fatal event promptly and preserve corrective-action records with appropriate legal guidance. A company can dispute classification or subpoena scope while still examining whether platform design, communication, or incentives created a preventable risk. Workers and families should likewise preserve device and account evidence before routine retention systems alter it.

For the underlying procedural history and limits, read DOSH v. Uber: Investigatory Authority Did Not Eliminate Subpoena Limits.

The firm’s Employment practice page explains the scope of representation and how to request a review.

Practical checklist for an incident-centered response

For California workers, families, platforms, and responding businesses, preservation should begin before the scope dispute is resolved. The goal is to keep evidence intact while giving the agency and reviewing court a specific basis to evaluate relevance and burden.

• Issue a hold for account, route, dispatch, safety, support, insurance, and communications data tied to the event.
• Name the systems and custodians that hold each data category and identify ordinary retention periods.
• Create a request chart stating production, objection, nonexistence, or proposed narrowing for every item.
• Support burden assertions with volumes, retrieval steps, cost estimates, and available alternatives.
• Separate privileged legal analysis from the underlying operational facts and corrective-action evidence.

What to do next is usually a documented meet-and-confer, followed by a focused enforcement record if disagreement remains. A classification position should not be used to delay preservation. Likewise, investigatory urgency does not eliminate the need to explain how remote years, markets, or users bear on the fatal incident.

Preserve the worker’s side of the digital record

The worker’s device, screenshots, account statements, route history, messages, and support contacts may contain evidence not retained in the same form by the platform. Families should avoid altering the device and should identify account credentials through secure estate or legal procedures. Note gaps caused by automatic deletion without speculating about their meaning.

The company should preserve system dictionaries and audit information needed to interpret exported fields. Investigators should request enough technical context to avoid reading timestamps, status flags, or location points incorrectly. A neutral data map can reduce disagreement over what exists while leaving classification and legal scope for later decision.

Frequently Asked Questions

Can a company ignore a Cal/OSHA subpoena because it disputes employment status?

No. Classification may be contested, but the agency can have authority to investigate and seek relevant evidence.

Does investigatory authority make every request enforceable?

No. The appellate decision required a meaningful analysis of scope and relevance.

What supports an overbreadth objection?

Specific evidence about systems, burden, time periods, populations, and the weak connection between a request and the incident.