About
Built for the work of proving a delay actually happened.
Anyone who’s worked a construction claim knows the real work isn’t writing the narrative — it’s finding the evidence inside a stack of P6 schedule updates. Which activity slipped, when, and why. Whether the logic actually supports the story. Whether the schedule itself was healthy enough to trust in the first place.
That work is mechanical, detail-heavy, and easy to get wrong by hand. Claims Digger does the mechanical part automatically, so the people doing the actual analysis spend their time on judgment rather than data entry.
Compare
Diff two schedule versions
Every added, deleted, and modified activity between one update and the next, with the fields that changed and by how much.
Check
Run the DCMA 14-point assessment
The full health check on every schedule you upload, so you know whether the logic is sound enough to build an argument on.
Evidence
Trace what slipped, and when
Findings arrive with the context a reviewer needs to judge them, and export to Excel when the analysis becomes a document.
Still being built, with the people who use it
We’re a small team building this directly with project controls professionals, and the product is moving fast. If there’s a check, a report, or a workflow you wish existed, we want to hear about it.
Request access