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 confirming the governing disclosure requirements, tracing potentially protected employment records to their participants and document families, and recording counsel’s withholding or redaction decisions. Concentrate on complaint investigations, promotion and termination approvals, and communications mixing legal advice with personnel management. The deliverable is a source-linked service log supported by a separate internal decision register and reconciled against production. Pending questions need assigned reviewers and deadline-aware dispositions; leaving an item unresolved internally does not extend the applicable disclosure deadline.
When to use this workflow
Use this workflow when litigation counsel or an in-house team reviewing employment records encounters possible attorney-client communications or trial-preparation material. Typical triggers include requests for an internal discrimination investigation, disciplinary approval chain, reduction-in-force analysis, or correspondence about an agency charge.
The workflow emphasizes US federal district-court discovery. Identify applicable privilege law, controlling precedent, local rules, and case-specific orders. Do not automatically apply federal discovery procedures to state litigation, arbitration, or an EEOC investigation.
Rule 26(b)(5)(A) requires an express protection claim and a description allowing assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. Neither provision supplies the substantive privilege test. Confirm the applicable arrangements before preparing the service log. Federal Rules of Civil Procedure, Rules 26(b)(5) and 26(f). (uscourts.gov)
What you need
Assemble the review population and the information governing its treatment:
- Discovery requests, responses, withholding statements, orders, and agreements addressing log content, exclusions, grouping, and timing.
- Native documents or reliable review copies, attachments, headers, thread relationships, document IDs, and available Bates numbers.
- A participant directory identifying counsel, HR staff, managers, investigators, consultants, and their roles during the relevant period.
- Complaint dates, investigation instructions, disciplinary milestones, counsel engagement information, and evidence of communication purpose.
- Production records, proposed redactions, earlier privilege decisions, and an escalation list with responsible reviewers and verified deadlines.
Keep preservation separate from production. EEOC guidance describes retention of relevant employment records after a discrimination charge until final disposition, including records concerning employees holding or seeking similar positions. Verify the employer category and applicable regulations. Retention does not establish privilege or complete the preservation analysis. EEOC recordkeeping requirements. (eeoc.gov)
Use the template
Use the Employment Discrimination Matters — Privilege review log as an internal working register. You can copy this table into your working document or spreadsheet. Prepare the service version separately, removing internal reasoning and assignments and adapting the descriptive fields to governing requirements.
| Item / family | Date / type | Author / role | Recipients / roles | Source cite | Protection / treatment | Nonrevealing description | Basis / uncertainty | Action / owner |
|---|---|---|---|---|---|---|---|---|
“Item / family” supplies a stable ID and parent–attachment relationship. “Source cite” identifies the reviewed page, message, or redacted passage. Use a review ID for withheld documents without Bates numbers; do not invent production references.
Record document dates, not collection dates, and identify direct, copied, and known blind-copy recipients. A separate participant directory can expand abbreviated names and roles. “Protection / treatment” distinguishes the asserted basis from withholding, redaction, production, or pending review.
“Basis / uncertainty” and “Action / owner” are internal fields. Include document-specific reasoning, missing evidence, reviewer, next action, and decision deadline there. Add version and approval references within the action field or a linked control sheet. Do not assume that labeling this register internal makes it privileged.
Step by step
1. Establish the review and logging rules
Approve written instructions identifying the applicable privilege framework, required descriptions, review unit, redaction conventions, escalation route, and service deadline. Determine whether an order or agreement permits categorical entries or exclusions; do not assume that counsel correspondence is automatically excluded from logging.
For federal party document requests, Rule 34 requires specific objection grounds and reasons, and disclosure of whether responsive material is withheld because of an objection. Reconcile the log with those responses; nonparty subpoenas require separate procedural analysis. Federal Rules of Civil Procedure, Rule 34(b)(2)(B)–(C). (uscourts.gov)
Record: Assign item IDs, preliminary treatments, the governing instruction version, and escalation deadlines in the register.
2. Reconstruct families and participant roles
Open the documents and attachments. Identify authors, recipients, forwarding history, and missing family members. For a termination approval chain, distinguish legal advisers from staff approving headcount, evaluating performance, or implementing the decision.
Ask the custodian or supervising lawyer when the source does not establish a participant’s function. An investigator’s assignment, reporting relationship, and distribution instructions may matter more than the title “outside consultant.” Retain uncertainty rather than inferring roles from email domains.
Record: Enter dates, roles, source citations, and family links. Assign missing attachments and unidentified recipients to named reviewers.
3. Separate confidentiality from privilege
Treat medical information, compensation, harassment allegations, and comparator personnel records as sensitivity questions requiring their own analysis. Identify whether a proposed restriction rests on privilege, an applicable confidentiality arrangement, a protective order, or another basis requiring counsel’s assessment.
Federal Rule 26(b)(1) confines discovery to nonprivileged matter relevant to claims or defenses and proportional to the case; admissibility is not required. It does not authorize unrestricted personnel-file access. Federal Rules of Civil Procedure, Rule 26(b)(1). (uscourts.gov)
Record: Identify the proposed protection precisely. Route nonprivilege sensitivity concerns separately instead of entering “confidential” as the privilege basis.
4. Assess each proposed protection in context
Examine whether HR was reporting ordinary investigation findings, requesting legal advice, or combining functions. For proposed work-product protection, identify evidence supporting the asserted litigation-related purpose and have counsel apply the governing test. A complaint date or lawyer’s involvement is a review lead, not a substitute for that analysis.
Escalate mixed-purpose communications, third-party participation, and broader forwarding. Also flag any proposed reliance on the investigation or counsel’s advice in defending the employment decision: counsel must assess the implications under controlling law rather than treating privilege as settled.
Record: Enter each asserted protection separately, its factual basis, and unresolved legal questions. Assess attachments independently of their parent messages.
5. Draft descriptions that allow assessment
Describe participants’ functions, the general subject, and the asserted protected activity. For example: “HR director’s email to employment counsel requesting legal advice concerning response to an employee’s discrimination complaint.” Check that the source actually supports that characterization.
Avoid both “privileged email,” which says little, and a description revealing counsel’s recommendation about terminating the complainant. For mixed material, have counsel decide whether partial redaction is appropriate and identify the relevant passages internally. Do not rewrite routine staffing discussions as legal-advice requests.
Record: Enter the description, proposed treatment, and passage citation. Have another reviewer compare the description with the source and approved legal basis.
6. Resolve exceptions and reconcile production
Compare related threads and duplicates without assuming identical treatment. Versions may differ in recipients, added text, or attachments. Inspect the proposed production copy to confirm that redactions match counsel’s decision and protected passages are not exposed in another produced version.
Match withheld items and privilege redactions to log entries or documented exclusions under the approved instructions. Check that independently producible attachments have not disappeared with withheld parent emails. Resolve pending items before the governing deadline or obtain an appropriate procedural resolution; an internal assignment alone is insufficient.
Record: Update treatment, production references, approval, and reasons for changed decisions. Give unresolved issues an owner, deadline, and explicit disposition.
7. Prepare the service version and preserve the record
Create the service version from approved entries, excluding internal analysis and assignments. Independently inspect names, descriptions, claimed protections, and withheld-versus-redacted status. Check that exporting or copying the table has not exposed hidden columns or comments.
Retain a dated internal version connecting served entries with documents, approvals, and production records. If later review changes an entry, document the change and have counsel determine the necessary correction or disclosure response under applicable requirements.
Record: Identify the approved service version, responsible reviewer, service date, and corresponding production in the control record.
Worked example
Fictional scenario: Maren Vale alleges that fictional employer Bracken Quay Systems denied her promotion and later terminated her after she complained of sex discrimination. Counsel reviews the investigation and approval chain. All parties, documents, and communications below are fictional; dates are in 2026.
The set contains an advice request, a staffing recommendation copied to counsel, and an investigator memorandum with incomplete distribution evidence. An existing performance spreadsheet accompanies the first email. None of the three proposed treatments has final approval.
| Item / family | Date / type | Author / role | Recipients / roles | Source cite | Protection / treatment | Nonrevealing description | Basis / uncertainty | Action / owner |
|---|---|---|---|---|---|---|---|---|
| PR-01 / F-11 | Feb. 4 / email | S. Iven / HR director | D. Orr / employment counsel | DOC-011, p. 1 | Attorney-client / proposed withholding | HR request for legal advice about response to discrimination complaint | Express request supports claim; confidentiality and attachment treatment need confirmation | Confirm distribution; review spreadsheet DOC-012 separately / matter counsel |
| PR-02 / F-18 | Feb. 6 / email | L. Fern / supervisor | HR; counsel copied | DOC-018, pp. 1–2 | None approved / pending | Staffing recommendation concerning promotion vacancy | Operational content evident; surrounding context not yet reviewed | Review related messages; produce absent supported protection / lead reviewer |
| PR-03 / F-24 | Feb. 9 / memo | T. Ash / investigator | HR confirmed; others unknown | DOC-024, pp. 1–4 | Undetermined / pending | Investigator memorandum concerning employee complaint | Engagement instructions and complete distribution unavailable | Obtain assignment and routing evidence; escalate before log deadline / matter counsel |
The analysis narrows the proposed withholding population. PR-01 remains a candidate, but neither the email nor spreadsheet receives automatic approval. PR-02 does not enter the approved log merely because counsel was copied. PR-03 requires factual development before counsel can characterize its purpose and assess protection.
The team does not invent engagement instructions or treat missing metadata as proof of confidentiality. It assigns gaps and addresses them against the service deadline rather than silently withholding unresolved material indefinitely.
Common mistakes
- Treating the entire HR investigation as protected. Review communications, interview records, reports, and attachments separately; identify each proposed claim’s basis.
- Using attorney participation as the complete rationale. Establish purpose, roles, and context before applying governing law.
- Flattening a termination thread into one recipient list. Inspect individual messages and forwarding events; preserve material differences within the approved logging method.
- Revealing the advice in the description. Explain subject and function without disclosing recommendations, admissions, or strategy.
- Dropping pending items from reconciliation. Maintain ownership, deadlines, and an express procedural disposition for every unresolved item.
Final quality check
Before approving service, confirm:
- Format, timing, exclusions, and grouping match applicable requirements.
- Each entry was verified against the actual cited source.
- Dates, participants, roles, and family links are accurate or expressly identified as uncertain.
- Counsel approved each asserted protection under governing law.
- Descriptions permit assessment without revealing protected substance.
- Withheld documents, redactions, attachments, and production references reconcile.
- Internal analysis and hidden comments are absent from the service copy.
- Open issues are resolved or assigned with deadlines and an authorized disposition consistent with service obligations.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and redaction and production capabilities can support the source review underlying this register. Counsel retains responsibility for classifications, descriptions, and release decisions. Explore its litigation workflow or book a demo to discuss employment-discovery review. The register is the team’s working document, not a claimed dedicated logging module.
Frequently asked questions
Should every HR email copied to counsel appear on the log?
No automatic classification should follow from the recipient list. Review purpose, content, roles, and context. The service log should describe actual withholding or redaction claims according to governing requirements, not every item screened for privilege.
How should we handle an outside investigator’s report?
Collect engagement instructions, assignment evidence, intended recipients, and distribution history. Ask counsel to assess protection and any implications of relying on the investigation. Missing facts belong in the internal register, with an owner and deadline—not in an unsupported definitive claim.
Can repetitive messages share one entry?
Check the applicable order, agreement, and requirements before grouping. Maintain an internal mapping to every source item and verify that the shared description accurately covers dates, participants, and asserted protection without obscuring meaningful differences.
What if an email mixes legal advice and personnel administration?
Identify distinct passages and ask counsel whether redaction is appropriate under applicable law. Record passage citations internally, then inspect the production copy and related versions to ensure the approved treatment was implemented consistently.
Sources
- Federal Rules of Civil Procedure: Rules 26(b)(1), 26(b)(5), 26(f)(3)(D), and 34(b)(2)(B)–(C), including amendments effective December 1, 2025.
- EEOC — Recordkeeping Requirements: agency guidance concerning employment-record retention following a discrimination charge.
Scope: General professional workflow guidance using an October 13, 2026 research cutoff; 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.
