Building the Master Chronology Before Filing Anything

Scope and warning#

This roadmap explains a method for recording events. It does not identify which dates are legally significant in any case; that is for a lawyer reviewing the facts (Roadmap 008).

The factual situation this roadmap addresses#

Someone has a box of letters, a phone full of messages and a memory of events, and needs to turn them into something a lawyer can read in fifteen minutes.

Governing law#

Dates matter because different causes of action and procedural mechanisms attach different legal significance to an event, an actual filing, and issuance or receipt of notice. Wallace v. Kato, 549 U.S. 384 (2007), addresses accrual of a particular § 1983 false-arrest/false-imprisonment claim, not all federal or California claims. California Government Code § 12965(c)(1)(D) addresses an employment FEHA right-to-sue notice and civil-action period, subject to statutory provisions and tolling; § 12960(f), as amended by SB 477 effective January 1, 2026, contains distinct administrative-closure/tolling rules that require separate examination. Government Code § 911.2 applies in covered public-entity claim-presentation situations, not universally. See Roadmap 008 for claim-by-claim analysis.

Whether the other side can obtain a chronology depends on who made it and what it contains. Four categories are treated differently:

• Independent factual chronology. A self-prepared, shared chronology may be discoverable; merely sending an existing nonprivileged record to counsel does not automatically shield its underlying facts or originals.
• Confidential attorney-client consultation. Qualifying confidential communications between lawyer and client are protected by California Evidence Code §§ 951, 952 and 954, potentially including an appropriate prospective-client consultation; waiver and exceptions require care (including Evid. Code § 912).
• Attorney opinion work product. The absolute nondiscoverability language of California Code of Civil Procedure § 2018.030(a) concerns a writing reflecting the attorney's own impressions, conclusions, opinions, legal research or theories; it should not be mechanically applied to a layperson's neutral factual index.
• Other attorney work product. Section 2018.030(b) supplies a qualified protection for other attorney work product that may yield on the statutory unfair-prejudice or injustice showing. Federal litigation uses its distinct Rule 26(b)(3) analysis, not California's statutory two-tier rule by default.

Which category applies depends on purpose, authorship, contents, confidentiality, intended recipients and governing forum. A lawyer's request may be relevant but does not alone immunize all preexisting facts or sources. Maintain a neutral chronology separate from privileged legal analysis when counsel advises, and record any permitted disclosures or circulation rather than assuming a blanket privilege. (Grade: Settled statutory structure; particular chronology privilege and waiver fact-specific; official California codification not directly authenticated in this review.)

A chronology is an index to proof, not a substitute for proof

The most useful chronology does two jobs at once. It tells the story in date order, and it tells a lawyer where the proof for each event can be found. A row should therefore be short enough to scan but specific enough that another person can trace it back to a source without asking the author what they meant. The chronology is not the place to argue that an accommodation was reasonable, that a clinician was deliberately indifferent, or that a corporate entity controlled another entity. Those are propositions to analyze after the underlying events are fixed.

A practical way to separate fact from inference is to use three fields: event, source, and comment. The event field states only what occurred. The source field identifies the record. The comment field can identify an unanswered question—such as whether a supervisor approved the decision—but should not silently convert that question into a fact. If a later document answers the question, add a new entry or update the comment with a dated revision rather than rewriting history.

Six different dates can matter for the same event

One event can produce multiple evidentiary and legally different dates. Keep them separate (and record time zone or approximate range where material):

1. Event date: when the conduct occurred.
2. Document date: when a letter, order, chart entry, payroll record, grievance or email was created.
3. Receipt date: when the person actually received a notice or communication.
4. Knowledge date: when facts supporting a claim were discovered or reasonably could have been discovered.
5. Decision/effective date: when a decision was made and when it took effect, which may be different.
6. Transmission, filing and acceptance dates: when a charge, complaint, claim, grievance, electronic filing or notice was sent, received by a portal, accepted or rejected; preserve each separate system confirmation and time zone. Filing is not established solely by a document's draft date.

