Document Crunch review

What it actually does

Document Crunch ingests the contract documents on a construction job — prime contract, subcontract, exhibits, general conditions, any binding spec sections — and produces a working catalog of:

• Critical risk provisions flagged by category (indemnity, LDs, consequential damages, betterment, no-damage-for-delay)
• Payment terms + payment dispute triggers mapped to specific clauses
• Notification windows (claim notices, schedule impact notices, change order timelines) extracted with date math baked in
• Spec non-compliance signals — when a submittal or RFI references requirements that don't actually exist in the spec, or vice versa
• Specification ↔ contract conflicts — Division 01 says one thing, the agreement says another

The output is a structured, clause-by-clause rule set the platform calls the project's "contractual DNA." Per Trimble's April 2 announcement, that DNA is what gets pushed into Trimble Construction One workflows after Q2 close.

Where it works

Highest-ROI workflows we've seen contractors actually adopt:

1. Pre-award contract review. Run before signing. Get a flag list ranked by risk severity. The PM who's never read clause 12.7 of an AGC document sees it now.
2. Notification surveillance. On an active job, the tool knows you have 14 days to notice a delay impact. Three days before window-close, it pings the PM.
3. Submittal-to-spec compliance pre-check. Before a submittal goes to the GC for review, the tool checks whether the cut sheet meets the spec section's stated requirements.
4. Change-order chain of custody. When a PCO gets rejected, the tool can trace whether the rejected scope was actually inside the original contract or out of scope.

Where it doesn't

Honest list:

• Negotiating redlines. Flags bad clauses, doesn't negotiate them. The clause that says "Contractor accepts all design responsibility for performance specifications" still gets crossed out by your construction lawyer, not by an LLM.
• Project-specific risk weighting. A flagged consequential-damages clause matters differently on a $2M tenant fit-out vs. a $90M data center. The tool produces a generic severity ranking; project context is on you.
• Ambiguity resolution. Spec says one thing, drawings another — the tool flags the conflict, the RFI still goes to the design team.
• Field-modified contracts scanned at 200 dpi. OCR breaks on handwritten amendments.
• State law overlays. "No damage for delay" enforceability varies by state — Document Crunch flags the clause, doesn't tell you Maryland courts enforce it differently than Virginia.

The math

Public pricing isn't published. Per ENR's reporting on the acquisition, Trimble paid under 10× revenue, and Document Crunch had 10,000+ projects deployed.

Time savings observed in mid-sized GC pilots: 6-12 hours/week on the project engineer or contract administrator who was doing this review manually. Even at $75/hr blended, that's $25-50K per PE per year. Run on three jobs and it pays for itself.

The bigger value isn't time saved — it's the avoided one-bad-clause-buried-on-page-247 outcome. One claim correctly noticed on day 8 instead of day 22 pays for the platform for a decade.

Pilot it in two weeks

1. Pick one active project. Ideally one mid-claim or with an unusual contract.
2. Upload the contract bundle: prime contract or subcontract, general conditions, all relevant exhibits, the spec sections you signed against.
3. Run the risk report. Read every flagged clause with the actual PE or PM on the job — calibrate against what they already knew. The ones that surprise them are the value.
4. Run notification surveillance on the active project for the two-week pilot.
5. Score the pilot: (a) clauses flagged the PM hadn't read, (b) notifications surfaced that would have been missed, (c) submittals pre-checked for compliance vs. spec.
6. If a + b + c is ≥ 3 events you'd have missed otherwise, scale to all jobs. If 0–2, the value isn't there for your mix.

Coverage on this site

• Tool teardown — issue №002 (2026-05-14)
• Punch list — Trimble acquisition coverage