How to prepare a privilege review log for Wrongful Termination Matters

Prepare a privilege review log by separating potentially protected communications from ordinary termination records, verifying participants and purposes, and documenting each proposed withholding or redaction against its source. Review HR investigations, legal consultations, termination approvals, and attachments individually rather than treating counsel’s involvement as decisive. The deliverable is a source-linked internal review log and an approved disclosure version that explains asserted protections without exposing protected substance. Keep unresolved questions assigned and visible so they cannot become unsupported withholding decisions.

When to use this workflow

Use this workflow when employment counsel must review responsive documents before production, explain privilege redactions, or reconcile decisions across HR, management, and employee collections. Employer-side review commonly involves internal investigations and termination approvals; employee-side review may involve consultations with personal counsel and communications forwarded from workplace accounts.

Focus on records surrounding complaints, performance assessments, decision approvals, and later explanations. Establish responsiveness separately; this workflow does not determine the merits of the termination dispute.

The procedural discussion assumes US federal district-court litigation. Check separate requirements for state litigation, agency proceedings, and arbitration. Federal forum does not invariably mean federal privilege law: Federal Rule of Evidence 501 directs application of state privilege law concerning a civil claim or defense for which state law supplies the rule of decision. Assign mixed-claim and choice-of-law questions for controlling-authority research before approving claims.

What you need

Assemble these inputs before final decisions:

• Review population: Responsive records, stable IDs, metadata, complete threads, attachments, and links to proposed production versions.
• Termination context: Complaint dates, investigation scope, decisionmakers, stated termination reasons, and effective termination date.
• Participant directory: Authors, recipients, employers, functions, counsel’s capacity, outside advisers, aliases, and distribution-list membership.
• Governing instructions: Claims and defenses, applicable privilege authorities, discovery requests, orders, logging arrangements, and verified disclosure deadlines.
• Decision controls: Approved outcomes, escalation owners, redaction conventions, prior-production history, and any relevant disclosure or clawback arrangements.

Flag missing attachments, unknown recipients, and uncertainty about who commissioned an investigation. A “legal” label is a review lead, not a determination. Identify who represents whom, particularly where managers, corporate counsel, and separately represented employees appear together.

Use the template

The companion template is Wrongful Termination Matters — Privilege review log. You can copy this table into your working document or spreadsheet. It is an internal working table, not a ready-to-serve log: its reasoning and follow-up fields may disclose counsel’s analysis.

Use stable IDs for withheld documents without production Bates numbers. Family IDs connect emails and attachments without assigning them identical treatment. Specify whether each date is a sent date, creation date, or another verified date; record unknown dates as unknown.

Distinguish authors, direct recipients, copied recipients, and verified roles. Link to a participant directory where necessary. The locator should identify the reviewed version and page, paragraph, spreadsheet tab, or message segment.

Name the protection under consideration rather than writing “confidential.” Put proposed external wording in the description field and precise redaction locations in the decision field. The final field records internal support, missing facts, the responsible reviewer, and approval status. Use linked continuation notes when necessary; do not compress substantive reasoning into an ambiguous code.

Step by step

1. Establish the logging requirements and governing analysis

Read applicable orders, local requirements, discovery arrangements, and substantive privilege authorities before choosing a disclosure format. Rule 26(b)(5)(A) requires an express protection claim and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) includes compliance timing and method in discovery planning. These provisions do not prescribe one universal table or establish substantive attorney-client privilege.

Determine permitted grouping, required information, and verified deadlines. Do not assume communications after a particular date are exempt from logging. Distinguish governing-law questions from format questions.

Record: Link rows to approved review instructions; assign unresolved scope, format, or timing issues to responsible counsel.

2. Reconstruct documents and families

Map each potentially protected item to its complete source. A termination-approval email may attach an attendance spreadsheet, draft notice, employee complaint, and counsel’s comments. Review those components separately.

Check for omitted messages, missing attachment versions, and unresolved distribution lists. Preserve originals while creating review and production copies. Distinguish duplicate copies with different annotations or recipients. Where an email embeds earlier messages, identify the specific message supporting the proposed claim instead of treating the entire thread as one undifferentiated communication.

Record: Enter document and family IDs, verified dates, exact locators, and missing components. Mark incomplete families for follow-up rather than uniform withholding.

3. Verify participants and purpose

Determine who communicated, in what capacity, and for what function. An HR director may request legal advice in one message and operational approval in another; in-house counsel may participate in both.

Read the communication with available context. For investigations, locate commissioning instructions, stated purpose, intended recipients, and subsequent circulation. For employee-side records, investigate forwarding and account-access facts when relevant to the applicable analysis. An outside recipient presents a question to resolve, not an automatic conclusion either way.

Record: Populate roles and a provisional nonrevealing description. Assign unexplained recipients, representation questions, and missing context to a named owner.

4. Assess each asserted protection separately

Apply the governing analysis to each item and, where appropriate, each portion. Separate attorney-client privilege from work-product protection. For the latter, 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, subject to the rule’s qualifications. Investigate preparation circumstances; an HR investigation label does not supply those facts.

For mixed business/legal discussions, assess whether protected passages can be separated from responsive business content. Inspect preexisting performance records and complaint attachments independently. Counsel’s presence, a footer, or creation before consultation is not a substitute for the complete analysis.

Record: Enter each proposed protection, factual support, and outcome: produce, redact, withhold, or hold for counsel’s decision. Assign questions about disclosure, waiver, or reliance on an investigation rather than presuming their resolution.

5. Draft descriptions that explain without revealing

Describe document type, verified participants, and general subject specifically enough to support assessment. “Email requesting legal advice concerning proposed termination after an employee complaint” is more useful than “privileged HR email,” provided the source supports that description.

Avoid stating counsel’s recommendation, witness assessment, or predicted exposure. Check titles and attachment names as well as the description. Do not characterize an investigation as counsel-directed without supporting records. An unknown participant should remain identified as unresolved internally until counsel determines appropriate disclosure treatment.

Record: Add proposed external wording and any information requiring further treatment. Keep substantive reasoning in internal notes, not the served description.

6. Reconcile decisions with production and responses

Compare approved decisions with actual production files. Verify that redactions cover the specified passages and that duplicated quotations, comments, hidden content, or another collected copy do not defeat the intended treatment. Confirm that separately produced attachments match their individual decisions.

Keep privilege distinct from responsiveness and personnel confidentiality. Rule 34(b)(2)(B)–(C) requires specific grounds for objections and disclosure whether responsive materials are withheld on their basis. Reconcile the privilege log with document responses; do not substitute one for the other.

Record: Add available Bates references, exact redaction locations, and reconciled dispositions. Assign discrepancies and any suspected prior disclosure for counsel’s assessment.

7. Approve and preserve the decision record

Responsible counsel should review proposed claims against sources and governing instructions. Scrutinize termination reasons, complaint investigations, and circulation beyond verified legal-advice participants. Check consistent treatment across duplicates without overriding meaningful differences.

Generate the disclosure version from approved entries only. Compare it against the internal table to remove reasoning, review comments, and revealing titles. Preserve version history so corrections remain traceable. A provisional hold must be resolved or escalated under the verified disclosure schedule; it is not an indefinite withholding category.

Record: Identify approving counsel, approval date, approved version, open-issue owner, and required next action.

Worked example

Fictional scenario: Harbor Finch Components faces a former employee’s termination and discrimination claims. The fictional records concern an August 18, 2026 termination. HR director Mira Cole communicated with operations manager Theo Lane and company counsel Lena Voss. All parties, documents, dates, and descriptions are invented.

HR initially marked an entire approval family privileged because counsel received its parent email. Review identifies a legal-advice request, a preexisting attendance attachment, and a separate investigation summary circulated to an unidentified outside address. No investigation instructions were located. The table records proposals, not final privilege conclusions.

These rows replace blanket family withholding with differentiated decisions. HF-041 contains a documented advice request, but its scope and circulation still require assessment. HF-042’s operational contents support proposed production; neither its earlier date nor attachment relationship alone decides protection.

HF-057 remains unresolved. The available record does not establish counsel-directed preparation or the outside recipient’s capacity. Follow-up could change the analysis, but the reviewer cannot supply missing evidence. Counsel must resolve or escalate this row before the applicable disclosure deadline.

Common mistakes

• Withholding every counsel-copied approval. Identify legal-advice requests separately from staffing and operational decisions; apply the governing test.
• Giving attachments the parent’s disposition. Review attendance records, complaint materials, and draft notices independently while preserving family links.
• Describing every investigation as legal work. Verify commissioning facts and purpose; do not infer them from counsel’s receipt of a summary.
• Equating sensitive personnel information with privilege. Address confidentiality through the applicable handling arrangements, separately from privilege claims.
• Serving internal notes or leaving provisional holds untracked. Build a separate approved disclosure version and assign unresolved decisions against verified deadlines.

Final quality check

Before approving the log, confirm:

• Each entry resolves to the correct source version and precise locator.
• Dates, participants, representation, and distribution facts are verified or expressly assigned.
• Each asserted protection has documented, matter-specific support.
• Attachments, duplicates, and mixed-purpose passages received appropriate separate review.
• Descriptions permit assessment without exposing protected substance.
• Redactions, withholding decisions, Bates references, and responses agree.
• Primary authorities, forum requirements, logging arrangements, and deadlines are verified.
• Open issues are resolved or expressly assigned for timely escalation; the disclosure version excludes internal reasoning.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, redaction, and production. Use that support to examine termination communications while retaining counsel’s judgment over protection claims, descriptions, and approval. The table remains your team’s work product, not a promised dedicated logging module. For related litigation preparation, see trial preparation. To discuss this workflow against your team’s requirements, book a demo.

Frequently asked questions

Should every HR document appear on the served log?

No. Determine responsiveness and treatment first, then apply the governing logging requirements to withholding and redaction claims. Keep internal records of production decisions without automatically including them in the disclosure version.

Can one entry cover a termination email and its attachments?

Check the permitted disclosure method. Internally, retain separate decisions and locators so an ordinary attendance record does not disappear within a withheld consultation. Any permitted grouping must still support assessment of the claims.

Are communications after termination automatically protected?

Do not assign protection by date alone. Review purpose, participants, content, and preparation circumstances. Separate later business explanations from legal consultations, and verify any agreed or ordered date-based logging treatment.

What if investigation instructions cannot be found?

Record the missing evidence and search owner. Assess available communications without inventing counsel direction or litigation purpose. If the gap remains material, obtain counsel’s decision and address disclosure obligations on schedule rather than leaving an unexplained hold.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34: work-product provisions, protection-claim descriptions, discovery planning, and document-response requirements; text incorporates amendments effective December 1, 2025.
• Federal Rules of Evidence, Rule 501: governing privilege framework in federal proceedings.

This general professional workflow uses an October 13, 2026 research cutoff; individual protection claims require matter-specific analysis.

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.