WoluTools

Legal & Compliance

Build a case chronology from your documents

Upload PDF, DOCX or TXT files and get a dated timeline in a workbook, each event linked to its source passage. Disputed and undated items are kept apart.

or drop them here

PDF, DOCX, TXT · Up to 4,000 words · 64,000 extracted characters maximum
AI tool: needs an account and credits, cost shown before you start

No file at hand? See the prepared example

AI job1 credit = 1 small AI job3 AI creditsper job · Pro includes 40 credits a month · packs from €6.99
  • PDF / DOCX / TXT
  • Up to 4,000 words
  • 64,000 extracted characters maximum
Prepared result preview · fictional sample dataFictional correspondence bundle
Source
Email A, page 1: On 12 May 2027, Alex wrote: Shipment arrived damaged.
Email B, page 3: On 13 May 2027, Morgan wrote: Packaging appeared intact.
Measured interpretation
  • First dated statement: 12 May 2027
  • Conflicting statement retained: Packaging appeared intact

Chronology workbook, evidence HTML, source-linked events and conflict queues

BringPDF, DOCX, TXT
GetChronology workbook, evidence HTML, source-linked events and conflict queues
PrivacyEncrypted source · 24-hour result

One clear job, from source to download

  1. 1

    Add the source

    Supported formats and limits are visible before the upload.

  2. 2

    Confirm the settings

    Review the exact source, options, units and access before processing.

  3. 3

    Inspect and download

    Check the preview and warnings, then unlock the complete package.

A dated timeline that keeps every source visible

What you put in

You upload the documents in the case as PDF, DOCX or TXT. One run reads up to 4,000 words and 64,000 extracted characters. Only dated statements in those files are taken. Nothing is added from outside the bundle. A larger bundle has to be split across several runs. The job costs 3 AI credits and needs an account. You see the cost before it starts.

Checking the chronology

You get a chronology workbook and an evidence HTML file. Each event row names the document and page it came from. The evidence file opens the quoted passage, so a reviewer can read the exact wording. When two documents describe the same event differently, both rows stay, each with its own citation. Undated statements go into their own queue instead of onto the timeline. Duplicates are kept too, so nothing drops out without notice.

Date format and the reviewer's call

Date display offers DD.MM.YYYY, YYYY-MM-DD or MM/DD/YYYY. Pick the one your team reads, which helps when a bundle mixes European and American dates. Each row labels the speaker and the source status. An allegation stays an allegation. The chronology never decides which account is true. Turning contested statements into findings is work for the lawyer or reviewer handling the case, and the output does not replace that judgment.

Questions before you run it

What happens when two documents describe the same event differently?

Both stay in the chronology as separate rows, each with its own citation. The sample keeps the damaged shipment and the intact packaging account side by side rather than picking a winner.

Does every event link back to the document it came from?

Yes. Each row carries the document and page it was extracted from, and the evidence HTML opens the quoted passage so a reviewer can check the wording.

What happens to statements with no date?

Undated items are kept in their own queue instead of being guessed onto the timeline. Duplicates are retained too, so nothing disappears quietly.

Can I choose the date format?

Yes. Date display accepts DD.MM.YYYY, YYYY-MM-DD or MM/DD/YYYY, which matters when a bundle mixes European and American conventions.

Does the chronology decide which account is true?

No. An allegation stays an allegation, with its speaker and source status labelled. Turning contested statements into findings is the reviewer's work.