A case chronology is a dated, sourced index of the events and documents that matter to a case, with each entry tied back to its supporting discovery document and Bates range. It gives legal teams a searchable timeline of the evidence without requiring them to reconstruct dates, documents, and references manually across the entire production.
Key Takeaways:
- A case chronology turns discovery documents into a dated, searchable timeline with each entry linked to its source.
- Bates stamping and chronology building are different jobs. Parseur does not apply Bates numbers, but it can extract information from documents that have already been stamped.
- A useful chronology can include Bates ranges, document dates, document types, custodians, recipients, summaries, privilege flags, and links to the source PDFs.
- Parseur's Vision AI can extract those fields from PDFs, scans, emails, and other documents and send the structured data to spreadsheets or downstream workflows.
- AI can handle the repetitive reading and data-entry work, but relevance, privilege, and legal significance still require human review.
What A Case Chronology Is, And What Goes In One
A case chronology is a chronological record of the events that matter to a case, organized by date and supported by the underlying discovery documents. It gives attorneys and legal teams a timeline they can scan quickly instead of piecing together dates, people, actions, and supporting evidence across hundreds or thousands of pages.
The need is current: a 2026 survey by Nextpoint of 101 legal professionals asked respondents to name their firm's biggest discovery challenges. Document management, review, and reduction led at 58%, followed by data collection at 34%, working with clients on collections at 31%, and chronology and timeline building at 28%.
A typical case chronology spreadsheet includes:
| Field | What to capture |
|---|---|
| Date | When the event occurred |
| Event | What happened, stated clearly and factually |
| People involved | The parties, witnesses, employees, or other relevant people |
| Document | The discovery document that supports the event |
| Page / Bates number | Where the supporting information appears |
| Source | Email, contract, medical record, report, photograph, deposition exhibit, etc. |
| Notes | Context, inconsistencies, follow-up questions, or other useful details |
The chronology is not the same thing as a privilege log or a deposition summary.
A privilege log tracks documents or portions of documents being withheld from production because of attorney-client privilege, work-product protection, or another applicable protection. Its purpose is to identify the withheld material and provide enough information to evaluate the asserted privilege. It is a discovery-management record, not a timeline of events.
A deposition summary organizes what a witness said during a deposition. It may include key testimony, admissions, disputed facts, and relevant transcript pages. Unlike a chronology, it focuses on testimony, not necessarily the sequence of events in the underlying case.
A case chronology can draw information from both. A deposition might establish that something happened on a particular date, while an email, invoice, report, or contract provides the documentary support. The chronology brings those pieces together into one timeline.
Document-heavy work is also where legal teams have been putting AI first. Thomson Reuters' 2025 Generative AI in Professional Services Report found that among legal professionals already using AI tools, document review was the most common application at 77%, with document summarization at 74%. Worth noting the base: active generative AI use among legal organizations stood at 26% at the time, so those figures describe how early adopters use the technology, not how common it is across the profession.
The exact columns will vary by case, but the basic goal stays the same: turn scattered discovery into a timeline that a legal team can search, verify, and use.
What Is a Bates Number?
A Bates number is a unique sequential identifier stamped on each page or document in a legal production set. It typically takes the form of an alphanumeric prefix followed by a zero-padded number, such as ABC000001, ABC000002, and so on.
The name comes from the Bates Manufacturing Company, which produced the "Bates Numberer" starting in 1891: a mechanical hand stamp that automatically advanced its counter with each impression. Before digital document management, legal teams used these devices to create traceable, unique references across large volumes of paper.
Today, Bates numbering is still the standard method for identifying and tracking pages in discovery productions. When legal teams refer to a "Bates range," they mean the span from the first stamped page of a document (ABC000001) to its last (ABC000004). That range lets any party locate the specific pages supporting an event in the chronology without reopening the entire production set.
Tools such as Adobe Acrobat, Relativity, and Everlaw handle the actual stamping. Once documents are stamped, Parseur can read those numbers from the pages and include them as structured fields in a case chronology or discovery index.
Why Building One By Hand Takes So Long
Building a case chronology manually turns document review into a data-entry project. Someone has to open the discovery files, find the relevant dates and events, record the Bates numbers, write a useful description, and then keep the spreadsheet consistent as the review grows.
Paralegals describe this workflow regularly in practitioner forums. In one thread, a paralegal dealing with 14,000 pages of discoverable documents asked for ways to make the process more efficient because they had to record each document, its date, and its Bates number in chronological order. One response described the usual setup as a Word or Excel chart with columns for date, Bates number, document type or source, and description.
That sounds straightforward until you multiply it across thousands of pages.
The spreadsheet is not the hard part
Excel or Word can handle the final table. The slow part is getting reliable information into it.
A typical manual workflow looks something like this:
- Open a discovery document.
- Search or scan for dates, names, and relevant events.
- Identify the document's Bates range.
- Read enough surrounding context to understand what happened.
- Write a concise description.
- Add the row to Excel or a Word table.
- Repeat for the next document.
- Go back and fix dates, duplicate entries, missing Bates numbers, or inconsistent descriptions.
The tools may change, but the human still has to do the reading and judgment.
Throughput estimates from practitioners vary widely. In one discussion of discovery indexing, a paralegal maintaining an index with fields for Bates number, date, sender and recipients, description, document type, notes, and hot documents estimated 500 documents in 8 hours when moving quickly, while others in the same discussion put 300 to 400 documents closer to a realistic pace. These are individual estimates rather than measured benchmarks, and they depend heavily on document length, quality, and how much context each entry requires. The useful signal is not the specific number but its shape: this work is measured in hours per few hundred documents, and it scales linearly with production.
Word tables, Excel, and Ctrl+F only solve part of the problem
Legal teams have plenty of ways to make the manual process less painful.
Some use Word tables. Others use Excel to sort and filter by date, Bates number, document type, or notes. One paralegal described using Excel to track discovery and recommending fields such as Bates range, date, document type, parent or child relationship, sender, recipient, subject, and notes. Macros can take some repetitive work off the table too.
And yes, Ctrl+F helps. It can find a name, date, phrase, or keyword inside a searchable document much faster than reading every word.
But finding a phrase is not the same as building a chronology.
The person doing the review still has to decide whether the hit represents a meaningful event, determine its date, understand the surrounding context, connect it to the correct Bates range, and turn it into a useful chronology row.
That distinction becomes more important as the document set grows. A spreadsheet can organize thousands of rows. It cannot read the documents and decide which facts belong in those rows.
The result is a workflow that looks automated from the outside because the final product is an Excel file. In reality, much of the work happened between the PDF and the first cell.
That is the part worth automating.
Bates Stamping Versus Bates Indexing - Where Parseur Fits
Bates stamping and Bates indexing are two different jobs. Parseur does not apply Bates numbers to documents. Bates stamping is the process of assigning a unique identifier, usually a sequential number or alphanumeric code, to pages or documents in a legal production set. Tools such as Adobe Acrobat, Relativity, Everlaw, and other legal discovery platforms can handle Bates numbering and related production workflows.
Bates indexing comes later. Once documents are stamped, a legal team may need to organize information about them into a searchable index or case chronology.
That distinction matters if you are building a case chronology from discovery documents.
Parseur does not decide that page 1 should become ABC000001 and page 2 should become ABC000002. It comes into play after the documents have been prepared and stamped.
The remaining problem is often much more repetitive:
Open the document → read it → identify the relevant event → find the date → record the Bates number → write the description → add the row to the spreadsheet.
If you have hundreds or thousands of pages, that means repeating essentially the same document-reading and data-entry process hundreds or thousands of times.
This is where document parsing can help.
Parseur can take the discovery documents you have already prepared and extract the information you want into structured fields. Depending on the documents and workflow, that might include:
- Event dates
- Names of people involved
- Document types
- Descriptions or relevant text
- Bates numbers already present in the document
- Other fields needed for the chronology
The extracted data can then be sent to a spreadsheet, database, API, or automation workflow rather than being copied into each row manually.
The important boundary is simple: Parseur does not replace Bates-stamping software. It automates the work that can happen after stamping: reading documents and turning the information inside them into structured data.
That makes it useful for the question that often comes immediately after Bates stamping: how do I turn this pile of stamped discovery documents into a usable index or chronology?
The Field Schema
A useful discovery document index should capture enough information to identify, sort, review, and trace each document without reopening the entire production set.
These fields come from the document itself, and are what an extraction engine reads:
| Field | What it captures |
|---|---|
| Bates begin | The first Bates number assigned to the document |
| Bates end | The last Bates number assigned to the document |
| Document date | The date shown on or associated with the document |
| Date received | When the document was received, if that information is available |
| Document type | Email, contract, invoice, report, letter, photograph, spreadsheet, and so on |
| Author or custodian | The person who created the document or the person responsible for maintaining it |
| Recipient | The person or people the document was sent or addressed to |
| One-line summary | A concise description of what the document contains or why it matters |
| Privilege designation | Any privilege marking already applied to the document during review |
These fields describe the file rather than its contents, and Parseur captures them through metadata fields rather than through AI extraction:
| Field | What it captures |
|---|---|
| Page count | Number of pages in the document |
| Production volume | The production set, volume, or other grouping the document belongs to |
| Link to source PDF | A direct path or link back to the original document |
The distinction matters in practice. Asking an AI engine to report a page count or produce a link to the source file is asking it for information that is not written on the page. Those values come from the document's metadata, and treating them as extraction fields is a common way to end up with rows that look complete but are not.
The privilege field deserves particular care. It records a designation a reviewer has already applied. The extraction engine does not make it, and you should never treat it as one.
The Bates begin and Bates end fields anchor the row to the production itself. The metadata fields make the index searchable and sortable. The one-line summary gives a reviewer enough context to decide whether the document deserves a closer look.
The link to the source PDF is particularly useful. An index should make it easier to find the underlying evidence, not create another place where the evidence gets separated from its context.
Not every document set will contain every field. For example, a received date may not exist in the production, and a custodian may be unknown. The schema is a starting point, not a requirement to manufacture metadata that the documents do not contain.
The important part is consistency. If every document becomes a row with the same fields, the resulting spreadsheet can be sorted by date, filtered by document type or custodian, searched by Bates range, and connected back to the source document.
That is where automation becomes useful: the schema is fixed, but the documents are not. PDFs, emails, scans, spreadsheets, and reports all present their information differently. The work is extracting the same useful fields from each one and putting them into the same structure.
How To Build It With Parseur
Once you define the field schema, the workflow is straightforward. Parseur uses its Vision AI capabilities to read the documents, identify the information you need, and return it as structured data.
1. Upload your discovery documents
Upload the discovery documents you want Parseur to process. Parseur can read PDFs, including scanned documents and image-based files, and extract the fields you define.
Keep documents from the same production or workflow together where possible. This helps maintain a consistent structure as Parseur processes the files and returns the extracted data.
2. Let Vision AI extract the fields
Vision AI reads each document and returns the fields written on the page:
- Bates begin and Bates end
- Document date
- Date received
- Document type
- Author or custodian
- Recipient
- One-line summary
- Any privilege designation already marked on the document
Page count, production volume, and the link back to the source file come from metadata fields rather than from the AI engine, since none of that information appears in the document's content.
The important part is that you are not asking the system to extract everything. You define the information your chronology actually needs and turn those fields into structured data.
This is especially useful when the source material includes PDFs, scanned documents, emails, and other formats. The layout can change from one document to the next without requiring you to rebuild the spreadsheet structure manually.
3. Review the extracted data
Automation does not mean skipping review.
Check the extracted results, particularly dates, Bates ranges, names, summaries, and any fields where the source document is difficult to read. Correct anything that needs attention before sending the data downstream.
The goal is to review the extracted data, rather than manually type every row from the original documents.
4. Export the chronology
Once the data looks right, send it to the destination your workflow uses.
You can export the structured results to a spreadsheet or connect Parseur to other tools through integrations, APIs, webhooks, or automation platforms.
From there, you can sort the chronology by document date, filter it by document type or custodian, search by Bates number, and link each row back to the underlying source.
The result is the same structured chronology you would build manually, but Parseur automates the repetitive step between discovery documents and spreadsheet rows.
Where The Spreadsheet Goes Next
A case chronology does not have to stop at an Excel file sitting in someone's Downloads folder. Once Parseur turns discovery documents into structured rows, those rows can feed the tools your legal team already uses.
For a straightforward workflow, send the results directly to Google Sheets or Microsoft Excel. Parseur has native integrations for both, so the chronology can become a live spreadsheet rather than a one-time export.
If the spreadsheet is only one step in a larger process, use an automation platform:
- Zapier can take parsed fields from Parseur and send them to thousands of connected applications, including spreadsheets and other business tools.
- Make is useful when the workflow needs branching, data transformation, or multiple destinations. Parseur sends the extracted data to Make, which handles the routing.
- Power Automate fits teams already working in the Microsoft ecosystem and can route extracted data into Excel, SharePoint, Dynamics, and other connected applications.
- APIs or webhooks make more sense when the destination is a case management system, internal database, or custom application without a ready-made integration. Parseur can send the extracted fields as structured JSON to an endpoint you control.
The choice depends on what you want to happen after the chronology is created. A simple case may need nothing more than a Google Sheet. A larger legal operation might want the same extracted data routed into a case management system, stored in an internal database, or used to trigger another workflow.
The useful part is that the document-reading step does not have to end with manual spreadsheet entry. Parseur extracts the fields once, and the structured data can keep moving through the workflow automatically.
Before You Upload - Confidentiality And Retention
Discovery documents are not ordinary business files. A production set may contain privileged material, information covered by a protective order, trade secrets, medical records, or personal data belonging to people who are not parties to the case. Before any of it goes into a third-party service, the key questions are where it is stored, for how long, and who can access it.
With Parseur, the relevant controls are:
Retention. The retention period is configurable from one day to unlimited, depending on the plan, and is set per mailbox. For discovery work, a short retention window is usually the right default: Parseur reads the documents and hands the structured data to your spreadsheet or case management system, so the source files rarely need to persist in the parsing layer afterward.
Hosting and compliance. Parseur offers EU hosting and publishes its security controls, subprocessors, and compliance posture through its Trust Center. A data processing agreement is available and applies automatically on signup.
Access. Mailboxes can be scoped so that only the people working a given matter can see the documents in them.
What Still Needs A Human
Automating document intake does not mean automating legal judgment. Parseur can read discovery documents and turn the information into structured fields, but a lawyer or qualified legal professional still needs to decide what the information means and what to do with it.
That distinction matters most in three areas.
Privilege calls. A privilege flag can help organize documents for review, but Parseur should not be treated as the decision-maker on whether attorney-client privilege, work-product protection, or another legal protection applies. Those are legal determinations that require human review.
Relevance. A document can contain the right date, names, and keywords and still be irrelevant to the issue you are investigating. Conversely, a document that looks routine may become important when considered alongside other evidence. Automated extraction can surface information. It cannot reliably determine its legal significance.
Legal judgment. A chronology is ultimately a working tool for attorneys and legal teams. Deciding which events matter, how to interpret conflicting evidence, whether a statement is significant, or what additional discovery is needed requires context and professional judgment.
Think of Vision AI as a data-entry and document-reading assistant, not a replacement for legal review. It can take the repetitive work of finding and structuring information off the team's plate while leaving the decisions that require legal expertise with the people responsible for making them.
That is also why a review step belongs in the workflow. Automate the extraction. Keep the judgment human.
This article describes a document-processing workflow and is not legal advice. Qualified legal professionals working on the matter make decisions about privilege, relevance, production obligations, and how to handle discovery material.
Last updated on
