How to organize performance and disciplinary histories for Wrongful Termination Matters

Organize performance and disciplinary histories as a source-linked chronology that separates what happened, when it was recorded, and what termination decisionmakers knew. Preserve complete review cycles, applicable policy versions, employee responses, and competing accounts rather than extracting only adverse entries. The resulting deliverable lets counsel trace each asserted performance problem through evaluation, warning, opportunity to improve, and termination rationale, while identifying missing records and unresolved explanations. Use the chronology to test the record, not to convert disputed allegations into established facts.

When to use this workflow

Use this workflow when employment counsel or an in-house team receives a termination demand, discrimination charge, complaint, or personnel-file production and needs to assess the employee’s performance history. It is particularly useful when favorable evaluations coexist with later discipline, supervisors changed, or termination explanations differ across documents.

The task is evidence analysis, not a complete litigation plan. Identify the asserted claims, governing law, contractual rights, and forum before deciding which events matter. This guide uses a US practice orientation; its federal discovery and evidence references do not supply the requirements for every state proceeding, agency matter, or arbitration. Check the applicable forum’s rules separately.

What you need

Collect complete evaluation cycles: rating criteria, self-assessments, supervisor narratives, calibration records if maintained, and relevant compensation recommendations. Add disciplinary notices, coaching records, performance improvement plans, underlying work examples, relevant attendance records, and employee acknowledgments or rebuttals.

Obtain the policy version effective for each disciplinary event, including exceptions and acknowledgment language. Include employment agreements or collective bargaining provisions counsel identifies as relevant to performance review or discipline. Gather termination notices, internal approvals, and manager communications showing when concerns arose and who received them. Keep agency submissions and retrospective accounts identifiable as later statements.

For comparison records, collect context about role, supervisor, standards, period, and conduct. Start with an inventory of custodians, systems, date coverage, and missing attachments. Restrict circulation of sensitive personnel information and keep counsel’s analysis distinguishable from source extracts.

For covered employers, 29 CFR 1602.14 requires retention of an involuntarily terminated employee’s personnel records for one year after termination. Following covered discrimination charges or specified enforcement actions, relevant records must remain preserved through final disposition, including records concerning employees in similar positions. This is not a universal retention schedule or permission to destroy after one year; assess other preservation duties separately. (ecfr.gov)

Use the template

The companion template is Wrongful Termination Matters — Personnel history chronology. Copy this table into your working document or spreadsheet. Use one row per material event or distinct account; connect related rows with stable entry IDs.

“Event date” identifies the underlying conduct, evaluation, meeting, or decision. “Record date” identifies source creation; note revisions without overwriting the original date. Use separate rows for termination approval, communication, and effective termination.

In “Source / custodian,” enter the document ID, page or clause, and custodian. For spreadsheets, include the sheet and cell range. Link additional sources rather than compressing several unsupported assertions into one entry.

“Decisionmaker knowledge” records evidence of receipt or awareness. “Status / response” distinguishes attributed allegations, disputed accounts, source-supported facts, and counsel’s inferences. Include the employee’s response or a linked row. Each material gap needs an owner and a concrete next action, not simply “investigate.”

Step by step

1. Define the review period and performance questions

Start with the stated termination reasons. Translate each into a factual question: Which deadlines were missed? Which quality standard applied? Was the warning delivered? Choose a period that captures the performance baseline and disciplinary sequence, expanding it when earlier records explain later ratings.

Keep collection and review connected to claims and defenses. In federal district court, Rule 26(b)(1) limits discovery to relevant, nonprivileged matter proportional to the case. Personnel-record requests are not automatically unlimited, and discoverability does not require admissibility. (uscourts.gov)

Record: A scope entry identifying the period, termination reasons being tested, relevant roles, and unresolved scope questions. Label it as a review instruction rather than a historical event.

2. Establish source identity and date reliability

Assign document IDs before extracting events. Preserve originals and distinguish signed evaluations, drafts, system exports, email attachments, and retrospective summaries. Check whether displayed dates represent creation, approval, delivery, acknowledgment, or export. An exported report may list old events without establishing when each entry was first recorded.