That distinction prevents a common chronology error: treating the date printed on a document as though it automatically establishes the date of receipt, accrual, notice, or injury. Roadmap 008 explains why those legal consequences have to be evaluated separately.

Record the source and its reliability

For each entry, record how the date is known. Useful source labels include contemporaneous document, system-generated record, third-party record, later recollection, and estimated date. A calendar entry written months later is not the same kind of proof as an email header or electronic medication-administration timestamp. Even system times require source context: time-zone offsets, daylight-saving conversions, server-versus-device clocks, imported records, later addenda and back-entered information can alter apparent sequence. Identify when timestamp provenance has not been verified. The chronology should expose those limitations rather than conceal them.

A source reference can be as simple as HR-014, MED-203, or EMAIL-2025-05-20-01, provided a separate index maps that identifier to the actual file. Record where it came from and whether it was lawfully acquired, the original filename, received/collected date and any transformations. Preserve the native original where authorized and work from a documented review copy. A PDF printout or screenshot may omit email headers, metadata, audit history or context, and it does not by itself authenticate a record or authorize retention of employer/patient information.

One event per row; competing versions stay separate

If two witnesses or records describe the same event differently, do not blend them into a compromise sentence. Enter the competing versions separately and mark the dispute. For example:

This format allows a reviewer to see both sequence and conflict without deciding credibility inside the chronology.

Separate four tracks that otherwise get mixed together

Complex CFMG/Wellpath matters often become clearer when the master chronology can be filtered into parallel tracks:

• Merits: clinical event, employment decision, policy application, grievance, accommodation discussion, discipline, termination.
• Procedure: government claim, EEOC/CRD charge, grievance/exhaustion, notice of intent, lawsuit, service, appeal.
• Losses/remedies: missed wages, benefits, medical expenses, death-related losses, mitigation efforts.
• Entity/bankruptcy: employer names, contract amendments, debtor notices, bar-date notices, confirmation/effective dates.

The tracks should remain part of one master chronology so that a procedural event can be compared with the underlying conduct. Filters or tags are safer than maintaining four conflicting chronologies.

Preserve revision history

A chronology becomes less trustworthy when earlier entries are silently rewritten. Keep a simple change log: date changed, entry changed, reason, and source that prompted the change. Correcting an obvious typo is different from changing an event date after locating a new document. The latter should be visible. A versioned chronology also helps counsel understand which conclusions were formed before and after particular records were obtained.

Privilege and work product require care

The fact that a chronology is useful to counsel does not itself make every underlying fact privileged. Attorney-client privilege protects qualifying confidential communications, and California work-product law protects qualifying attorney work product; those doctrines do not erase discoverable facts merely because the facts were communicated to a lawyer. A person preparing material for counsel should ask counsel how to label, transmit and store it rather than placing legal theories or counsel's advice into the same document used as the neutral factual index.

For the same reason, do not circulate a counsel-directed chronology widely. Distribution can create separate privilege questions. The safest public-education principle is simple: keep the factual master record accurate and let counsel decide how privileged analysis should be maintained.

Elements of the claim#

Not applicable; this page supports every claim. Each chronology entry has six parts:

1. Date, with how it is known (document date, postmark, phone record, memory).
2. What happened, in neutral words.
3. Who acted, with name and title as they appeared at the time.
4. Which organisation that person acted for, if a document shows it (Roadmap 003).
5. The record that shows it, and where that record is kept.
6. Gaps: what is not known and which record might show it.

Potentially relevant defendants#

Not determined here. Keep organisation names exactly as they appear on each document, because similar names can refer to different entities (Roadmap 004).

Administrative prerequisites#

Record every filing made and every response received, with dates: agency charges, government claims, grievances and appeals, notices of intent, and bankruptcy filings.

Limitation periods#

None stated here. The chronology should mark, without calculating, every date that might start or pause a clock: the event itself, the date it was discovered, notices received and filings made (Roadmap 008).

