I'm organizing the deliverable into a cover letter with general preservation and scheduling statements, then structured responses to each request that lay out the specific objections, what's being produced versus withheld, and any narrowing proposals with timelines, followed by the privilege log and clawback protocol.

For Request 1, I'm proposing to narrow the scope to Osprey and vehicles sharing its battery system, pack supplier, or thermal management architecture, running from January 1, 2021 through production end to capture development and pilot complaints alongside customer data. I'll conduct structured searches across CRM fields, warranty claims, and field service tickets using targeted keywords, with a Phase 2 sampling approach for other lines with common cell or module suppliers. On reseller data, I'm committing to a reasonable inquiry—reviewing reseller agreements, sending questionnaires, and reporting within 21 days—while preserving everything and not asserting lack of control at this stage.

Request 2 involves the 18 million message volume issue, which appears to be disproportionate.

For Request 3, I'm proposing five key custodians covering battery engineering, Osprey systems, product safety, warranty management, and supplier quality, with a date range from January 1, 2020 or 2021 depending on the custodian's role. I'll use refined search terms with proximity operators and exclusion filters to avoid false hits, provide hit counts for negotiation, validate results with a 500-document sample, and phase the collection starting with the five primary custodians before expanding based on what we find. I'm also offering to run the agency's proposed search terms upfront and report hit counts before full production begins.

On Request 3's privilege objection, I'm distinguishing between blanket assertions and targeted production—I'll produce underlying engineering photographs, test data, and incident facts from source repositories in their native form without asserting privilege. For Request 5, I'm not objecting to production and can deliver within about 10 business days, with collection happening in 8 days. I need to produce the incident database export with specified fields, test results, raw source data, photographs with their metadata, and everything in native formats with hash values following ESI protocol. The term "substantially similar events" is too vague, so I'm proposing a specific definition: thermal events would include venting, smoke, fire, thermal runaway, or thermal warning diagnostic trouble codes on the Osprey's traction battery or charging system, coded per warranty and field-incident standards—I'll ask the agency to confirm this. There's a narrow work-product exception for post-event analyses prepared under counsel's direction for the Emberline litigation, but I'm still producing all the underlying facts, photos, and raw data.

For Request 6, I'm splitting the Emberline materials: the annual validation reports from 2020 through 2024 under the standing engineering contract are ordinary business operations, not work product, so those go out in full including drafts and supporting data. The separate confidential engagement by outside counsel after the second event is work product—I'll withhold the analyses and opinions and log them—but I'm producing the underlying facts and raw test data from that engagement since the physical testing and measurements would normally be routine work, and I'll note that Oriole will provide the test setup, measured data, and photographs. The work product protects the report itself, but the facts underneath aren't protected, so I'm offering to produce the raw data and test measurements while withholding opinions and mental impressions.

Now I'm working through the general structure of the response: preservation details like when the litigation hold was issued and which sources are affected, no boilerplate language, a reservation of rights, key definitions, the ESI protocol, a rolling production schedule, contact information, and a meet-and-confer deadline of seven days. I'm also setting up the privilege log with fields for control numbers, dates, authors, recipients, document type, subject matter without revealing the advice, which privilege applies, and the factual basis like whether counsel directed the work and whether litigation was anticipated.

For the privilege log itself, I need to track whether documents are redacted or fully withheld, their family relationships to other documents, and their source. Attachments get logged separately since they don't automatically inherit privilege from the parent document—each one gets assessed on its own merits, and if an attachment isn't privileged, I'll produce it with a slip sheet noting the parent was withheld. Mixed documents should be redacted rather than withheld entirely, with a clear annotation and log entry. I'm also compiling a list of attorneys with their bar status and in-house designations. The timing works on a rolling basis with logs due within fourteen days of each production and a final log twenty-one days after we're substantially done. We can propose categorical logging for outside counsel communications with Firm X after representation started that relate solely to this investigation, and for internal drafts of responses to the subpoena itself.

For communications that come after the subpoena date, there's a common convention that these don't need to be logged at all—I should propose a specific cutoff date for that. On the clawback side, I'm setting up a Rule 502(d)-style protocol where production doesn't waive privilege, notice goes out within five business days of discovery, and the agency has five business days to sequester and return materials or delete them from all workspaces. If there's a dispute, the agency can challenge by submitting the document under seal to the ALJ without arguing that production itself waived privilege. I'll provide an amended log within ten days of any clawback, and I'm confirming that we're conducting reasonable review using TAR and targeted search terms with attorney-level screening of the hits.

