How to prepare a privilege review log for Employee Retaliation Matters

Prepare a privilege review log by identifying responsive retaliation-related records, evaluating each proposed privilege or work-product claim under the applicable law, and documenting withholding or redaction decisions with source-linked support. Review complaint intake, HR investigations, decision drafts, and legal communications separately rather than assigning one designation to an entire investigation. The deliverable is an exchange-ready log that permits assessment without exposing protected content, backed by an internal worksheet recording participant roles, document families, uncertainty, and counsel’s approval. Do not exchange the internal analysis with the log.

When to use this workflow

Use this workflow before producing retaliation-related employment records, when revising a deficient privilege log, or when inconsistent designations emerge across HR and management communications. It applies to employer counsel and employee counsel reviewing their respective clients’ records. The example below uses employer-side review.

The procedural scope is principally US federal district-court EEO retaliation litigation. Rule 26(b)(5)(A) requires express claims and descriptions permitting assessment without revealing protected information; Rule 26(f)(3)(D) addresses the timing and method of compliance in discovery planning. Neither establishes a universal log format. Check local rules, case-management orders, and discovery agreements. See Federal Rules of Civil Procedure, Rules 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

State litigation, arbitration, and administrative proceedings require separate procedural analysis. Counsel must also identify the applicable substantive privilege law rather than treating federal discovery procedure as the privilege standard.

What you need

Assemble these inputs before substantive review:

• Requests, responses, production specifications, orders, and agreements governing logging, redactions, grouping, and timing.
• Complaint intake, HR investigation records, performance histories, scheduling changes, decision drafts, messages, and counsel communications.
• Stable document IDs, complete threads, attachments, available metadata, and page or message references.
• A contemporaneous role directory identifying investigators, decisionmakers, recommenders, lawyers, consultants, and administrative recipients.
• Counsel-approved privilege and work-product standards, including unresolved mixed-purpose, distribution, and waiver questions.
• A complaint and challenged-action timeline, investigation instructions, and an internal worksheet separate from the external log.

Preserve the actual complaint language. The EEOC’s nonbinding guidance distinguishes participation from opposition and explains that not every workplace grievance constitutes protected EEO activity. Use that distinction to orient the factual review, not to decide privilege. See EEOC guidance, Sections II.A–B. (eeoc.gov)

Use the template

Use Employee Retaliation Matters — Privilege review log as the internal review worksheet. You can copy this table into your working document or spreadsheet. Prepare the external log from approved fields; do not exchange the worksheet unchanged.

Row / source identifies the entry, document ID, and page, paragraph, message, or attachment pinpoint. Date / type records the communication or document date, not collection date. Separate message dates within a thread where needed.

People / roles distinguishes authors, direct recipients, copied recipients, and relevant roles. Neutral description contains proposed external wording. Protection / purpose separates the asserted protection from internal analysis explaining its factual basis.

Treatment / family records withholding, redaction, release, or pending review, with parent and attachment IDs. Support / question records source evidence, request references, and uncertainty. Decision / owner identifies approval, reviewer, follow-up, and the applicable internal target date.

Keep releasable and pending records internally for reconciliation. Add fields required by the matter’s protocol, including production identifiers where applicable; these eight columns are not a universal external-log specification.

Step by step

1. Set the review unit and required deliverable

Read the governing discovery documents before choosing document-level, message-level, or permitted categorical entries. Establish how attachments, repeated chains, redactions, and duplicate copies will be represented. Obtain approval for any categorical approach rather than adopting it solely to reduce row count.

Create a control row for the approved fields, logging unit, governing documents, timing, and approving lawyer. Distinguish an internal review target from an agreed or ordered exchange deadline. Assign ambiguities to counsel before reviewers begin applying inconsistent conventions.

Record: A control row linking the protocol and recording the approved review and exchange requirements.

2. Separate responsiveness from protection

Map each record to the relevant request before determining its treatment. In retaliation matters, distinguish complaint receipt, investigation activity, decision initiation, recommendations, approval, and implementation. Rule 26(b)(1) addresses relevant, proportional, nonprivileged discovery; potential privilege is not a substitute for responsiveness analysis. See Rule 26(b)(1). (uscourts.gov)

Use the timeline to identify a record’s factual function without deciding the merits. The EEOC identifies actor awareness, timing, inconsistent explanations, comparator evidence, and legitimate reasons as relevant evidentiary considerations—not automatic proof of retaliation. See EEOC guidance, Section II.C. (eeoc.gov)

Record: Request reference and factual function in Support / question, separate from the proposed protection.

3. Read the complete communication and document family

Inspect the message, preceding thread, attachments, and available versions. A legal-advice request may attach an existing performance spreadsheet or complaint form. Give each attachment its own assessment instead of extending the parent’s proposed designation throughout the family.

For investigation materials, locate commissioning instructions and identify whether the record contains interviews, operational recommendations, legal consultation, or mixed content. Compare later counsel-directed work with earlier routine HR records. Identify missing family members rather than inferring their contents from filenames or surrounding emails.

Record: Parent and attachment IDs, relevant passages, version information, and missing-source questions.

4. Verify roles, purpose, and each asserted protection

Check participant roles at the time of the communication. Determine whether in-house counsel was performing legal or operational work and why outside recipients participated. Do not use an email domain, job title, or copied lawyer as the entire rationale.

Have counsel evaluate attorney-client privilege and work product separately under the approved standards. For a proposed work-product claim, identify the asserted preparation circumstances and supporting evidence; a litigation-related filename is insufficient review support. Escalate mixed purposes, unexplained distribution, investigation arrangements, and potential waiver or reliance questions. If the employer intends to rely on an investigation in its defense, flag that intended use for legal analysis rather than assuming it either preserves or defeats protection.

