A chronology is more than a list of email timestamps. A message sent on Tuesday may describe an event on Sunday, attach a letter dated Monday and refer to something happening later that week. Sorting only the messages can misrepresent the underlying sequence, while filling gaps can create events the sources never establish.
This article proposes a source-linked matter chronology for a lawyer's review. The worked correspondence is fictional. The assistant organises statements and date evidence; it does not decide which account is true, resolve disputed facts or draw legal conclusions from the timeline.
Define the permitted correspondence collection
Start with the matter reference, approved source locations and covered period. Identify which mailboxes, uploaded files and attachments the preparation process may inspect. A broad search for similar party names can pull in unrelated matters unless the application enforces the permitted scope.
Record the inventory and retrieval state. If part of a thread is missing or an attachment is unreadable, show that limitation before drafting the chronology. A gap in the collection is different from evidence that no communication or event occurred.
Google's Gmail push guide documents mailbox-change notifications and history-based retrieval of changes. A notification is not the full message or a complete matter record. The application needs authorised retrieval, verified matter mapping and collection checks. Source: Gmail push notifications
Record each date according to its evidence
For every candidate event, store the stated event date, message or document date, source location and date interpretation. Keep the original timezone or offset when a timestamp matters. A local display can be useful, but should not erase the source value or introduce an unsupported location assumption.
Label date-only statements as date-only. Two events on the same date may have unknown order. Do not assign midnight timestamps merely to make sorting easy or infer that the first extracted paragraph happened first.
Relative wording needs its own status. If the source says later that week, record a tentative sequence relationship and the supporting phrase. Ask the lawyer to review the interpretation where needed. Do not replace it with a specific day to make the chronology visually complete.
Reviewable matter chronology
Use this complete hypothetical chronology for TEST-MATTER-A. Entries reflect source statements, not established findings. References and dates are fictional fixtures.
| Entry | Candidate event or communication | Date basis and source | Review status |
|---|---|---|---|
| E01 | Sender says a discussion took place on 1 November 2026 | Event date explicitly stated in M01, sent on 3 November | Attributed statement; lawyer reviews relevance and factual status |
| E02 | A letter is dated 2 November and was attached to M02 on 4 November | Letter date in L01; transmission date in M02 | Keep document date and sending date separate |
| E03 | Another sender places the same described discussion on 2 November | Event statement in M03, sent on 5 November | Conflict with E01; preserve both accounts without choosing |
| E04 | M04 states a follow-up occurred later that week | Relative phrase in M04; no explicit event date | Tentative sequence after the referenced event; no exact date invented |
| E05 | Message M05 was sent on 6 November | Communication timestamp in approved source header | Communication event only; attached material remains unreadable |
Source-register collection note: two imported copies of M01 resolve to the same verified original message. Retain E01 as the single event statement and record both collection references in the source register. This is a collection check, not another chronology event.
The working chronology stores entry reference, matter reference, source version, source author context, faithful event description, event-date candidate, date basis, message or document timestamp, timezone interpretation if used, source location, uncertainty, related entries and lawyer review status. Keep source statements attributed, especially where parties disagree.
Attach three companion records: a source register with collection and access status; a conflict list linking incompatible dates or accounts; and a gap list identifying missing threads, unreadable attachments and unresolved relative wording. None should claim that absence in the supplied collection proves an event did not happen.
Review actions: verify the extraction against the original; correct date-purpose mistakes; approve any inferred sequence used; decide how disputed accounts should be presented; and identify required additional evidence through the authorised process. Record corrections with reviewer and version while leaving the original correspondence unchanged.
Acceptance fixtures: a straightforward stated event; a message describing an earlier event; a document date different from transmission; an undated relative statement; conflicting dates; duplicate messages; and an unreadable attachment. Expected results preserve all date bases and uncertainty, with no fabricated event or unsupported credibility decision.
The chronology is ready for review when every entry resolves to an authorised source and every uncertainty has a visible disposition. A reviewed draft may support the lawyer's work, but its structure does not turn attributed statements into proven facts.
Retrieve passages without claiming complete coverage
OpenAI's file-search guide describes semantic and keyword retrieval from uploaded files with citations. This can help locate passages relevant to an event, but does not guarantee that every correspondence item or reference has been found. Maintain the approved inventory and compare it with the reviewed entries. Source: OpenAI file search
A citation should point to the source actually supporting the event description. Do not cite a thread generally when the relevant statement is in a particular message or attachment. If exact source location is unavailable, record the limitation and hold the entry's review rather than attaching a nearby passage.
Keep access boundaries intact in the final pack. An incoming reviewer should open sources through the firm's authorised path. A chronology shared for a narrower audience may need less detail and different links than the internal working version.
Use structure to preserve distinctions, not erase them
OpenAI's Structured Outputs guide supports constrained responses and refusal handling. A schema can require separate event date, communication date, date basis and uncertainty. It does not establish chronology accuracy or factual truth. Source: OpenAI structured outputs
Validate the relationships after extraction. An entry with a correct date format can still use the email date for the described event. Check that the wording and source support the assigned purpose, and retain null or unresolved values where an exact date is absent.
Do not ask the model to resolve contradictions merely to produce a clean sort order. Group disputed candidates or show them alongside the established communication sequence, according to the lawyer's approved presentation. The point is reviewable evidence, not an artificially smooth narrative.
Work through normal, missing and duplicate correspondence
In a hypothetical normal case, M01 explicitly states an event date and has a separate sending date. The assistant records both and attributes the event to the sender. The lawyer can inspect the source and decide its factual and legal significance without reconstructing the extraction.
In a missing-date case, M04 provides only relative wording. The chronology preserves a tentative sequence relationship and the exact uncertainty. It does not infer the day from a later email or use a common business-week assumption.
In a duplicate case, two imports contain the same verified message. The chronology records one statement with provenance for both copies. If two similar messages are actually different sources, preserve them separately until the identity and relationship are confirmed. Repeated wording is not automatically independent corroboration.
FAQ about AI-assisted matter chronologies
Can the chronology present allegations as facts?
Keep source statements attributed and their review status visible. The lawyer determines how disputed accounts should be used. A well-formed timeline is not a factual finding.
How should events with the same date be ordered?
Use verified time evidence where it exists. Otherwise mark the order unresolved or apply an explicitly approved presentation convention that does not imply known sequence. Do not invent times.
What if a later source contradicts an earlier entry?
Preserve both source references, flag the conflict and return it to the reviewer. Record any approved correction or presentation decision without overwriting the original evidence.
If your business needs help defining this process, explore AI agents for law firms, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.