How to prepare a privilege review log for Product Liability Matters

Prepare a product liability privilege review log by separating routine engineering and business records from communications potentially protected by privilege or work product, verifying participant roles and purposes, and recording each decision against a stable document identifier. Assess attachments and mixed legal-business discussions separately, then draft descriptions that permit assessment without revealing protected substance. The deliverable is a log ready for counsel approval and service, reconciled to the production and supported by an internal decision record documenting evidence, uncertainties, and the governing protocol.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must describe responsive product records withheld or redacted for privilege or work-product protection. Triggers include reviewing failure-analysis correspondence, producing safety committee records, and reassessing engineering files containing communications with outside counsel. The task is to substantiate and describe protection decisions, not to decide product defect or causation.

The federal litigation baseline is Rule 26(b)(5)(A): expressly assert the protection and describe withheld material sufficiently to permit assessment without revealing protected information. Rule 26(f)(3)(D) includes compliance timing and method in discovery planning. Neither provision supplies a universal log format. Check local rules, orders, and agreements before selecting fields or grouping records. See Federal Rule of Civil Procedure 26.

Verify state-court and arbitral requirements separately. In federal civil litigation, Evidence Rule 501 makes state law govern privilege regarding claims or defenses for which state law supplies the rule of decision. Mixed federal and state claims require further analysis; do not choose privilege law from the court's location alone.

What you need

Assemble these inputs before substantive review:

• Controlling instructions: discovery requests and responses, local rules, orders, logging agreements, production specifications, and nonwaiver arrangements.
• Review population: stable document IDs, native records or readable images, metadata, email headers, attachments, family relationships, and proposed production identifiers.
• Product context: model and lot identifiers, alleged failure mode, incident dates, test programs, warning revisions, and engineering change identifiers.
• People and roles: counsel, engineers, quality personnel, safety committee members, suppliers, insurers, and consultants, including their roles when the records were created.
• Purpose evidence: engagement materials, investigation or testing instructions, and contemporaneous records explaining ordinary operational, legal-advice, or litigation purposes.

Include routine technical records alongside candidate protected communications. Reviewers need to distinguish an existing thermal-test report from a later request for advice about that report. Identify who can resolve missing roles, distribution-list membership, and commissioning instructions.

Use the template

Use Product Liability Matters — Privilege review log as the internal working template. You can copy this table into your working document or spreadsheet. It is a review record, not necessarily the version to serve.

Use stable IDs before production numbers exist. Identify the relevant message, page, or redacted passage in “Date / pinpoint”; distinguish document dates from incident dates. Record full author and recipient identities, including copied recipients, in the row or a linked participant register.

“Product / purpose” connects the record to a component, test, warning, or incident while identifying the activity's purpose. “Protection / support” records the asserted basis and supporting source IDs, not just a tag. “Disposition” distinguishes release, partial redaction, full withholding, and pending review.

The proposed description is candidate external text. Supporting analysis and open questions may contain sensitive internal reasoning and should remain separate. Add protocol-required service fields to the external log, including production references where required. Assign each unresolved issue to a named reviewer with a specific question and decision date tied to the production schedule.

Step by step

1. Define the logging population and governing protocol

Identify responsive documents requiring protection decisions. Determine how the protocol treats redactions, email chains, duplicates, attachments, and permitted categories. Do not assume that categorical logging or thread consolidation is authorized. Record the controlling source for the log's timing rather than adopting an assumed deadline.

Keep privilege decisions separate from relevance and other objections. For federal party production requests, Rule 34(b)(2)(B)–(C) requires specific objection grounds and disclosure of whether responsive materials are withheld on an objection. The log does not replace those responses. See Federal Rule of Civil Procedure 34.

Record: candidate IDs, preliminary dispositions, protocol questions, owners, and a reference to the controlling protocol.

2. Reconstruct document families and technical context

Read communications with their attachments and surrounding messages. Identify whether testing concerns the incident unit, a different lot, or a later design revision. Preserve distinctions between existing technical material and subsequent commentary about it.

Inspect participants and purpose for each materially different message. For presentations, examine available speaker notes and embedded content. A legal discussion on one slide calls for passage-level assessment, not an unexplained decision covering the entire safety presentation. Preserve original sources while preparing any redacted production version.

Record: family links, message or page locations, product identifiers, and missing attachments. Mark unavailable material as a gap; do not reconstruct its contents from a covering email.

3. Verify participant roles and communication purpose

Check authors, recipients, copied parties, and ascertainable distribution-list membership. Determine whether counsel was acting in a legal capacity in the communication. Identify external recipients and refer their effect on the proposed claim for matter-specific legal analysis.

Safety teams may discuss testing, corrective action, customer communications, and legal exposure together. Ask what the particular communication sought or conveyed and what evidence supports that characterization. Treat a lawyer's name or confidentiality legend as a review signal, not a sufficient rationale. Record uncertainties about shared mailboxes or forwarded messages.

Record: verified roles, purpose evidence with source IDs, and unresolved identities. Attribute custodian explanations rather than presenting them as document text.

4. Make a document-specific protection decision

Counsel should apply the governing privilege law to the verified facts. Keep privilege and work-product rationales distinct. For mixed-purpose records, identify the applicable legal test rather than assuming one test governs every jurisdiction.

For federal work product, Rule 26(b)(3) addresses documents and tangible things prepared in anticipation of litigation or for trial by or for a party or its representative. It also provides circumstances for discovery of otherwise protected material and protection for specified mental impressions and legal theories. It is not an absolute exemption for every counsel-directed investigation. See Federal Rule of Civil Procedure 26(b)(3).

For engineering investigations, verify who commissioned the work, why, and what contemporaneous evidence supports that purpose. Determine whether the supported claim covers the whole record or particular passages.

Record: protection asserted, supporting sources, passage-level scope, disposition, and approving reviewer. Keep internal reasoning separate from service language.

5. Draft an assessable description without exposing substance

Describe the record type, relevant participant roles, general subject, and protected purpose to the extent supported and appropriate under the protocol. “Email regarding product” offers little basis for assessment. A supported description identifying a safety director's request to counsel for legal advice concerning incident-response obligations is more informative.

Do not summarize counsel's answer, disclose strategy, or recast an engineering finding as an admission. Do not replace an ordinary business purpose with legal phrasing to strengthen a weak claim. Compare the description directly with the source and ask whether it explains this record rather than merely repeating a protection label.

Record: candidate service language, supporting pinpoint, and description issues requiring revision.

6. Reconcile decisions with redactions, production, and service

Compare approved decisions with the actual production set. Confirm that released attachments remain released, withheld documents are excluded, and redacted versions match approved passage boundaries. Map stable IDs to production identifiers, including records lacking a conventional page range.

Review nonwaiver arrangements with counsel. Evidence Rule 502(d)–(e) distinguishes a federal court's nonwaiver order, with cross-forum effect for covered disclosures, from a private agreement binding only its parties unless incorporated into a court order. Neither substitutes for checking what the order or agreement actually covers.

Prepare the external log without internal analysis. Preserve versions and resolve discrepancies before release, or obtain explicit counsel instructions consistent with the governing protocol.

Record: final dispositions, production references, reconciliation results, approved descriptions, and release authorization.

Worked example

Fictional scenario: Harborline Appliances faces claims that its fictional EmberTrail countertop cooker overheated because of a connector defect. The parties, product, records, dates, and descriptions below are fictional. Counsel reviews a safety director's request for legal advice, its attached routine thermal-test report, and a separate investigation memorandum.

The fictional protocol requires document-level entries and identification of redacted records. It does not authorize treating an email and all attachments as one protected unit. These abbreviated internal entries illustrate review decisions, not universally sufficient service descriptions.

The review separates three decisions. The legal-advice request receives an individual privilege assessment, but its wording alone does not complete the governing-law analysis. The attachment remains independently reviewable: evidence of scheduled quality testing supports the proposed release, rather than merely the fact that it predates the email.

The investigation memorandum stays pending because its commissioning purpose and external recipient are unresolved. Counsel's involvement elsewhere cannot fill those gaps. The team must obtain reliable evidence or document what the available record supports; it must not invent instructions. Before service, counsel converts approved withholding or redaction decisions into protocol-compliant entries and resolves pending records or authorizes their treatment under that protocol.

Common mistakes

• Withholding an entire safety committee packet: assess technical updates, business decisions, and legal discussions individually; substantiate any whole-document claim.
• Extending an email's claim to all attachments: assess test reports, complaint spreadsheets, and warning drafts separately while retaining family links.
• Inferring litigation purpose from timing: find commissioning evidence; “after the incident” is not a complete purpose analysis.
• Ignoring supplier or consultant recipients: verify identity and function, then obtain counsel's assessment under applicable law rather than assuming automatic protection or loss of protection.
• Serving the internal table unchanged: remove sensitive reasoning, add required service fields, and verify every description against its source.

Final quality check

Before approving the log and production, confirm:

• Logging method and timing match verified rules, orders, and agreements.
• Every protection claim has document-specific support and legal approval.
• Participant identities and roles are verified or expressly assigned for resolution.
• Attachments and materially different messages have appropriate assessments.
• Descriptions match source text without revealing protected substance.
• Redactions, withheld records, released records, and production identifiers reconcile.
• Open issues have owners and explicit release instructions; pending candidates are not silently converted into final claims.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, redaction, and production capabilities can support this review while counsel verifies sources, participant roles, governing law, and protection decisions. The log and internal decision record remain team work products. Explore litigation preparation or book a demo focused on product-record privilege review and production reconciliation.

Frequently asked questions

Should we log every document copied to a lawyer?

No blanket classification follows from lawyer participation. Assess purpose and the asserted protection, then apply the protocol to responsive records actually withheld or redacted on that basis. Record ordinary business communications as release decisions where appropriate.

How should we handle routine test results attached to legal advice?

Assess the results independently and retain their family link. Identify evidence supporting any claim for the attachment itself. In the fictional example, scheduled quality testing supports proposed release; a different commissioning history could change the assessment.

Can we combine all emails about one product incident?

Check the protocol before grouping. Shared subject matter does not resolve differences in recipients, purpose, attachments, or protection. If grouping is permitted, retain internal record-level detail showing precisely what each external entry covers.

What if an engineer cannot explain why an investigation began?

Seek contemporaneous instructions and other reliable purpose evidence. Identify the gap and assign counsel to assess the available record before the applicable release or logging date. An unresolved purpose cannot be repaired by inventing a litigation rationale.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34: protection claims, work product, discovery planning, and party production responses; compilation amended through December 1, 2025.
• Federal Rules of Evidence, Rules 501 and 502: governing privilege law and disclosure-related nonwaiver orders and agreements.

Scope: General US legal-workflow guidance using an October 13, 2026 research cutoff; applicable law and matter-specific orders control.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.