How to trace employment decisions and stated reasons for Employment Discrimination Matters

Trace an employment decision by separating what happened, who participated, what each participant knew, and when each explanation appeared. Compare contemporaneous records with approval materials, employee communications, agency submissions, discovery responses, and testimony. Record each proposition against a precise source rather than treating the employer’s explanation as one continuous account. The resulting employment decision timeline should distinguish documented events, attributed statements, disputed inferences, and missing evidence so counsel can assess apparent contradictions, test alternative explanations, and assign focused follow-up.

When to use this workflow

Use this workflow when counsel must assess why an employer rejected an applicant, disciplined an employee, denied a promotion, demoted someone, or terminated employment. A concrete trigger is an agency position statement or testimony that appears different from the contemporaneous explanation. Employer counsel can test an account before relying on it; employee counsel can distinguish meaningful inconsistencies from added detail.

This guide emphasizes US federal district-court litigation. Identify the statute, forum, controlling precedent, local rules, and case-specific orders before drawing conclusions. Federal procedural and evidence rules do not automatically govern state proceedings, arbitration, or administrative investigations. See the scope provisions in the Federal Rules of Civil Procedure and Federal Rules of Evidence.

Reason tracing is not itself a discrimination finding. In Reeves, a prima facie case combined with sufficient evidence of a false justification could permit, but did not compel, a finding of intentional discrimination. The holding arose from an ADEA verdict reviewed under Rule 50; it does not supply every statute’s elements or causation standard. Reeves, 530 U.S. 133, 147–149.

What you need

Start with the challenged action and possible decision window, then assemble:

• Decision records: recommendations, approval chains, scoring sheets, selection lists, HR entries, and employee notices.
• Underlying reasons: performance records, attendance data, investigation materials, restructuring plans, headcount approvals, and applicable policy versions.
• Later explanations: agency submissions, discovery answers, declarations, deposition testimony, and corrected or supplemental accounts.
• Context and provenance: organization charts, participant roles, relevant complaints, custodians, native files, attachments, audit histories, and collection limitations.

Include favorable and adverse evidence. Keep source text separate from counsel’s interpretation, and route potentially privileged material through the matter’s review process before circulating the timeline. Identify the source universe and review cutoff so later users understand what the assessment covers.

Check preservation coverage alongside collection. EEOC guidance describes post-charge retention of relevant employment records through final disposition, including records concerning employees holding or seeking similar positions. Confirm employer coverage and applicable regulations; the guidance neither supplies a comparator test nor completes a litigation-preservation analysis. EEOC recordkeeping requirements.

Use the template

The companion template is Employment Discrimination Matters — Employment decision timeline. Copy this table into your working document or spreadsheet. Use one row per decision event or attributed explanation; several rows may concern the same action.

Event / record dates separates the event described from record creation. Use full dates where known. Label recommendation, approval, communication, and effective dates rather than collapsing them into “termination date.” Enter “unknown” instead of estimating an unsupported date.

Actor / knowledge identifies the speaker’s role and evidence of relevant knowledge. Stated reason contains a short quotation or labeled paraphrase, not counsel’s reconstructed justification. Source / pinpoint identifies the document, page or Bates number, message timestamp, or transcript page and line. Cite attachments separately.

Assessment / gaps distinguishes documented fact, attributed account, inference, dispute, and missing evidence. Cross-reference related event IDs; if using a spreadsheet, references such as “EV-03; G4” can connect an assessment to its supporting row. Next action / owner assigns a verification task and responsible person. Keep sensitive interview notes and legal analysis in appropriately restricted materials.

Step by step

1. Define the decision and split its stages

Write a narrow question: “Who decided not to promote the employee, when, and on what stated basis?” Avoid starting with an assumed motive. Identify whether the challenged action involved one decision or several—for example, shortlist removal followed by a separate compensation decision.

Create rows for recommendation, review, approval, communication, and implementation where supported. A payroll effective date does not establish when a manager selected someone for termination. Record competing dates separately, including time-zone differences when material. Output: stage-specific rows, a bounded decision window, and identified date disputes in the assessment column.

2. Map sources to the decision window

Identify custodians and systems for each stage: the supervisor’s messages, HR’s case records, finance’s headcount materials, and the approver’s communications. Include attachments and version histories that may explain a changed rationale. Record search coverage and missing periods before interpreting silence as absence.

For federal discovery, target relevant, nonprivileged, proportional material. Rule 26(b)(1) does not require discoverable information to be admissible, but it does not authorize unrestricted personnel-file collection. Federal Rules of Civil Procedure, Rule 26. Output: source references for available records and narrowly described collection gaps, each assigned to an owner.

3. Attribute each reason without erasing differences

Extract each explanation in its own terms. “Position eliminated,” “lowest assessment score,” and “repeated missed deadlines” may address different questions—or conflict. Preserve those differences before categorizing reasons for comparison. If one document states multiple reasons, separate them into linked rows when their evidentiary support differs.

Identify whether the speaker was the recommender, approver, HR communicator, submission author, or litigation witness. Do not assume an organizational submission reflects every participant’s contemporaneous view. Identify factual contributors where supported. Output: attributed reasons with record dates, pinpoints, and links to earlier or later versions.

4. Trace participation and knowledge separately

Distinguish proposing an outcome, supplying information, approving it, and communicating it. Ask what evidence establishes each participant’s knowledge at the relevant time. Where protected-status or complaint-related knowledge matters to the asserted theory, trace receipt, discussion, or acknowledgment rather than relying only on access permissions.

A distribution-list message documents transmission without necessarily establishing that a particular decisionmaker read it. Record that limitation. Separate firsthand accounts from inference and secondhand reports; note which documents a witness reviewed before giving an account. Output: actor-specific participation and knowledge entries, with unsupported propositions expressly unresolved.