I also need to address the agency's obligations around not using quarantined material and their own inadvertent-production procedures if they find privileged content. There's a separate protocol for handling hard copies versus ESI, and I need to disclose the privilege screening methodology including attorney names and search terms. I'm drafting a brief internal note to the general counsel explaining that objections don't justify withholding everything—there's real risk of enforcement and sanctions if we don't follow Rule 3 properly.

For the document itself, I'm setting concrete dates: subpoena served February 10, 2026, with response due February 24, 2026, and the investigation period running through December 31, 2026. I'll structure this as a proper legal document with clear headers and use fictional names throughout.

Since the subpoena reaches into December 2026 and we're currently in February, that's a prospective request—I should object to the future-dated material and propose a supplemental production schedule instead, where Oriole provides quarterly updates rather than an open-ended obligation. I'm also tracking three thermal events: March 14, 2024, August 2, 2024 (when counsel retained Emberline on September 5), and June 9, 2025. The Osprey program itself was authorized in 2020, production started September 2021, and commercial service began January 1, 2022. I need to incorporate details about the Kestrel battery pack and Volt-Arc Cells as the supplier, plus reference other product lines like Harrier.

For the production strategy, I'm thinking Osprey and Harrier share the same battery architecture—same cell, module, and BMS software family—while Kite and Merlin use a different supplier with LFP chemistry. So Phase 1 covers Osprey, Phase 2 handles Harrier through sampling, and I withhold Kite and Merlin unless there's a specific showing of relevance. I'm also identifying the five key custodians who would have responsive documents: the Chief Engineer for Battery & Thermal Systems, the Director of Product Safety & Regulatory Compliance, the Manager of Field Quality & Warranty Analytics, the Director of Supplier Quality for Cells & Modules, and the Osprey program lead.

Now I'm working through the reseller side—42 independent regional resellers with Master Reseller Agreements that need contract review within 21 days, plus questionnaires and preservation notices. I'm structuring the response document with a cover section laying out preservation obligations and ESI format details, then responses to each request, and finally a privilege log. The document will be substantial but organized.

I'm also planning the supporting materials: a clawback and non-waiver protocol, a summary table with custodians and key dates, search term and custodian appendices, and a brief transmittal note to the General Counsel at the front explaining the objection strategy since they want to push back on production. I'll continue with the search terms, including specific DTC codes for the Osprey system and event identifiers like incident numbers and VIN fragments to make the examples concrete.

Now I'm refining the search to exclude common false positives like fire drills, fire marshals, and HR-related terms, while also filtering out newsletter content by domain. I'll report the hit counts and sample up to 500 documents for precision.

The unfiltered dataset is around 18 million documents, but narrowing to five key custodians and applying the search terms should bring that down to roughly 220,000 documents, which after deduplication and threading could reduce to about 95,000 unique items—though I'm estimating around 180,000 families affected and will provide actual counts within 10 days.

For the phasing schedule, I'm setting the subpoena service date as February 10, 2026 with a response due by February 24, then breaking production into phases: Phase 1A covers five core incident materials by March 6, Phase 1B handles board and safety committee documents by March 20, and Phase 1C focuses on Osprey complaint data with a structured export due March 13.

Phase 2 begins April 10 with rolling ESI production from multiple custodians, substantially complete by May 15 pending term validation, while Emberline's ordinary-course reports are due March 6, the reseller inquiry report by March 17, and privilege logs rolling within 14 days of each production with a final deadline of June 5. I'm also noting that Oriole will produce non-privileged responsive material even where objecting in part, and supplemental quarterly productions will continue within 30 days of each quarter end while the investigation remains open.

Now I'm working through the privilege screening methodology, starting with compiling the attorney name list and... I should propose categorical log entries for post-service communications with Sanders & Wray on this investigation, internal litigation-hold directives, and response drafts, all certified by responsible counsel. The privilege log itself needs to specify sufficient facts for evaluation—including whether authors or recipients are attorneys or acting under counsel direction, whether nonlawyers had legitimate need-to-know, and for work product claims,