Skip to content

Privacy and preparation

Legal matter chronology dataset: when a timeline is a reasoning task

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

A legal timeline is a useful reasoning task when a model must order dated, sourced facts, choose the controlling document and reconcile conflicting dates, not summarize a folder. Each case needs counsel-approved nonprivileged sources, the contract version in force on each date, the amendments and approvals that changed it, recorded date conflicts and an exclusion record showing what was withheld and why.

Record timeline

Legal matter chronology

This page covers legal matter chronology dataset: when a timeline is a reasoning task.Illustrative

Key takeaways

  • A chronology becomes a task only when the question, allowed sources, answer key and reasons for wrong answers are fixed.
  • Rebuild timelines from business records after counsel screens them; litigation chronologies are often work product.
  • Store every candidate date with its precision and basis, and keep conflicts instead of resolving them silently.
  • Rank sources by authority so an executed amendment beats an email that sounds certain.
  • An exclusion record describes what was withheld by category, never its content.
  • Score ordering, date basis, controlling source, conflict detection and respect for exclusions separately.

A legal timeline is a useful reasoning task when the model has to decide what happened, when, and under which version of the governing terms, using sources that disagree. A folder of contracts, emails and notices only becomes a task once someone fixes the question, the allowed sources, the expected answer and the reasons a wrong answer is wrong.

That is the difference between a pile of documents and a legal matter chronology dataset. Each case holds a defined source set, a target chronology in which every entry cites the passage it rests on, a record of date conflicts and how they were resolved, a map of which contract version was in force on each date, and an exclusion record for everything counsel kept out.

Litigation tools already treat chronology this way. Relativity's Case Dynamics documentation describes facts as statements that can be shown to be true, each with a primary fact date, a date type for single dates or ranges, linked documents and supporting excerpts, displayed in date order in a timeline builder. Research benchmarks take the same approach to legal reasoning: LegalBench packages each legal task as a dataset of input and output pairs so a model's answers can be checked, rather than judged by how fluent they sound.

Why is a lawyer's own chronology usually the wrong starting file?

The chronology a litigation team already built is usually the wrong file to start from, because it is often attorney work product and it carries counsel's selection and emphasis. Federal Rule of Civil Procedure 26(b)(3) generally protects documents and tangible things prepared in anticipation of litigation or for trial by or for a party or its representative, which describes most litigation chronologies.

Rebuild the task from the underlying business records instead: the signed agreement, its amendments, purchase orders, delivery confirmations, formal notices and approval logs. Counsel then screens that set, removes anything privileged or prepared for the dispute, and approves what remains. The target chronology is written fresh from the approved sources, by a reviewer who knows the answer key will be audited against them.

Why is a lawyer's own chronology usually the wrong starting file?
Record classUsual statusEntry rule for the dataset
Signed contracts, amendments and statements of workBusiness record; confidentiality terms may restrict sharingEligible after a counterparty confidentiality check
Operational records such as orders, deliveries, invoices and system approval logsBusiness record created in the ordinary courseEligible; strongest evidence for dates
Formal notices sent between the partiesBusiness record, sometimes drafted with counselEligible as sent; drafts and internal comments excluded
Emails between business staff about performanceBusiness record; may contain personal dataEligible after privilege and personal data screen
Emails to or from counsel, legal memos, counsel's chronologiesLikely privileged or work productExcluded and logged by category
Documents received in discovery from another partySubject to protective orders and court rulesExcluded unless counsel confirms the order allows it

Which fields must a chronology case fill before it counts as a task?

The brief is the asset: a fixed set of fields that every case must fill before it counts as a task. Field names are suggestions; the validation checks are the part a qualified reviewer should not waive.

  • Use roles, not names, for people in event entries; keep the role map with counsel.
  • Write event descriptions in neutral language; characterizations such as breach or waiver are conclusions for the answer key, not facts in the timeline.
  • Keep the brief versioned so a later re-review can show what changed and why.
Which fields must a chronology case fill before it counts as a task?
FieldWhat it holdsWhy the task needs itValidation check
Matter scopeThe question the chronology must answer, the date window and the parties by roleFixes what counts as a relevant eventScope approved by counsel before sourcing starts
Source registerDocument ID, system of origin, document type, created date, custodian role, authority levelLets every entry be traced to one recordEvery document resolves to a stored copy and a hash
Event entriesEvent ID, event date, date precision, date basis, actor role, short neutral description, source excerpt pointerThe chronology itselfNo entry without at least one source excerpt
Governing version mapWhich agreement version, amendment or order of precedence applied on each dateMany questions turn on the terms in force at that momentEffective dates do not overlap without an explicit precedence rule
Authority recordWho signed or approved each change, in what role, and the authority it relied onSeparates a binding change from a suggestionSigner role matches the authority clause or approval policy
Conflict registerEach pair of sources that disagree on a date or fact, and the resolution with its reasonThis is where the reasoning is testedEvery conflict is resolved or left open on purpose, never deleted
Exclusion recordCategory of each withheld item, reason, reviewer role and date, without its contentShows the task is incomplete by designCount of excluded items reconciles to the source register
Task questions and answer keyQuestions asked of the model and the expected answer with citationsMakes the case scorableEach answer cites entries, not the reviewer's memory
Counsel sign-offReviewer role, date and the version of the brief approvedRecords that privilege and confidentiality were checkedNo case is released without it
LimitsWhat the case cannot support, such as facts outside the recordStops over-reading of the answer keyPresent on every case, even when short