5. Compare reasons and test competing interpretations

Classify differences as contradiction, elaboration, different stage, different participant perspective, or unresolved. Adding a scoring method may elaborate on “qualifications”; denying that performance mattered may conflict with an approval expressly based on performance.

Test both readings. For restructuring, examine role disposition and selection materials. For performance, check cited incidents, policy versions, and evidence that the decisionmaker received the records. Where other employees matter, record role, supervisor, period, conduct, history, and outcome. Preserve unknown values and defer legal comparability to claim-specific authority. Output: an assessment explaining both the inconsistency theory and its strongest supported alternative.

6. Assign focused follow-up and foundation questions

Convert gaps into answerable questions: Who supplied the criteria? Was the incident discussed before approval? Does the missing attachment contain original rankings? Identify the record, witness, or clarification sought rather than entering “more discovery.” Prioritize questions that could materially change the interpretation.

Track evidentiary foundation separately from significance. Federal Rules 901 and 803(6) address distinct authentication and hearsay questions; authenticating an HR email does not resolve embedded statements or every admissibility objection. Federal Rules of Evidence, Rules 901 and 803(6). Output: actions with owners, dependencies, and unresolved foundation questions recorded in the table.

7. Reconcile the timeline and state its limits

Check every material proposition against its source. Preserve superseded explanations and corrections rather than overwriting them. Summarize what the record supports, contradicts, and leaves unknown. Identify conclusions dependent on untested testimony or missing records, and record the review cutoff.

Label the intended use. A working chronology is not automatically evidence. Federal Rule 1006 addresses qualifying summaries of voluminous admissible materials and requires underlying originals or duplicates to be available to other parties at a reasonable time and place. Rule 107 separately governs illustrative aids. Federal Rules of Evidence, Rules 1006 and 107. Output: a verified timeline and qualified decision-reason assessment.

Worked example

Fictional scenario: Alder Quay Services terminated analyst Mira Vale during a department reorganization. Vale alleges age discrimination. The record contains a supervisor’s recommendation, an HR termination letter, and a later agency submission. All parties, documents, dates, and statements below are fictional.

The recommendation proposes selecting Vale because of recurring reporting errors within a planned role reduction. The employee letter refers only to restructuring. The agency submission says performance was not considered. Counsel has not received the final approval packet, role-selection spreadsheet, or error log referenced by the supervisor.

Separating restructuring from employee selection changes the analysis. EV-01 can coexist with EV-02: restructuring may explain the reduction while performance explains the supervisor’s proposed selection. EV-03 raises a sharper issue because it excludes performance from selection altogether.

The record still does not establish that the final approver accepted the recommendation. Nor does the supervisor’s reference establish that the alleged reporting errors occurred. Counsel should obtain the missing materials and test the agency account’s factual basis before treating the discrepancy as evidence supporting discriminatory intent. These three records also provide no basis for a comparator conclusion.

Common mistakes

• Treating implementation as decision: An HR effective date may postdate approval. Separate stage rows and verify the sequence.
• Combining all employer voices: A supervisor’s rationale and HR’s notice serve different functions. Attribute statements and trace information between actors.
• Calling every omission a changed story: A brief notice may omit selection details. Compare affirmative propositions before labeling a contradiction.
• Treating missing records as nonexistent: Identify collection coverage, absent attachments, and unsearched custodians. Record uncertainty instead of supplying a negative fact.
• Testing only the preferred theory: Include consistent explanations, rejected recommendations, and adverse evidence. Explain their effect on the assessment.

Final quality check

• Every material event has a stable ID and precise source reference.
• Event, creation, communication, and effective dates are distinguishable.
• Each explanation has an identified speaker or expressly unknown attribution.
• Participation and knowledge are supported separately.
• Apparent contradictions have been tested against elaboration and stage differences.
• Quotations, paraphrases, attachments, and source versions match the underlying records.
• Missing evidence and foundation issues are resolved or assigned to owners.
• The assessment states its cutoff and intended use without turning disputed inferences into findings.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, evidence analysis, chronology, and deposition preparation. Use the chronology viewer to support chronological review and carry unresolved decision-reason questions into deposition preparation. Counsel remains responsible for verifying sources, assessing inconsistencies, and applying governing law. To discuss this workflow, book a demo.

Frequently asked questions

Should each employment action have a separate timeline?

Use distinct action identifiers for discipline, promotion denial, and termination. They may share one table if links remain clear. Do not assume an earlier disciplinary rationale carried into termination without supporting evidence; trace each action’s participants and approval separately.

How should counsel record an oral explanation?

Identify speaker, listener, reported statement date, and recording date. Cite the interview record or testimony and mark whether the account is firsthand. Preserve uncertainty about exact wording. Do not present a later recollection as a contemporaneous document or conceal inconsistent recollections.

Does a newly added reason establish pretext?

Not automatically. Determine whether it supplements, contradicts, or addresses a different stage of the earlier explanation. Reeves permits an inference in the circumstances described above rather than requiring one. Apply the claim’s governing authority to the full record. Reeves, 530 U.S. 133, 147–149.

What if the final decisionmaker is unknown?

Leave the approval role unresolved. Trace authorization records, routing messages, and witness accounts, distinguishing formal authority from actual participation. Assign specific follow-up rather than substituting the person who delivered the notice. Retain competing accounts until the evidence resolves them.

Sources

• Federal Rules of Civil Procedure, particularly Rules 1 and 26(b)(1).
• Federal Rules of Evidence, particularly Rules 107, 803(6), 901, 1006, and 1101.
• EEOC: Recordkeeping Requirements.
• Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133 (2000).

Scope: General legal-workflow guidance based on the supplied research through October 13, 2026; 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.