Lawgorithm

What is Lawgorithm?

Discovery arrives as volume, and the work of making it usable — intake, deduplication, organisation, timeline — consumes the hours that should go to argument. Lawgorithm handles the intake and organisation, builds a timeline whose every entry links to the document that supports it, and keeps research attached to the matter rather than accumulating in someone's folder. Deletions respect legal hold, because in this domain an over-eager cleanup is a serious problem.

Problems it solves

• Intake and organise large discovery sets
• Build an evidence timeline linked to source documents
• Find relevant material without reading everything
• Keep research attached to the matter
• Respect legal hold on deletion

Key capabilities

Document Intelligence

Read long, structured documents — drawings, filings, specifications — and extract what matters with the page it came from.

Timeline Construction

Assemble dated events into a timeline, each entry linked to its source.

Chain of Custody

Hash and log evidence on intake so its handling can be demonstrated later.

Evidence Trail

Every figure carries the record it came from, so a reader can check the answer instead of trusting it.

Fact / Inference Separation

Keep what is known, what is inferred and what is alleged visibly distinct.

How it is built

Structured intake

Discovery material is organised on arrival rather than later.

Source-linked timeline

Every timeline entry opens onto the document supporting it.

Legal-hold-aware

Deletion respects hold status by design.

How it works

How the work is structured, and what each step's output rests on.

1. 1

   Intake

   Source

   Receive discovery material and record its provenance.

2. 2

   Organise

   Observed

   Deduplicate, classify and index.

3. 3

   Extract events

   Observed

   Identify dated events and their supporting documents.

4. 4

   Build the timeline

   AI-inferred

   Assemble events with links to their sources.

5. 5

   Review

   Human-verified

   A person confirms entries; confirmations are recorded distinctly.

Example use cases

Each example has its own page you can read and share.

Ask Lawgorithm

Illustrative examples. Results depend on your own data.

• “Build a timeline of events from this document set.”
• “Which documents support this event?”
• “What material mentions this entity?”
• “What is still unreviewed in this matter?”

Security, governance and human control

Where the software deliberately limits itself.

Questions

Is this legal advice?

No. It organises material and builds timelines. Legal judgement is the lawyer's.

How does it handle legal hold?

Deletion is guarded by hold status, so retention obligations are not violated by routine cleanup.