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

A construction defect claims and defenses evidence matrix connects each researched claim element or defense to an assembly, responsible actor, supporting evidence, contrary evidence, and unresolved proof question. Build it from the pleadings, governing contracts, defect register, project records, and expert materials—not from document summaries alone. The deliverable is a working table showing what counsel can presently support, what remains disputed, and which collection, inspection, or witness task should come next. Keep contractual responsibility, defective performance, causation, and repair costs distinct.

When to use this workflow

Use this workflow when litigation counsel or an in-house legal team must assess a defect demand, test pleaded allegations, prioritize discovery, or prepare expert and witness examinations. It is particularly useful when water intrusion, cracking, or system failures cross several trades and the parties offer competing explanations.

Define the project, buildings, assemblies, parties, and procedural stage first. A condominium envelope dispute requires different technical records and responsibility questions from a commercial mechanical-system dispute.

This guide uses a US practice orientation and an October 13, 2026 research cutoff. Federal procedural references concern district-court litigation; federal evidentiary references apply within the Evidence Rules’ scope. Neither automatically governs state litigation or arbitration. Identify governing substantive law, contract terms, applicable statutory versions, local rules, and case-specific orders before adopting proposed elements or defenses. See the Federal Rules of Civil Procedure and Federal Rules of Evidence.

What you need

Gather a bounded working set rather than waiting for complete discovery:

• Issue documents: pleadings, demands, responses, researched elements and defenses, and applicable notice materials.
• Responsibility records: executed contracts, incorporated specifications, amendments, drawings, submittals, RFIs, change orders, and warranties.
• Condition records: a location-coded defect register, marked plans, photographs, inspection reports, testing records, daily logs, and sample inventories.
• Timing and alternative-cause records: installation and completion records, first complaints, maintenance logs, collected weather records, repairs, and recurrence reports.
• Loss records: remedial scopes, estimates, invoices, payment records, credits, and completion evidence.
• Evidence controls: stable document IDs, collection status, witness roles, expert opinion versions, and privilege-review status.

Record missing versions explicitly. A repair drawing cannot silently substitute for the drawing governing original installation. Preserve links between native files, attachments, and their review copies.

Use the template

Use the Construction Defect Claims — Claims and defenses matrix below. You can copy this table into your working document or spreadsheet. Maintain stable row IDs when sorting or splitting entries.

“Row / defect” combines a matrix identifier with a location or assembly code. “Issue / authority” identifies one researched element, defense, or subsidiary factual proposition and links to the relevant legal research. Split a cause of action into separate rows when its components require different proof.

Use document IDs and pinpoints in both proof columns: page, clause, photograph number, drawing detail, or transcript lines. An evidentiary gap belongs in “Gap / status,” not in “Adverse proof” unless the absence itself has an established evidentiary basis.

Identify actors without treating allegations as findings. Put the task owner and completion criterion in “Next action / owner.” The decision column records the present assessment and its reason—not a final liability conclusion. Keep access-sensitive analysis in an appropriately controlled working file.

Step by step

1. Define the issue map and legal predicates

List asserted claims and defenses, then break each into counsel’s researched components. Link them to affected assemblies and alleged damage. Mark unresearched theories as questions; “defective work” does not supply a governing legal test.

Include defense rows rather than only evidence contradicting the claimant. Depending on counsel’s research, these may address notice, contractual exclusions, maintenance obligations, or timing. Identify the proposition, relevant burden, and factual predicate without assuming the defense is available.

For matters subject to Florida Chapter 558, section 558.004(1)(b) requires reasonably detailed defect and known-damage descriptions and locations identifiable from at least visual inspection. Testing is not required for that notice. This is not a nationwide standard. See Florida section 558.004(1)(b).

Record: issue rows, authority references, jurisdiction assumptions, and unresolved applicability questions.

2. Normalize defects, locations, and dates

Assign consistent building, floor, room, elevation, assembly, and trade codes. Link alleged defects to marked plans and photographs. Treat “staining at east window” as an observation, not proof that the window installer caused it.

