Build a wrongful-termination chronology by separating what happened, when it happened, when it was recorded, and what the decisionmakers knew. Link each factual entry to a document and pinpoint location, preserve conflicting accounts, and distinguish the termination decision from notice and effective separation. The deliverable is a source-linked working chronology that helps counsel test stated reasons, identify missing evidence, and prepare focused witness questions without converting assumptions into facts. Use the table below as the working record, keeping legal analysis distinct from documented events.
Use this workflow when employee-side counsel, employer-side counsel, or an in-house team must reconstruct a challenged discharge. Concrete triggers include receiving a demand, assessing an administrative charge, reviewing an initial production, or preparing to question the recommending manager.
Focus on the decision sequence: employment expectations, performance or conduct concerns, relevant employee activity, management knowledge, approvals, notice, and separation. Include later explanations where they illuminate the earlier record, but identify them as later statements.
This guide assumes US practice. Wrongful termination is a matter category, not one cause of action. Establish the statutory, contractual, or state-law theory, coverage, administrative prerequisites, limitations issues, and forum separately. Federal rules discussed below do not automatically govern state proceedings, agencies, or arbitration. The chronology organizes evidence; it does not replace that legal assessment.
Start with a defined document collection and an explicit account of its limits. Gather:
Maintain a source register with document ID, filename, custodian, collection origin, metadata, and confidentiality or privilege handling. Identify missing attachments and incomplete conversations before extraction. A recommendation may look materially different when its preceding thread is restored.
Choose an initial window covering the relevant review cycle and decision process; expand it for identified questions. In federal district court, discovery concerns nonprivileged matter relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. That framework does not justify unlimited personnel-record collection. Federal Rule of Civil Procedure 26(b)(1).
The companion template is Wrongful Termination Matters — Case chronology. Copy this table into your working document or spreadsheet. Use one row per event or distinct assertion; several rows may cite the same document.
| Event ID | Event date/time | Created; effective date | Event and actors | Source ID; pinpoint | Custodian; origin | Status; contrary evidence | Issue; action; owner |
|---|---|---|---|---|---|---|---|
“Created; effective date” contains separately labeled document-creation and termination-effective dates. Split them into separate spreadsheet fields if useful. Mark unsupported dates “unknown,” not estimated without explanation.
“Source ID; pinpoint” identifies the page, paragraph, message timestamp, or spreadsheet cell supporting the assertion. “Custodian; origin” connects the row to the source register. “Status” distinguishes a documented statement, corroborated event, disputed account, or inference. A document may establish that a statement was made without proving its truth.
Use the final column for an issue tag, specific verification task, and responsible reviewer. Link competing rows by event ID. Keep extensive strategy in a separately controlled memo. Distinguish unavailable information from inapplicable or unchecked fields.
Identify the challenged action, proposed decisionmakers, stated reasons, and employee’s account. Translate them into questions: When was discharge first proposed? Which concerns predated it? Who knew about the complaint? Did the explanation change?
Do not label every complaint legally protected or treat proximity alone as a causation conclusion. Reserve legal classifications for analysis under the applicable claim. Use neutral factual tags such as “complaint receipt” and “decision approval.” Include relevant contract or policy milestones when the asserted theory makes them important.
Template output: initial milestone rows, neutral issue tags, and assigned questions rather than guessed dates.
Assign stable IDs before summarizing. Preserve message-and-attachment relationships; distinguish exact duplicates from revised versions. Identify whether the source is a native file, scan, production image, interview note, or transcript.
Set a consistent time-zone display convention while retaining original timestamps in the register. Distinguish sent time, meeting date, file creation, signature, and HR-system entry. A scan’s creation date does not establish when the underlying event occurred. Preserve earlier source IDs when later production adds Bates numbers so existing references remain usable.
Template output: stable source references, provenance, separately labeled dates, and visible uncertainty.
Write short descriptions identifying actor and action. Prefer “Manager’s email reports three missed deadlines” to “Employee repeatedly missed deadlines” until underlying records are checked.
Separate compound events. The employee’s complaint, HR’s receipt, and a supervisor’s acknowledgment may occur at different times. Likewise, distinguish recommendation, authorization, notice, and effective separation. If one source supports several stages, create separate rows with precise pinpoints rather than assuming identical dates.
Label witness materials accurately: signed statement, interview note, recording, or deposition testimony. A lawyer’s summary is not a verbatim witness account.
Template output: discrete, attributed events and a status reflecting what each source establishes.
Trace who proposed, reviewed, approved, and communicated discharge. Identify records available at each stage. Place later explanations on their actual dates rather than importing them into an earlier decision.
For relevant complaints or requests, distinguish submission, receipt, and knowledge by each decisionmaker. An email’s addressee field is relevant evidence, but does not itself establish when someone read it or understood its contents.
Where a source mentions an undated earlier meeting, use “before March 8; exact date unknown.” If software requires a sortable date, keep any sorting convention separate from the supported event date.
Template output: linked decision-stage rows, knowledge evidence, and unresolved receipt or approval questions.
Compare contemporaneous reviews, discipline, employee responses, and the termination explanation. Check that apparently conflicting records concern the same job, period, expectations, and supervisor.
Preserve contrary evidence beside favorable evidence. A positive annual review may precede a later documented incident; a negative assessment may have been revised after the decision. Identify both circumstances rather than compressing them into a single characterization.
Compare internal approvals, the termination notice, later submissions, and testimony. Flag whether differences might reflect elaboration, distinct concerns, or contradiction, without prematurely resolving which explanation fits.
Template output: paired citations, competing-account status, and a specific reconciliation question for each material discrepancy.
Replace “need more documents” with an event-specific task: obtain the recommendation’s attachment, locate complaint forwarding, or establish approval-meeting attendance. Identify the likely custodian and responsible reviewer.
Distinguish “not found in the reviewed set” from “did not exist.” Record missing custodians, systems, and date ranges. Production receipt does not establish collection completeness.
Plan authentication alongside substantive review. Federal Rule of Evidence 901 requires evidence sufficient to support a finding that an item is what its proponent claims; testimony from a knowledgeable witness is one recognized method. Authentication does not resolve hearsay or every other admissibility issue. Federal Rule of Evidence 901.
Template output: missing-evidence tasks, possible authentication witnesses, owners, and resolution status.
Have a reviewer reopen each material source and check actor, date, attribution, and pinpoint. Re-sort corrected dates, then read the sequence for unexplained jumps. Review access restrictions and separate factual entries from strategic analysis before circulation.
Record the version date, collection cutoff, incorporated productions, and intended audience. Carry unresolved issues forward explicitly.
An internal chronology is not automatically admissible. Federal Rule of Evidence 1006 permits summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced. Underlying originals or duplicates must be available for examination or copying at a reasonable time and place. Purely illustrative aids fall under Rule 107. Federal Rules of Evidence 1006 and 107.
Template output: verified rows, assigned open issues, and a controlled version note.
Fictional scenario: Northglass Instruments terminates scheduling coordinator Lena Ortiz. Ortiz alleges retaliation for complaining about discriminatory scheduling. The employer cites attendance and missed dispatch deadlines. Counsel has a complaint email, recommendation, and notice, but lacks attendance exports and dispatch logs. All parties, documents, dates, and facts below are fictional.
| Event ID | Event date/time | Created; effective date | Event and actors | Source ID; pinpoint | Custodian; origin | Status; contrary evidence | Issue; action; owner |
|---|---|---|---|---|---|---|---|
| E01 | March 3, 2026, 9:12 a.m. | Created March 3; effective N/A | Ortiz emails HR alleging discriminatory scheduling | NG001; body and To field | HR; email collection | Submission documented; manager knowledge unknown | Knowledge; obtain forwarding chain; associate |
| E02 | March 5, 2026 | Created March 5; effective unknown | Manager recommends discharge for dispatch delays; references February 27 discussion | NG014; p. 1 | Manager; email collection | Recommendation documented; earlier discussion unverified | Timing; obtain meeting evidence and dispatch logs; counsel |
| E03 | March 8, 2026 | Created March 8; effective March 12 | Notice cites attendance as discharge reason | NG021; p. 1 | HR; personnel file | Notice documented; attendance data missing; compare E02 | Reasons; locate approval and attendance records; associate |
A date list places the complaint before the recommendation and may encourage a premature inference. The source-backed version instead exposes three questions: whether the manager knew about the complaint, what occurred on February 27, and why the notice identifies a different reason.
Do not insert a February 27 termination decision as fact: NG014 reports only a discussion. Nor does the absent attendance export establish invented concerns. The immediate decision is to pursue targeted verification, not select a definitive narrative. Forwarding records could clarify knowledge; contemporaneous meeting evidence could change the apparent sequence; operational records could support or undermine either explanation. Until obtained, those possibilities remain open.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its chronology capabilities alongside document review and evidence analysis to support source-focused organization, then carry verified questions into deposition preparation. Counsel retains responsibility for verifying dates, evaluating competing accounts, and determining legal significance. To assess fit with your chronology workflow, book a demo.
Start with the relevant review cycle, employee activity, and earliest identified decision discussion. Expand when sources identify earlier warnings, policy changes, or contract milestones. Record the boundary and its limitations rather than presenting the chosen window as complete employment history.
Include specific comparator events when they illuminate the challenged decision. Record role, supervisor, applicable policy, and relevant circumstances; similar titles alone do not explain the comparison. Link detailed comparator material separately and control access to sensitive personnel information.
First determine whether they describe different milestones. Notice and payroll-effective dates may both be accurate. If they describe the same event, retain both citations, mark the conflict, and assign verification. Do not silently choose the date that better supports a theory.
Potentially, after a separate assessment of purpose, underlying evidence, admissibility, disclosure requirements, and forum rules. Distinguish an evidentiary summary from an illustrative aid. Do not use the internal analytical version merely because its entries contain citations.
Scope: General professional workflow guidance, 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.