Do not silently resolve conflicting dates. Identify the conflict and the evidence needed to explain it. Link duplicates while retaining meaningful differences, such as a handwritten response or changed rating. Mark an undated document as undated; a surrounding email may establish transmission without establishing creation.

Record: Event and record dates, exact source locations, custodian, version status, and date uncertainty.

3. Reconstruct complete evaluation cycles

Read each evaluation as a whole. Capture the covered period, rating scale, evaluator, role expectations, strengths, deficiencies, and employee response. A favorable overall rating may coexist with a specific weakness. An unfavorable rating may address changed responsibilities rather than deterioration under unchanged standards.

Connect ratings to supporting work records. Identify supervisor changes, workload, targets, and job duties. Separate a source’s explanation from counsel’s hypothesis. If a improvement plan sets checkpoints, compare each checkpoint with the recorded follow-up and final assessment. Missing evaluations or checkpoint notes are gaps, not proof that no review occurred.

Record: Evaluation and checkpoint rows linked to criteria, supporting examples, employee responses, and missing portions of the cycle.

4. Trace discipline against the applicable policy

For each warning or improvement plan, identify the alleged conduct, incident dates, issuing manager, cited policy, expected correction, review period, and recorded outcome. Link the operative policy and acknowledgment. Distinguish receipt from agreement with the warning’s contents.

Compare the sequence with the policy’s actual language, including discretion and exceptions. Do not assume every policy requires progressive discipline or that a departure establishes liability. Identify whether a follow-up was required, merely contemplated, or not addressed. Flag contractual and governing-law questions for counsel instead of resolving them through chronology labels.

Record: Linked incident, warning, response, follow-up, and outcome rows, with precise policy citations and unresolved departures.

5. Connect performance records to decisionmaker knowledge

Identify who recommended, approved, and communicated termination. Establish which performance records each person received before the relevant decision. Use dated emails, meeting records, acknowledgments, or attributed testimony. A document’s presence in HR does not itself establish a manager’s awareness.

Compare contemporaneous reasons with later accounts. In its ADEA disparate-treatment context, Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133, 147–149 (2000) explains that a prima facie case combined with sufficient evidence rejecting the employer’s explanation may permit—but does not compel—a discrimination finding. It is not a universal test for every termination claim. (law.cornell.edu)

Record: Knowledge evidence, when each reason appeared, and differences requiring explanation. Distinguish “earliest supplied record” from “first time the concern arose.”

6. Test competing accounts and comparison context

Place the employee’s response beside each disputed criticism. Identify whether disagreement concerns the event, responsibility, severity, applicable standard, or treatment of others. Preserve the manager’s explanation too; do not substitute a blended narrative that neither source supports.

For proposed comparisons, record role, supervisor, period, conduct, policy, and outcome. Identify missing context before drawing an inference. Counsel should determine the legally relevant comparison under the particular claim; the chronology supplies evidence, not a universal comparator test. A similar job title alone should not settle the assessment.

Record: Dispute status, contrary evidence, comparison limitations, and a targeted question assigned to a reviewer or witness.

7. Verify citations and close the review loop

Have a reviewer reopen every material cited source and confirm the wording. Check whether the entry accurately reports an allegation without endorsing it. Identify an author, recipient, system custodian, or other potential witness who can explain important records.

Under Federal Rule of Evidence 901, authentication requires sufficient evidence that an item is what its proponent claims; testimony from a knowledgeable witness is one recognized method. Authentication does not resolve relevance, hearsay, or other admissibility questions. (uscourts.gov)

Record: Verified citations, potential foundation witnesses, corrected characterizations, and owners for remaining gaps. Issue a dated working version while retaining unresolved competing accounts and keeping analytical notes distinct from factual entries.

Worked example

