How to prepare a document collection checklist for Wrongful Termination Matters

Prepare a wrongful termination document collection checklist by mapping the asserted claims and defenses to the termination decision, identifying the people and systems holding relevant records, and assigning a bounded collection task to each source. Include performance history, complaints, decision approvals, communications, payroll, and exit records—not just the personnel file. The resulting deliverable should show what counsel requested, what was collected, its source, the verification performed, and who must resolve each gap before the defined collection task is closed.

When to use this workflow

Use this workflow when counsel receives a termination complaint, discrimination charge, demand letter, or discovery request, or when an internal review identifies a likely employment dispute. It serves employee-side counsel collecting client-held evidence and employer-side teams coordinating HR, IT, managers, and outside counsel.

Wrongful termination is a matter category, not one cause of action. Identify the actual theories, governing law, statutory coverage, contractual terms, administrative prerequisites, and forum. Discrimination, retaliation, contractual, and state public-policy claims may call for different collection boundaries.

This guide emphasizes US federal district-court discovery and covered employment-discrimination disputes. Federal procedure does not automatically govern state litigation, agency proceedings, or arbitration. The checklist organizes collection; it is not a discovery response, privilege log, or production authorization.

What you need

Gather these inputs before assigning collection tasks:

• Matter documents: complaint, charge, demand, response, employment or severance agreement, discovery requests, and applicable collection protocols.
• Decision details: stated termination reasons, recommendation and approval dates, effective termination date, decisionmakers, and proposed comparison employees.
• Employment history: role changes, supervisors, performance cycles, discipline, attendance, complaints, leave or accommodation issues, and policy versions.
• Source inventory: HR and payroll systems, manager email, business chats, shared drives, investigation repositories, paper files, and relevant personal-device business communications.
• Collection constraints: system owners, departing custodians, access permissions, retention settings, historical data availability, and existing preservation instructions.

Employee-side counsel should distinguish records the client possesses from employer-controlled records requiring discovery or another authorized route. Do not direct a client to bypass access restrictions. Employer-side counsel should identify who can authorize collection of sensitive personnel, medical, and investigation material.

Use the template

The Wrongful Termination Matters — Document collection checklist is a working inventory. Copy this table into your working document or spreadsheet. Use one row for each source-specific collection task; split rows when custodians, periods, or methods differ.

ID / issue connects the task to a disputed proposition, such as who approved termination or whether performance concerns predated a complaint. Records / period defines categories and date boundaries; explain extensions needed to capture a complete review cycle or earlier event.

Source / locator initially identifies the repository. After collection, add batch identifiers, document IDs, and page, message, or spreadsheet-cell references. Link a separate manifest where necessary.

Risk / access records deletion exposure, account closure, sensitive content, and authorization questions. Owner / method identifies the person responsible and the collection approach. Status / gap distinguishes requested, received, verified, unavailable, and unresolved. Receipt is not verification.

Next action / basis states the remaining task and its reason. Include the responsible person and an internal target date. Label that date as an internal target, not a court deadline.

Step by step

1. Define the questions the collection must answer

Translate the dispute into factual questions. Who proposed dismissal? What information reached the approver? Did the employee dispute the performance record? Were complaints or accommodation requests communicated before the decision? Which documents establish compensation and claimed losses?

In federal discovery, Rule 26(b)(1) limits scope to nonprivileged matter relevant to claims or defenses and proportional to the case. Information within that scope need not be admissible to be discoverable. Do not treat every employee file as automatically discoverable. Federal Rules of Civil Procedure, Rule 26(b)(1)

Record: Assign an issue ID to each category, with its factual purpose and date rationale. Submit speculative or unusually burdensome categories for counsel’s scope decision before issuing collection instructions.

2. Map decision participants to actual repositories

Identify the recommending supervisor, approving executive, HR adviser, investigator, payroll contact, and relevant employee witnesses. Ask where each kept business records: email, chat, shared documents, local files, paper notes, or personal-device communications.