Which date goes on the timeline when the documents disagree?

Record the date the evidence supports at the precision it supports, and store the other candidate dates as conflicts rather than averaging them away. A signature date, an effective date, a sent date and a received date can all be different for one notice, and the governing terms usually say which one matters.

Computed dates need their rule. Under Federal Rule of Civil Procedure 6(a), a period stated in days excludes the day of the triggering event, counts every day including weekends and legal holidays, and runs to the next business day when the last day falls on a weekend or holiday. Contract notice clauses often count differently, so the brief stores the rule used for each deadline and the clause it came from.

Which date goes on the timeline when the documents disagree?
Date conflictTypical causeHow to enter it
Signature date differs from effective dateAgreement made effective as of an earlier or later dayEnter both; the version map uses the effective date
Notice sent on one day, received days laterCourier, mail or email delivery rules in the contractEnter both; cite the clause that says when notice is deemed given
Email timestamp in a different time zone from the contractServer time or sender's local timeStore the original timestamp and zone, convert once, record the conversion
Only a month or quarter is knownUndated memo or a later reference to an earlier eventSet precision to month or quarter; never invent a day
Two records give different days for one deliverySystem entry made after the eventKeep both in the conflict register with the resolution reason

Which source, amendment or signature controls an entry?

A signed amendment executed under the agreement's own amendment clause outranks an email, a call note or a system field that says something different. The brief's authority record exists so the model is tested on that ranking, not on which document sounds most certain.

Rank sources before writing the answer key, and write the ranking into the case so a reviewer can disagree with it explicitly.

  • Executed agreement and executed amendments, read through any order of precedence clause.
  • Formal notices given in the manner the agreement requires.
  • Approvals recorded in a contract or procurement system by a role the approval policy authorizes.
  • Operational records created when the event happened, such as delivery confirmations and invoices.
  • Business correspondence about the matter, which shows intent and knowledge but usually does not change terms by itself.
  • Unsigned drafts and redlines, which are context only and never control an entry.
  • Later summaries, including internal status reports, which are checked against the records above and never cited alone.

Worked example: a supply agreement termination notice (illustrative)

This example is illustrative. The parties, dates and counts are invented to show the brief working; no real matter is described.

A distributor and a manufacturer sign a supply agreement that requires written amendments signed by both parties and termination notice of 60 days, deemed given on receipt. The task question is: on what date could the manufacturer's termination take effect, and which records control that answer?

  • Answer key: notice was deemed given on June 12 and the 60-day period runs from that receipt, with the computation and clause cited; the June 2 email is a recorded conflict that a model must notice and reject.
  • Common wrong answer: counting 30 days from June 10. It fails twice, on the controlling source and on the trigger date.
  • Exception: if the amendment clause allowed changes by email confirmation from named roles, the June 2 email would need an authority check against that clause, and the answer key would change. The brief records that the clause was checked.
Worked example: a supply agreement termination notice (illustrative)
EntryDate and precisionSourceRole in the answer
Agreement signed and effectiveMarch 3, exactExecuted agreementSets the 60-day notice and the written amendment rule
Amendment 1 extends the termJanuary 15 the next year, exactExecuted amendment signed by both partiesControls the term end date
Sales manager emails that the notice period will be 30 daysJune 2, exactBusiness emailConflict: not a signed amendment, so it does not change the notice period
Termination notice sent by courierJune 10, exactNotice letter and courier recordSent date; not the date notice is deemed given
Courier confirms deliveryJune 12, exactCourier delivery confirmationReceipt date that starts the notice period
Final purchase order shippedMid-August, month precisionWarehouse reportContext; precision too low to anchor any deadline
Counsel memo on the disputeNot enteredExcluded as privilegedLogged by category in the exclusion record

Where do privilege, client confidences and court orders draw the boundary?

Privilege screening comes before any reasoning design, and it is counsel's call on the specific documents. When a party withholds material in litigation as privileged or as trial-preparation material, Rule 26(b)(5)(A) requires it to make the claim expressly and describe the withheld items well enough for others to assess the claim without revealing the protected content. The exclusion record borrows that logic: it shows what category was withheld and why, never the content.

Court orders do not stretch to dataset building. A Federal Rule of Evidence 502(d) order lets a court decide that privilege or work-product protection is not waived by disclosure connected with the litigation before it; that protects litigation production, not a later decision to share records for model training. Documents received from an opponent under a protective order belong to that order's terms.

