Litigation and Recovery
Litigation Document Chronology Guide
Build a litigation chronology with separate dates, provenance, citations, uncertainty, duplicates, conflicts, gaps, privilege, access, versions, and review.
Direct answer
A litigation document chronology is a reviewed index of documents and events that preserves the event date, document date, received or filed date, source, actor, issue, assertion or verified-fact label, confidence, citation, access status, and review history. Record duplicates, contradictions, gaps, privilege, and document versions as explicit states. A chronology organizes and tests the record; it does not prove facts, determine credibility, establish admissibility, or replace qualified legal judgment.
Definitions
Event date
The date and time when the described act, occurrence, communication, decision, or condition is said to have happened, kept separate from dates attached to the document.
Document date
The date shown on, embedded in, or assigned to a document, message, file, recording, or system record, such as a letter date, creation timestamp, or authoring date.
Received or filed date
The date and time a document was received by a person or system, filed with a court or authority, uploaded to a repository, or otherwise entered the governed record.
Source
The originating repository, system, custodian, filing office, communication channel, physical collection, or external authority from which the chronology item was obtained.
Actor
The person, organization, system, or service attributed to performing, sending, receiving, recording, approving, filing, or describing the event.
Assertion
A statement made by a person, party, document, or system about an event, condition, or interpretation that is preserved as a statement rather than treated as an established fact.
Verified fact
An organization-defined review label for a proposition supported by identified sources and review steps within a declared scope; it is not a universal legal conclusion or guarantee of truth.
Confidence
A documented assessment of how well the available source, date precision, provenance, corroboration, and review support the chronology entry, using an approved qualitative vocabulary.
Citation
A reproducible pointer to the supporting source, page, paragraph, Bates range, exhibit, message ID, docket entry, file hash, transcript location, or system record.
Chronology item
One governed record connecting a described event or document to dates, actors, issues, source material, labels, uncertainty, access, and review history.
Duplicate
A record that represents the same source content or event as another item under the organization-approved matching rule, while preserving the original identifiers and duplicate decision.
Contradiction
A documented conflict between sources, dates, actors, descriptions, versions, or assertions that requires visibility and review rather than silent selection of one account.
Chronology gap
A missing, uncertain, inaccessible, or unresolved period, source, event, link, or date relationship that may affect the declared chronology scope.
Privilege or access status
A governed indication of whether the item is unrestricted, restricted, confidential, potentially privileged, work product, sealed, or otherwise subject to controlled review or distribution.
Document version
An identifiable state of a document or source record, with predecessor, successor, effective or captured time, change reason, and relationship to other versions.
Review decision
A recorded determination about the chronology item’s inclusion, date treatment, source sufficiency, issue mapping, label, access, contradiction, or follow-up, with reviewer and date.
Field definitions
Identity and scope
- chronology_item_id
- Stable identifier for the governed chronology record and its review history.
- Type: String
- Requiredness: Always required
- Validation: Unique within the matter and never reused after merge, exclusion, or closure.
- Owner: Chronology administrator
- matter_id
- Reference to the matter, investigation, claim, proceeding, or recovery workflow that defines the chronology scope.
- Type: Matter reference
- Requiredness: Always required
- Validation: Link to an active or archived matter record and preserve the governing jurisdiction and access policy.
- Owner: Matter owner
- scope_and_issue
- The declared claims, defenses, issues, topics, elements, deadlines, or questions to which the item relates.
- Type: Structured issue references
- Requiredness: Always required for included items
- Validation: Use approved issue values and permit an explicit unresolved or out-of-scope state with rationale.
- Owner: Review lead
- item_status
- Workflow state such as candidate, included, excluded, duplicate, disputed, gap, restricted, or reviewed.
- Type: Controlled value
- Requiredness: Always required
- Validation: Require a reason, reviewer, and date for excluded, duplicate, disputed, restricted, or final reviewed states.
- Owner: Chronology reviewer
Dates and event meaning
- event_date
- The date or date range attributed to the event described by the source, independent of document or receipt dates.
- Type: Date, datetime, or range
- Requiredness: Required when an event is described; otherwise explicit unknown
- Validation: Store original expression, normalized value, precision, time zone, basis, and uncertainty state.
- Owner: Chronology analyst
- document_date
- The date shown on or embedded in the source document, message, file, recording, or system record.
- Type: Date or datetime
- Requiredness: Required when available
- Validation: Do not map it to event_date without a cited source statement or approved inference.
- Owner: Collection analyst
- received_filed_date
- The date and time the item was received, uploaded, docketed, filed, or entered into the governed collection.
- Type: Datetime
- Requiredness: Required when available
- Validation: Identify the receiving system, filing office, or recipient and preserve the relevant time zone.
- Owner: Records or litigation support
- date_basis
- The source citation and review explanation for the selected event date, range, inference, or unresolved conflict.
- Type: Structured note
- Requiredness: Always required when event_date is inferred, approximate, or disputed
- Validation: Reference the source text, metadata, related items, alternative dates, and reviewer decision.
- Owner: Chronology reviewer
Source, actor, and proposition
- source_reference
- The repository, custodian, record ID, file or docket reference, collection event, and reproducible citation for the source.
- Type: Structured source record
- Requiredness: Always required
- Validation: Distinguish native source, copy, production, transcript, summary, external record, and analyst-created material.
- Owner: Collection analyst
- actor_and_roles
- The actor attributed to the event and separately recorded author, sender, recipient, filer, custodian, reviewer, or system roles.
- Type: Person, organization, and role references
- Requiredness: Required when stated or available; otherwise explicit unknown
- Validation: Preserve aliases and label attribution as stated, system-derived, disputed, or unresolved.
- Owner: Chronology analyst
- proposition
- The quoted or concise paraphrased event, assertion, observation, system entry, admission, allegation, or analyst question.
- Type: Text with citation
- Requiredness: Always required for included items
- Validation: Separate source language from analyst interpretation and cite the exact supporting location.
- Owner: Chronology analyst
- assertion_fact_label
- The approved label distinguishing source assertion, corroborated account, reviewed operational fact, disputed proposition, or unresolved status.
- Type: Controlled value with rationale
- Requiredness: Always required
- Validation: A verified-fact label requires named sources, review basis, scope, and reviewer; it never means the chronology proves the fact.
- Owner: Review lead
Quality, access, and lineage
- confidence
- The organization-approved qualitative assessment of source, date, attribution, corroboration, and review support.
- Type: Controlled value with rationale
- Requiredness: Always required
- Validation: Record the dimensions considered, evidence basis, reviewer, and reason when confidence changes.
- Owner: Chronology reviewer
- citation
- A precise pointer to the source location supporting the date, actor, proposition, issue, or review decision.
- Type: Citation set
- Requiredness: Always required for included or reviewed items
- Validation: Use page, paragraph, line, Bates, exhibit, docket, timestamp, message ID, hash, or source record reference as applicable.
- Owner: Chronology analyst
- duplicate_and_version_link
- Links to exact or near duplicates, predecessor and successor versions, translated or redacted copies, and source relationships.
- Type: Related item references
- Requiredness: Required when a relationship exists
- Validation: Preserve the matching rule, relationship type, source identifiers, and duplicate or version decision.
- Owner: Litigation support
- contradiction_gap_record
- A structured record of competing sources, unresolved intervals, missing material, broken links, or date and attribution conflicts.
- Type: Issue record
- Requiredness: Required when a contradiction or gap is identified
- Validation: Record scope, sources, effect, owner, requested action, due date, disposition, and reviewer history.
- Owner: Review lead
- privilege_access_status
- The source and chronology access classification, privilege or work-product review status, redaction state, and permitted audience.
- Type: Controlled value with access policy
- Requiredness: Always required
- Validation: Require basis, reviewer, date, distribution rule, and segregation or redaction reference where applicable.
- Owner: Matter counsel or access administrator
- review_version
- The chronology or item version, review decision, reviewer, reviewed time, change reason, and predecessor reference.
- Type: Versioned review record
- Requiredness: Always required after the first review action
- Validation: Preserve prior values and distinguish source changes from analyst corrections or interpretation changes.
- Owner: Chronology administrator
Controlled vocabulary guidance
- Date precision
- Examples: EXACT-DATETIME; EXACT-DATE; MONTH; YEAR; RANGE; APPROXIMATE; RELATIVE; INFERRED; UNKNOWN; CONFLICTING
- Governance: Require original date text, time zone or source convention, basis, and reviewer treatment for inferred, approximate, unknown, or conflicting values.
- Assertion or fact label
- Examples: SOURCE-ASSERTION; CORROBORATED-ACCOUNT; REVIEWED-OPERATIONAL-FACT; DISPUTED; UNRESOLVED; ANALYST-INTERPRETATION
- Governance: Use labels as organization-designed review states. A reviewed operational fact is scoped to the recorded sources and process and must never be presented as chronology-based proof or a legal conclusion.
- Confidence
- Examples: HIGH; MEDIUM; LOW; NOT-ASSESSABLE
- Governance: Publish qualitative anchors based on source quality, provenance, date precision, corroboration, attribution, and review completeness. Do not add or average labels as arithmetic scores.
- Source relationship
- Examples: ORIGINAL; EXACT-DUPLICATE; NEAR-DUPLICATE; REVISED; SUPERSEDES; TRANSLATION; REDACTED-COPY; PRODUCED-COPY; DERIVED-SUMMARY
- Governance: Preserve both source records and the relationship decision. A duplicate rule must be versioned and must not erase provenance, access, or contradiction evidence.
- Conflict or gap status
- Examples: NONE; OPEN; UNDER-REVIEW; PARTIALLY-RESOLVED; ACCEPTED-LIMITATION; RESOLVED; REOPENED
- Governance: Require affected scope, source references, owner, action, due date or review trigger, rationale, and disposition authority. Do not silently close a conflict because the timeline needs a single date.
- Privilege and access
- Examples: UNRESTRICTED; CONFIDENTIAL; RESTRICTED; POTENTIALLY-PRIVILEGED; WORK-PRODUCT; SEALED; PERSONAL-DATA-RESTRICTED
- Governance: Apply matter-specific policy and qualified review. Keep access status separate from truth, relevance, admissibility, and inclusion decisions.
Practical workflow
Declare the chronology question and scope
State the matter, claims or defenses, jurisdictions, entities, custodians, source collections, relevant period, time zone, issue taxonomy, intended audience, and review purpose. A chronology for internal investigation, discovery preparation, deposition preparation, or hearing support may use different access and review rules. Do not begin by assuming that every document belongs in one undifferentiated timeline.
Assign a stable chronology item ID
Create a non-reused identifier for each item or linked event record. Keep the chronology ID separate from a document ID, Bates number, docket number, message ID, hash, or repository key so later deduplication, reprocessing, and versioning do not erase source identity.
Capture source and provenance
Record the source repository, collection or custodian, source record ID, file path or docket reference, collection method, collector or service, collection time, source system, export or processing version, and any transformations. Distinguish a native source, a produced copy, a working copy, a transcript, a summary, and an analyst-created note.
Separate every relevant date
Store event date or date range, document date, received or filed date, source-capture date, and any publication, effective, reply, deadline, or version date in separate fields. Preserve the original date text, normalized value, time zone, precision, date type, and source citation. Never substitute a document date for an event date merely because it is easier to sort.
Record date precision and uncertainty
Mark exact timestamp, exact date, month, year, approximate date, date range, relative date, inferred date, unknown, or conflicting date. Preserve the basis for an inference and the alternatives considered. Do not manufacture a day, time, or sequence from a filename, email chain position, or document order without labeling the assumption.
Identify actors and roles
Record the actor connected to the event and separately identify author, sender, recipient, custodian, filer, reviewer, approver, source-system actor, and person mentioned in the text. Use stable person or organization references where possible, preserve aliases, and label attribution as stated, system-derived, disputed, or unresolved.
Extract issues and propositions
Map each item to one or more governed issues, claims, defenses, elements, topics, deadlines, damages questions, or investigation questions. Quote or paraphrase the relevant proposition with a citation, identify whether it is an assertion, admission, allegation, observation, system event, or analyst interpretation, and keep interpretation separate from the source text.
Label assertion versus reviewed fact
Treat a party statement, witness account, document description, metadata value, or system entry as the source’s assertion unless the defined review process supports a separate verified-fact label. Record the supporting sources, scope, corroboration, unresolved alternatives, and reviewer basis. A verified-fact label is a workflow status, not a statement that the chronology proves the proposition or that a court must accept it.
Attach precise citations
Link the item to a page, paragraph, line, Bates range, exhibit, docket entry, transcript timestamp, message ID, file hash, record ID, or other reproducible pointer. If the item is derived from multiple sources, cite each source and identify which source supports the date, actor, proposition, and issue. Record citation failures as gaps rather than leaving an uncited summary.
Detect duplicates and related versions
Apply a documented duplicate rule using hash, native identifier, message or docket ID, content comparison, attachment relationship, and source context as appropriate. Preserve all source references, label exact and near duplicates, and distinguish a duplicate from a revised, translated, redacted, produced, annotated, or superseding version. Do not delete the duplicate decision or the original provenance.
Surface contradictions and competing accounts
Create a contradiction record when sources disagree about date, actor, content, sequence, version, receipt, or characterization. Cite each competing source, describe the conflict neutrally, identify the issue affected, assign a review owner, and preserve the unresolved state until the authorized review is complete. Do not resolve a conflict by choosing the most recent, most detailed, or most convenient source without a recorded basis.
Identify chronology gaps
Review expected source coverage, date transitions, referenced attachments, missing pages, absent custodians, unproduced systems, unavailable versions, unexplained intervals, and broken event links. Record the gap type, time or scope, reason known or suspected, potential effect, requested follow-up, owner, due date, and whether the gap is resolved, accepted, or still open.
Apply privilege and access controls
Separate unrestricted, confidential, restricted, potentially privileged, work-product, sealed, personal, and other organization-defined statuses. Record the basis, reviewer, access audience, redaction or segregation action, privilege log reference where applicable, and change history. A chronology summary can inherit sensitivity from its sources; do not copy privileged content into a broadly accessible timeline.
Preserve document and chronology versions
Version changes to source files, normalized dates, extracted text, issue mappings, labels, citations, duplicate decisions, contradiction decisions, access status, and analyst notes. Preserve the prior value, new value, effective or review time, actor, reason, and approval where required. Do not overwrite an earlier chronology merely because a later review changes the interpretation.
Run independent review and reconciliation
Use a second reviewer or defined quality gate for high-impact items, inferred dates, verified-fact labels, privilege decisions, contradictions, gaps, and hearing or filing outputs. Reconcile the chronology to the source inventory, document versions, issue list, and known procedural events. Record review status, reviewer, date, sample or census basis, corrections, and residual limitations.
Package and report with limitations
Produce the requested chronology view with field labels, source citations, access handling, open conflicts, gaps, version state, and review status. Keep source material and analyst conclusions distinguishable. State that the chronology is an organized review aid and does not prove facts, determine credibility, establish admissibility, or replace counsel’s analysis of the governing law and record.
Comparison
| Chronology choice | Risky shortcut | Controlled approach |
|---|---|---|
| Date handling | Sort one date column that mixes event, document, and receipt dates. | Store labeled dates separately with precision, time zone, original expression, and citation. |
| Source meaning | Rewrite a document assertion as an established fact. | Preserve the proposition, assertion or fact label, source basis, scope, and uncertainty. |
| Attribution | Treat the author, custodian, sender, and event actor as interchangeable. | Record each role separately and label attribution as stated, system-derived, disputed, or unknown. |
| Citations | Use a file name or broad document reference with no precise location. | Link page, paragraph, Bates range, docket entry, timestamp, message ID, hash, or record ID. |
| Duplicates | Delete repeated records or choose one copy without preserving provenance. | Link exact, near, produced, redacted, translated, revised, and superseding relationships. |
| Contradictions | Select the latest or most detailed account without explanation. | Preserve competing sources, conflict scope, reviewer, rationale, and unresolved state. |
| Gaps | Fill unexplained periods with inferred events or omit them from the output. | Record the gap, affected period, reason, impact, follow-up, owner, and accepted limitation if applicable. |
| Access and privilege | Copy sensitive or potentially privileged narrative into a broad chronology. | Apply source and chronology access controls, segregate content, and record review basis. |
| Versioning | Overwrite dates, labels, or notes when later review changes them. | Preserve prior values, version links, change reason, reviewer, and effective review time. |
| Conclusion | Present a complete-looking timeline as proof of what happened. | Present an evidence-linked review aid with limitations, uncertainty, conflicts, and legal-review boundaries. |
Limitations and exceptions
- A chronology is an organizing and review aid. It does not prove that an event occurred, establish the truth of an assertion, determine credibility, authenticate a document, establish admissibility, or replace qualified legal analysis.
- A source may be incomplete, inaccurate, altered, translated, summarized, incorrectly dated, generated by a flawed system, or missing context. Provenance and citations make those limits visible but do not cure them.
- Document date, event date, received date, filed date, and source-capture date can describe different moments. A normalized timeline can still mislead if date type, precision, time zone, or inference basis is hidden.
- A verified-fact label is an organization-designed workflow status. It is scoped to the recorded sources and review process and must not be presented as a universal evidentiary finding or court determination.
- Duplicate and version matching can produce false positives or false negatives, especially for attachments, exports, translations, redactions, OCR, native files, and system-generated records. Preserve the matching rule and allow review.
- Contradiction and gap handling identifies issues but does not resolve disputed testimony, recollection, intent, causation, damages, or legal significance. Those questions require the appropriate investigation, discovery, and legal process.
- Privilege, work product, confidentiality, privacy, sealing, and access treatment depend on the matter, jurisdiction, source, order, policy, and qualified review. A chronology field cannot create or waive protection by itself.
- This guide does not set universal retention periods, discovery obligations, filing deadlines, authentication requirements, sampling rules, confidence thresholds, or production specifications. Tailor the method to the governing rules and matter strategy.
Primary sources
Methodology
This is an organization-designed litigation chronology method checked against the cited United States Courts, eCFR, and National Archives sources on August 13, 2026. Begin with a declared matter question, issue scope, source universe, relevant period, jurisdiction, time-zone convention, audience, and access policy. Create one stable chronology item per governed source or linked event and preserve source provenance. Keep event date, document date, received or filed date, capture date, effective date, deadline, and version date in separate fields. Preserve original date text, normalized value, precision, time zone, source citation, and any inference or conflict. Record source, actor, author, sender, recipient, custodian, filer, and reviewer as distinct roles. Quote or paraphrase the proposition and label it as source assertion, corroborated account, reviewed operational fact, disputed, unresolved, or analyst interpretation. A reviewed operational fact is a scoped workflow status, not proof that the chronology establishes a fact. Cite every material proposition to a reproducible page, paragraph, Bates range, docket entry, transcript timestamp, message ID, hash, or source record. Apply a versioned duplicate rule that distinguishes exact and near duplicates from revised, superseding, translated, redacted, produced, and derived records. Preserve contradictions and gaps as first-class records with affected scope, competing citations, owner, follow-up, and disposition. Apply matter-specific privilege, confidentiality, privacy, sealing, and least-access controls before producing views. Version all source, extraction, normalization, label, access, and review changes, then use independent review for inferred dates, high-impact labels, contradictions, gaps, privilege, and hearing or filing outputs. Report open limitations and never state that a chronology proves facts, resolves credibility, establishes admissibility, or replaces qualified legal judgment.
Build a source-linked litigation chronology
Reach out and learn more about our offerings and how CaseDocker can help you
Built for legal operations teams
Share your use case and we will connect you with the right team for product guidance, pricing, and rollout planning.
Clear next steps
Expect a response from our team with the most relevant next step for your inquiry.
Get in Touch
Get in Touch
FAQs
Related CaseDocker capabilities
Case management
Connect chronology items to matters, issues, people, tasks, deadlines, source records, access controls, review decisions, and audit history.
ExploreWorkflow playbooks
Turn chronology intake, date normalization, issue coding, contradiction review, privilege routing, and quality checks into repeatable procedures.
ExploreCompliance management
Coordinate preservation, evidence review, access decisions, exceptions, and source-linked reporting when a chronology supports an investigation or control response.
ExploreDocument eSigner and execution
Maintain controlled document versions, execution records, timestamps, and supporting source links when signed records enter a matter chronology.
ExploreTurn this guide into an operating plan
Share your current legal workflow and CaseDocker can map the right modules, integrations, controls, and rollout sequence.