Evidence#

Records to obtain#

Through lawful channels only: personnel and payroll records (Cal. Lab. Code § 1198.5; Cal. Lab. Code § 226, subd. (b); Cal. Lab. Code § 432), the person's own medical records (Cal. Health & Saf. Code § 123110; 45 C.F.R. § 164.524), grievance copies, agency correspondence and public records (Cal. Gov. Code § 7920.000 et seq.). Access to a record through employment does not by itself establish a right to copy or keep it; patient confidentiality, proprietary information and employment duties raise separate questions (Cal. Civ. Code § 56 et seq. (Confidentiality of Medical Information Act)).

A practical chronology template

A useful working table can contain these columns:

Do not force a false precision. If the record establishes only “between 8:00 and 10:00 p.m.,” write the range. If the date is recalled as “late April,” say so. An honest uncertainty is more useful than a precise date that cannot later be defended.

Use the chronology to expose missing records

Once events are arranged in sequence, gaps often become obvious. A referral appears in a progress note but no specialist appointment appears. An HR email refers to an attached accommodation request that is missing. A grievance response refers to an investigation but the investigation file is absent. A staffing schedule shows an empty slot but payroll has not yet been obtained. Those gaps become a records plan for Roadmap 007 and, later, a discovery plan for counsel.

A gap is not proof that the missing record is unfavorable. Record it as a gap. The disciplined wording is “record not located” rather than “record was destroyed,” unless there is evidence supporting destruction.

Favorable and adverse facts#

Favorable facts

• Entries tied to documents made at the time.
• A consistent sequence across independent records.

Adverse facts

• Entries resting only on memory where records should exist.
• Gaps around the dates that matter most.

Likely defenses#

The opponent may assert a different legally relevant date (issuance instead of receipt, effective rather than announced termination), late or incomplete administrative filing, incorrect defendant identification, no proof of notice or knowledge, inconsistent payroll/medical timestamps, hearsay, or selective omission of favorable facts. A chronology cannot defeat those arguments merely by assigning precise dates; preserve the records, counter-sources, uncertainty and route-specific legal standards. See Roadmap 008 for substantive limitations defenses.

Causation#

The chronology shows sequence. Sequence alone does not prove that one event caused another.

Chronology design for causation and damages

A chronology can preserve more than liability facts without becoming a damages argument. For an employment matter, add separately sourced entries for each missed pay period, benefits change, job-search event and replacement income. For a medical matter, add hospital transfers, new diagnoses, procedures, recovery milestones and later treatment. For a death, preserve the medical/custody sequence separately from family-loss evidence. The entries should still describe what happened; the damages calculation belongs in a separate ledger.

Causation is easier to evaluate when the chronology includes the baseline before the event and the course after it. A patient with an abnormal laboratory value needs enough preceding and following data to show whether the abnormality was new, worsening or chronic. An employee alleging lost compensation needs the compensation structure before the disputed decision and what actually happened afterward. The sequence cannot prove causation by itself, but it tells experts and counsel which intervals require explanation.

Chronology quality-control questions

Before relying on the file, run these tests:

• Does every exact date have a source, or is it clearly marked as recalled/estimated?
• Are document creation, receipt and effective dates separated?
• Are disputed versions preserved instead of merged?
• Are entity names copied exactly from contemporaneous records?
• Do important events have stable source IDs?
• Are missing records described as missing rather than presumed destroyed?
• Are later-learned facts distinguished from what actors knew at the time?
• Are entries chronological even when they undermine the working theory?
• Is there a revision history for material corrections?
• Can a reviewer move from any row to the underlying source in less than a minute?

A chronology should not become a repository of privileged advice

Once counsel is retained, the lawyer may want a separate restricted work-product timeline, witness outline or legal-element chart. Do not circulate lawyer mental impressions with a neutral chronology intended for operational sharing. Access controls and distribution history matter: voluntary broad sharing of confidential advice can create waiver disputes under California Evidence Code § 912, and labeling a file “privileged” does not resolve legal protection. Store or transmit records using counsel-approved secure methods; do not publish patient, juvenile, protected employee or attorney communications.

