Skip to content
Lintel

2026-09-16

From clause to claim: designing a chain of evidence

A claim is a chain of links. Each link needs a source, a date and a place in the order of events. Here is how to design the chain so it exists before you need it.

General information, not legal advice.

When a claim is prepared, the team usually starts from the end: there is an amount, a period, or a dispute. The work is then to reconstruct how the project got there. That is slow, and it depends on what someone happened to keep. A better approach is to design the chain forward, so that each link is created as the work happens.

A useful working chain has six links.

  1. Contract. The agreement and every amendment, in the versions that apply.
  2. Clause. The specific provisions that create rights and obligations.
  3. Obligation. What a party must do, by when, and what follows if it does not.
  4. Event. Something that happened on the project and may have contractual consequences.
  5. Evidence. The records that show what happened and when.
  6. Claim. The assembled case: the event, the clause basis, the evidence, the effect on time and cost.

Each link should point to the ones on either side. From a claim you should be able to walk back to the evidence, the event, the obligation and the clause. From a clause you should be able to walk forward to every event that engaged it.

A source. Every statement should say where it came from: a page in the contract, a document in the vault, a message with its date. If a statement has no source it is an assertion, and assertions are the first thing challenged.

A date, recorded at the time. Records made at the time carry more weight than reconstructions. The date should be captured by the system, not typed later from memory. Where a date is entered by a person, the record should also show when it was entered.

A fingerprint. If a file changes after it is stored, people will ask whether it was altered. Storing a cryptographic hash of each file when it arrives makes later changes detectable. It also lets you show that a file is the same as when it was received.

An owner. Someone is responsible for each event and for each notice that follows from it.

Order matters#

The strength of a chain often lies in the order of events. Did the instruction come before the delay, or after? Was notice given before the window closed? A timeline built from system timestamps and recorded trigger dates answers these questions quickly. A timeline built from memory invites disagreement.

  • Verbal instructions. They happen. The fix is to confirm them in writing promptly and file the confirmation.
  • Evidence in personal accounts. Photos on phones and messages in private chats are hard to produce later. Give people an easy way to file them.
  • Amendments that are not connected. If a time limit was changed by an amendment, the obligation should point to the amended clause, not the original.
  • Narratives with no citations. A narrative should cite the evidence item behind each fact, so a reviewer can check it in one click.

Readiness is a checklist, not a feeling#

Before a claim leaves the building, a plain checklist helps: Was notice given within the window? Are the clauses identified? Is each fact supported by a filed record? Is the effect on time stated and how was it derived? Has the appropriate person reviewed it? Marking these items as complete, and seeing which are not, turns readiness into something the team can act on.

Where humans stay in charge#

Software can help assemble the chain: propose the clauses that may apply to an event, link evidence, draft a narrative from linked material, and show what is missing. It should never send a notice or a claim on its own. Decisions about whether to claim, what to assert and when to send belong to the responsible people and their advisers. This is decision support, not legal advice.

A design principle#

Design the chain so that the easiest thing for a busy person to do is also the thing that keeps the chain intact. If logging an event takes ten seconds and automatically opens the right notice window, it will be done. If it requires reconstructing a spreadsheet, it will not.

That is the idea behind Lintel’s Evidence Vault and Claims Workbench, which are in early access. The sample console shows the chain with fictional data.

General information, not legal advice. Back to resources

Start with one contract.

Join early access, or book a walkthrough and we will show you how a single agreement becomes a live register.