How to create a claims and defenses evidence matrix for Construction Delay Claims

Create a construction delay evidence matrix by breaking each claimed delay into disputed propositions, then linking contractual entitlement, schedule impact, notice, defenses, and damages to identifiable records. Keep supporting evidence, adverse evidence, and missing proof visible together. Separate an event’s duration from its alleged effect on completion, and distinguish documented facts from expert analysis or counsel inference. The resulting deliverable is a source-linked working table showing what counsel can support, what remains contested, and who must resolve each gap before counsel relies on the claim or defense.

When to use this workflow

Use this workflow to evaluate a delay demand, prepare a response, test a scheduler’s analysis, or identify targeted discovery. It is particularly useful when the contractor attributes a period to late access, the owner identifies procurement problems, and successive schedules show changing completion forecasts.

Define the immediate decision. Evaluating a time extension differs from substantiating extended general conditions or defending liquidated damages. Link related theories without treating their proof as interchangeable.

This is a US-oriented workflow guide, not advice for a particular dispute. Verify the governing law and forum: the federal rules cited below do not automatically govern state litigation, arbitration, or contract appeals boards. Contract rights require analysis of the executed language and facts.

What you need

Collect a bounded initial record for the disputed windows:

• Executed contract, incorporated conditions, amendments, scheduling requirements, notice provisions, change orders, reservations, and releases.
• Baseline and updated schedules, preferably native files, with data dates, calendars, logic, constraints, narratives, and revision history.
• RFIs, submittal and procurement logs, daily reports, meeting minutes, access records, photographs, and relevant correspondence.
• Delay submissions, responses, notices, delivery evidence, mitigation proposals, and schedule analyses.
• Cost ledgers, invoices, payroll, subcontractor demands, credits, and supporting calculations.
• Pleadings or demands, witness accounts, document identifiers, and the immediate review question.

Identify missing versions rather than silently substituting a later update. Establish stable document IDs so citations survive renaming and production. Keep counsel’s assessments separate from underlying project records and control circulation of the working matrix.

Use the template

Use the Construction Delay Claims — Claims and defenses matrix below. You can copy this table into your working document or spreadsheet. Create one row per testable proposition within a defined delay window, not one row per document or an entire multi-month claim.

Give rows stable IDs, such as M-01. Identify the theory, remedy, and contractual anchor in Claim or defense. Frame the Proof question neutrally: “Did delayed release of Area B affect substantial completion?” is more useful than “Owner delay.”

Citations should identify document ID, clause or page, and schedule activity or worksheet cell where relevant. Distinguish the type of evidence—project record, witness account, expert opinion, or inference—from the assessment: supported, contested, unsupported, or awaiting analysis. Record an internal review date with each assigned action. The decision should explain the current assessment and cross-reference dependent rows.

Step by step

1. Define the claims, remedies, and delay windows

Start with the demand and response. Separate additional time, delay compensation, disruption, acceleration, and defenses to assessed damages. Identify the milestone each theory concerns and the period allegedly affecting it.

Divide long periods into windows corresponding to events or schedule updates. These boundaries are analytical choices, not assumptions that each window is independently recoverable. Record calendar or working days consistently with the underlying allegation and contract.

Enter the theory, requested remedy, window, milestone, and allegation source. If the milestone is unclear, assign that gap rather than assuming every claim concerns final completion.

2. Translate contract provisions into proof questions

Read scheduling duties, access obligations, changes, extensions, compensation limitations, notices, mitigation, releases, and damages provisions together. Check amendments before identifying operative language.

Build questions around entitlement, causation, notice, concurrency, mitigation, release, and damages. These are review categories, not universal legal elements. Separate contractual wording, party allegations, and issues requiring governing-law research.

Record each clause citation and neutral proposition. A change order may establish authorization without resolving delay compensation. If a party invokes a release or damages limitation, identify the actual language and disputed scope; do not reduce the issue to a checked box.

3. Link favorable and unfavorable project evidence

Identify the strongest contemporaneous support and conflicting record for each proposition. Link complete communications and attachments where context matters. A minute recording an access complaint may establish that the complaint was made, without proving the restriction’s duration or responsibility.

Preserve conflicting dates and identify whether an entry reflects observation, reported information, or inference. Record the source’s author and knowledge basis where that affects its weight.

In federal district-court litigation, discovery covers nonprivileged material relevant to claims or defenses and proportional to the case; information need not be admissible to be discoverable. Use that distinction to prioritize gaps, not justify indiscriminate collection. Federal Rule of Civil Procedure 26(b)(1). (uscourts.gov)

Enter exact citations, contradictions, and the missing record—not simply “more discovery.”

4. Test schedule causation and competing delays

Compare the event with contemporaneous logic, available work fronts, forecast completion, and subsequent updates. Ask whether the affected activity controlled the relevant milestone during the window. An incident lasting fifteen days does not itself demonstrate fifteen days of completion delay.

Ask the scheduler to identify competing causes, changed sequencing, available float, and limitations from missing native files. Keep concurrency open for factual and legal analysis rather than automatically subtracting overlapping calendar periods.

In Lusk Mechanical Contractors, the CBCA emphasized missing critical-path proof for an additional interior-work suspension and also found the suspension duration reasonable. This fact-specific federal procurement decision is not a universal rule for private construction or disruption claims. Decision, pages 8–10. (cbca.gov)

Record schedule version, data date, activity IDs, competing explanation, and required analysis.

