Most contractors who lose a dispute weren't wrong. They just couldn't prove they were right. The decision was made correctly — but it lived in a phone call, a hallway conversation, or an email thread that nobody can locate eighteen months later. By the time a claim or a contested closeout arrives, reconstructing "who knew what, when, and from which document" is nearly impossible. The record either exists or it doesn't.
What "defensible" actually means
A defensible record has four properties. Miss any one and it weakens:
- Complete — every meaningful question and decision is captured, not just the ones someone remembered to file.
- Dated — every entry is time-stamped, so a timeline can be reconstructed.
- Cited — every answer names the exact source: sheet, detail, spec section, revision, or change-order number.
- Source-of-truth linked — it points to the governing document version, so "we built to the current set" is provable.
Five habits that build the record as you go
- Cite every answer. "Per E-2.1, Rev 3, detail 4" isn't just clearer in the moment — it's a record entry. An uncited answer is invisible to your future self.
- Log every question and its answer, with a date. The Q&A history is the project narrative. A searchable, dated log means the timeline already exists when you need it.
- Keep one source of truth for current documents. So you can prove which revision governed at the time — see the cost of a superseded revision.
- Capture conflicts and their resolutions. When a spec and drawing disagreed, record that you caught it, how it was resolved, and by whom. That's often the crux of a claim.
- Don't rely on memory or scattered inboxes. If the record only exists in people's heads and email, it effectively doesn't exist for a dispute.
How IntelMS builds it as a byproduct
The hard part of a defensible record is that it's tedious to maintain by hand, so it doesn't get maintained — until it's too late. IntelMS builds it automatically: every question your team asks and every cited answer it returns is logged, dated, and tied to the source document and revision. It keeps a cited timeline of decisions and can assemble that evidence into a packet for a claim or closeout. It assembles the record — your team and counsel make the determinations; IntelMS doesn't adjudicate disputes or give legal advice.
Build the record while you build the job
Start a 14-day pilot. Every answer is cited and logged from day one — so the evidence is there if you ever need it.
Start a free pilot →Preguntas frecuentes
What is a defensible project record?
A complete, dated, source-cited account of the decisions on a project — who asked what, the answer, the document and revision it came from, and when. It's the evidence base for disputes and closeout.
Why do contractors lose winnable disputes?
Because they can't prove they were right. The decision lived in memory or a lost email thread. No dated, cited record means a legitimate position becomes he-said-she-said.
How do I build the record as I go?
Cite every answer, log every Q&A with a date, keep one source of truth for documents, and capture conflicts and resolutions. A tool that logs cited Q&A builds it automatically.