A construction dispute evidence packet is the organized, dated, citable set of project documents that proves what was required, what happened, who knew, and what it cost — contract, drawings and revisions, RFIs, change orders, submittals, daily reports, schedules, pay apps, minutes, photos, and correspondence, each tied to the clause it supports. The time to build it is during the project, because contemporaneous records decide claims and reconstructions don't.
The stakes justify the discipline. Per the Arcadis 2025 Global Construction Disputes Report, the average U.S. construction dispute is now worth $60.1 million, and North American disputes average roughly 12.5 months to resolve — a year of management attention, legal spend, and strained relationships. And the leading cause in North America, for the third year running, is errors and omissions in contract documents — which means most disputes are, at bottom, document problems. Resolution times have been trending up globally, which makes a record that shortens the argument worth real money.
What goes in the packet — and what each piece proves
| Document | What it proves | Common gap |
|---|---|---|
| Contract + amendments + exhibits | The baseline obligation: scope, price, time, notice requirements | Unsigned amendments; exhibits referenced but never attached |
| Drawings & specs with full revision history | What governed on the date the work was done | Can't show which revision was current when — the superseded-revision trap |
| RFI log with answers | Notice of the problem and what direction was given | Verbal answers never confirmed in writing |
| Change orders — approved and disputed | Agreed scope/cost/time changes; reservation of rights on the rest | Work performed on a handshake pending paperwork |
| Daily reports & photos | Conditions, manpower, weather, delays — as they happened | Generic entries ("worked on level 3") that prove nothing |
| Schedule updates & fragnets | When the delay hit and what it pushed | Baselines never updated, so impacts can't be isolated |
| Pay applications & backup | What was billed, approved, paid — and when | Backup that doesn't reconcile to the SOV |
| Meeting minutes & correspondence | Who knew what, when — and the notice trail | Decisions made in calls and never minuted |
Notice what the table rewards: not volume, but linkage. A terabyte of project files is not an evidence packet. The packet exists when each assertion in your claim narrative points at a specific document, page, and date — and when the documents an opposing expert will ask for first (the governing revision, the notice letter, the contemporaneous cost records) are already pulled, indexed, and consistent with each other. Assembling that linkage after the fact is what burns months of the 12.5-figure; maintaining it as you go costs minutes a week.
Assembling it: the five-step method
- Start a chronology, not a pile. One dated timeline per issue: event → notice → direction → cost/time impact. Every entry points at a document.
- Tie each fact to its source page. "The spec required X" is an assertion; "Spec 09 91 23, paragraph 2.3.A, Rev 2, issued 14 Mar" is evidence. Citations are what make a packet persuasive.
- Resolve the revision question early. For every disputed scope item, establish which drawing/spec revision governed on the date of the work — this single question decides more claims than any other.
- Quantify from contemporaneous records. Cost from coded timecards and invoices, time from schedule updates — not from end-of-job estimates.
- Have someone hostile read it. If a reviewer who wants you to lose can't follow the chain from clause to notice to impact to dollars, neither can a mediator.
The same packet, scaled to the everyday dispute
The headline numbers describe the megaprojects, but the discipline matters just as much at the scale most contractors actually fight: the $40,000 back-charge, the contested CO, the final-payment holdback. Those rarely see a lawyer — they're decided in a conference room by whoever brings the better paper. The packet for a small dispute is the same structure, lighter weight:
- One page of chronology. Five to ten dated entries: what was required, what was directed, what it cost. Each entry cites its document.
- The three documents that decide it. Most small disputes turn on a single clause, a single RFI answer, and a single revision date. Find them, copy them, highlight the lines.
- The notice proof. The email or letter, with its date, that told the other side in time. If notice is weak, know that before you posture.
- The number, supported. Timecards and invoices for the claimed amount — a figure with backup gets negotiated; a round number gets discounted.
A contractor who can hand over that packet in the first meeting usually doesn't need a second meeting. And the inverse is the trap: a valid position argued from memory loses to an invalid one argued from documents more often than anyone likes to admit. The habit that wins the $60-million arbitration and the habit that wins the $40,000 back-charge are the same habit — answer from the documents, keep the citations, keep the dates.
The cheap version: a record that builds itself
Teams that win disputes rarely "prepared for a dispute" — they just answered every question during the job from the documents, in writing, with citations, and kept the trail. That's the habit IntelMS automates. Every question your team or the owner's side emails in gets answered from the project record with the exact source cited — and the question, the answer, and the citation are logged. When a dispute does surface, the chronology already exists: what was asked, what the documents said, which revision governed, and when everyone knew. Anything touching contractual interpretation, cost responsibility, or who-pays gets escalated to a human rather than answered automatically — the packet's judgment calls stay with you and your counsel. It's the difference between starting discovery from a banker's box and starting from a record that was defensible all along.
Build the record before you need it
14-day pilot on one real job. Every answer cited, every question logged — a dispute-ready trail as a side effect of normal work.
Start a free pilot →Frequently asked
What documentation do you need for a construction dispute?
Contract and amendments, governing drawings/specs with revision history, RFI log, change orders, submittals, daily reports, schedules, pay apps, minutes, photos, and correspondence — each tied to dates and clauses.
How much is the average dispute worth?
Arcadis's 2025 report puts the average U.S. dispute at $60.1 million, with North American resolution averaging about 12.5 months.
What causes most disputes?
Errors and omissions in contract documents — the top North American cause three years running — plus failure to understand contract obligations and owner-directed changes.
When should you start the packet?
Day one. Contemporaneous records carry the weight; reconstructions don't.