5. Examine notice, mitigation, and releases separately

Map each notice provision to its trigger, sender, recipient, method, contents, timing, and delivery evidence. Distinguish initial notice from later particulars. Check whether the contract makes sending, delivery, or receipt relevant; a letter date alone does not establish transmission or receipt.

Test mitigation proposals against actual site conditions and resources. Identify proposed resequencing, feasibility, response, and implementation. Separately inspect reservations, releases, and final-payment records.

Create separate rows where these issues could change the result despite strong causation evidence. Record the operative language, factual gap, and owner. Assign interpretation and any waiver arguments to counsel rather than treating missing documentation as an automatic forfeiture.

6. Reconcile days and dollars without merging them

Trace days to schedule analysis and dollars to underlying cost records. Identify actual versus estimated amounts, covered periods, credits, and possible duplication between contractor and subcontractor demands.

A ledger entry documents an expense, not necessarily its causal connection to the disputed delay. Conversely, support for additional time does not establish the requested compensation. Make those dependencies explicit.

Record calculation locations, source records, disputed amounts, and linked causation rows. Reconcile the gross demand before assessing recoverability. If the delay window changes, revisit dependent cost rows rather than carrying forward the original total.

7. Assign gaps and test evidentiary readiness

Convert each gap into a bounded task: obtain a native update, identify an access-log custodian, interview the superintendent about alternative work, or reconcile specified ledger entries. Assign an owner and internal review date.

For likely exhibits, identify an authentication route. Federal Rule of Evidence 901 requires sufficient evidence to support a finding that an item is what its proponent claims; knowledgeable-witness testimony is one example. Authentication does not independently resolve hearsay or other admissibility questions. Rule 901. (uscourts.gov)

Record readiness separately from substantive support. Preserve the previous rationale when materially revising an assessment, and identify which linked decisions need reconsideration.

Worked example

Fictional scenario: Bracken Construction seeks a twenty-calendar-day extension and $160,000 from Alder Quay Properties for restricted mechanical-room access. All parties, documents, amounts, and contract terms below are fictional.

Section 4.2 addresses owner-provided access. Section 8.3 requires written delay notice delivered to the designated owner representative within seven days after recognizing a likely milestone impact. Section 8.5 addresses delay compensation. Change Order 06, §3, reserves mechanical-room delay issues while releasing separately described roofing changes.

The demand alleges restricted access throughout June 3–22. Daily reports document restrictions on several dates, but the June 1 schedule update is available only as a PDF. An email forecasts equipment delivery on June 12. A notice letter is dated June 6; transmission and receipt evidence have not been located.

The matrix replaces one broad allegation with distinct decisions. The procurement forecast challenges part of the period but does not prove actual delivery or net delay. The missing delivery evidence leaves notice unresolved. Similar cost descriptions warrant reconciliation, not an immediate $15,000 deduction. Change Order 06 supports treating the mechanical-room reservation separately from the roofing release; it does not establish entitlement. No missing evidence is assumed into existence.

Common mistakes

• Equating event duration with milestone delay. Identify affected activities, schedule versions, and the causal analysis.
• Using only the final as-built schedule. Examine contemporaneous updates and disclose later reconstruction.
• Burying contractor-caused events. Place procurement, staffing, rework, and sequencing evidence beside the theory they challenge.
• Combining notice and merits. Separate contractual compliance from schedule causation and compensation.
• Treating posted costs as recoverable damages. Require period matching, causal analysis, credits, and duplicate checks.

Final quality check

• Each row addresses a defined proposition, remedy, and window.
• Contract citations match executed documents and amendments.
• Source citations resolve to exact pages, activities, or cells.
• Favorable and adverse records have both been examined.
• Schedule conclusions disclose assumptions and missing native data.
• Days and dollars reconcile through reproducible calculations.
• Evidentiary readiness is distinct from substantive support.
• Open issues are resolved or expressly assigned, with reasons and review dates.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its document review and evidence analysis capabilities to examine delay records, with chronology review supporting comparison of event sequences. Its trial preparation capabilities support deposition preparation. The matrix remains counsel’s working document; schedule causation and legal conclusions require professional judgment. Book a demo to discuss this evidence-analysis workflow.

Frequently asked questions

Should each document have its own row?

Usually not. Organize by proposition, linking multiple supporting and challenging records. Split rows when notice, causation, or quantum requires a separate decision. Keep a document index separately if needed.

How should overlapping delays be recorded?

Identify each event, affected activity, window, and source. Separate the scheduler’s analysis from counsel’s assessment of legal effect. Calendar overlap alone should not become an unexplained deduction from claimed days.

Can the matrix itself be used as trial evidence?

Do not assume so. Federal Rule of Evidence 1006 addresses summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced. Underlying originals or duplicates must be available to other parties at a reasonable time and place. An illustrative aid under Rule 107 is different. Rules 1006 and 107. (uscourts.gov)

What if the native schedule is unavailable?

Record the missing file, available PDF, and analytical limits. Seek the native version from an identified custodian. Ask the scheduler which conclusions remain supportable, and label reconstructed logic rather than presenting it as original project data.

Sources

• Federal Rules of Civil Procedure: Rule 26(b)(1).
• Federal Rules of Evidence: Rules 107, 901, and 1006.
• Lusk Mechanical Contractors, Inc. v. General Services Administration, CBCA 7759, April 30, 2024, pages 8–10.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.