Separate installation, completion, first symptom, inspection, notice, repair, and recurrence dates. Identify contemporaneous records separately from later recollections. Retain distinct location references until technical evidence supports grouping similar symptoms.

For a timing defense, identify which event counsel’s legal research makes relevant. Do not substitute first observed leakage for another legally significant event merely because it is easier to document.

Record: defect codes, source pinpoints, date uncertainty, and whether each proposition is an observation, opinion, or allegation.

3. Separate scope allocation from performance and causation

Read executed scope documents alongside incorporated details and modifications. Identify installation, design coordination, inspection, maintenance, and repair responsibilities. Note disputed incorporation or missing amendments without deciding them from a scope summary.

Create distinct rows for the governing requirement, actual installation, alleged departure, and causal connection to damage. A subcontract allocating flashing work does not prove a flashing defect; a water-entry test does not by itself identify the responsible trade.

Where responsibility is disputed, connect each actor’s position to its source. Separate contractual allocation from evidence identifying who actually performed the work.

Record: actor, contractual pinpoint, performance evidence, and remaining causal link. Assign technical inferences to the appropriate expert rather than presenting counsel’s inference as an expert conclusion.

4. Pair supporting and adverse evidence

For every material proposition, search for contrary records and alternative explanations. Compare complaints with maintenance histories, inspection results, repair records, and witness accounts. Before using silence in a daily log, establish what that log ordinarily recorded and its coverage.

Separate foundation from persuasive value. Federal Evidence Rule 901 requires sufficient evidence that an item is what its proponent claims; knowledgeable-witness testimony is one method. Authentication does not alone resolve hearsay, relevance, or other admissibility questions. See Rule 901.

For photographs, identify the depicted location, approximate date, photographer or knowledgeable witness, and whether alterations affect the proposition being tested.

Record: both evidence directions, witness or custodian references, and unresolved foundation questions. Use “not located in reviewed set” rather than “does not exist” when collection is incomplete.

5. Connect repair amounts to disputed conditions

Trace proposed remedial tasks to defect IDs and causal theories. Separate emergency mitigation, permanent repair, maintenance, and upgrades. Reconcile estimates against invoices, payments, credits, and completion evidence; do not add an estimate to an invoice that superseded it.

Identify whether an estimate covers an observed location, an entire elevation, or assumed hidden conditions. If investigation is localized, record the technical basis still needed for broader work. Keep factual cost support separate from counsel’s analysis of legally recoverable categories.

Record: cost-document pinpoints, scope coverage, duplication concerns, and missing technical or legal support. Cross-reference a detailed cost ledger rather than crowding every invoice into the matrix.

6. Convert gaps into targeted evidence tasks

Give each material gap a concrete question, owner, and completion criterion. “More discovery” is not an assignment; “obtain the approved flashing submittal and revision history from the general contractor” is.

In federal district court, Rule 26(b)(1) permits discovery of nonprivileged information relevant to claims or defenses and proportional to the case. Discoverability does not require admissibility. Explain the requested record’s decision value without labeling it trial-ready proof. See Rule 26(b)(1).

Before proposed invasive testing, assign preservation and access planning: notice decisions, participants, photographs, sample identifiers, custody, removed components, and storage. Distinguish evidence awaiting collection from evidence awaiting technical interpretation.

Record: specific evidence sought, decision value, owner, and completion criterion.

7. Reassess and record the present decision

Review high-impact rows with the responsible lawyer and technical reviewer. Use statuses such as supported, disputed, incomplete, or not assessed. Avoid numerical confidence scores that conceal a missing causal opinion or unresolved legal predicate.

State what would change the assessment: an approved detail, installation photograph, work-sequence testimony, or testing distinguishing competing pathways. Retain earlier source references and explain material changes rather than overwriting the reasoning.

Record: present position, concise reason, unresolved dependencies, and follow-up. Date the assessment in the working file and identify the evidence set reviewed.

Worked example

Fictional scenario: Alder Quay Offices LLC alleges that Northspan Builders Inc. delivered defective east-elevation window assemblies. Northspan identifies Cove Flashing LLC as the perimeter-flashing subcontractor. All parties, documents, clauses, amounts, and facts below are fictional.

Openings E-201 through E-206 are disputed. Subcontract SC-04, section 3.2, assigns perimeter flashing to Cove but excludes sealant maintenance. Report IR-07 records water entry at E-204 and recommends further investigation; it does not identify the concealed pathway. A later ticket records a sealant patch. The owner presents a $240,000 estimate for replacing all six assemblies.

Counsel has not resolved the governing liability tests or maintenance allocation. These rows assess factual propositions and a potential alternative-cause position, not established legal defenses.

The matrix changes the immediate decision. Counsel cannot equate flashing responsibility with causation or one test with six failed assemblies. The priority becomes concealed-condition evidence and the technical basis for broader replacement. Limited testing is a gap, not affirmative proof that the other openings are sound. No missing photograph or expert conclusion is assumed to exist.

Common mistakes

• One row for the building: split by assembly and disputed proposition; group only with a documented technical basis.
• Symptoms treated as mechanisms: separate observed staining, causal opinion, and actor attribution.
• Scope treated as breach: add distinct performance and causation rows instead of relying on contractual responsibility alone.
• Missing evidence treated as adverse proof: identify collection limits and assign follow-up; do not imply the missing record disproves the allegation.
• Defenses buried in narrative: create separate rows for researched defenses, their factual predicates, and contradictory evidence.
• Lump-sum damages carried forward: connect remedial categories to locations, quantities, records, and duplication checks.

Final quality check

• Every material claim component and asserted defense has a row or research assignment.
• Each row identifies an assembly or explains its project-wide scope.
• Authorities support the stated propositions and applicable forum assumptions.
• Document IDs and pinpoints resolve to the correct source versions.
• Supporting and adverse records are checked; gaps are labeled accurately.
• Observations, allegations, expert opinions, and counsel’s inferences remain distinguishable.
• Repair amounts reconcile to scope without duplicate or superseded figures.
• Foundation, protection, and material open issues are resolved or expressly assigned with decision dependencies.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its trial preparation capabilities include document review, privilege and confidentiality analysis, chronology, and evidence analysis. Use them to examine project records feeding counsel’s matrix, while retaining legal and technical judgment. The matrix remains the team’s working document, not a promised dedicated product module. To discuss this construction-defect evidence workflow, book a demo.

Frequently asked questions

Should each subcontractor have a separate matrix?

Start with one issue-centered matrix identifying actors by row. Trade-specific working views can help, but retain shared defect IDs and source references so competing responsibility and causation positions remain comparable.

What if no expert has identified the water-entry pathway?

Mark causation incomplete. Record symptoms, test conditions, and competing explanations, then assign the technical question. Contractual responsibility for an assembly cannot substitute for evidence establishing the pathway.

Can the matrix become a trial exhibit?

Not automatically. Federal Rule 1006 permits summaries of voluminous admissible materials that cannot conveniently be examined in court, even when those materials have not been introduced. Originals or duplicates must be available to other parties at a reasonable time and place. Separately assess a proposed evidentiary summary; purely illustrative aids fall under Rule 107. See Rules 1006 and 107.

Does a construction defect notice resolve timing defenses?

No. Track notice separately from timing research. Florida section 558.004(1)(d), for example, states that a Chapter 558 notice does not toll a Chapter 95 repose period. It supplies neither the applicable period nor its trigger. Assign those questions separately and do not conflate repose with limitations. See section 558.004(1)(d).

Sources

• Federal Rules of Civil Procedure: Rule 26(b)(1), discovery scope.
• Federal Rules of Evidence: Rules 901, 1006, and 107, authentication, evidentiary summaries, and illustrative aids.
• 2026 Florida Statutes, section 558.004: subsections (1)(b) and (1)(d), notice content and repose non-tolling.

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.