Do not assume HR holds the entire decision record. Its file may contain the signed notice while a manager’s mailbox contains drafts and objections. Ask system owners about attachments, historical versions, archived accounts, linked files, and records migrated between systems.

Record: Create separate rows for each custodian and repository. Identify the technical source owner and collection owner, even when neither is the factual witness. Flag sources outside the client’s possession or authorized access for counsel’s decision.

3. Triage preservation and access before collecting

Ask whether accounts will close, chats expire, devices will be reassigned, or paper records may be discarded. Escalate risks promptly; checklist preparation should not delay preservation decisions. Record the action actually confirmed, by whom, rather than merely marking “hold sent.”

For covered employers, 29 CFR 1602.14 requires keeping an involuntarily terminated employee’s personnel records for one year after termination. Following a discrimination charge or specified enforcement action under Title VII, the ADA, or GINA, relevant personnel records must be preserved through final disposition, including relevant records of employees in similar positions. This is not a universal retention schedule or permission to destroy after one year. 29 CFR 1602.14

Record: Enter the risk, responsible person, confirmation evidence, and unresolved access question. Assess other preservation obligations separately; do not substitute routine retention settings for that assessment.

4. Specify employment-specific collection boundaries

Request complete performance cycles, applicable policy versions and acknowledgments, improvement plans, employee responses, and underlying records supporting discipline. Collect drafts, recommendations, approvals, termination notices, and exit documents. Include later agency or unemployment explanations when relevant, while distinguishing them from information available at the decision date.

Treat complaints, accommodation files, and investigations as distinct sources with controlled access. For proposed comparators, identify the role, supervisor, conduct, period, and decision context supporting collection; do not begin with the entire workforce. Contract-based claims may require offer letters, amendments, incentive terms, and provisions governing termination or severance.

For damages, identify payroll, benefits, severance, and relevant client-held post-termination earnings or job-search records.

Record: Specify categories, periods, inclusions, exclusions, and rationale. Require collectors to identify unavailable categories expressly rather than silently omitting them.

5. Collect with provenance sufficient to explain the records

Agree how the collector will retain useful context: sender and recipient details, timestamps, attachments, spreadsheet structure, and versions. Screenshots may provide leads, but ask whether fuller source records are available. Keep source material distinct from counsel’s annotations and extracts.

Capture who supplied each batch, its originating system, collection date, filters, and known limitations. Rule 901 requires evidence sufficient to support finding that an item is what its proponent claims and recognizes authentication through a knowledgeable witness. Provenance assists that evaluation; authentication does not resolve hearsay or every other admissibility issue. Federal Rules of Evidence, Rule 901

Record: Add batch IDs, locators, method, and the person able to explain the records. Flag missing metadata, incomplete threads, or conversions that removed useful context.

6. Reconcile receipt against the request and decision sequence

Compare each batch with the requested categories and period. Check whether referenced attachments arrived, reviews contain all pages, and approval messages identify uncollected meeting notes. Compare termination explanations without assuming every difference establishes wrongdoing.

Distinguish “not supplied,” “not located after the described search,” “reported deleted,” and “never created according to the custodian.” Ask which repositories and periods were searched and whether filters excluded likely records. Preserve conflicting explanations instead of selecting one prematurely.

Record: Add representative document and page citations, the verification performed, and each shortfall. Assign targeted follow-up collection. Record the account supporting a gap explanation, rather than converting that account into an established fact.

7. Close collection tasks without authorizing production

Separate collection completeness from privilege, confidentiality, responsiveness, and production decisions. Route sensitive records to appropriate reviewers. Counsel’s participation alone should not be used as the review team’s shortcut for classifying every communication as privileged.

When otherwise discoverable information is withheld on privilege or trial-preparation grounds in federal litigation, Rule 26(b)(5)(A) requires an express claim and a description permitting assessment without revealing protected information. The checklist flags review needs; it does not replace that process. Federal Rules of Civil Procedure, Rule 26(b)(5)(A)

Record: Close a row only after verifying its defined task or documenting a limitation accepted by counsel. Assign unresolved gaps. If discovery requests prompted collection, link the separate response tracker so missing records are not confused with withholding decisions.