Record: Each proposed protection, its factual support, unresolved questions, and the responsible lawyer. Unapproved entries remain pending.

5. Select withholding, redaction, or release

Identify the precise material proposed for protection. Review surrounding passages and attachments independently, and check whether production of another copy would expose the same content. Do not redact an entire staffing discussion merely because a later message contains legal consultation.

Pay particular attention to factual complaint-routing and decision-development records. A manager’s acknowledgment of complaint receipt and a subsequent legal-advice request may require different treatment. Conversely, do not assume a factual passage is independently releasable without applying the governing standard to its context.

Record: Approved treatment, message or page boundaries, related production IDs, and reasons for different treatment within a family.

6. Draft descriptions that permit assessment

Use verified attributes: date, participants and roles, document type, general subject, and relationship to the asserted protection. “Email regarding employee” does not explain the basis of a claim. Where supported, describe a confidential request for legal advice concerning handling of an employment complaint without stating the advice sought or received in substantive detail.

Avoid revealing recommendations, litigation assessments, or strategy. Equally, do not add an unsupported legal purpose to strengthen an entry. Rule 26(b)(5)(A) requires enough information for assessment without disclosure of the protected information itself. See Rule 26(b)(5)(A). (uscourts.gov)

Record: Proposed neutral description, verified participant information, and counsel’s approval or revision.

7. Reconcile the log with production and resolve exceptions

Compare approved entries with the actual withheld set and redacted production. Investigate inconsistent duplicate decisions, absent attachments, incorrect dates, and redactions without approved entries. Review embedded copies as well as standalone documents.

For federal party document requests, also reconcile the log with the responses. Rule 34(b)(2) requires specific objection grounds and disclosure of whether responsive materials are withheld on that basis. See Rule 34(b)(2). (uscourts.gov)

Resolve pending rows before exchange or obtain counsel’s direction for handling them consistently with the governing protocol. Assigning an owner alone does not complete a required disclosure.

Record: Final status, production references, resolved exceptions, and approved handling of any outstanding issue.

Worked example

Fictional scenario: Cedar Vale Components is defending Mara Ellis’s claim that a shift reassignment followed her discrimination complaint. Every party, document, date, and communication below is invented.

Counsel’s collection contains an HR intake email copied to a lawyer, a separate advice request, and a staffing chain containing later legal consultation with an attached shift-selection spreadsheet. The initial review tags all three families for withholding because counsel appears in each. These completed internal review entries identify why that preliminary treatment needs revision; they are not approved external-log entries.

R01 requires purpose verification, not a claim based on copying counsel. R02 supports further privilege analysis but lacks a completed distribution check. R03 requires separate decisions for messages and the attachment, rather than family-wide withholding.

The missing spreadsheet history does not establish preparation for counsel. Nor does counsel’s receipt of the chain establish when the operations manager learned of the complaint. Those gaps remain explicit. The revised decision is to stop blanket withholding, conduct targeted checks, and move only approved claims into the external log. A released record remains in the internal worksheet to explain its absence from that log.

Common mistakes

• Treating the HR investigation as one privileged object. Separate commissioning instructions, interviews, business recommendations, and legal communications.
• Equating lawyer involvement with protection. Verify role, purpose, recipients, and the applicable standard.
• Ignoring attachments or repeated chains. Assign separate decisions and reconcile all copies before production.
• Disclosing advice in the description. Describe the communication’s general subject and protected function, not counsel’s conclusion.
• Treating pending rows as completed claims. Obtain approval or documented handling under the applicable protocol.
• Exchanging internal review notes. Inspect a separate external version for strategy, tentative analysis, and reviewer comments.

Final quality check

• Every approved entry identifies the correct source, date, and pinpoint.
• Participant roles and distribution have been verified or explicitly escalated.
• Proposed descriptions match the source without revealing protected substance.
• Each asserted protection has counsel-approved support under the applicable law.
• Attachments, duplicates, and redaction boundaries reconcile with production.
• External fields and timing match governing requirements and withholding responses.
• Open issues are resolved or assigned with approved handling that addresses applicable obligations.
• Internal analysis, release decisions, and unapproved designations are excluded from the exchanged version unless the protocol requires otherwise.

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 review of retaliation-related records. Counsel retains responsibility for applicable standards, source verification, descriptions, and final decisions. Explore litigation preparation capabilities or book a demo focused on reviewing HR communications and reconciling privilege decisions with production.

Frequently asked questions

Should every HR document involving counsel appear on the log?

No. Counsel’s involvement triggers analysis, not an automatic claim. Apply the approved logging protocol to material withheld or redacted on an asserted protection. Keep release decisions internally for reconciliation.

Can complaint and decision dates remain in an entry?

Use verified dates consistent with the applicable protocol and assess whether the description exposes protected content. Do not substitute collection dates or vague timeline labels for known communication dates.

How should mixed HR and legal email chains be handled?

Review messages and attachments separately, identify proposed protected passages, and compare repeated copies. Record the rationale internally, then use the approved logging unit and redaction approach externally.

What if a recipient’s role cannot be established?

Keep the designation pending and assign a targeted check of contemporaneous directories, engagement records, or other reliable evidence. If exchange is approaching, obtain counsel’s direction under the governing protocol rather than asserting privilege simply to close the row.

Sources

• Federal Rules of Civil Procedure, amended through December 1, 2025: Rules 26(b)(1), 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2).
• EEOC Enforcement Guidance on Retaliation and Related Issues: Sections II.A–C; nonbinding agency interpretation.

Scope: General professional workflow guidance using the supplied research cutoff of October 13, 2026, not advice for a particular matter.

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.