Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Prepare a privilege review log by separating legal-advice communications from routine HR records, examining each document’s purpose and participants, and recording the basis for every proposed withholding or redaction. In workplace harassment matters, focus on mixed investigation files, counsel’s interview materials, and records supporting the employer’s response. The resulting deliverables are a source-linked internal review table and a disclosure-ready log that explains asserted protections without exposing protected substance. Counsel should resolve governing-law and investigation-reliance questions before approving affected production decisions.
When to use this workflow
Use this workflow when counsel must evaluate harassment investigation materials for discovery, respond to a privilege challenge, or prepare collected records for anticipated production. Employer counsel will often review HR and investigator files; employee-side counsel can apply the same discipline to client communications, interview materials, and litigation-preparation records.
The scope is privilege classification and logging—not deciding the harassment claim or conducting the investigation. Federal Rule 26(b)(5)(A) requires an express protection claim and a description permitting assessment without revealing protected information. It does not establish privilege or prescribe universal log columns. See Federal Rule of Civil Procedure 26. (uscourts.gov)
This guide uses a US federal civil-discovery orientation. Confirm controlling privilege law, local rules, orders, and agreed procedures; do not automatically apply federal discovery requirements to state litigation, arbitration, or administrative proceedings. The steps below are workflow recommendations, not additional legal requirements.
What you need
Assemble these inputs before substantive review:
- Production framework: requests, responses, withholding positions, orders, stipulations, and logging conventions, including timing and treatment of redacted records.
- Original investigation records: hotline submissions, complaint emails, HR tickets, interview notes, findings, discipline records, and follow-up communications, with attachments and versions preserved.
- Communications context: complete threads, metadata, distribution lists, and participant roles at the relevant time—not merely current titles.
- Counsel’s assignment: whom counsel represented, who requested advice, the assignment’s purpose, and evidence explaining when and why litigation preparation began.
- Reliance position: whether the employer expects to use investigation findings or corrective-response evidence, and who will decide related disclosure questions.
- Stable references: document IDs, page or paragraph locations, family relationships, production identifiers, and links to supporting context records.
Missing context should create an assigned question, not an inferred privilege basis. Do not reconstruct an undocumented legal assignment merely because a lawyer appears in the correspondence.
Use the template
Use the companion Workplace Harassment Matters — Privilege review log as an internal decision record. You can copy this table into your working document or spreadsheet.
| Doc / family ID | Date / type | Participants / roles | Purpose / source cite | Protection / basis | Treatment / scope | External description | Review / owner |
|---|---|---|---|---|---|---|---|
“Participants / roles” identifies authors, recipients, copied recipients, and relevant capacities. Expand distribution lists where feasible. “Purpose / source cite” links the classification to the document and any separate assignment or context record. Distinguish recorded facts from counsel’s inference.
“Protection / basis” captures the proposed protection and reasoning for counsel to test. “Treatment / scope” distinguishes production, full withholding, partial redaction, and pending review; identify precise redacted passages. “External description” contains only disclosure-suitable language. “Review / owner” records reviewer, status, unresolved question, decision owner, and approval date.
This table is not automatically the served log. Maintain a separate disclosure version with the required fields; split these combined columns if the applicable protocol requires separate author, recipient, date, or protection fields. Keep internal reasoning and produced-document entries out of that version unless disclosure is appropriate.
Step by step
1. Establish the governing requirements and review unit
Read the discovery requests, scheduling order, and logging agreements. Determine whether the required unit is a document, message, redacted passage, or permitted category. Do not assume one email-thread entry or investigation-folder entry is acceptable.
Federal discovery covers nonprivileged matter relevant to claims or defenses and proportional to case needs. Rule 26(b)(1) supplies that framework, not a blanket entitlement to personnel files. (uscourts.gov)
Check the discovery plan and scheduling order for logging arrangements. Rules 26(f)(3)(D) and 16(b)(3)(B)(iv) expressly address the timing and method of compliance with Rule 26(b)(5)(A). See Rules 16 and 26. (uscourts.gov)
Record the review unit and protocol reference in the template. Assign unresolved format or timing questions before large-scale coding begins.
2. Reconstruct investigation context without merging records
Map complaint intake, HR escalation, counsel’s involvement, interviews, findings, and corrective decisions. Keep the original employee account separate from HR’s summary and counsel’s analysis. Review retaliation-related follow-up and remedial communications alongside the initial complaint, without assuming they serve the same purpose.
Check attachments and forwarded messages. Analyze an existing HR report separately from a later communication sending it to counsel; do not carry one classification across the family. Preserve distinctions between original interview notes, revised notes, and counsel’s summary.
Record dates, types, participants, and source locations. If a note lacks an author or date, flag the gap and identify who can verify it. Document creation dates should not silently become incident dates.
3. Separate legal advice from operational HR purposes
Read substance and context. Ask whether the record requests legal advice, records routine fact gathering, implements a personnel decision, or combines those functions. These are review questions, not automatic conclusions.
For mixed communications, identify potentially protected passages and operational content separately. A confidentiality heading, copied lawyer, or investigation label should trigger examination—not replace it. Ask what task the communication actually performs and what evidence supports that assessment.
Enter the purpose and citation. Record competing explanations, such as an interview serving both policy administration and counsel’s advice. Assign mixed-purpose questions to supervising counsel for application of the governing standard; do not impose an unresearched universal test.
4. Test each proposed protection and its factual support
For attorney-client claims, identify the client, lawyer, participant roles, legal-advice purpose, and confidentiality facts requiring evaluation. For trial-preparation claims, identify the asserted litigation connection, preparer, timing, and supporting context. Have counsel apply the governing standards rather than treating these facts as a mechanical checklist establishing protection.
Review distribution and later forwarding. Identify the role of any outside investigator, consultant, parent-company employee, or accused employee. Do not assume that company counsel also represented an individual participant.
Record the proposed protection, supporting evidence, and uncertainty separately. Where both protections are proposed, explain each basis. If support is missing, mark the decision pending instead of drafting a confident external description around an assumption.
5. Examine investigation reliance before approving withholding
Ask merits counsel which investigation facts, conclusions, or communications the employer intends to use. Compare that position with proposed withholdings and identify potentially inconsistent positions. Assign possible disclosure or waiver disputes for jurisdiction-specific analysis; assume neither that reliance waives everything nor that counsel’s involvement protects everything.
The Title VII framework described in Vance permits an affirmative defense to supervisor harassment without a tangible employment action when both employer prevention-and-correction and employee unreasonable-failure components are established. Supervisor status turns on employer-conferred authority to take tangible employment actions, not simply a “team lead” title. See Vance v. Ball State University, majority opinion. Vance provides merits context, not a privilege-waiver rule. (law.cornell.edu)
Record affected IDs, intended reliance, the legal question, and the responsible lawyer. Revisit those entries when the reliance position changes.
6. Choose treatment and draft a bounded description
Decide whether to produce, redact, withhold, or escalate each item. For approved partial production, identify precise passages and inspect surrounding text, comments, and embedded material for unintended disclosure. Track personnel privacy and confidentiality restrictions separately from privilege decisions.
Describe the general legal purpose without revealing advice or strategic conclusions. A description identifying an HR-to-company-counsel request for advice about complaint response is more useful than “privileged investigation email,” but only if the document and verified context support it. Do not call a communication confidential while its distribution remains unresolved.
Enter treatment and external description. Test whether the description permits assessment under Rule 26(b)(5)(A) without disclosing protected substance. (uscourts.gov)
7. Reconcile the log with the response and production
Compare the internal table with production copies, redactions, and discovery responses. In federal party discovery, Rule 34(b)(2)(B)–(C) requires specific objection grounds and disclosure of whether responsive materials are withheld on those grounds. See Federal Rule of Civil Procedure 34. (uscourts.gov)
Check that approved withholdings have corresponding entries where required. Confirm that produced attachments are not described as withheld with their parent. Review duplicates consistently while preserving different recipients, annotations, and versions.
Record approval and production references. Escalate pending items before the applicable response or logging date; a pending internal label is not a substitute for resolving the external obligation. Preserve the internal version separately from the disclosure log.
Worked example
Fictional scenario: Harbor Finch Design LLC receives a harassment complaint from employee Maya Chen concerning team lead Ellis Rowan. HR director Nora Vale opens a policy investigation. Company counsel Ada Kerr later advises on the response. Litigation follows, and employer counsel reviews three records responsive to a request for investigation materials. All names, records, and dates below are fictional.
The collection contains an intake email, a request for legal advice, and investigator notes. No investigator assignment has been located. Merits counsel has not decided whether to rely on the investigator’s conclusions. Rowan’s title does not establish supervisor status, and the collection does not resolve that question.
| Doc / family ID | Date / type | Participants / roles | Purpose / source cite | Protection / basis | Treatment / scope | External description | Review / owner |
|---|---|---|---|---|---|---|---|
| HF-014 / F-03 | Feb. 4, 2026 / email | Chen, employee; Vale, HR | Complaint intake; p. 1 | No privilege basis identified | Proposed production; check privacy restrictions | Internal only: complaint to HR | Production counsel: approve disposition |
| HF-039 / F-11 | Feb. 7, 2026 / email | Vale, HR; Kerr, company counsel; distribution unverified | Requests legal advice on response; p. 1 | Attorney-client proposed; audience unresolved | Pending recipient verification | Draft only: HR-to-counsel email requesting legal advice about complaint response | Reviewing lawyer: verify distribution and confidentiality |
| HF-062 / F-19 | Feb. 10, 2026 / notes | Investigator; commissioning party unverified | Witness interview; pp. 1–4; assignment missing | Undetermined; purpose and role unsupported | Pending; no approved withholding | Not ready for external log | Merits counsel: locate instructions; resolve reliance |
These distinctions change the decision. HF-014 does not receive the same treatment as HF-039 merely because both concern the complaint. HF-039 contains evidence of a legal-advice request, but its audience still needs verification. HF-062 cannot be classified from its title: neither a counsel-directed assignment nor a litigation purpose has been established.
Counsel should seek assignment records and distribution evidence, not fill those gaps with assumptions. If further evidence changes a classification, retain the earlier reasoning internally and revise the disclosure version to match the approved outcome.
Common mistakes
- Treating the investigation folder as one privileged unit. Separate intake records, attachments, legal communications, and remedial decisions under the approved protocol.
- Using titles or labels as conclusions. Verify counsel’s function, investigator instructions, participant capacities, and document purpose.
- Confusing privacy with privilege. Record personnel sensitivity and confidentiality handling separately; identify the actual basis for any proposed restriction.
- Serving internal reasoning. Remove strategy, credibility assessments, unresolved questions, and reviewer comments from the disclosure version.
- Describing advice rather than purpose. Explain the communication’s general legal function without summarizing counsel’s conclusions.
- Ignoring reliance changes. Reopen affected entries when merits counsel changes the intended use of investigation findings.
Final quality check
Before releasing the log, confirm:
- Each entry matches the original record, metadata, and cited passage.
- Authors, recipients, distribution lists, and roles are verified or flagged.
- Each asserted protection has counsel-approved reasoning and checked governing authority.
- Descriptions permit assessment without exposing protected substance.
- Redaction scopes match the actual production copies.
- Attachments, duplicates, and thread components have explainable dispositions.
- Open reliance or classification issues have an owner and an explicit release decision.
- The disclosure log, response, production inventory, and required timing reconcile.
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 harassment investigation materials. Counsel retains responsibility for governing-law analysis, reliance questions, classifications, and the final log. Explore litigation preparation workflows or book a demo to discuss this process.
Frequently asked questions
Does copying company counsel justify withholding an HR email?
Do not decide from the address line alone. Examine content, purpose, participant capacities, and confidentiality context. Record the supporting facts, then have counsel apply the governing standard to the particular communication.
Should the internal table include documents that will be produced?
Yes, where useful for reconciliation. Those rows explain different treatment within the same investigation. The external log should follow the governing requirements rather than automatically reproduce every internal entry.
How should interview notes with an unclear assignment be handled?
Preserve the notes and seek instructions, engagement records, or reliable clarification. Assign the missing facts to a named owner before the release decision. Do not invent a litigation purpose or describe an unverified assignment as counsel-directed.
Can one description cover the entire investigation?
Use grouped treatment only after confirming the applicable framework permits it and the description supports assessment. Otherwise, separate records sufficiently to explain different purposes, participants, protections, and dispositions. Convenience should not conceal mixed HR and legal work.
Sources
- Federal Rules of Civil Procedure, Rules 16, 26, and 34: logging arrangements, discovery scope, protection descriptions, and withholding disclosures.
- Vance v. Ball State University, majority opinion: Title VII supervisor-status and affirmative-defense context, not privilege doctrine.
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.