Fictional scenario: Alder Quay Instruments terminated service coordinator Mira Sol effective September 18, 2026. Its notice cited repeated dispatch delays despite coaching. Counsel receives a favorable prior-year evaluation, a June warning, Sol’s rebuttal, the applicable policy, a September approval email, and the termination notice.

The warning alleges three late dispatches. The supplied records contain neither dispatch logs nor the staffing roster referenced in the rebuttal. Policy §4 calls for documented follow-up, but no follow-up record has been supplied. The September approval also mentions incomplete service records. All parties, documents, dates, and policy wording in this example are fictional.

The three representative entries below summarize linked events; the working chronology would give the warning, rebuttal, approval, and effective termination separate rows.

The chronology changes the immediate review decision. The favorable annual review does not disprove later delays because the periods differ. The warning records an allegation, but supplied evidence does not corroborate the dispatch dates or resolve staffing responsibility. Missing follow-up requires a targeted inquiry, not a conclusion that follow-up never happened.

The incomplete-records concern was documented before effective termination. It therefore should not be labeled a post-termination explanation. The unresolved questions are when it arose, what supported it, whether it influenced approval, and why the notice omitted it.

Common mistakes

• Sorting only by document date. Retrospective allegations can appear contemporaneous. Maintain separate event and creation dates and flag later additions.
• Extracting negative sentences alone. This obscures strengths and rating qualifications. Preserve the full review cycle and cite contextual passages.
• Treating acknowledgment as admission. Read the signature language and link any rebuttal; record receipt separately from agreement.
• Applying today’s policy to an earlier warning. Obtain the operative version and identify exceptions before describing a departure.
• Calling every difference a changed reason. Differences may reflect period, detail, or audience. Describe the difference precisely and seek supporting explanation.

Final quality check

• Every material entry has a stable ID and retrievable page, clause, or cell citation.
• Event dates, creation dates, revisions, and effective termination remain distinguishable.
• Complete evaluations, employee responses, and disciplinary outcomes are represented.
• Policy references match the relevant version and preserve discretion or exceptions.
• Decisionmaker knowledge rests on identified evidence or is expressly unknown.
• Material characterizations have been verified against sources, including contrary evidence.
• Open issues are resolved or assigned to an identified owner with a specific question.
• The working version separates source facts from analysis and has an appropriate circulation list.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its chronology viewer supports organizing events and reviewing their source documents, which can assist examination of the performance and discipline sequence. Counsel remains responsible for source verification, competing accounts, and legal conclusions. To discuss this personnel-history workflow with your team, book a demo. (decover.ai)

Frequently asked questions

How far back should the history go?

Capture the performance baseline and relevant disciplinary sequence. Expand when supervisor changes, revised duties, policy revisions, or missing evaluations make the initial period misleading. Document the boundary and its reason rather than choosing an arbitrary number of years.

Should positive reviews remain if termination concerns later conduct?

Yes. Label their periods and criteria. They supply context without necessarily contradicting later criticism. Test whether the records concern different duties or standards, or whether the later explanation leaves an unexplained inconsistency.

How should undocumented oral coaching appear?

Create an attributed-account row identifying who reports the coaching and when the account was recorded. Separate the alleged conversation date from the statement date. Identify missing notes, recipient responses, or corroborating witnesses without assuming the conversation occurred—or that missing notes prove it did not.

Can the chronology itself become trial evidence?

Not automatically. Federal Rule of Evidence 1006 permits evidentiary summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not the underlying materials are introduced. Originals or duplicates must be available for examination or copying. Rule 107 separately addresses illustrative aids. A working chronology containing disputed assertions and counsel’s analysis needs separate assessment before either use. (uscourts.gov)

Sources

• Federal Rules of Civil Procedure, Rule 26(b)(1), incorporating amendments effective December 1, 2025.
• Federal Rules of Evidence, Rules 901, 1006, and 107.
• 29 CFR 1602.14, personnel-record preservation; the supplied research records page currency through October 9, 2026.
• Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133, 147–149 (2000), Court opinion reproduced by Cornell.

Scope: General legal-workflow guidance for professional readers, 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.