entropy Sign in
The platform

Your project record already holds the story.

Entropy turns daily logs, meeting minutes, monthly reports, and other records into a sourced chronology and a plain-language account of what happened on the job.

It reports what the record says. It does not decide who is right.  One record, read for whoever needs the answer.

JANFEBMARAPRMAYJUNJUL
Scroll
The problem

The answers are already written down. Getting to them is the expensive part.

The record is scattered

Project records (e.g., daily logs, meeting minutes, status reports) sit in different systems and folders on every project.

People read it by the hour

Consultants and associates rebuild the chronology by hand, often once per expert, mediation or deposition.

The story arrives late

By the time there is a timeline everyone trusts, positions have hardened and the fees are spent.

One anonymized sample project
13,685

recorded events in four years of daily logs and meeting minutes. Someone has to read them.

How it works

Entropy pulls the record apart, then puts it back together as a story.

01

Collect

Upload the logs, minutes and reports your team already keeps. Entropy notes which system each came from.

02
EVENTPERSONISSUEQUOTE

Pull apart

Each document is broken into dated events, people, issues and verbatim quotes, each tied to its page.

03

Organize

The pieces become a chronology, an issue list, a cast of characters and a document register.

04

Tell the story

The record is written up at three depths: a short summary, a story in plain language and a full register.

Expert layer

A practitioner-built issue taxonomy guides what is pulled out and how it is grouped, based on 20+ years of experience.

Uses existing tech

Procore, Autodesk Build, Box, Google Drive, and dozens of other existing tech solutions detected upon upload.

Inside the platform

The whole record sits on one canvas: by issue, by person, by document.

PRIVILEGED & CONFIDENTIAL — PREPARED AT THE REQUEST OF COUNSEL
Firm / Projects / XYZ Demo
Overview Chronologies Issues People Documents
ROWS Issues Doc types Critical path Overlays
Underground utilities
Steel delivery
Building enclosure
Permanent power
JANFEBMARAPRMAYJUNJULAUGSEPOCTNOVDEC
DATA DATE
Schematic with demo data. Live screenshots available on request.

Chronologies

Rows switch by issue, document type or critical-path mention.

Issues

Each thread, with the first and last dates it appears in the record.

Cast of characters

Who appears in the record, for which organization, and when.

Documents

Every record listed with its date, type and main idea.

What you receive

You get the story at three depths, and every line traces back to a page.

Document 1 · 2 pages

Executive summary

What happened, in phases. The patterns that recur. The key dates.

Document 2 · 5 pages

The story

A plain-language account for readers who were not on the job.

Document 3 · 12 pages

Timeline and issue register

Every milestone and issue thread, dated from first mention to last.

p.2
The record itself

Source page and quote

The document, page and verbatim quote behind each entry.

From one anonymized sample project
13,685

recorded events in the project record

2 + 5 + 12

pages across the three documents

< 1 day

from upload to first read

Why you can trust the output

It reports what the record says. It does not decide who is right.

The story says

The daily logs record six days with no work at the east footings after the excavation flooded.

See timeline row A-37
Timeline row A-37
Date Mar 14, 2024 Event East footing excavation flooded; no work recorded Source ENT-XYZ-0412 p.2
Source document, page 2

“No work at east footings today. Excavation flooded, pumps running.”

ENT-XYZ-0412 p.2 · GC daily log
Illustrative demo data

Play-by-play only

Not color commentary. Statements are attributed to whoever made them, with no fault or apportionment assigned.

Open questions stated

Each report closes with the items the project team should confirm or refute.

Gaps in the record flagged

Missing series, misfiled documents and date anomalies are reported, not smoothed over.

Data security and reliability

Your documents are handled like the evidence they are.

Your documents

Encrypted in transit, stored in the United States, and never publicly accessible

Client isolation

Each client’s data is kept separate from every other client’s

Access and sign-in

Invite-only access with verified sign-in

AI, privately

Runs on Amazon Bedrock, inside the same AWS environment as your documents
Content is never sent to third-party AI services or used to train models

Infrastructure

Underlying AWS infrastructure independently audited (SOC 2, ISO 27001)

Operations and continuity

Backed up automatically, with a tamper-evident audit trail of administrative actions
Full security overview on request: info@entropy.build
What it replaces

Entropy replaces the most expensive reading in a dispute.

typical today
with entropy
Time to a first read
Weeks or months
< 1 day
Who does the reading
Teams of staff consultants and associates
One practitioner and the platform
Fee model
Hourly and open-ended
Flat fee (budgeted)
Reuse
Rebuilt for each expert, mediation and deposition
One sourced record, reused each time
Where it sits

Before the expensive pipeline. Know what happened first, then decide how much document review, expert time and discovery the matter actually needs.

Who it is for

One record, read for whoever needs the answer.

General counsel

A neutral read of what the record supports, before positions harden and fees mount.

When a claim is taking shape

Executive leadership

What is happening on a troubled job, in plain language, from your own team’s records.

When a job is slipping

Outside counsel

Chronologies by issue and by witness, sourced to the page, for mediation and deposition prep.

When preparing a claim, mediation or deposition

Mediators and neutrals

One objective chronology both sides can mark up, so the points of difference become the agenda.

When the parties need common ground
Where it stands

Built by a practitioner, and working on real project records today.

Dave Hettinger
Dave Hettinger
Founder & Principal
Construction litigation and claims professional
Forensic dispute analysis across 150+ complex projects
Trusted advisor with deep industry knowledge
The experience is in the product

Entropy’s issue taxonomy and playbooks come from that casework. Every step is informed by experience.

Live today
Daily logs, meeting minutes, monthly reports, emails processed
Chronology, issues, cast of characters, deep-linked documents
Source system detected on upload
Export with document, page and quote for every event
Report set: summary, story, timeline and issue register
In progress
Direct connections: Procore, Autodesk Build, Box, Google Drive
Report set generated inside the platform
Per-issue and per-witness chronologies as standard reports