We need answer user's request: draft final form legal document: specific written objections/responses to Requests 1-6, privilege-log and clawback protocol. Need think through law/facts. Need likely produce as memo/letter? We need draft in final form. Need ensure preserves privilege, no blanket, identify reseller-control under investigation, no state outside control before reasonable inquiry complete. Must include for each request what produce, withhold, investigate, concrete narrowing/phased proposal. Need address requests. Need consider each request under governing law.

We need produce professional draft. Let's analyze facts and rules deeply to ensure accuracy.

Context: Oriole Mobility, e-vans, subpoena from Federal Transport Safety Office administrative subpoena investigating three battery-thermal events involving Osprey van. Osprey commercial service Jan 1, 2022. Investigation period Jan 1, 2018-Dec 31, 2026. Requests:

1. All customer complaints concerning heat, smoke, fire, charging, batteries, or electrical odor for every Oriole vehicle from 2018-2026.
Prelim: reaches four vehicle lines using different battery systems. Osprey did not exist commercially before 2022. Need object/narrow. Law: reasonably relevant to lawful safety investigation. Can narrow when scope, custodians, time, search design burden grossly disproportionate. Need produce responsive nonprivileged reasonably available. Must state reseller control facts under investigation, cannot say not control before reasonable inquiry complete. For Request 1, produce what? Customer complaints for Osprey (since Jan 1 2022) concerning terms? Maybe other vehicle lines? Investigation is three Osprey events, but subpoena says every Oriole vehicle 2018-2026. Need object as overbroad/burdensome as to non-Osprey vehicles and pre-2022, but propose narrowing to Osprey from commercial service Jan 1 2022 through Dec 31 2026, maybe include other vehicles only if complaint references Osprey/battery thermal event? Could produce Osprey complaints; investigate reseller systems; perhaps produce known Oriole-maintained complaints for other lines if reasonably available? But likely not reasonably relevant to Osprey investigation, unless safety investigation may consider common patterns across vehicle lines? The subpoena's investigation is three events involving Osprey. Law says reasonably relevant to lawful safety investigation. Broad but may narrow. Need not object to every request and produce nothing. So should propose phased: Phase 1 Osprey customer complaints from Jan 1 2022; if agency needs comparative data, narrow to battery/charging complaints for other vehicle lines with similar battery/charging architecture? But facts say different battery systems. Could propose to produce Osprey complaints first; after review if relevant, perhaps produce limited set for comparable vehicles? Need identify concrete proposal.

Customer complaints may contain third-party PII? Not asked but could redact? Need maybe propose production format, no PII? But governing law doesn't mention. Can include standard redaction of unrelated personal info? But don't overcomplicate. Need privilege? Customer complaints likely not privileged unless request for legal advice. Need produce nonprivileged. Some complaints may be stored by reseller. Need state reasonable inquiry ongoing: identify reseller ticketing systems, contracts, volume, whether Oriole has contractual/practical right. Do not state outside control. Need preserve sources.

2. All company communications containing any form of words battery, heat, smoke, fire, charge, no custodian/date. Returns 18M messages incl cafeteria fire drills, routine charging. Need object as overbroad/burdensome, propose custodians, date range, search terms, maybe exclude routine terms? But must preserve privilege? Communications may include attorney-client/work product. Need propose produce nonprivileged responsive after reasonable search; withhold privileged with log. Need specific terms: e.g., ("battery" AND ("thermal" OR "overheat" OR "smoke" OR "fire" OR "burn" OR "flame" OR "spark" OR "melting" OR "charging" OR "charge" OR "SOC" OR "BMS" OR "pack" OR "cell" OR "module" OR "HV" OR "12V" OR "electrical odor" OR "foul odor" OR "burning" OR "hot" OR "temperature" OR "HVAC?" etc). But request asks any form of words battery heat smoke fire charge. Need propose limiting to custodians (five initial), date range maybe from Osprey commercial service Jan 1 2022 to date? Or development from? Since investigation period 2018-2026, but Osprey entered 2022. Could include design/manufacturing from 2018? If battery system developed 2018-2021. Need concrete: five initial custodians: VP Engineering/Chief Engineer, Head of Battery Engineering, Director of Vehicle Integration/Charging, Director of Quality/Field Operations, General Counsel? Or Chief Safety Officer, Chief Engineer, Head of Field Service, Head of Product Compliance, Corporate Secretary? Need propose. The Office asks identify five initial custodians, reasonable Osprey date range, proposed search terms. We can include in response/protocol. Need not reveal privileged search terms? Search terms are not privileged generally. Could include custodians. Need avoid blanket privilege. For Request 2, perhaps phased: Phase 1 custodians and Osprey-related terms from 2022-2026; Phase 2 if needed include 2018-2021 design/development communications for custodians with terms. Or produce nonprivileged responsive from all custodians? But 18M is grossly disproportionate. Need concrete narrowing. Use date range: Jan 1 2022 (commercial service) through present/Dec 31 2026? Since investigation period ends 2026, but current date? It's fictional maybe response due now; but can say through date of production. Need maybe include Osprey development from Q1 2018? But if subpoena period begins 2018, and Osprey didn't exist before 2022, but design battery system could be relevant. Need perhaps propose two phases: Phase 1: communications from Jan 1 2022 through production date involving identified Osprey custodians and refined terms; Phase 2: if Office identifies specific issue, include development period 2018-2021 for selected custodians and terms. Or maybe produce all responsive nonprivileged from 2022 onward; object to 2018-2021 absent showing relevance because no commercial vehicle. But design might be relevant to safety; cannot categorically exclude. The law says demand may be narrowed. Need likely propose date range Jan 1 2022 to Dec 31 2026 for Osprey, with optional 2018-2021 for design if agency needs. But user asks reasonable Osprey date range. Since Osprey entered service Jan 1 2022, a reasonable Osprey date range is Jan 1 2022 to Dec 31 2026. Could include 2018-2021 only for battery-system design/test communications, not all company communications. Need concrete.

Search terms: Need propose specific. The request includes any form of words "battery", "heat", "smoke", "fire", "charge". We can't just exclude those words because request demands. But can limit custodians/date and use search terms with synonyms/technical terms? But must not refuse request terms. Could propose initial search using those terms in proximity to Osprey terms and battery/charging context, plus excluding routine false positives? But law permits search design. Need avoid overproducing privileged? Search terms can be concrete. Maybe:
- Custodians: (1) Chief Engineer, Osprey; (2) Battery System Lead Engineer; (3) Charging/Powertrain Engineer; (4) Director of Field Quality/Service; (5) VP Product Compliance/Safety. Also maybe General Counsel? For communications request, all company communications including counsel? But Request 3 covers communications between Oriole and any lawyer. Request 2 all company communications. Could include internal and external. Need identify five initial custodians perhaps include GC for legal? But Request 2 might include counsel communications, but Request 3 separate. Maybe custodians for Request 2: product, engineering, field ops, quality, compliance. Not GC to avoid privilege log huge? But if GC communications are responsive, maybe need review? Could include as later phase.
- Date range: Jan 1 2022 to present; optional 2018-2021 design.
- Terms: ("Osprey" OR "OM-" OR model numbers) AND ("battery" OR "battery pack" OR "high-voltage" OR "HV" OR "BMS" OR "cell" OR "module" OR "pack" OR "thermal" OR "heat" OR "overheat" OR "temperature" OR "thermal runaway" OR "smoke" OR "fire" OR "burn" OR "burning" OR "flame" OR "spark" OR "melting" OR "charging" OR "charge" OR "charger" OR "state of charge" OR "SOC" OR "fast charge" OR "DC" OR "AC" OR "electrical" OR "odor" OR "foul" OR "burning smell")? But the subpoena specifically says any form of the words. If we propose terms only if also Osprey, we might be narrowing by relevance, okay. Need include variants? "any form" means stemming, plural. Use search syntax: (batter* OR heat* OR smok* OR fire* OR charg*) AND (osprey* OR OM* OR ...). But if we exclude communications not mentioning Osprey, is that okay? The investigation is Osprey events. Could be relevant to other vehicles? Request 2 all company communications without custodian/date. We can propose limiting to Osprey-related. Need concrete: use terms plus exclusionary filters for cafeteria fire drills/routine charging reminders: exclude messages with certain sender groups, list server newsletters? Need not overdo.

Need also state what produce: after review, produce nonprivileged responsive; withhold privileged; log. What investigate: refine custodians/terms after initial sample; reseller? Request 2 likely internal company communications; maybe reseller not. Need investigate false positives via sampling. Could propose sampling of 100 or 200 documents to validate search terms? Law says counsel should propose sampling. Good.

3. All communications between Oriole and any lawyer concerning battery safety, product compliance, reporting duties, recalls, customer complaints, or the three events.
This is clearly potentially attorney-client privilege and work product. But not all communications with lawyers are privileged: underlying facts, ordinary engineering data, final business decisions, documents copied to counsel not protected. Need not blanket assert privilege. Need produce nonprivileged responsive: e.g., underlying incident facts, engineering photos, test data, business decisions, non-legal advice, routine compliance reports? Need withhold confidential legal advice/requests and work product. Need log with fields. Need perhaps segregate mixed documents: produce nonprivileged portions, withhold/redact privileged portions; for attachments: if attachment is underlying facts/data, produce; if prepared primarily for litigation, withhold work product; if legal advice, withhold; if mixed, produce/reduct. Need concrete response: Oriole will produce responsive nonprivileged communications and documents to/from counsel that do not contain confidential legal advice or work product, including factual incident reports, engineering data/test results, photographs, compliance/business decisions, and communications seeking only factual information? But if communication is request for legal advice? The request for legal advice is protected. If a letter asks counsel to analyze whether event is reportable under law, that's protected. But factual incident report attached may be producible if underlying facts. If same document contains both legal advice and facts, redact.
Need perhaps identify categories and log. Need not state all withheld. Need propose maybe produce a log first? Under law: privileged material may be withheld only with log. Could produce nonprivileged and log withheld. Maybe propose to produce in phases: within X days produce nonprivileged; log within same? Need maybe not specify exact days but response due 14 days. Could say within 14 days produce responsive nonprivileged from identified custodians? But for Request 3, need identify what will produce. Could say Oriole will produce nonprivileged responsive communications in two tranches: (1) communications that are purely factual (incident reports, engineering data, test data, photos, business decisions, compliance reports, reseller/customer communications) and (2) portions of mixed documents after redaction. It will withhold/log confidential legal advice, requests for legal advice, and work product. It will investigate whether communications with non-Oriole lawyers (reseller counsel? outside consultants?) are subject to privilege/work product; not blanket.
Need also maybe state that ordinary business documents copied to counsel are produced. Need log fields. Need mention subject matter stated without revealing advice.

4. All board and safety-committee materials concerning Osprey battery system and three events.
Includes ordinary board minutes, attachments from outside counsel, mixed legal-business presentations. Need object as overbroad? It says all board and safety-committee materials concerning Osprey battery system and three events. Not as broad as request 2 but may include privileged counsel attachments. Need produce nonprivileged: ordinary board minutes, safety committee materials, engineering reports, business presentations, factual materials. Withhold/log privileged portions: outside counsel legal advice, presentations prepared primarily for enforcement/litigation, portions of minutes/presentations containing legal advice. Need mixed documents redact. Need maybe propose produce all nonprivileged board/safety committee materials from Jan 1 2022 (or 2018 development?) through 2026. But need maybe date range. Board and safety committee materials concerning Osprey battery system: since Osprey commercial 2022; design before could be relevant? Could propose Jan 1 2022 onward, plus pre-2022 design/test materials if specifically relevant. But board materials likely from 2022. Need concrete: produce nonprivileged board/safety committee materials from Jan 1 2022 through production date; investigate pre-2022; withhold/log privileged. Need maybe limit to Osprey battery system and three events, not all safety committee? The request already limited. We can agree with narrowed scope: produce all nonprivileged responsive board/safety-committee materials; no need object maybe except privilege and mixed. Could object to request 4 only to privilege, not scope? But assignment says specific objections/responses. We can state no scope objection, but object to extent it seeks privileged/work product, and will redact. Or object as overbroad if "all board and safety-committee materials" includes unrelated safety committee materials concerning Osprey battery system? It is concerning Osprey battery system and events; okay.

5. The complete incident database, test results, source data, photographs, metadata for three events and substantially similar Osprey events.
Prelim can be collected from incident DB and engineering repo within eight days. Need respond: produce responsive nonprivileged; likely no privilege? Some metadata? Maybe work product if test results prepared because anticipated litigation? But reports in ordinary course product testing not protected. Need distinguish: complete incident database, test results, source data, photos, metadata for events and substantially similar Osprey events. Need define "substantially similar" concrete: Osprey battery thermal events with similar symptoms (heat/smoke/fire/charging/battery/electrical odor) or same battery pack/charger/BMS/software version? Need propose phased: produce three event records within 8 days; then substantially similar Osprey events within e.g. 14-30 days. Need preserve. Need object to vague "substantially similar"? Need propose definition: (a) Osprey vehicles; (b) event classified as thermal, battery, charger, HV, or electrical odor; (c) same battery platform/version, charging system, or BMS/software; or (d) event with smoke/fire/overheat during charging. Or use customer complaint codes? Need concrete. Need produce source data? If raw data large, can propose native formats, metadata, load files, or database extract. Need metadata: maybe full metadata for three events; for similar events maybe core metadata. Need not withhold all. Need maybe work product: test reports prepared by Emberline? Request 6 separate. For Request 5, some test results may be prepared in ordinary course; not privileged. If after second event outside counsel retained Emberline to analyze litigation/enforcement risk under new confidential engagement, those work product? But Request 5 asks incident database, test results, source data, photos, metadata for events and similar events. The post-event risk analysis by Emberline under litigation engagement might be work product and not incident test results? Need maybe in Request 5 or 6. For Request 5, if test results include post-event forensic analysis prepared because of anticipated enforcement? Need work product if prepared primarily because of anticipated litigation/enforcement. But ordinary incident database and test data not. Need identify what withhold: forensic/test reports and analyses prepared primarily after events by counsel-retained Emberline? But facts: Emberline prepared annual battery-validation reports 2020-2024 under standing engineering contract. After second thermal event, outside counsel separately retained Emberline to analyze litigation and enforcement risk under new confidential engagement. That likely work product, maybe not "test results"? It is analysis. Request 6 asks all reports by Emberline concerning Osprey batteries. Need address there.

Request 5 can be collected within eight days. Need propose produce complete database extract? Need maybe object to "complete incident database" if includes all vehicles? But request limits three events and substantially similar Osprey events. "Complete incident database" maybe means the entire database? It says complete incident database, test results... for the three events and substantially similar Osprey events. Could be read as entire incident database? Need clarify: produce records for events within scope, not entire database unless contains responsive records. Object to producing entire database if it includes unrelated events; propose database extract/structured data for in-scope events. Need preserve. Need maybe phased: Phase 1 within 8 days: complete records for three events (incident reports, photos, metadata, test results/source data in engineering repo). Phase 2 within 14 days? Define substantially similar and produce. Since response due 14 days, maybe produce Phase 1 now/within 14, Phase 2 by 30? But assignment asks response due in 14 days; can propose phased production beyond. Need concrete.

6. All reports by Emberline Engineering concerning Osprey batteries.
Facts: annual battery-validation reports 2020-2024 under standing engineering contract. After second event, outside counsel separately retained Emberline to analyze litigation and enforcement risk under new confidential engagement. Need respond: produce ordinary course reports 2020-2024 (and any 2025-2026 ordinary course reports) that are not prepared primarily because of anticipated litigation/enforcement and not containing confidential legal advice? Work product rule: report prepared in ordinary course product testing not protected merely because litigation later arises. So annual battery-validation reports are likely not work product. But if after second event, Emberline reports prepared under new engagement to analyze litigation/enforcement risk, prepared primarily because of anticipated litigation/enforcement, likely work product; withhold/log. Need distinguish. Also if Emberline report contains legal advice? No, engineering consultant not lawyer, but if prepared at direction of counsel for litigation, work product. Also if contains underlying test data? Produce nonprivileged data; withhold conclusions/analysis prepared for litigation? Need mixed documents: produce underlying test data/factual measurements, withhold analytical portions prepared primarily for anticipated enforcement. Need log. Need maybe produce annual reports 2020-2024; object to post-second-event reports/analyses under litigation engagement as work product; but need not categorical; evaluate each. Need maybe produce all Emberline reports concerning Osprey batteries that are not work product; withhold/log work product. Need investigate whether any ordinary-course reports were revised or supplemented after events for litigation; if so, separate. Need date range? 2020-2024, maybe 2025-2026 if reports. Since Osprey commercial 2022 but battery validation from 2020. Investigation period 2018-2026. Need produce 2020-2024 ordinary; investigate 2018-2019 if any; 2025-2026 if any. Need maybe propose phased: produce ordinary-course validation reports within 14 days; log litigation-engagement reports. Need not assert blanket privilege over all Emberline.

Need also include privilege-log and clawback protocol: required log fields: date, author, recipients, document type, subject matter stated without revealing advice, privilege asserted, sufficient facts to evaluate claim. Also perhaps Bates number, custodian, document title, date, sender/recipient, cc, document type (email, memo, report, attachment), category (AC/WP/mixed), short description not revealing privilege, reason, withholding/redaction. Categorical logging only if agency agrees; so propose specific logs for each document/series? Need maybe state Oriole will provide individual logs unless Office agrees to categorical for repetitive routine documents? But must not assume. Need treatment of mixed documents and attachments: produce nonprivileged portions; redact privileged; for attachments: log and produce nonprivileged attachments; if an attachment is solely privileged, log; if mixed, redact. Need maybe use "privilege legend" and "privilege log supplement"? Need timing: log with production or within X days; maybe 7 days after initial production; updated as review continues; rolling basis. Need inadvertent production: clawback/nonwaiver agreement; preserve rights; if identified after production, notify Office, seek return/sequestration, not waive; but doesn't excuse unreasonable review or deliberate overproduction; so Oriole will implement QA, privilege review, sampling, metadata filtering, two-pass review? Need mention no deliberate overproduction. Need include fields for inadvertently produced? Maybe protocol: if inadvertent, immediately notify, provide log entry, request non-disclosure, return/destruction, maintain confidentiality; if already disseminated, take reasonable steps. Need mention no waiver for inadvertent under agreement; but deliberate overproduction not protected. Need include QA: search, first pass, privilege review, secondary review, sampling.

Need also include preservation and reasonable inquiry: preserve all potentially responsive sources; reseller-control facts under investigation. Need maybe separate section: preservation and control/reseller. The draft must identify reseller-control facts still under investigation and not state outside control before reasonable inquiry complete. Need include in objections/responses, especially Request 1. Also maybe Request 3? Communications with reseller? No.

Need likely structure:
- Caption/header: In re Federal Transport Safety Office Investigation / Administrative Subpoena No. ...; Re: Oriole Mobility, Inc. Response and Objections to Administrative Subpoena; Privilege Log and Clawback Protocol.
- Introduction: represents Oriole; acknowledges subpoena; will respond within 14 days; proposes good-faith narrowing; preservation; agrees to nonwaiver/clawback; reasonable inquiry ongoing.
- General statements: scope, production protocol, search and review, reseller control investigation, privilege protocol.
- Request-by-request:
  For each: Response/Objection; What Oriole will produce; What it will withhold; What it will investigate; Proposed narrowing/phased production.
Need ensure each request has specific. Could use tables or bullets.

Need think about exact legal grounds. Under law 2: objection must identify particular request, precise ground, proposed response. So for each, state "Request X is objected to as overbroad/burdensome because ...; to the extent not objectionable, Oriole responds as follows." Need precise. Need not use boilerplate. So for Request 1: overbroad/burdensome as to (a) pre-2022 non-Osprey vehicles (Osprey did not exist), (b) other vehicle lines with different battery systems absent showing relevance, (c) all customer complaints from all channels/resellers without date/custodian limit? Need produce. Ground: relevance to Osprey thermal events; burden grossly disproportionate. Proposed response: produce all nonprivileged customer complaints from Oriole-maintained systems for Osprey from Jan 1 2022 to present concerning heat, smoke, fire, charging, batteries, electrical odor; conduct reasonable inquiry into reseller ticketing systems; if responsive reseller complaints exist and within control, produce after inquiry; propose optional comparative subset for other lines if agency identifies specific relevance (e.g., same battery/charging architecture or similar symptoms) with narrowed terms/date. Need maybe produce known complaints for other lines if already in Oriole's systems? Since law says must produce responsive nonprivileged reasonably available even when object to another portion. Are other-line complaints reasonably available and reasonably relevant? Investigation of Osprey events. If other vehicles different battery systems, likely not. But if subpoena specifically demands every Oriole vehicle, agency may assert relevance to company-wide safety culture? But we can object. Yet rule 3 says produce responsive nonprivileged reasonably available. If we object to other vehicles as not reasonably relevant, we don't produce. But if agency insists, perhaps produce later. Need maybe state "to the extent Office contends complaints for other vehicle lines are reasonably relevant to the Osprey investigation, Oriole will produce nonprivileged complaints for vehicles sharing the Osprey battery/charging architecture or with battery thermal symptoms, after identification of relevant fields." But need not produce all four lines. Could propose a phased alternative: produce Osprey complaints first; if Office needs cross-line comparative, provide complaint categories/counts for other lines or narrowed subset. Need concrete.

Potential issue: Request 1 includes "all customer complaints" from 2018-2026. Osprey didn't exist before 2022, but other Oriole vehicles existed. Could there be relevant complaints about company-wide battery safety? The investigation is three Osprey events; subpoena period includes 2018 maybe for design. But customer complaints for other lines maybe not relevant. Need maybe not overstate. We can say "Object as to pre-2022 complaints for non-Osprey vehicles and, as to post-2022 complaints for non-Osprey vehicle lines, object to the extent they do not reference battery thermal symptoms or share the Osprey battery/charging platform; proposed production limited to Osprey." That's precise.

Need maybe include "customer complaints" may include privileged? If customer asks for legal advice? Unlikely. But if complaint copied to counsel and contains request for legal advice? Customer communications not with counsel generally not privileged unless in course of representation? Could be if customer seeks legal advice from company counsel? Maybe some. We can include: withhold/log any confidential legal advice embedded in complaint handling (e.g., counsel's legal assessment), but produce underlying factual complaint. Need maybe not overcomplicate.

Request 2: Need detailed search protocol. Let's design.

Five initial custodians:
1. Chief Engineer, Osprey Program
2. Lead Battery Engineer / Battery Systems Manager
3. Charging & High-Voltage Systems Engineer
4. Director of Field Quality and Service / Director of Field Operations
5. Director of Product Compliance and Safety Reporting
Could include VP Engineering? But need five. Need maybe also "Corporate Secretary"? Board request separate. For communications, these are relevant.
Date range: Jan 1 2022 through Dec 31 2026 (or production date). Because Osprey commercial service. But if design 2018-2021? Need propose optional Phase 2: Jan 1 2018-Dec 31 2021 for selected design/development custodians and only battery/thermal terms tied to Osprey battery platform. But Office asks reasonable Osprey date range; likely 2022-2026. We can say initial reasonable Osprey date range is Jan 1 2022 to present; if Office requires development history, propose narrowed second phase 2018-2021 limited to identified custodians and battery design/test terms. Need not object to 2018-2021 entirely, but propose not first phase due burden. Need preserve.

Search terms: Need concrete syntax. Could define:
Primary terms (as required): batter*, heat*, smok*, fire*, charg* (stemming to include battery/batteries, heating/heat/overheat, smoke/smoked, fire/fires/firefighting? charging/charge/charger). But to reduce false positives, use context terms:
Osprey terms: "Osprey", "OM-100" (fictional model?), "Osprey EV", model codes (we can invent? Need not? Could say "Osprey model codes currently used by Oriole"). Use "Osprey*" plus known platform codes? Need maybe not invent too much. But concrete is good: "Osprey, Osprey EV, OMY-25, OMY-25B, Osprey Battery Pack, OSP-BP" but if invented, okay fictional. Better to say "Osprey, Osprey model codes (e.g., OSR-200/OSR-210)"? Could be too specific. Since fictional, can define placeholders. Need final form, so maybe use "Osprey model/design codes maintained in Oriole's engineering database" without actual codes. But assignment asks proposed search terms; concrete enough: (osprey* OR OSR-* OR "Osprey program") AND (batter* OR heat* OR smok* OR fire* OR charg* OR thermal* OR "thermal runaway" OR "overheat*" OR "temperature" OR "spark*" OR "flame*" OR "burn*" OR "melting" OR "HV" OR "high voltage" OR "BMS" OR "cell" OR "module" OR "pack" OR "state of charge" OR "SOC" OR "fast charg*" OR "DC charg*" OR "AC charg*" OR "electrical odor" OR "burning odor" OR "foul odor"). Need include "any form of words" so stem. Maybe use search engine syntax: (batter* OR heat* OR smok* OR fire* OR charg*) AND (osprey* OR "osprey ev" OR osr-* OR "osprey program" OR "osprey battery" OR "osprey pack") AND NOT (list of excluded newsletter senders?) Need include exclusion filters: exclude mass mailing lists, cafeteria notices, safety training lists, routine charging reminders? But cannot exclude if responsive? Use filters: sender domain list-server@oriele? OR subject contains "fire drill" OR "routine charging reminder" OR "parking" etc? Need be careful. Could propose: initial search will apply exclusionary terms for nonresponsive routine communications: "fire drill", "fire alarm maintenance", "evacuation", "parking", "charging reminder", "EVSE schedule", "fleet charging schedule"? But routine charging reminders may be about charging, maybe not relevant to safety? Could be false positives. Law permits search design. Need propose sampling to validate.

Maybe better: Use tiered terms:
Tier 1 (direct Osprey thermal/battery events): (osprey* OR OSR-*) AND (batter* OR heat* OR smok* OR fire* OR charg* OR thermal* OR "thermal runaway" OR overheat* OR spark* OR flame* OR burn* OR melt* OR "HV" OR "high voltage" OR BMS OR cell OR module OR pack OR "state of charge" OR SOC OR "electrical odor" OR "burning odor").
Tier 2 (Osprey battery/charging generally): (osprey* OR OSR-*) AND (batter* OR charg* OR HV OR BMS OR cell OR module OR pack OR thermal OR heat OR temperature OR smoke OR fire).
But the subpoena demands any form of battery heat smoke fire charge. Need produce responsive nonprivileged. Could say initial search will include the subpoena terms, but limited by Osprey relevance and custodians. Need not propose only Tier 1 if request terms are broader. We can propose: search for any form of battery, heat, smoke, fire, charge, in documents also referencing Osprey or Osprey battery/charging systems, plus synonyms. That narrows.

Need maybe produce sample: random sample of 200 potentially responsive documents to confirm terms/custodians. Good.

Request 2 privilege: Need maybe many privileged. Need log.

Request 3: Need maybe specific categories:
- Will produce: (i) nonprivileged communications with lawyers that are purely factual: incident facts, test data, photographs, customer/reseller complaint facts, compliance/business decisions, engineering data; (ii) communications concerning legal advice? no, withhold; (iii) documents copied to counsel but not for legal advice: produce; (iv) underlying facts in mixed documents.
- Will withhold: confidential legal advice and requests for it from/to any lawyer (internal/external); work product (memos/analyses prepared primarily because of anticipated enforcement/litigation, including counsel's risk assessments, strategy, legal interpretations of reporting duties/recall obligations). Need maybe "any form of communication with lawyer" includes nonprivileged business decisions. Need log.
- Investigate: identify all lawyers (outside counsel, reseller counsel? maybe consultants?) and communications; determine whether non-Oriole entity communications are protected; identify mixed documents. Need maybe not state all withheld.
- Proposed response: produce nonprivileged within 14 days from identified custodians? Need concrete: produce nonprivileged responsive communications from Osprey engineering, quality, compliance, field service, and GC from Jan 1 2022 through production date concerning listed topics; log privileged; for 2018-2021, produce after search if relevant; maybe produce factual incident reports first. Need maybe limit to communications concerning Osprey and events, not all battery safety? Request says concerning battery safety, product compliance, reporting duties, recalls, customer complaints, or three events. That's broad. Could object as overbroad? It may reach all company legal communications on battery safety for all vehicles 2018-2026. But investigation Osprey. Need narrow: limit to Osprey battery system, Osprey events, and Osprey-related customer complaints/reporting duties/recalls; pre-2022 design if relevant. But request doesn't limit to Osprey, says battery safety etc. Need precise ground: overbroad as to non-Osprey vehicles and pre-2022 absent relevance. But some product compliance/reporting duties may be company-wide. Need propose: Phase 1 Osprey and three events from Jan 1 2022; Phase 2 if Office identifies issue, include other vehicles/reporting obligations. Need produce nonprivileged.

Need maybe mention "all communications between Oriole and any lawyer" includes communications with reseller's lawyers? If reseller counsel not company counsel? Privilege may not apply. Need investigate. But not necessary.

Request 4: Board/safety committee. Need propose produce all nonprivileged responsive board/safety committee materials from Jan 1 2022 through 2026 (and pre-2022 design if identified). Withhold/log privileged counsel attachments and portions. Need mixed presentations: redact. Need maybe produce minutes as received, redacting privileged discussions? But board minutes are business documents. If they contain legal advice from counsel present, redact. If attendance by counsel? Not all privileged. Need log.

Request 5: Need detailed.
- Will produce: complete incident database records for three events and substantially similar Osprey events; test results/source data/photos/metadata. Need define format: native formats, load files, database extract, metadata. Need maybe produce within 8 days the three events. For substantially similar, propose within 21 days? Need concrete. Since response due 14 days, maybe produce three events with response; substantially similar within 21 days after agreement. But assignment asks response due in 14 days; can propose phased production. Need state "Oriole can and will produce the three event records within eight days of the date of this response." Good.
- Objection: "substantially similar" vague; need definition. Propose: Osprey vehicle events involving battery pack, high-voltage system, charger, BMS, or electrical system that produced heat/smoke/fire/spark/electrical odor/melting, or classified under incident codes T1-T5? Need maybe define by fields: event type includes thermal, battery, charging, HV arc, odor; or same battery pack design revision, charger model, BMS software version. Need maybe produce using existing incident classification: "thermal/battery/charging/electrical" incident codes. Need concrete.
- What withhold: any records prepared primarily because of anticipated enforcement/litigation, e.g., counsel-directed forensic test reports or analyses; log. But ordinary incident data and product testing produce. Need maybe no broad privilege.
- Investigate: identify all substantially similar events across regions/resellers; validate definitions; collect metadata; source data from engineering repo; determine whether any test results are work product.
- Phased: Phase 1 three events within 8 days; Phase 2 substantially similar within 21 days; Phase 3 source data/raw files if needed within 30 days. Need maybe include sampling.

Request 6: Need detailed as above.

Need also include privilege-log and clawback protocol separately. Let's design protocol:
- Privilege Log:
  - Provided in Excel/CSV with fields: Log ID, Bates/Doc ID, date, author/sender, recipients, cc, document type, title/subject, custodian, description of subject matter (without revealing legal advice), privilege(s) asserted (attorney-client, work product, both, mixed), basis (confidential communication for legal advice; prepared in anticipation of enforcement/litigation; mixed document), portion withheld (whole/redacted lines/pages), whether produced/redacted, date logged.
  - For attachments: separate log entries if distinct; if inseparable, log parent and describe attachment; produce nonprivileged attachments; redact privileged portions; if a document contains both privileged and nonprivileged, produce redacted version and log privileged portions.
  - For mixed legal-business presentations: produce nonprivileged factual slides/attachments; withhold/redact slides containing legal advice or work-product analysis; log each slide/portion.
  - Categorical logging: only with Office agreement; Oriole will not rely on categorical logging unless agreed in writing. If agreed for repetitive categories (e.g., identical boilerplate compliance notices), log category with date range, authors, recipients, description, privilege basis.
  - Timing: initial log within 7 days of initial production or simultaneously; rolling updates within 7 days after each production; final log within 10 days after final review. Maybe because due 14 days. Need be concrete: "with each production tranche, and in no event more than 7 days after a production; an updated log for newly identified withheld documents within 7 days." Good.
  - Subject matter stated without revealing advice: e.g., "Counsel's advice regarding reporting obligation under [regulation] following Event 1" maybe reveals? Need "legal advice concerning regulatory response to a field event" without stating advice. Need "work product: counsel's assessment of enforcement risk regarding battery events". Need enough facts. Could provide examples.
- Clawback:
  - Accept nonwaiver and clawback agreement. Scope: covers inadvertent production of privileged/work product or confidential information; does not protect unreasonable review or deliberate overproduction.
  - If Oriole identifies after production a document that should have been withheld, it will: promptly (same business day) notify Office; provide log entry/privilege legend; request sequestration, return, and destruction/non-use; preserve nonwaiver; not use produced material in any proceeding; if Office has disseminated, request deletion from derivative works? Need maybe.
  - If Office identifies, similar. Need maybe include "privilege review QA": three-pass? (1) collection and search; (2) first-pass responsiveness; (3) privilege review; (4) secondary QA sampling of 10% of produced documents and 10% of withheld? Need maybe too much. But law says clawback doesn't excuse unreasonable review; so show reasonable review. Could include: "privilege review by trained staff, QC review, random sampling, two-level review for mixed documents, redaction verification." Good.
  - Inadvertent production of nonprivileged but confidential? Nonwaiver maybe only privilege; but can include confidential business information? The Office offered nonwaiver and clawback likely for privilege. Need focus.

Need also include preservation statement: Oriole has issued/litigation hold preserving all potentially responsive sources, including custodians, databases, reseller complaint systems to extent identified, Emberline files, board materials. Need preserve while objections proceed.

Need also maybe include "control over third-party reseller data": Rule 7. Need specific facts: Oriole sells through independent regional resellers; some complaints may be stored in reseller ticketing systems. Oriole's file does not yet establish how many, whether contracts give right to retrieve, or which systems. Need state ongoing reasonable inquiry: identify resellers, review sales/support contracts, ticketing APIs, data ownership, request access, estimate volume. Until complete, Oriole cannot state such records are outside control. Will produce responsive nonprivileged reseller complaints after inquiry to extent within control; if not within control, will report findings. Need maybe propose timeline: complete reasonable inquiry within 21 days? Need concrete. The response due 14 days; can propose 30 days? Need reasonable. Since subpoena response due 14 days, can propose production schedule. Need maybe "reasonable inquiry into reseller systems will be completed within 21 days of the date of this response; if responsive records are within Oriole's control, production will follow within 10 days after inquiry." Need be careful not too slow? But okay.

Need also maybe include "search terms, custodians, date ranges" in a protocol section, as Office asked. Could integrate with Request 2 but also general. Need maybe list five initial custodians. Need maybe include "reasonable Osprey date range" and "proposed search terms" in response. Good.

Need think about possible pitfalls:
- Asserting work product for ordinary annual Emberline reports after litigation later arises: prohibited by Rule 5. Need not. We'll produce ordinary reports, only post-event litigation-risk engagement maybe work product. Need maybe if annual reports from 2020-2024 were prepared under standing contract before second event? Some after second event? Annual reports are routine; even if after second event, if ordinary course product testing, not protected merely because litigation arises. But if after second event, report may be prepared primarily because of anticipated enforcement? The facts say annual battery-validation reports 2020-2024 under standing engineering contract. After second event, outside counsel separately retained Emberline to analyze litigation and enforcement risk under new confidential engagement. So annual reports likely ordinary. The new engagement reports are work product. Need distinguish. If annual report in 2023 (after second event? When is second event? Not specified. Could be 2023? But annual battery-validation reports are routine regardless. Need say "annual battery-validation reports prepared under the standing contract are presumptively ordinary course; Oriole will review each report and supplement if any portion was prepared primarily in anticipation of enforcement. The separate litigation/enforcement-risk analysis is withheld as work product." That's safe.
- Attorney-client privilege for communications with Emberline? If retained by counsel for legal advice? Emberline is engineering, not lawyer. Communications with non-lawyer consultants can be part of attorney-client if necessary to facilitate legal advice? But work product more likely. Need not assert AC for Emberline unless counsel's legal advice. For Request 3, "any lawyer" only lawyers, not Emberline.
- Work product for board materials: if prepared primarily because anticipated litigation. Board materials in ordinary course business are not. Need evaluate.
- Metadata: generally produce, but metadata may contain privileged routing? Need maybe redact privileged metadata? Metadata can reveal attorney-client communication? Usually metadata is produced but can redact if it reveals privileged advice? We can say produce metadata; if metadata contains confidential legal advice (e.g., routing to counsel for legal advice) may log? But metadata is factual. Need not overdo. For Request 5, produce metadata. For Request 2, produce metadata? It's communications; produce nonprivileged with metadata. If metadata reveals privileged? Could redact? Need maybe include in protocol: metadata produced unless it independently reveals privileged legal advice; then redacted and logged. Good.

Need ensure final answer is "final form" maybe as letter/motion? Could be a formal response to subpoena. Need not be actual filing? It says draft in final form. We can produce as a document with headings. Need maybe not include analysis. Just draft.

Need decide on exact tone: "VIA EMAIL AND SERVICE". Add placeholders for dates, names. Since final form, maybe use [Date], [Office Name], [Subpoena No.]. Could include "Oriole Mobility, Inc." and "Federal Transport Safety Office". Need use fictional agency. Could write:

Federal Transport Safety Office
Attn: ...
Re: Administrative Subpoena No. [___] issued to Oriole Mobility, Inc.; Investigation of Osprey Battery Thermal Events
Date: [within 14 days]

Dear Counsel:
On behalf of Oriole ...

Then sections.

Need maybe include "We accept the Office's nonwaiver/clawback proposal as set forth in attached Protocol." But not actually attach? We can include protocol in draft.

Need ensure not object to every request and produce nothing. We will produce.

Need perhaps include a summary schedule:
- Within 8 days: Request 5 Phase 1 three events; maybe Request 6 ordinary Emberline? Could produce soon.
- Within 14 days: response and initial nonprivileged productions for Request 1 Osprey complaints? Need maybe. Since due in 14 days, can say with this response Oriole produces initial nonprivileged materials: Request 5 three events, Request 6 ordinary Emberline reports? But the assignment asks draft objections/responses, not actual production. But can state what will produce and schedule. Need maybe "Attached hereto: initial production for Request 5 Phase 1 and Request 6 ordinary reports"? But final form maybe includes schedule. We can say "Oriole will produce...".

Need maybe not overstate production before actually reviewed for privilege. But can state will produce after review. Since due 14 days, could produce initial tranches. But drafting assignment likely expects response document, not actual productions. We can state "with this response, Oriole submits initial nonprivileged production..." but we don't have actual docs. Better to state schedule.

Need include "no blanket privilege" language.

Let's craft detailed request-by-request.

Potential request 1 details:
- Objection: overbroad/burdensome as to (i) all Oriole vehicles, because investigation concerns Osprey battery thermal events and Osprey did not exist before Jan 1 2022; (ii) other vehicle lines using different battery systems absent specific relevance; (iii) no custodian/date/channel limit for reseller-stored complaints.
- Response: produce all responsive nonprivileged customer complaints in Oriole-maintained systems for Osprey from Jan 1 2022 through Dec 31 2026 that reference heat, smoke, fire, charging, batteries, or electrical odor, including complaint tickets, call notes, field service reports, warranty claims, and photos/attachments? Wait photos for complaints maybe. Need include "customer complaints" not necessarily attachments. But can include responsive attachments. Need produce. If complaint includes legal advice? log.
- Investigate: reseller ticketing systems: identify which resellers, systems, contracts, access, volume; determine control; preserve.
- Proposal: Phase 1: Osprey complaints from Oriole systems by [date] (e.g., 14 days). Phase 2: reseller complaints after reasonable inquiry within 30 days if within control. Phase 3: if Office needs comparative complaints for other vehicles, provide narrowed set limited to (a) vehicles sharing Osprey battery/charging/BMS platform, or (b) complaints with battery thermal symptoms and same complaint codes, from Jan 1 2022 (or 2018 if same platform existed?) Need concrete.
- Maybe "customer complaints concerning heat/smoke/fire/charging/batteries/electrical odor" for Osprey. Need include all channels? yes.

Potential request 2 details:
- Objection: overbroad/burdensome because 18M messages, no custodian/date, captures routine nonresponsive. Ground: grossly disproportionate.
- Response: produce nonprivileged responsive after reasonable search using proposed custodians/date/terms. Withhold/log privileged.
- Investigate: refine custodians/terms after initial sampling; identify additional custodians if Office identifies new issues; preserve.
- Proposal: Phase 1: initial custodians (list) and date Jan 1 2022-Dec 31 2026 (or production date), search terms; produce nonprivileged within e.g., 30 days? Need schedule. Phase 2: if needed, 2018-2021 for battery design/development custodians and terms; maybe after sampling. Need include sampling: 200-document sample. Need maybe exclude false positives via filters. Need produce no privileged.
- Need maybe state "Oriole will not produce the entire 18 million message set; it will produce responsive nonprivileged communications from proposed scope." Good.

Potential request 3 details:
- Objection: overbroad as to non-Osprey, pre-2022, and all lawyers; but main is privilege. Need precise: object to extent it seeks confidential legal advice/work product; object to overbreadth as to all Oriole vehicles/companies and pre-2022 absent relevance; respond otherwise.
- Produce: nonprivileged communications concerning Osprey battery safety, product compliance, reporting duties, recalls, customer complaints, three events, including factual incident reports, engineering data/test data, photos, business decisions, communications not for legal advice, documents copied to counsel. Withhold/log AC/WP.
- Investigate: all outside counsel, reseller counsel, consultants; mixed docs; work product.
- Proposal: Phase 1: communications concerning three events and Osprey from Jan 1 2022; Phase 2: other Osprey battery safety/compliance/recalls/complaints; Phase 3: pre-2021 design if Office identifies. Need maybe produce nonprivileged within 14 days? Could say "with this response, Oriole produces nonprivileged factual incident and compliance communications for the three events; additional tranches as schedule." Need not overcomplicate.

Potential request 4:
- Objection: to extent privileged; maybe no scope objection. Could say "No scope objection; object only as to privileged/work product and mixed materials." But assignment asks objections and responses. We can state "Object only as to privileged and work product; otherwise responsive." Need produce: all nonprivileged board/safety committee materials concerning Osprey battery system and three events, including minutes, decks, reports, data, from Jan 1 2022 (and 2018-2021 if design). Withhold/log: outside counsel legal advice, work product, portions. Mixed: redact.
- Investigate: pre-2022 materials; identify counsel attachments; mixed slides.
- Proposal: produce within 14 days all nonprivileged; log privileged with production.

Potential request 5:
- Objection: "complete incident database" ambiguous; "substantially similar" vague. Ground: vagueness/overbreadth if entire database. But request limits. Need propose definition.
- Produce: three event complete records within 8 days; substantially similar within 21 days; source data/photos/metadata. Withhold/log work product (counsel-directed forensic analyses) if any. Investigate: identify similar events, reseller events, source data, metadata, test results; determine WP.
- Proposal: definition of substantially similar; phased; format.

Potential request 6:
- Objection: to extent work product for litigation-engagement reports; not to ordinary reports. Need produce ordinary annual validation reports 2020-2024; investigate 2018-2019, 2025-2026, any reports. Withhold/log work product from new confidential engagement (litigation/enforcement risk). Mixed: produce underlying test data; redact analytical portions prepared for litigation.
- Proposal: Phase 1 ordinary reports; Phase 2 log; if Office disputes, meet and confer.

Need maybe include "privilege log and clawback protocol" after requests.

Need think about schedule consistency. Let's set dates relative to response date:
- Response date: [Date].
- Request 5 Phase 1 (three events): within 8 days of response (or with response if possible). Since preliminary collection shows can be collected within eight days. Could say "Oriole will produce Phase 1 by [Date + 8 days], i.e., before or within the 14-day response period." Good.
- Request 6 ordinary Emberline reports: within 14 days? Could be with response? We can say "by [Date + 14 days]".
- Request 4 board/safety: within 14 days? Could be.
- Request 1 Osprey complaints: within 14 days? Need collect/reseller? Oriole-maintained maybe within 14 days. Reseller inquiry 21/30 days.
- Request 2: initial search and production maybe 30-45 days after agreement. But response due 14 days; propose schedule. Need not produce all within 14. Could say "initial production of nonprivileged communications from Phase 1 custodians/date range within 30 days of agreement; rolling productions." Since 18M impossible. Good.
- Request 3: nonprivileged communications within 30 days? Need maybe. But to show cooperation, maybe produce factual incident/legal-related communications for three events within 14 days; broader within 30.

Need maybe not specify exact dates to avoid unrealistic. But assignment asks concrete. Use relative days.

Need consider legal standard: administrative subpoena, not litigation? Work product protects material prepared primarily because of anticipated litigation or enforcement. Here administrative subpoena for safety investigation/enforcement, so work product applies if anticipated enforcement. Need state.

Need maybe include "privilege does not protect underlying incident facts, ordinary engineering data, final business decisions, or documents merely copied to counsel" in protocol. Good.

Need maybe include "categorical logging not permitted unless agency agrees" in protocol. We can say "Unless Office agrees in writing to categorical logging, Oriole will log each document or portion. If Office agrees, categorical entries will include ...".

Need maybe include "sufficient facts to evaluate claim" examples. Could list:
- Log entry: Date; Sender/Author; Recipients; CC; Document Type; Description: "Email from outside counsel to product compliance director concerning legal interpretation of agency reporting deadline after Event 2"; Privilege: Attorney-Client; Basis: confidential communication between client and counsel for purpose of legal advice; Portion: entire message; Produced: No.
- Work product: "Report by Emberline retained by counsel assessing likelihood and exposure of enforcement action based on Event 2 test data"; WP; Basis: prepared primarily in anticipation of administrative enforcement; Underlying test data produced separately.
Need be careful: description should not reveal legal advice. "Legal interpretation of reporting deadline" maybe reveals advice? It states subject matter, not advice. Acceptable. Need not say "counsel advised that no recall is required". Good.

Need maybe include "subject matter stated without revealing advice" as requirement.

Need maybe include "treatment of mixed documents and attachments":
- For a document containing both nonprivileged and privileged content: produce nonprivileged; redact privileged; log redacted portions; if redaction would destroy meaning, produce nonprivileged portions and withhold entire? But law says produce responsive nonprivileged even when object to another portion. So redact.
- Attachments: separate log if attachment is discrete document; produce nonprivileged attachments; if attachment is privileged, log and withhold; if attachment contains underlying facts and legal advice, redact.
- Board presentations: produce factual slides/attachments; redact legal advice slides; log.
- Emails: if body contains legal advice, redact; produce underlying attached data.

Need maybe include "metadata and production format":
- Produce in native format with metadata where feasible; for email, PST/MBOX; for database, extract/load file; for test data, native or CSV; for photos, native with EXIF. If metadata reveals privilege, redact and log. Good.

Need maybe include "review protocol" to show reasonable:
- Collection from custodians/databases; date/custodian filters; search terms; deduplication; first-pass responsiveness; privilege review; QC sampling; privilege log; clawback.
Need maybe not too long but final answer can be thorough.

Need maybe include "preservation and control":
- "Oriole has preserved all potentially responsive sources, including emails, collaboration, ticketing, incident DB, engineering repos, board materials, Emberline files, reseller systems identified or to be identified."
- "Reasonable inquiry into reseller control: ... We have begun review of reseller agreements, ticketing APIs, data processing addenda, and support workflows. We have not yet established volume, systems, or contractual right. Until inquiry complete, we do not represent that such records are outside Oriole's control. We will report findings and produce within-control responsive nonprivileged records."

Need maybe address "company must preserve all potentially responsive sources while objections and negotiations proceed." Include.

Need maybe address "clawback does not excuse unreasonable review or deliberate overproduction". Include in protocol: "Oriole will not rely on clawback for documents produced due to failure to conduct reasonable review; review is reasonably calculated." Good.

Need maybe include "no blanket privilege" in each request.

Need maybe think about possible issue with Request 3: "All communications between Oriole and any lawyer concerning battery safety..." Could be work product/AC. Need maybe produce nonprivileged communications that are not confidential? For example, communication with lawyer in front of third parties not privileged? But all communications with lawyer concerning legal topics might still be nonprivileged if not confidential or not for legal advice. Need state. Could include "Oriole will produce nonprivileged communications, including communications made in the presence of third parties where confidentiality is not maintained, communications seeking or providing factual information, and business decisions." Good.

Need maybe include "recipients" in log: if privileged communication with third party (e.g., counsel present with non-client), log and explain why privilege maintained? Maybe.

Need maybe include "work product log" separate? Could be one log with privilege asserted. Good.

Need maybe include "subject matter stated without revealing advice" for categorical? If agency agrees categorical, include category, date range, author/recipient, type, subject, privilege basis. Good.

Need maybe include "If the Office challenges, meet and confer and produce nonprivileged portions; if privilege cannot be determined, perhaps produce under privilege? No, can't. Could propose in camera? Administrative subpoena? Maybe not. Could say "if dispute remains, parties may seek appropriate relief; Oriole will segregate." Not necessary.

Need maybe consider "Federal Transport Safety Office" administrative subpoena. Could be analogous to FOA? Need not cite cases. Use governing law only.

Need maybe ensure final answer is not too terse. Desired oververbosity 9, so detailed.

Let's outline final document:

[Header]

I. Introduction and Preservation
- Represents Oriole, responds to subpoena, agrees to nonwaiver/clawback, proposes narrowing.
- Preservation and reasonable inquiry into reseller control.
- General production protocol (format, redactions, privilege log, schedule).

II. Request-by-Request Objections and Responses
For each:
A. Request 1
1. Objection
2. Response/production
3. Withholding
4. Investigation
5. Proposal
B. Request 2
...
C. Request 3
...
D. Request 4
...
E. Request 5
...
F. Request 6
...

III. Privilege Log and Clawback Protocol
A. Privilege Log Requirements
- fields, examples, mixed docs, attachments, categorical, timing.
B. Clawback and Inadvertent Production
- agreement scope, QA, process, no waiver for deliberate/unreasonable.
C. Search Terms, Custodians, Date Ranges (maybe here or in Request 2)
- list five custodians, date range, search terms, sampling.

Maybe put Search Terms/Custodians in Section II.B or separate "Office's Requested Items". Since Office asked identify five custodians, date range, search terms. Could include a separate section "Proposed Search Parameters" before or after Request 2. But assignment asks draft objections/responses and protocol. We can include in Request 2 and also summary.

Need maybe include "five initial custodians" with titles, not names? Could use placeholders: [Name], Chief Engineer. Final form can have placeholders. But maybe better use titles and placeholders for names. Since fictional, can use "[Name 1]". The user likely expects drafting with placeholders. Use bracketed placeholders for specific names/dates. But final form maybe can use generic titles. Need concrete. We can list:
1. [Name], Chief Engineer, Osprey Program
2. [Name], Lead Engineer, Osprey Battery System
3. [Name], Lead Engineer, Charging and High-Voltage Systems
4. [Name], Director, Field Quality and Service
5. [Name], Director, Product Compliance and Safety Reporting
Need maybe include "General Counsel"? But Request 2 company communications may include GC; if not initial custodian, maybe still search? Could include GC as sixth? Office asks five initial custodians. Need choose five most relevant. Maybe include GC because Request 3? But for Request 2, GC may have legal communications; but those are covered by Request 3 and privilege. If GC has nonprivileged business communications, maybe. But to minimize privilege log, maybe not. However if GC communications about battery safety nonprivileged, could be responsive. But we can include GC as initial custodian? Then more privilege review. Need five: Chief Engineer, Battery Engineer, Charging Engineer, Field Quality, Compliance. Good. Could add "General Counsel will be included for Request 3, not as one of five initial Request 2 custodians"? But Office asked five initial custodians generally. Maybe include "Initial custodians for nonprivileged company communications: ..." and "GC for legal communications under Request 3." Good.

Date range: "January 1, 2022 through the date of production, and no later than December 31, 2026, as the reasonable Osprey commercial-service date range; for design/development, optional 2018-2021 limited to identified custodians and terms." Need include.

Search terms: Need maybe present in a table.

Let's draft search terms carefully:
"Osprey relevance terms": osprey*, "osprey ev", "osprey battery", osr-*, "osprey program", "osprey van", model/design codes in Oriole's engineering system.
"Subpoena terms (with stems/variants)": batter*, heat*, smok*, fire*, charg* (to capture battery/batteries, heat/heating/overheat, smoke/smoked, fire/fires/firefighting, charge/charging/charger).
"Technical context terms": thermal*, "thermal runaway", overheat*, temperature*, spark*, flame*, burn*, melting, HV, "high voltage", BMS, battery management system, cell, module, pack, "state of charge", SOC, DC fast charg*, AC charg*, "electrical odor", "burning odor", "foul odor", "insulation", "arc", "smell", "odor".
"Exclusionary filters": routine administrative false positives: "fire drill", "fire alarm maintenance", "evacuation", "cafeteria", "parking", "routine charging reminder", "scheduled charge", "charge schedule", "battery backup", "UPS" (uninterruptible power supply), "firewall" (IT), "fire extinguisher", "fire code", "fire watch", "charging station maintenance"? Need not over-exclude. But if exclude "charging" routine? The request includes charging; but routine charging reminders not relevant to safety. Could use exclusionary terms plus human sampling. Need propose: initial filters exclude messages solely matching "fire drill", "fire alarm", "evacuation", "fire extinguisher", "fire code", "firewall", "UPS", "battery backup", "scheduled charge", "charging reminder", "parking", "cafeteria", "HVAC" unless also contains event/battery terms. But if a message says "fire drill" and "battery" maybe maybe not. Use NOT filters only if no event terms. Need maybe: apply NOT for routine administrative terms where they appear without any of the technical/event terms. But search syntax complex. We can describe: "Exclusionary terms will be applied only where a document does not also contain Osprey or technical event terms; e.g., messages about fire drills, fire alarms, fire extinguishers, firewalls, UPS, routine charging reminders, parking, cafeteria, HVAC, or general safety training will be excluded from first-pass production unless they also reference an Osprey vehicle, battery/charging system, or event." Good.

Need maybe include "proximity/phrase" options? Could propose phrase searches: "thermal event", "battery fire", "smoke from battery", "charging incident", "overheat", "electrical smell". But the subpoena terms are broad. We can include "supplemental phrase searches" to capture synonyms. Good.

Need maybe include "sampling": random sample of 200 produced/withheld? Let's specify: "After first search, Oriole will sample 200 potentially responsive messages for responsiveness and privilege calibration; if precision below 80% or recall issue, adjust terms and repeat." Maybe too specific. But concrete.

Need maybe include "phased production for Request 2": Phase 1: initial custodians/date range, produce nonprivileged by 30 days; Phase 2: additional custodians/date 2018-2021 if Office identifies issues, by 45 days. Good.

Need maybe include "what will withhold" for Request 2: AC/WP. Need not assert privilege over facts. Good.

Need maybe include "reseller control" in Request 1 and preservation. Need maybe in general section: "Control over reseller ticketing systems is being investigated. We have not established ... We do not state that such records are outside control. We will produce if within control." Good.

Need maybe include "privilege log fields" exactly as law: date, author, recipients, document type, subject matter stated without revealing advice, privilege asserted, sufficient facts to evaluate claim. Add Bates, custodian, etc.

Need maybe include "categorical logging only if agency agrees" and "if agreed, each category must still contain enough facts." Good.

Need maybe include "treatment of mixed documents and attachments" with examples:
- Board deck with 10 slides: produce slides 1-5 factual; redact slide 6 counsel advice; log slide 6; produce attachments if nonprivileged.
- Email from counsel: body privileged; attached engineering test data nonprivileged; produce data, withhold body; log body.
- Incident report with counsel comments: produce report, redact counsel comments; log comments.
Good.

Need maybe include "timing": initial log with initial production; rolling updates; final. Need maybe "within 7 days after production". Good.

Need maybe include "inadvertent production" process:
1. Identify (internal review, Office notice, QA sample).
2. Notify Office promptly with document ID, privilege basis, request.
3. Seek sequestration/return/destruction, non-use, non-disclosure, return of derivatives.
4. Log as corrected/withheld; no waiver under agreement.
5. If Office disputes, meet and confer; preserve.
Need mention "clawback not available for deliberate overproduction or unreasonable review; Oriole will conduct reasonable review and will not invoke for known privileged documents." Good.

Need maybe include "nonprivileged material that is reasonably available must be produced even when objects to another portion". We can state in general.

Need maybe include "no blanket privilege" language: e.g., "Oriole does not assert privilege over underlying facts, ordinary engineering data, final business decisions, or documents merely copied to counsel." Good.

Need maybe include "work product ordinary course": "Annual Emberline validation reports are ordinary course; not work product merely because events later occurred." Good.

Need maybe include "privilege for documents merely copied to counsel": produce. Good.

Need maybe think about potential need to mention "legal advice and requests for it" protected. Good.

Need maybe include "final form" with signature block.

Need maybe ensure not to say "we will not produce reseller records because outside control". Instead: "ongoing inquiry; will produce to extent within control after inquiry; if inquiry concludes not within control, we will report and not produce, but for now no representation." Good.

Need maybe include "the company must preserve all potentially responsive sources while objections proceed" in preservation.

Need maybe include "If Office objects to narrowing, meet and confer." Good.

Let's think of each request in more legal detail to ensure precise objections:

Request 1:
- It seeks "All customer complaints concerning heat, smoke, fire, charging, batteries, or electrical odor for every Oriole vehicle from 2018 through 2026." 
Potential objection: overbroad as to (a) non-Osprey vehicles because no showing of relevance to Osprey thermal events; (b) pre-2022 Osprey (nonexistent); (c) all complaints regardless of source/channel/custodian, including reseller systems not yet in control. Need not object to Osprey complaints. Need propose: limit to Osprey vehicles Jan 1 2022-Dec 31 2026; if agency wants other vehicles, limit to vehicles with same battery/charging platform or complaints involving battery thermal symptoms. Need maybe include "complaints concerning charging" for other EV lines might be relevant to company-wide charging practices? But if different battery systems, maybe not. Could propose a two-tier: first produce Osprey; then if agency identifies a specific hypothesis (e.g., common charger supplier, BMS software, manufacturing process), produce complaints for vehicles using that component. Need concrete: "For other vehicle lines, Oriole will produce complaints that (i) use a battery pack, charger, BMS software, or cell supplier shared with Osprey, or (ii) involve the same incident codes for heat/smoke/fire/charging/electrical odor, after a cross-reference of platform components." But we don't know shared components. Facts say four vehicle lines use different battery systems. Could still share charger? Need not assume. We can say "if the Office can identify shared battery/charging architecture or common component, Oriole will produce narrowed comparative set." Good.
- What produce: "all nonprivileged responsive complaints for Osprey in Oriole-maintained systems, including web, phone, email, field service, warranty, reseller-forwarded complaints, with attachments (photos, logs) unless privileged." Need maybe "customer complaints" can include reseller-forwarded. Good.
- What withhold: "any complaint communication containing confidential legal advice or work product; log." Could be rare.
- Investigate: reseller systems; volume; contracts; access. Also identify complaint classification codes. Good.
- Proposal: Phase 1: Osprey complaints within 14 days; Phase 2: reseller complaints after reasonable inquiry within 30 days if within control; Phase 3: optional comparative non-Osprey if Office identifies shared platform/symptoms, within 30 days after definition. Good.

Request 2:
- It seeks "All company communications containing any form of words battery, heat, smoke, fire, or charge, without custodian or date limitation." 
- Objection: overbroad/burdensome, 18M, routine false positives, grossly disproportionate. Need maybe also vague? "company communications" could include all employees, all platforms, all time. But precise ground: overbreadth/burden.
- Response: produce nonprivileged responsive after narrowed search. Withhold/log AC/WP.
- Investigate: refine custodians, terms, false positive rates, additional custodians, platforms. 
- Proposal: as above. Need maybe state "Oriole will not produce cafeteria notices or routine charging reminders unless they also reference Osprey battery/thermal/charging system or event." Good.
- Need maybe "company communications" includes internal and external. We'll include external to customers/resellers? If nonprivileged. But maybe external customer communications are in Request 1? Could include. We'll search.
- Search terms need include "any form" of words; but we limit by Osprey. Need maybe if agency insists on all, Oriole will meet and confer. Good.

Request 3:
- It seeks all communications between Oriole and any lawyer concerning battery safety, product compliance, reporting duties, recalls, customer complaints, or three events.
- Objection: overbroad as to all vehicles/time; privileged. But need precise. Could say "Object to the extent it seeks (i) confidential attorney-client communications and work product; (ii) communications concerning non-Osprey vehicles or pre-2022 period absent relevance; (iii) communications that are not confidential or not for legal advice are not privileged and will be produced." Hmm objecting to non-Osprey as overbroad. Need respond.
- Produce: nonprivileged communications. Need define categories:
  1. Factual incident communications: descriptions of events, root-cause findings, test data, photos, engineering analyses not prepared for litigation.
  2. Business/legal compliance communications that are final business decisions or ordinary compliance reports, not legal advice.
  3. Documents copied to counsel for non-legal purposes.
  4. Communications with non-lawyer consultants? Wait Request 3 only lawyer. But if Emberline retained by counsel? Not a lawyer. Not under Request 3 unless communication with lawyer about Emberline. Could be.
- Withhold: AC: confidential legal advice/requests; WP: materials prepared primarily because anticipated enforcement/litigation (e.g., counsel's legal risk memos, regulatory exposure, strategy). Need not withhold underlying facts. 
- Investigate: identify all outside counsel and law firms; reseller counsel? Determine confidentiality; identify mixed documents; determine work product. 
- Proposal: Phase 1: communications concerning three events from Jan 1 2022, produce nonprivileged factual within 14 days; log privileged. Phase 2: communications concerning Osprey battery safety/compliance/recalls/complaints within 30 days. Phase 3: pre-2021 design if Office identifies. Need maybe "any lawyer" includes in-house and outside. Good.

Request 4:
- It seeks all board and safety-committee materials concerning Osprey battery system and three events.
- Objection: to extent privileged/work product; maybe overbreadth? Not much. Could state "No objection as to scope except that 'materials' includes attachments; Oriole will produce nonprivileged responsive. Object only as to privileged/work product." But assignment asks objections; can be narrow. Need maybe object to "all" as overbroad if includes pre-Osprey? But it's concerning Osprey battery system and three events, so likely from 2022. Could include pre-2022 design board materials. Need maybe propose date range. 
- Produce: ordinary board minutes, safety committee decks, reports, data, engineering summaries, business decisions, from Jan 1 2022 (and pre-2022 design if responsive). 
- Withhold: outside counsel attachments containing legal advice; portions of presentations containing counsel's legal advice or work product; log.
- Investigate: pre-2022, mixed decks, counsel attendance.
- Proposal: produce nonprivileged within 14 days; log privileged.

Request 5:
- It seeks complete incident database, test results, source data, photos, metadata for three events and substantially similar Osprey events.
- Objection: "substantially similar" vague; "complete incident database" could be read as entire database. Ground: vagueness/overbreadth. Need propose definition.
- Produce: three event complete records within 8 days; substantially similar within 21 days; source data/metadata/photos. 
- Withhold: work product test analyses prepared primarily in anticipation of enforcement; log. 
- Investigate: identify all similar events, source data, reseller events, metadata, test results, determine WP.
- Proposal: define substantially similar:
  (a) Osprey vehicles; (b) event involving battery pack, high-voltage system, charger, BMS, or electrical system; (c) symptom: heat, smoke, fire, spark, melting, electrical odor, or thermal classification; (d) same battery pack design revision, charger model, BMS software/firmware version, or cell supplier, or same incident code for thermal/battery/charging. Maybe need not too narrow. "Substantially similar" should be objective. Could propose: "events in which an Osprey battery pack, high-voltage component, or charger produced abnormal heat, smoke, fire, spark, melting, or electrical odor, or was disabled/recalled/replaced for thermal/battery/charging cause, or events sharing the same battery pack design revision, charger model, or BMS/firmware version as the three events." Good.
- Phase: Phase 1 three events by day 8; Phase 2 similar events by day 21; Phase 3 raw source data by day 30 if needed. Good.

Request 6:
- It seeks all reports by Emberline concerning Osprey batteries.
- Objection: to extent work product; maybe not overbroad. Need produce ordinary.
- Produce: annual battery-validation reports 2020-2024 (and any ordinary course 2025-2026 or 2018-2019 if exist) that were prepared under standing contract in ordinary course. Include underlying test data, raw data, photos if in reports? If reports include attachments. 
- Withhold: reports/analyses from separate confidential engagement after second event by counsel to analyze litigation/enforcement risk, if prepared primarily in anticipation; log. Also any portions of ordinary reports containing counsel's legal advice? unlikely; if present, redact/log.
- Investigate: whether any annual reports were revised/supplemented after events for litigation; identify all Emberline reports, including 2025-2026; determine WP; separate underlying data.
- Proposal: Phase 1 ordinary reports within 14 days; Phase 2 log for litigation-engagement; if Office disputes, meet and confer. Need maybe produce underlying test data from work product reports separately if nonprivileged. Good.

Need maybe include "privilege log for Emberline work product reports" with description: "Emberline report retained by counsel assessing enforcement risk arising from Event 2 battery test data" etc.

Need maybe include "nonwaiver/clawback agreement" offered by Office. We should state accept, but with protocol. Good.

Need maybe include "meet and confer" and "negotiations". Good.

Potential final document length: likely 3000-5000 words? Desired oververbosity 9. We can produce a detailed document maybe 4000-6000 words. Need be concise enough but thorough. Token budget large. We can write ~5000 words. Need ensure final answer not analysis. Use clear headings.

Need maybe include placeholders like [Date], [Subpoena No.], [Name]. That's acceptable. Could use generic "Oriole Mobility, Inc." and "Federal Transport Safety Office". Need final form maybe no brackets? But names/dates unknown. Use bracketed placeholders for unknown. The user likely expects a draft with placeholders. Could also use "________". Use [Date], [Subpoena No.], [Office Contact]. Good.

Need maybe not mention "fictional" in document. Just draft.

Need maybe include "CC: ...".

Let's think if any governing law nuance:
1. Subpoena material reasonably relevant. Investigative relevance broad, but demand may be narrowed when scope, custodians, time, or search design creates burden grossly disproportionate. We use this.
2. Objection must identify particular request, precise ground, proposed response. We do.
3. Must produce responsive nonprivileged reasonably available even when objects to another portion. We do: redact, produce portions.
4. AC protects confidential legal advice and requests for it. Does not protect underlying facts, ordinary engineering data, final business decisions, docs copied to counsel. We do.
5. WP protects material prepared primarily because anticipated litigation/enforcement. Ordinary product testing not protected. We do with Emberline.
6. Privileged material withheld only with log fields; categorical only if agency agrees. We do.
7. Reasonable inquiry before stating not in control; control over third-party platform data depends on contractual/practical right. We do reseller.
8. Clawback protects against waiver from inadvertent production, not unreasonable review or deliberate overproduction. We do.
9. Preserve all potentially responsive sources. We do.
10. Counsel should propose concrete limits. We do.

Need maybe ensure "specific written objections and responses" for each request includes "what Oriole will produce, what it will withhold, what it will investigate, and concrete narrowing or phased-production proposal". We can format each request with these subheads to make clear. Good.

Need maybe include "privilege-log and clawback protocol" describing required log fields, treatment mixed docs/attachments, timing, handling inadvertent. Good.

Let's draft in final form.

Potential structure in detail:

[Letterhead]

VIA EMAIL

[Date]

Federal Transport Safety Office
Attn: [Name], Counsel
Re: Administrative Subpoena No. [___]; Oriole Mobility, Inc.; Osprey Battery Thermal Events

Dear Counsel:

This is Oriole's response... We accept nonwaiver... We have preserved... We make the following specific objections... 

A. General Protocol and Reasonable Inquiry
1. Scope and good faith
2. Preservation
3. Reseller control inquiry
4. Production format
5. Privilege and work product (no blanket)
6. Privilege log and clawback (see Section II)

B. Request-by-Request

Request 1:
- Objection: ...
- Response: produce ...
- Withhold: ...
- Investigate: ...
- Proposal: ...

Request 2:
- Objection: ...
- Response: ...
- Withhold: ...
- Investigate: ...
- Proposal: custodians/date/terms/phases/sampling.

Request 3:
...

Request 4:
...

Request 5:
...

Request 6:
...

C. Privilege Log and Clawback Protocol
1. Privilege Log
   a. Fields
   b. Mixed docs/attachments
   c. Categorical logging
   d. Timing
   e. Examples
2. Clawback/Inadvertent Production
   a. Acceptance and limits
   b. Review/QA
   c. Procedure
   d. No waiver for deliberate/unreasonable

D. Conclusion and requested agreement

Signature.

Need maybe include "Search Parameters" in Request 2. Could include table:
Custodians: list.
Date range: Jan 1 2022 to production date (Osprey commercial service), optional 2018-2021 for design.
Search terms: syntax.
Exclusions: ...
Sampling: ...

Need maybe use search syntax with wildcards. Let's craft a clear search terms paragraph:
"Initial Request 2 search will run on identified custodians' email, collaboration, and document-management systems for:
(osprey* OR "osprey ev" OR "osprey program" OR OSR-* OR "osprey battery" OR "osprey pack") AND (batter* OR heat* OR smok* OR fire* OR charg* OR thermal* OR "thermal runaway" OR overheat* OR spark* OR flame* OR burn* OR melting OR "high voltage" OR HV OR BMS OR "battery management system" OR cell* OR module* OR pack* OR "state of charge" OR SOC OR "DC fast charg*" OR "AC charg*" OR "electrical odor" OR "burning odor" OR "foul odor" OR "insulation" OR "arc" OR "temperature").
Because the subpoena uses the words battery, heat, smoke, fire, and charge, the search includes stems for those terms. The Osprey relevance term is used to exclude unrelated vehicles and routine messages. Supplemental phrase searches: 'thermal event', 'battery fire', 'smoke from', 'charging incident', 'overheat', 'electrical smell'. Exclusionary filters for routine false positives: 'fire drill', 'fire alarm', 'evacuation', 'fire extinguisher', 'fire code', 'fire watch', 'firewall', 'UPS', 'battery backup', 'scheduled charge', 'charging reminder', 'parking', 'cafeteria', 'HVAC', 'general safety training', unless the document also contains an Osprey, battery/charger, or event term."
Need maybe "any form" includes "firefighting" maybe not relevant; but if contains battery/fire? Could be. Fine.

Need maybe "date range" for Request 2: "January 1, 2022 through [production date], no later than December 31, 2026. If Office requires pre-commercial development, Phase 2: January 1, 2018-December 31, 2021, limited to same custodians plus design engineers and terms (battery pack design, cell, thermal, charge, fire, smoke) tied to Osprey platform." Good.

Need maybe "sampling": "After initial search, sample 200 potentially responsive messages (stratified by custodian and term) to calibrate; if less than 80% responsive, refine terms/exclusions and re-run; if privilege error rate above threshold, increase QA." Good.

Need maybe "phased production" for Request 2: "Phase 1 production within 30 days of agreement; Phase 2 within 45 days if Office requests development period." Good.

Need maybe include "what Oriole will produce" for Request 2: "responsive nonprivileged communications from Phase 1 scope; redacted privileged portions; metadata." Good.

Need maybe include "what will withhold": "confidential legal advice/requests; work product; log." Good.

Need maybe include "what will investigate": "additional custodians, terms, platforms, false positives, reseller? maybe not." Good.

Need maybe include "privilege log fields" exactly. Let's list:
- Log ID
- Bates/Doc ID
- Date
- Author/Creator/Sender
- Recipients (To/Cc)
- Document type (email, memo, report, slide, attachment, database record)
- Custodian
- Title/subject (non-revealing)
- Subject matter description (without revealing legal advice)
- Privilege(s) asserted (AC, WP, both, mixed)
- Basis/sufficient facts (e.g., confidential communication between client and retained counsel for legal advice; prepared in anticipation of Office enforcement)
- Portion withheld/produced (whole, redacted pages/lines/slides)
- Production status
- Date logged
Maybe "relationship of non-client third parties" if relevant. Good.

Need maybe include "subject matter stated without revealing advice" examples. Good.

Need maybe include "mixed documents" protocol:
- Identify discrete portions; produce nonprivileged; redact privileged; log each portion; if redaction leaves document unintelligible? Produce nonprivileged portions and log. If a single sentence contains both? Could redact? Need maybe "where a single sentence contains both privileged legal advice and nonprivileged fact, Oriole will produce the factual portion if it can be separated without revealing privilege; otherwise it will log the sentence as mixed and produce a redacted version that preserves the fact without revealing advice." Good.
- Attachments: separate log; produce nonprivileged; if attachment is privileged, withhold/log; if mixed, redact.

Need maybe include "timing" details:
- Initial log with initial production (or within 7 days after if voluminous). For each tranche, log before or with production. Rolling updates within 7 days. Final within 10 days after final production. If categorical agreed, log category with initial.
Need maybe because response due 14 days: "For tranches produced within 14 days, log will be provided simultaneously. For later tranches, log at least 7 days before production or simultaneously." Good.

Need maybe include "clawback" details:
- Oriole accepts nonwaiver and clawback as offered, to be incorporated. It protects inadvertent production of privileged/work product or confidential information? The agreement offered likely nonwaiver/clawback. We can say "as offered, and as set forth below." 
- Procedure: If inadvertently produced, Oriole will: (i) identify and sequester internally; (ii) notify Office in writing same business day (or promptly) with doc ID, privilege, request; (iii) request return/destruction, non-use, non-disclosure, deletion from derivatives; (iv) provide log; (v) if Office disputes, meet and confer; (vi) preserve nonwaiver. If Office discovers, same. 
- QA: "reasonable review" including collection, search, first-pass, privilege review, QC sampling, redaction verification. "Clawback will not be invoked for documents produced after a reasonable review indicated privilege, or for deliberate overproduction." Need phrase: "Oriole will not rely on clawback to cure a failure to conduct reasonable review or to produce documents it knew or should have known were privileged." Good.

Need maybe include "nonwaiver for inadvertent production" and "no waiver for nonprivilege?" Good.

Need maybe include "preservation" details:
- "Oriole has suspended routine deletion for all custodians, systems, databases, repositories, and reseller channels potentially responsive; litigation hold notice issued; preserves metadata, backups, Emberline files, board materials." Good.

Need maybe include "reseller control" specifics:
- "Oriole sells through independent regional resellers. Some complaints may reside in reseller ticketing systems. Our file does not yet establish (a) which resellers/systems store potentially responsive complaints, (b) the volume, or (c) whether Oriole contracts grant a right to retrieve or access them. We are reviewing reseller agreements, data-processing addenda, ticketing APIs, support workflows, and forwarding practices. Until that inquiry is complete, Oriole does not state that such records are outside its possession, custody, or control. After the inquiry, we will report which records are within control and produce responsive nonprivileged records from those systems." Good.
Need maybe timeline: "The inquiry is expected to be completed within 21 days; production of within-control reseller records within 10 days thereafter." Good.

Need maybe include "if the Office believes reseller records are within control, we can meet and confer; if needed, provide certifications." Good.

Need maybe include "no objection to reasonable subpoenas after narrowing". Good.

Let's consider if we need to mention "final business decisions" in Request 4/6. Yes.

Need maybe include "ordinary board minutes" produced. If minutes contain counsel advice, redact. Good.

Need maybe include "work product for board materials prepared primarily because anticipated litigation". E.g., safety committee materials after events prepared with counsel. Need log.

Need maybe include "test results in ordinary course" not privileged. Good.

Need maybe include "source data" for Request 5: raw data may be voluminous; propose load files, native, or database extract. Good.

Need maybe include "metadata" for Request 5: produce full metadata for three events; for similar events, produce standard metadata; if metadata contains privilege, redact/log. Good.

Need maybe include "photographs": produce; if photo contains privileged annotation? redact? Usually produce. Good.

Need maybe include "incident database" for Request 5: if complete database includes unrelated events, object; produce extract of in-scope events. Good.

Need maybe include "substantially similar" definition in Request 5. Good.

Need maybe include "Request 6: all reports by Emberline concerning Osprey batteries" may include reports not just validation but also post-event. Need propose produce ordinary; withhold WP. Good.

Need maybe include "privilege log for Emberline WP reports" description: "Emberline engagement report prepared under counsel's retention assessing litigation/enforcement risk from Osprey battery events; underlying test data produced separately in Request 5." Good.

Need maybe include "if Office disputes privilege, Oriole will segregate and meet and confer; if unresolved, seek appropriate review." Could include.

Need maybe think about administrative subpoena vs court: "appropriate review" maybe "administrative law judge" or "court"? Not needed.

Need maybe include "we request the Office's agreement to the proposed narrowing and production schedule." Good.

Potential final answer length: Let's draft with detailed bullets. Need ensure no missing elements.

Let's start writing in final. Need be careful with legal terms and not overstate. Use "Oriole will produce" not "will produce all". Use "to the extent responsive and nonprivileged".

Let's draft:

[Header]

I. Introduction
- We represent. This letter constitutes response due 14 days. We accept nonwaiver. We propose good faith. We preserve.

II. General Protocol
A. Preservation and control
B. Reasonable inquiry into reseller systems
C. Production format and privilege
D. No blanket privilege

III. Request-by-Request
Maybe combine with General? Let's make sections:
1. General protocol
2. Request-by-request
3. Privilege log and clawback protocol

Need maybe not too many sections.

Let's draft in polished legal style.

Detailed Request 1:

"Request 1. All customer complaints concerning heat, smoke, fire, charging, batteries, or electrical odor for every Oriole vehicle from 2018 through 2026.

Objection: Request 1 is overbroad and unduly burdensome to the extent it (a) reaches vehicles other than Osprey, (b) reaches the period before January 1, 2022 for Osprey (when Osprey was not in commercial service), and (c) reaches all complaint channels without a reasonably tailored source/custodian limit, including reseller systems not yet identified. The Office's investigation concerns three Osprey battery-thermal events; complaints for different vehicle lines with different battery systems are not shown to be reasonably relevant unless tied to a shared component, symptom, or event. 

Response/Production: Oriole will produce all responsive, nonprivileged customer complaints in Oriole-maintained systems for Osprey from Jan 1, 2022 through Dec 31, 2026 that reference heat, smoke, fire, charging, batteries, or electrical odor, including complaint tickets, call/email transcripts, field service/warranty reports, and nonprivileged attachments. 

Withhold: confidential legal advice/work product embedded in complaint handling; log.

Investigate: reseller ticketing systems ... 

Proposal: Phase 1 ... Phase 2 ... Phase 3 ..."

Need maybe "every Oriole vehicle" includes Osprey only? We'll state.

Request 2:
Need maybe include "18 million messages" in objection. Good.

Request 3:
Need maybe mention "any lawyer" includes in-house and outside. Good.

Request 4:
Need maybe no scope objection? But maybe object to privileged. We can say "Object only as to privileged/work product; otherwise responsive." But assignment says specific objections. It's okay to state limited objection. Could also object to "all board and safety-committee materials" if includes non-Osprey? But it's concerning Osprey. We'll state "No scope objection as to materials concerning the Osprey battery system and the three events; object as to privileged/work product and to the extent it seeks pre-2022 materials absent relevance." Good.

Request 5:
Need maybe object to vagueness. Good.

Request 6:
Need maybe object to WP only. Good.

Need maybe include "phased production" for each. Good.

Now privilege log protocol. Need maybe include examples. Let's write.

Potential examples:
1. Attorney-Client: "Email from outside employment? no, outside counsel to Director of Product Compliance concerning legal interpretation of agency reporting obligations after Event 2." That reveals subject but not advice. Good.
2. Work Product: "Memorandum prepared by counsel assessing likelihood and potential sanctions in an administrative enforcement proceeding based on Event 3 test data." Good.
3. Mixed: "Board deck: slides 1-4 produce; slide 5 redacted (counsel's legal advice regarding recall authority); slide 6 produce (test data)." Good.

Need maybe include "sufficient facts to evaluate claim" for each: e.g., "counsel retained for legal advice; communication confidential; purpose legal advice." For WP: "prepared after events and after subpoena/litigation anticipation; prepared by/for counsel; analytical." Good.

Need maybe include "categorical logging" protocol:
"Unless Office agrees in writing, Oriole will not use categorical logging. If agreed, categorical entry will include: category name, date range, custodians/authors, recipients, document type, privilege, description of subject matter, sufficient facts, number of documents, Bates range. Categorical logging will be used only for substantially similar routine documents (e.g., identical incident-report templates with only privileged comments)." Good.

Need maybe include "timing" as above.

Need maybe include "inadvertent production" procedure.

Need maybe include "nonwaiver agreement" acceptance. Good.

Need maybe include "if Office identifies privileged document, parties will meet and confer." Good.

Need maybe include "no deliberate overproduction" language.

Let's think if any issue with "produce nonprivileged communications between Oriole and any lawyer" - if a communication with lawyer is not confidential because third parties present, but still may be work product? Work product doesn't require confidentiality? It protects against opposing party, but administrative agency? Could be. We'll just say evaluate.

Need maybe include "documents merely copied to counsel" produce. Good.

Need maybe include "ordinary engineering data" produce. Good.

Need maybe include "final business decisions" produce. Good.

Need maybe include "underlying incident facts" produce. Good.

Potential challenge: Request 3 asks all communications between Oriole and any lawyer concerning battery safety etc. If a communication with lawyer contains underlying incident facts, the communication itself may be privileged if made for legal advice, even if facts are also elsewhere. But rule 4 says privilege protects confidential legal advice and requests for it; does not protect underlying incident facts. How to produce? We can produce underlying facts in separate nonprivileged documents; if the only source is privileged communication, maybe withhold the communication but produce facts if available. The rule says underlying incident facts not protected. But a privileged communication containing facts may still be protected as a communication? In many jurisdictions, facts are not privileged, but the document may be privileged if legal advice. Here governing law says "It does not protect underlying incident facts, ordinary engineering data, final business decisions, or documents merely copied to counsel." That implies if a communication contains underlying incident facts, those facts are not protected; but the legal advice portion is. Need redact. We can say "Oriole will produce the underlying factual information, including by producing separate nonprivileged incident reports or redacted factual portions of communications where separable; it will withhold only the legal advice/request." Good.

Need maybe include "if factual and legal advice are inextricably intermingled, Oriole will produce the facts to the extent it can be done without revealing advice, and log the withheld portions." Good.

Need maybe include "business decisions": if a communication with lawyer includes a final business decision, produce decision; withhold advice. Good.

Need maybe include "work product for counsel's mental impressions" strong. Good.

Need maybe include "ordinary course test reports" not WP. Good.

Need maybe include "Emberline annual reports from 2020-2024 under standing contract" are ordinary. But what if after second event, annual reports include event-specific analysis? Need review. We'll state "Oriole will review each report to identify any portion prepared primarily because of anticipated enforcement; such portions will be logged, and underlying data produced." Good.

Need maybe include "new confidential engagement" reports are likely WP. Need not overstate "will withhold all" but "will withhold/log those prepared primarily because of anticipated enforcement". Good.

Need maybe include "if Office disputes, we can provide privilege log and meet and confer." Good.

Need maybe include "response due in 14 days" schedule. Could include a table at end:
- Day 0: response.
- Day 8: Request 5 Phase 1.
- Day 14: Request 4 nonprivileged, Request 6 ordinary, Request 1 Osprey (if ready), initial logs.
- Day 21: reseller inquiry complete.
- Day 30: Request 1 reseller if in control, Request 5 Phase 2, Request 2 Phase 1 initial production? Maybe.
Need maybe not too many dates. But concrete. Could include in each request.

Need maybe ensure schedule is reasonable. For Request 2 18M, 30 days for initial production after narrowing maybe reasonable. Could be 45 days. But response due 14; propose 30 days after agreement. Let's set:
- Request 5 Phase 1: 8 days.
- Request 5 Phase 2: 21 days.
- Request 4: 14 days.
- Request 6 ordinary: 14 days.
- Request 1 Osprey: 14 days; reseller after inquiry 21+10=31 days.
- Request 2 Phase 1: 30 days after agreement; sampling first 14? Could say "initial search within 14 days, production within 30 days".
- Request 3 Phase 1: 14 days for three events nonprivileged; Phase 2 30 days.
Good.

Need maybe include "rolling production" and "no later than [date]". Good.

Let's consider if "Request 2 returns approximately 18 million messages" includes all company communications. We propose initial search returns maybe manageable? We don't know. We can say "The proposed limits are reasonably likely to reduce the set to a manageable population; sampling will confirm." Good.

Need maybe include "search terms" for Request 1? Could include complaint fields: "heat, smoke, fire, charging, battery, electrical odor, thermal, overheat, burn, spark, melt, HV, BMS, cell, module, pack, SOC, charger, DC/AC charging". Good. But Request 1 is customer complaints; could propose search complaint text/fields. Include in Request 1 proposal: "search complaint fields/text for [terms]". Good.

Need maybe include "Request 5 incident database fields" maybe use existing codes. Good.

Need maybe include "Request 6 date range" 2020-2024 plus 2018-2019/2025-2026 if exist. Good.

Need maybe include "privilege log for Request 1 customer complaints" if legal advice? Could be minimal. Good.

Need maybe include "no blanket privilege over entire requests" in introduction. Good.

Potential final document:

```
[ORIole MOBILITY LETTERHEAD]
VIA EMAIL
[Date]
...
Dear Counsel:
...
I. General Statements
...
II. Request-by-Request
...
III. Privilege Log and Clawback Protocol
...
Respectfully,
...
```

Need maybe include "Enclosures: Initial Production ..."? Not necessary.

Let's draft in final now. Ensure no analysis. Use detailed but clear.

Double-check all user requirements:
- Draft final form: yes.
- 1. specific written objections/responses to Requests 1-6, stating what produce, withhold, investigate, concrete narrowing/phased proposal for each. We'll ensure each has those.
- 2. privilege-log and clawback protocol describing required log fields, treatment mixed docs/attachments, timing, handling inadvertently produced. Yes.
- Preserve legitimate privilege/WP without asserting blanket over facts, ordinary engineering, entire requests. Yes.
- Identify reseller-control facts under investigation and not state outside control before reasonable inquiry complete. Yes.

Need maybe include "Oriole's general counsel wants to object to every request and produce nothing" but we shouldn't follow; we draft proper. No need mention GC. Good.

Let's think if any potential conflict: "The Office has offered a nonwaiver and clawback agreement and asks Oriole to identify five initial custodians, a reasonable Osprey date range, and proposed search terms." We should explicitly answer: accept agreement, identify five custodians, date range, terms. We'll include in Request 2 and maybe summary. Good.

Need maybe include "five initial custodians" exactly. Use placeholders. Good.

Potential issue: "reasonable Osprey date range" could be 2022-2026. We'll state. But if Osprey development 2018-2021, we propose optional. Good.

Need maybe include "search terms" for all requests? The Office asked proposed search terms likely for communications. We'll provide for Request 2 and use similar for Request 1/5. Good.

Need maybe include "sampling" as required by rule 10. We'll include.

Need maybe include "phased production" for Request 2, 1, 5, 6, 3. Good.

Need maybe include "what will investigate" for Request 4? Yes: pre-2022, mixed, counsel attachments. Good.

Need maybe include "what will investigate" for Request 6: all reports, ordinary vs litigation. Good.

Need maybe include "what will withhold" for Request 4: privileged portions. Good.

Need maybe include "what will withhold" for Request 5: WP. Good.

Need maybe include "what will withhold" for Request 1: privileged if any. Good.

Need maybe include "what will withhold" for Request 6: WP. Good.

Need maybe include "what will withhold" for Request 2: AC/WP. Good.

Need maybe include "what will withhold" for Request 3: AC/WP. Good.

Need maybe include "what will produce" for Request 3: nonprivileged. Good.

Need maybe include "what will produce" for Request 6: ordinary reports. Good.

Need maybe include "what will produce" for Request 4: nonprivileged board/safety. Good.

Need maybe include "what will produce" for Request 5: database/test data. Good.

Need maybe include "what will produce" for Request 1: Osprey complaints. Good.

Need maybe include "what will produce" for Request 2: nonprivileged communications. Good.

Need maybe include "concrete narrowing or phased-production proposal" for each. Yes.

Need maybe include "specific ground" for each: overbroad/burdensome, vagueness, privilege/work product. Good.

Let's refine Request 3 objection: If we object as overbroad, need not assert privilege over all. "Request 3 is overbroad to the extent it reaches communications concerning non-Osprey vehicles and the 2018-2021 period without relevance, and it must be limited to nonprivileged materials because it includes communications that are not confidential legal advice or work product." Good. But maybe "all communications between Oriole and any lawyer concerning battery safety, product compliance, reporting duties, recalls, customer complaints" could be relevant company-wide. We can propose narrowing to Osprey and events, with optional other if agency shows relevance. Good.

Need maybe include "customer complaints" in Request 3? Communications with lawyer about customer complaints. We produce nonprivileged factual complaint info. Good.

Need maybe include "recalls" final business decisions produced. Good.

Need maybe include "reporting duties" legal advice withheld, but underlying facts produced. Good.

Need maybe include "product compliance" ordinary compliance reports produced. Good.

Potential issue: "any lawyer" could include reseller's lawyer not retained by Oriole; privilege may not apply. We can investigate. Good.

Need maybe include "work product for administrative subpoena" because anticipated enforcement. Good.

Let's draft final now. Need ensure final is not too informal. Use "we".

One more thought: The user asks "Draft, in final form:" maybe they expect not a memo but the actual response document. We'll produce as a letter/response. Good.

Let's write final with headings and detailed content. Use placeholders. Ensure no mention of analysis.

Proceed to final.