Law firms face a further constraint. ABA Model Rule 1.6 covers all information relating to the representation of a client, whatever its source, and asks lawyers to make reasonable efforts to prevent unauthorized disclosure. ABA Formal Opinion 512 says a client's informed consent is needed before information relating to a representation goes into a self-learning generative AI tool, and that boilerplate in an engagement letter is not enough. Companies building from their own business records start from a different position, but their contracts still carry confidentiality clauses that counsel must read.

Ownership, access and permission are separate questions. Being able to open a record in the contract system does not mean the company may license it, and removing names does not create a right to share a counterparty's confidential terms.

How do you score a chronology without rewarding a confident story?

Score each part of the chronology separately, so a model that writes a tidy narrative from the wrong source loses points it would win on fluency alone.

Keep the answer key away from the task text, and run a second reviewer over a sample of cases before release. Disagreement between reviewers is a signal to tighten the brief, not to average the answers.

How do you score a chronology without rewarding a confident story?
MeasureWhat earns creditWhat fails
OrderingEvents in the correct sequence, with ties and ranges handled as recordedInventing a day to break a tie
Date basisThe right date type for the question, such as receipt rather than sendingUsing the first date found in the text
Controlling sourceCiting the executed document that governs the entryCiting an email or summary that conflicts with it
Conflict detectionNaming each recorded conflict and the reason it resolves one waySilently picking one side
Respecting exclusionsSaying the record is incomplete where the exclusion log shows a gapFilling the gap with assumed facts

When does a matter belong back with counsel instead of in the dataset?

Some matters cost more to screen than they are worth as tasks. Stop or narrow the scope when any of these appear, and record the reason in the brief.

  • The key events are documented mostly in communications with counsel, so the nonprivileged record cannot support an answer.
  • The matter is active, under a litigation hold, or subject to a protective order whose terms counsel has not cleared.
  • Counterparty confidentiality clauses forbid disclosure of the agreement or its terms without consent.
  • Records involve health, financial account or other sensitive personal data that needs a separate privacy review.
  • The answer depends on a contested legal interpretation rather than on documents, which makes the answer key an opinion.
  • A reviewer cannot reconcile the exclusion record to the source register.

Can a company license its contract and matter records for chronology tasks?

Contract archives, amendment trails and approval logs that a business already keeps can support chronology tasks once counsel has screened them. For a company that wants to license that screened material, SourceX manages the rights review, the contract, the preparation and the delivery.

A legal operations team can learn whether its company qualifies from a brief assessment that asks for no documents. Because the company signs off on scope and terms before a single record is delivered, active matters, particular counterparties or whole record classes can be carved out at the outset.

Frequently asked questions

What is a legal matter chronology dataset?

It is a set of cases in which each case pairs a fixed group of approved source records with a target chronology, a conflict register, a version map of the governing terms and an answer key. A model is tested on ordering events, choosing the controlling source and spotting conflicts, not on summarizing documents.

Can we use the chronology our litigation team already wrote?

Usually not as the source. Litigation chronologies are often work product and reflect counsel's selection. Rebuild the timeline from the underlying business records after counsel screens them, and write the answer key fresh.

Does a clawback or 502(d) order allow us to share documents for AI training?

No. A Rule 502(d) order addresses whether disclosure connected with the litigation waives privilege; it does not authorize other uses. Treat dataset sharing as a separate decision that counsel reviews.

How should approximate or missing dates be recorded?

Record the precision the evidence supports, such as month or quarter, and never invent a day. If two sources disagree, keep both in the conflict register with the reason one controls.

Who should sign off on each case?

Qualified counsel should approve the source set and exclusions, and a legal operations reviewer should check the brief's fields and answer key. Record both roles and the brief version in the case.

Sources

  • Relativity's Case Dynamics documentation lists fact fields including a primary fact date, a date type for single dates or ranges, fact documents and fact excerpts. Source
  • Relativity describes facts as statements that can be shown to be real or true, distinct from disputed issues, and a timeline builder that shows facts in chronological order. Source
  • LegalBench is a collaboratively built benchmark of legal reasoning tasks, each with a dataset of input and output pairs used to evaluate models. Source
  • The Federal Rules of Civil Procedure (as amended to December 1, 2025) include Rule 6(a) on computing time, Rule 26(b)(3) on trial-preparation materials and Rule 26(b)(5)(A) on claiming privilege for withheld materials. Source
  • Federal Rule of Evidence 502(d) (December 1, 2025 edition) allows a federal court to order that privilege or work-product protection is not waived by disclosure connected with the litigation pending before it. Source
  • The comment to ABA Model Rule 1.6 explains that confidentiality covers all information relating to the representation, whatever its source, and that lawyers must make reasonable efforts to prevent unauthorized disclosure. Source
  • ABA Formal Opinion 512 (July 2024) says informed client consent is required before information relating to a representation is entered into a self-learning generative AI tool, and boilerplate consent is not sufficient. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies