Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Trace repair history by linking each reported condition to a precise project location, dated interventions, and records supporting scope, completion, and cost. Reconcile estimates, change orders, invoices, payments, and credits without treating them as interchangeable evidence. The resulting repair history tracker should show what was attempted, whether symptoms recurred, which expenditures are documented, and which causal or cost questions remain unresolved. Counsel can use it to test a damages presentation, identify targeted evidence requests, and prepare witnesses and experts.
When to use this workflow
Use this workflow when successive repairs, overlapping contractors, or inconsistent accounting obscure the relationship between an alleged construction defect and claimed remediation costs. It serves claimant’s counsel substantiating expenditures and defense counsel testing necessity, allocation, duplication, and completion.
Start before repair activity changes the physical evidence where possible. The method also works retrospectively, but missing photographs, discarded components, and undocumented work must remain visible gaps—not reconstructed facts.
This guide uses a US practice orientation and an October 13, 2026 research cutoff. Identify governing substantive law, contract terms, project type, forum, and applicable orders. The federal rules cited below have their own scope and exceptions; do not assume they govern state litigation or arbitration. These are evidence-organization recommendations, not conclusions about liability or recoverable damages.
What you need
Collect records by location and repair episode, rather than searching only for “defect” or “repair.” Obtain:
- Original contracts, repair proposals, warranties, drawings, specifications, submittals, RFIs, and change orders identifying original and remedial scopes.
- Complaint logs, inspection reports, maintenance records, daily reports, and correspondence showing symptoms, interventions, and recurrence.
- Before-and-after photographs, marked plans, test results, sample records, and removed-component records.
- Estimates, purchase orders, invoice detail, payment applications, accounting entries, payment evidence, credits, and completion records.
- Custodian information, native project-platform records, and witness identities for the owner, property manager, contractors, consultants, and accounting team.
Inventory missing versions and attachments. A revised proposal may supersede a price without establishing that its scope was authorized or performed. Keep counsel’s assessments separate from factual records, and route potentially protected communications for individualized privilege review; storage location alone should not determine the classification.
Use the template
Use the Construction Defect Claims — Repair history tracker below. You can copy this table into your working document or spreadsheet. Create one row for each material repair event or separately traceable cost component. Link related rows through stable event and defect identifiers.
| Event ID | Defect / location | Dates / status | Work / category | Evidence / pinpoint | Cost / basis | Gap / assessment | Action / owner |
|---|---|---|---|---|---|---|---|
“Defect / location” identifies the building, elevation, floor, room, and assembly as needed. “Dates / status” distinguishes observation, authorization, performance, completion, and recurrence. Use linked event rows where those dates cannot be shown clearly together.
“Work / category” separates emergency mitigation, permanent remediation, maintenance, and upgrades. These are analytical categories, not damages conclusions. “Cost / basis” identifies estimated, approved, invoiced, paid, credited, or disputed amounts. “Evidence / pinpoint” holds document IDs and page, line-item, photograph, or worksheet-cell references.
Use a supporting cost worksheet for multiple transactions within one event. Identify its cells in the tracker, and label event totals so they are not added again to their component amounts. In “Action / owner,” name the follow-up task, responsible person, and target review date.
Step by step
1. Establish the defect and location references
Build a consistent location hierarchy before entering transactions. “Window leak” is insufficient where several elevations have different assemblies or histories. Give each alleged condition a defect ID linked to marked plans and photographs, and record historical naming variations.
Separate the observed symptom from the proposed cause. Water staining, an expert’s flashing opinion, and alleged subcontractor responsibility are distinct propositions requiring distinct support. Compare contractual scope with installation evidence rather than treating scope allocation as proof of defective performance.
Record: the defect ID, location code, source-supported symptom, and disputed mapping. Assign unresolved location matches to someone who can verify them.
2. Reconstruct each intervention without collapsing dates
Trace installation and relevant baseline condition, first reported symptoms, notice, inspection, repair authorization, actual work, completion, and later recurrence. Distinguish document dates from event dates: a July invoice may describe June work.
Identify whether each date comes from a contemporaneous record, later recollection, or inference. Preserve contrary evidence. A contractor’s completion email and a resident’s continuing complaint may address different work or locations; neither should silently displace the other.
Use the chronology to identify gaps between interventions, not to imply causation merely because one event followed another. If the original installation date is unavailable, mark it unknown rather than substituting the first complaint date.
Record: event dates, their sources, confidence limitations, and links to predecessor or recurrence events.
3. Connect repair activity to physical evidence
For each intervention, identify the condition documented before work, the assembly exposed or removed, the work performed, and the resulting condition. Check whether photographs show the claimed location and whether test results identify their method and scope.
Before further invasive work, recommend a documented preservation and access plan addressing notice decisions, inspection participants, photographs, samples, custody, storage, and removed components. Counsel should determine applicable obligations separately; this plan is not a universal procedural rule.
Identify foundation witnesses. Under federal Evidence Rule 901, authentication requires sufficient support for finding that an item is what its proponent claims; testimony from a knowledgeable witness is one method. Authentication alone does not resolve hearsay or other admissibility questions. See Federal Rules of Evidence, Rule 901. (uscourts.gov)
Record: before-and-after references, completion evidence, foundation candidates, and unavailable physical evidence.
4. Trace each cost through its supporting records
Follow the chain from remedial task to estimate, authorization, change order, invoice, payment, credit, and completion evidence. Record missing links rather than assuming the chain is complete.
Treat an estimate as evidence of a proposed price, not payment. Treat an invoice as evidence of billing, then verify performance separately. Match payment records to the billed scope rather than assuming an expenditure establishes its relationship to the alleged defect. Compare quantities, descriptions, location references, and exclusions across versions.
Keep paid costs and prospective costs in separate subtotals. For an invoice covering multiple defects, retain the original total and document allocation separately. Check retainage and partial payments before marking an invoice fully paid.
Record: amounts by accounting status, matching sources, and unsupported scope or payment connections.
5. Reconcile overlap, credits, and mixed-purpose work
Compare repeated repairs by task and location. A replacement proposal may include work previously billed, while an earlier patch may be a distinct intervention. Do not assume duplication or necessity from similar descriptions alone.
Separate maintenance and upgrades from alleged defect remediation for further analysis. Request itemization where a proposal combines waterproofing, aesthetic improvements, and unrelated maintenance. Do not invent percentages to allocate a lump sum. Ask whether access, demolition, and restoration costs serve several work categories.
Check credits, refunds, allowances, revised invoices, and change-order incorporation. Flag alternate bids and superseded estimates so they cannot enter a cumulative total. Show disputed allocations explicitly rather than burying them in supported subtotals.
Record: reconciliation calculations, excluded duplicates, cost categories, and the basis for each allocation.
6. Turn gaps into targeted evidence questions
Prioritize gaps that change the analysis: whether a repair occurred, whether symptoms recurred at the same location, whether an invoice was credited, and whether replacement scope includes upgrades.
Frame requests around identified custodians, periods, locations, and record types. In federal district court, Rule 26(b)(1) permits discovery of nonprivileged matter relevant to claims or defenses and proportional to the case, subject to court limitations. Discoverability does not require admissibility. See Federal Rules of Civil Procedure, Rule 26(b)(1). (uscourts.gov)
Match questions to actual knowledge. Accounting staff may explain credits but not concealed flashing; a repair technician may explain installation but not payment allocation. Ask the appropriate witness to resolve each missing link.
Record: the missing proposition, requested evidence, follow-up owner, target review date, and priority.
7. Prepare a reviewable history and cost presentation
Produce a linked narrative and reconciled schedule from verified rows. Separate documented expenditures, prospective scope, disputed amounts, and unresolved causation questions. Have a second reviewer trace material totals and chronology statements to sources. Retain a dated version and identify the record set reviewed.
Decide whether the output is internal analysis, expert input, an illustrative aid, or a proposed evidentiary summary. Federal Rule 1006 addresses summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not the underlying materials have been introduced. Originals or duplicates must be available to other parties for examination or copying at a reasonable time and place. Purely illustrative aids fall under Rule 107; an internal spreadsheet does not automatically qualify as evidence. See Federal Rules of Evidence, Rules 1006 and 107. (uscourts.gov)
Record: intended use, reconciliation status, supporting record set, and assigned unresolved issues.
Worked example
Fictional scenario: Counsel represents Alder Quay Owners Association in a dispute with Marlow Construction concerning residential water intrusion. All parties, documents, dates, amounts, and facts below are fictional; the events occur in the same fictional project year.
The association’s demand worksheet adds an $8,400 emergency sealant invoice, a $31,500 localized flashing invoice, and a $96,000 replacement proposal, presenting $135,900 as repair costs. Counsel tests what that total represents.
| Event ID | Defect / location | Dates / status | Work / category | Evidence / pinpoint | Cost / basis | Gap / assessment | Action / owner |
|---|---|---|---|---|---|---|---|
| R-01 | D-01; east elevation, units 201–203 | Feb. 4 symptoms; Feb. 6 work recorded | Sealant patch; mitigation | F-011 p. 2 work log; F-012 p. 1 invoice; F-013 row 18 payment | $8,400 invoiced and paid | Log identifies exterior joints; no test result located | Request testing and completion photos; paralegal |
| R-02 | D-01; east elevation, units 201–203 | Apr. 10 work reported; June 2 complaint | Local flashing repair; remediation | F-021 pp. 1–3 invoice; F-022 p. 1 credit; F-023 row 42 payment; F-024 p. 2 complaint | $31,500 invoice less $3,500 credit; $28,000 paid | Invoice reports work date; later staining in unit 202; performance and cause need verification | Expert to compare locations and scope; counsel to seek work logs |
| R-03 | D-01 plus west elevation | Aug. 15 proposal; authorization not located | Replacement, maintenance, finish upgrade | F-031 pp. 3–6 proposal | $96,000 proposed; no allocation | West-side work and upgrade included; no payment or completion record located | Request itemization and status confirmation; counsel |
The documented payment subtotal is $36,400, not $39,900, because the flashing invoice was reduced by a credit. The $96,000 proposal remains prospective in this presentation. Its west-elevation work and upgrade require allocation before counsel can identify a defect-specific proposed repair figure.
The June complaint supports a report of later staining at unit 202, not a finding that the April repair failed or replacement is necessary. The expert needs repair details and condition evidence. Counsel must also verify the April performance date beyond the invoice. These distinctions change both the cost presentation and follow-up requests without supplying missing test results or assuming an unsupported cause.
Common mistakes
- Adding every dollar figure as damages. Separate estimates, invoices, payments, and alternatives; reconcile credits and avoid counting component rows twice.
- Using broad location labels. Link each repair to an assembly and marked plan so unrelated interventions are not merged.
- Equating recurrence with failed repair. Record the later symptom, then investigate location, intervening conditions, and causal evidence.
- Accepting an unexplained lump sum. Request itemization; keep mixed maintenance, upgrade, and shared-access costs visibly unresolved.
- Treating billing or completion correspondence as conclusive performance evidence. Compare logs, photographs, testing, and contrary reports; state what each record establishes.
Final quality check
- Every material event has a stable ID and verified location reference.
- Event dates are distinguished from document dates and recollections.
- Material factual statements link to checked sources and precise pinpoints.
- Paid, invoiced, credited, and prospective amounts remain distinguishable.
- Totals reconcile without duplicate estimates, invoices, change orders, or component rows.
- Recurrence and causation remain separate; contrary evidence is visible.
- Open issues are resolved or assigned with a follow-up date.
- The record set, version date, and intended evidentiary use are identified.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, and chronology capabilities can support examining repair records across time. Tabular review supports work across multiple documents. Counsel maintains the tracker, checks calculations and source relationships, and decides causal and legal significance. To discuss this construction repair evidence workflow, book a demo.
Frequently asked questions
Should unsuccessful repairs remain in the tracker?
Yes. Preserve their scope, cost, physical evidence, and subsequent reports. Describe an intervention as allegedly unsuccessful where the evidence remains disputed. Its reasonableness and recoverability require separate analysis.
How should costs shared across multiple defects be allocated?
Retain the original amount and seek task-level or quantity-based support. Document the allocation method and shared access or restoration costs. If no defensible split is available, classify the amount as unallocated rather than supplying an arbitrary percentage.
What if a payment cannot be matched to an invoice?
Record it separately with its source and possible matches. Ask accounting personnel about combined payments, credits, and reference numbers. Do not force a match because amounts are similar, or count the unmatched payment again beside a possibly corresponding invoice.
Can the tracker establish the recoverable repair amount?
Not by itself. It identifies supported costs and evidentiary gaps. Counsel must separately assess governing law, contractual allocation, causation, remedial scope, and the evidence supporting the proposed remedy.
Sources
- Federal Rules of Civil Procedure — Rule 26(b)(1): federal discovery relevance and proportionality.
- Federal Rules of Evidence — Rules 901, 1006, and 107: authentication, evidentiary summaries, and illustrative aids.
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.