Worked example

Fictional scenario: Alder Quay Instruments dismisses Maya Chen, a service supervisor, on June 18, 2026, citing repeated scheduling errors. Chen alleges retaliation for her March 12 internal discrimination complaint. Employer’s counsel receives a termination notice and two performance reviews. The notice references a scheduling audit, but the packet contains none.

Counsel creates three priority tasks. All parties, records, identifiers, dates, and facts below are fictional. Each collection period falls within 2026.

The HR packet cannot be treated as complete merely because it contains the formal notice. The audit becomes a discrete task, while impending account closure makes the supervisor’s communications urgent.

The complaint supports HR’s receipt of the allegation, not the termination approver’s knowledge. Counsel seeks routing evidence rather than marking knowledge established. Similarly, the email’s reference to an earlier chat does not establish when termination was approved. Neither missing source is reconstructed from assumptions; the checklist preserves the uncertainty and identifies who must investigate it.

Common mistakes

• Equating the personnel file with the record. Map manager communications, approvals, payroll, and investigation sources separately.
• Collecting only support for the stated reason. Include employee responses, earlier evaluations, contrary accounts, and contemporaneous explanations.
• Applying one period to every source. Tie performance collection to relevant review cycles and communications to the decision sequence.
• Treating comparator collection as unrestricted. Explain the proposed comparison and obtain counsel’s scope and confidentiality decision.
• Closing a task when files arrive. Reconcile categories, periods, attachments, and referenced materials before marking verification complete.
• Calling every missing document nonexistent. Record the search and custodian’s account; retain uncertainty where the evidence stops.

Final quality check

Before handing off the checklist, confirm:

• Every category maps to a claim, defense, or factual question.
• Decisionmakers, repositories, and collection owners are separately identified.
• Date boundaries capture necessary performance and policy context.
• Preservation risks have confirmation evidence or an assigned escalation.
• Document IDs, page references, and manifests match the actual source records.
• Missing attachments, versions, and decision materials are resolved or expressly assigned.
• Sensitive and potentially privileged records have an appropriate review route.
• Closed rows identify verification and limitations; the handoff does not imply production approval.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, chronology, and evidence analysis capabilities can support counsel’s assessment of collected employment records. Use the chronology viewer when examining the termination sequence and trial preparation capabilities for later witness and evidence work. These activities do not establish collection completeness. The checklist remains counsel’s work product, and counsel determines scope, gaps, and disclosure. To discuss review of records collected through this workflow, book a demo.

Frequently asked questions

Should counsel collect the employee’s entire personnel file?

It can be a useful starting source, but define the task and inspect completeness. The file may omit manager communications, prior versions, or underlying disciplinary evidence. Collecting it does not mean every item is responsive or appropriate for production.

How should personal-device business messages be handled?

Identify the application, account, custodian, and period. Have counsel resolve access, authorization, privacy, and method before collection. Preserve unanswered questions rather than directing a blanket device search or relying only on selected screenshots.

What if performance data cited at termination cannot be located?

Create a gap entry identifying who relied on it, its reported location, the search performed, and possible alternative copies. Seek supporting communications without treating them as substitutes for the missing data. Do not reconstruct evidence and label it contemporaneous.

When is the checklist ready for handoff?

When each defined task has a verified result or a limitation expressly accepted by counsel, with open issues assigned. Include source locators, collection boundaries, and follow-up ownership. Handoff does not mean privilege review, discovery responses, or production approval are complete.

Sources

• Federal Rules of Civil Procedure, Rules 26(b)(1) and 26(b)(5)(A); text incorporating the December 1, 2025 amendments.
• Federal Rules of Evidence, Rule 901(a) and (b)(1).
• 29 CFR 1602.14, personnel-record preservation.

Scope: General professional workflow guidance using the supplied October 13, 2026 research cutoff. The supplied eCFR verification extends through October 9, 2026; other retention and preservation obligations require separate assessment.

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.