The neutral chronology can still link to a separate issue code—such as ENTITY, ADA, MEDICAL, MONELL, DEADLINE—without stating counsel's legal conclusion. That makes one factual database reusable across legal theories.

Damages and remedies#

Record losses as they occur: lost pay, medical costs and other expenses, with documents.

Common chronology failure modes

A chronology can become misleading even when every sentence is literally true. Watch for these patterns:

Only recording adverse events. If routine care, successful accommodations, favorable responses or corrective actions disappear from the timeline, the chronology becomes an advocacy filter rather than a research tool.

Using “learned” without a source. “Management learned of the problem” should identify the communication, meeting, report or recipient that supports the statement. The same applies to a clinician's knowledge.

Backdating later interpretations. A diagnosis made in June should not appear in a March entry as though it was known in March. Put later interpretations on the later date and link them back to the earlier event.

Entity drift. If the source says “California Forensic Medical Group, Inc.,” do not shorten it to “Wellpath” in the entity field unless the source itself establishes the relationship relevant to that entry. A separate “brand/affiliation” column can preserve context without changing legal identity.

Combining absence of evidence with evidence of absence. “No referral found in records reviewed through 1 October” is defensible. “No referral was made” may not be until the relevant systems and witnesses are checked.

Using a court filing as proof of the allegation. Record that a complaint alleged something, or that a declaration stated something, unless the proposition was admitted or found.

Build a source index beside the chronology

The companion source index should contain at least: source ID, original filename/title, date, creator/issuer, entity, document type, storage location, confidentiality flag, and a one-sentence description. If the same document supports several entries, reuse the source ID rather than making duplicate copies.

For public sources, add URL and date accessed. For court documents, add court, case number, docket number, document title and filing/entry date; distinguish an allegation from an order, judicial finding or party admission. For email, retain the original message/header or lawful export if available, rather than relying only on a cropped screenshot. For protected clinical or personnel records, the index can describe the authorized custodian and lawful request pathway without storing confidential substance or unauthorized copies in an open chronology.

Use issue tags, not legal conclusions

Tags such as accommodation, medical-clearance, grievance, referral, staffing, entity, bankruptcy, notice, and damages help filter the chronology. Avoid tags such as illegal, retaliation-proved, or deliberate-indifference; those labels can smuggle the conclusion into the data set.

How counsel can use the chronology later

A well-built chronology can become the backbone for pleadings, Rule 26 disclosures, deposition preparation, discovery requests and settlement analysis. That reuse is another reason to keep it neutral. The stronger the source linkage, the less time later work spends rediscovering where a statement came from.

Discovery#

In litigation, the chronology guides discovery requests by showing which records exist and which are missing.

Reconcile sources without choosing a winner too early

When records conflict, create a reconciliation entry that identifies each source, rather than deleting one. An HR letter, payroll record and manager email can each be authentic while describing different aspects of the same employment event. A progress note, MAR and audit log can each be authentic while carrying different timestamps. The chronology should expose the disagreement and let later evidence determine which fact each source proves.

For important events, a “source stack” can list the primary record, corroborating record, contrary record and missing record. That structure is particularly useful before depositions because it shows where a witness's testimony can actually add information rather than merely repeat a document.

Use witness names carefully

A chronology can identify a witness to an event without asserting that the witness agrees with the author's version. If the information comes from the witness, label it as an interview/recollection and record the date the statement was made. Do not attribute statements to a person based on what another witness said they heard unless the hearsay source is made clear.

Flag deadline-related dates without computing a deadline

Use a visual tag such as TIME-SENSITIVE for a government-claim rejection, right-to-sue notice, grievance decision, death, discovery of injury, termination, bankruptcy notice or other potential trigger. The tag means “lawyer should evaluate this date,” not “the deadline is X.” This preserves urgency without turning the chronology into an unreliable legal calculator.

The final chronology should survive hostile reading

Before sending it to counsel, read every entry as though an opposing lawyer will challenge it. Ask: Is this fact supported? Is the source accurately characterized? Is an inference labeled? Is contrary evidence included? Are entity names exact? Does the date reflect what the source proves? A chronology that remains useful under that test is far more valuable than one optimized only to tell a persuasive story.

CFMG/Wellpath-specific relevance#

Record each exact legal-entity name as the underlying source displays it; payroll, badges, email domains, contracts and bankruptcy schedules may differ (Roadmap 004). For any event potentially connected to a Wellpath debtor, separately record the alleged event, debtor identity if documented, actual notice receipt, docket filing/entry and relevant bankruptcy procedural milestone. The inherited references to a November 11, 2024 petition and Bar Date Notice (Dkt. 776, Jan. 2, 2025; order Dkt. 491, Dec. 18, 2024) are docket-identification leads in this editing pass, not independently verified findings that a specific employer was a debtor, that all entities had the same bar date, or that notice was legally sufficient. Counsel must verify the docket and claim-specific consequences.

Primary authorities#

Related roadmaps#

Start Here; preservation; deadlines; finding counsel.

Companion worksheet (print-ready)#

Print-ready companion worksheets are in development.

Final chronology deliverables

For a complex matter, the finished chronology package should contain four related files rather than one overloaded document:

1. Master chronology: neutral dated events with source IDs.
2. Source index: what each source is, where it came from, and where the original is stored.
3. Gap/request list: missing records, unresolved identities and records to seek lawfully.
4. Change log: material corrections to chronology entries and why they changed.

A fifth, separate damages ledger can track money and losses. Counsel may create additional privileged legal-analysis files after engagement.

This structure makes the factual record portable. A lawyer can filter it by defendant, issue or date without losing the original sequence; an expert can focus on clinical events; and a corporate/entity review can focus on names and authority. The master chronology remains the common factual spine.

Additional analysis — parallel clocks and the chronology of institutional knowledge#

A strong chronology maintains event time, record creation time, receipt time and decision time separately. An email can be sent at one moment, delivered to a mailbox at another and read later or never. A physician's clinical note may describe a consultation completed hours earlier than the note was signed. A county agenda item's meeting date, execution date and effective date may differ. Treating these values as equivalent can distort both a legal time limit and the meaning of an institutional decision.

For events that involve multiple organizations, add a named-entity field and do not collapse recipients under the most visible brand. A notice delivered to a staffing vendor is not automatically notice to every legally separate corporation; an executed policy circulated enterprise-wide may, by contrast, support analysis of common practices if distribution and adoption are verified. The chronology should distinguish a person who originated a concern from one who reviewed it, approved action, or implemented a response.

A contradiction ledger should record competing versions rather than resolve them silently. If a letter says employment ended on one date, an agency record uses another and payroll reflects a later accounting event, all three may be authentic yet refer to different legal or administrative phenomena. A reliable timeline identifies the source function and preserves the discrepancy for counsel or a competent factfinder. It should not choose whichever date offers the most favorable theory.

An especially valuable addition is an explicit list of events for which no original record has been located. A missing record does not prove it was withheld or never existed. A public Roadmap can explain how to describe the gap and identify lawful source channels without instructing readers to copy confidential employer or patient materials.

Records that anchor dates independently

When several systems disagree, independently created records can help verify chronology. A court filing stamp, county board action, transport manifest, electronic sign-in, official postal tracking record or payroll period can provide a separate anchor. Each has its own meaning and limitations. A payroll effective date may not establish the date a decision was communicated, just as a medical-chart signature date may not establish when a clinical assessment occurred. Preserve all timestamps and describe the purpose for which each was generated.

What this page cannot do#

It cannot say which dates are legally significant or whether any deadline has passed.