How to prepare a document collection checklist for Construction Delay Claims

Prepare a construction delay collection checklist by mapping each disputed delay window to the contract provisions, schedule versions, project communications, and cost records needed to test it. Identify custodians and repositories, specify usable file formats, and assign each gap an owner and next action. The resulting deliverable is a source-linked collection register that distinguishes requested records from received and verified material. It should help counsel evaluate competing explanations without treating incident duration, completion impact, and recoverable loss as interchangeable.

When to use this workflow

Use this workflow when a contractor asserts delayed completion or disruption, an owner seeks delay-related relief, or counsel receives discovery requests concerning project performance. It suits outside counsel and in-house teams coordinating project personnel, IT staff, and scheduling or damages consultants.

The task is to define, collect, and validate the documentary record—not determine entitlement or calculate a final claim. Include favorable and adverse evidence, such as contractor sequencing problems, late owner decisions, mitigation efforts, and overlapping constraints.

This guide uses a US practice orientation. In federal district court, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. This governs discovery scope, not every internal collection decision. Check state rules, arbitral requirements, and matter-specific orders separately. See Federal Rule of Civil Procedure 26(b)(1).

What you need

Start with the executed agreement, incorporated conditions, amendments, change orders, releases, and available notices. Identify provisions addressing schedule submissions, extensions, changes, suspension, acceleration, payment, and claims. Rights depend on actual wording, governing law, facts, and project context.

Gather these operational inputs:

• Disputed windows: alleged event dates, affected areas, activities, milestones, and competing explanations.
• Schedule inventory: baseline, accepted or rejected updates, recovery schedules, narratives, calendars, and native files.
• People and systems: project managers, superintendents, schedulers, commercial staff, subcontractor contacts, email accounts, phones, shared drives, and project platforms.
• Performance records: RFIs, submittals, procurement logs, delivery records, daily reports, photographs, meeting minutes, inspections, and weather records.
• Financial records: job-cost ledgers, cost-code definitions, timesheets, equipment records, invoices, subcontractor claims, credits, and payment records.
• Matter constraints: preservation instructions, discovery requests, collection agreements, access restrictions, and known unavailable sources.

Record missing inputs immediately. A project manager’s assurance that all schedules are in one folder is a lead to verify, not evidence of collection completeness.

Use the template

Use the Construction Delay Claims — Document collection checklist below. You can copy this table into your working document or spreadsheet. Use one row per defined collection task. Split rows when different custodians, repositories, formats, or follow-up actions require separate tracking.

Assign a stable collection ID, such as COL-001, and a delay-window reference. “Issue / records” explains the question being tested: whether late steel delivery affected the completion sequence, rather than simply “procurement.” Include the relevant contract clause when the request concerns notice or entitlement.

“Dates / format” identifies the requested range and file characteristics. “Evidence / citation” identifies received document IDs, pages, or spreadsheet sheet-and-cell references—not merely a folder name. Store detailed inventories separately if one row covers many files, and link that inventory by a stable reference.

Use distinct statuses: identified, requested, partially received, received, and verified. Record the verifier and verification date in the last column; record the next-action date with its owner. Verification means the defined collection checks passed, not that the records prove liability. Keep sensitive legal analysis outside broadly circulated collection requests.

Step by step

1. Define the disputed windows and collection questions

Break the allegation into periods and work areas. Ask what happened, which activities were affected, what completion consequence is asserted, and what alternative causes need testing. Include reasonable lead-in and recovery periods rather than limiting collection to alleged stoppage dates.

Distinguish completion delay from reduced productivity, resequencing, and acceleration. Their records overlap, but their collection questions differ. Productivity allegations may require crew-level hours and installed quantities even when completion dates are unchanged. Record allegations as allegations until supported; do not convert an interview recollection into a documented event.

Record: window IDs, issues, initial date ranges, and unresolved scope questions in the first two columns.

2. Translate contract provisions into document requests

Identify the contract version applicable to each event. For notices, request the communication, attachments, transmittal, recipient information, delivery evidence, and responses. Collect amendments, releases, and final-payment records where relevant. Distinguish a request for more time from a request for compensation; do not assume one communication addresses both.

Do not import federal procurement provisions into private work. For a federal contract incorporating FAR 52.243-4, collect evidence concerning the relevant order, written notice, adjustment assertion, and final-payment status. Inspect the incorporated version and deviations before analyzing obligations. See the FAR Changes clause, a federal contract-specific example rather than a general construction deadline rule.

Record: clause citations, requested communications, and version uncertainties. Assign interpretation questions to counsel, not collectors.

3. Map custodians, repositories, and access

Interview the people who created and maintained the records. Determine whether the scheduling consultant retained native updates, whether site instructions moved from email to texts, and whether subcontractor records remain outside client systems.

For project platforms, establish what an available export contains and omits. Attachments, comments, timestamps, revision history, and linked records may need separate collection. Coordinate with legal and technical personnel before accounts close or systems migrate. Record the original location and collection method so reviewers can trace a file back to its source.

Identify external repositories separately. Counsel should determine the appropriate access or discovery route rather than assuming the client can obtain every project participant’s records.

Record: custodian, source location, access contact, availability concern, and collection owner.

4. Specify schedule and performance collections precisely

Request baseline and contemporaneous updates, including relevant rejected or superseded versions. Specify native files, calendars, logic, constraints, data dates, narratives, and revision history. Preserve readable reports alongside native files without treating them as equivalent substitutes. Ask the scheduler to identify software and version information needed to inspect the files.

Pair schedules with daily reports, access restrictions, RFI responses, delivery records, and meeting minutes. These test the assumptions behind activity dates and sequencing.

In Lusk, the CBCA found an additional interior-work suspension reasonable and emphasized the contractor’s failure to establish critical-path impact. This fact-specific federal procurement decision supports asking what schedule evidence exists—not imposing identical proof requirements on every disruption claim. See Lusk, pages 8–10.

Record: versions requested, associated performance records, received IDs, and native-file gaps.

5. Collect cost and mitigation records against the same windows

Request records permitting later reconciliation, not only claim summaries. Capture cost-code definitions, transaction detail, payroll periods, equipment allocation, subcontractor backup, and credits. Distinguish actual charges from estimates and forecasts. Identify whether costs are project-wide or attributable to a particular work area or period.

Request records of alternative work fronts, resequencing proposals, additional shifts, and rejected mitigation options. Include unrelated work and overlapping constraints that may explain the same expenditure. Where one record serves multiple windows, cross-reference it rather than creating the appearance of separate costs.

Record: the window and cost category tested, ledger or spreadsheet citations, missing backup, and a named reconciliation reviewer. A total-cost spreadsheet alone should not close the task.

6. Separate collection completeness from privilege and production decisions

Maintain source references while routing potentially protected material for legal review. Inspect mixed business/legal chains and attachments individually; do not assume an attachment shares the parent message’s treatment. Record participants and roles where needed for review without publishing legal advice in shared status fields.

In federal discovery, Rule 26(b)(5)(A) requires an express privilege or trial-preparation protection claim and a description enabling assessment without revealing protected information when otherwise discoverable material is withheld. It does not prescribe one universal log format. See Rule 26(b)(5)(A).

Link collection rows to discovery-request IDs where applicable. Keep responsiveness, privilege, production, and collection statuses distinct, with response deadlines maintained in the matter’s discovery tracker.

Record: review routing, attachment issues, reviewer, and outstanding collection work.

7. Validate receipt and close or assign every gap

Test whether files open, schedules contain expected data dates, attachments are present, and exports cover the requested period. Compare receipts with the repository inventory and custodian explanations. Check selected revisions against their internal contents rather than relying on filenames.

For unavailable material, record searches performed, the person confirming the gap, and possible substitutes. A PDF report may answer some questions without supplying missing schedule logic. Escalate consequential gaps for counsel’s scope or follow-up decision. Reopen a row if later evidence reveals an omitted version, custodian, or attachment.

Record: verifier, date, checks performed, result, and remaining action. Close only against the defined request, or retain an incomplete status with an assigned next step.

Worked example

Fictional scenario: Alder Quay Development hired Northbank Build to construct a distribution facility. Northbank alleges that electrical-room access restrictions during June 1–24, 2025 caused 24 days of late completion and $180,000 in extended site costs. Alder Quay alleges that late switchgear delivery independently constrained energization. All parties, records, dates, amounts, and allegations below are fictional.

Counsel receives a PDF schedule, a notice-email printout, and a claim spreadsheet. The fictional contract’s section 12.4 requires written delay notice to the owner’s designated representative. Its application remains for counsel to assess against the full contract and governing law. The collection window includes May planning and July recovery records.

The first row changes priority: obtain contemporaneous logic and procurement evidence before equating restricted access with completion delay. The second separates a notice allegation from evidence of required contents and transmission. The third redirects collection from a claimed total to transactions and allocation support.

The checklist does not establish concurrency, notice compliance, or recoverable costs. It identifies the evidence needed to test those questions. The missing calendar remains missing; the switchgear allegation remains unverified until records support or contradict it.

Common mistakes

• Collecting only the final schedule. Request contemporaneous versions and narratives so later revisions do not obscure the original sequence.
• Searching only incident dates. Include planning, procurement, and recovery periods needed to test causation.
• Treating an export as complete. Check attachments, revision history, comments, and date boundaries against the defined request.
• Collecting only favorable records. Include competing causes, mitigation, and adverse communications.
• Closing rows on receipt. Verify contents, source references, and gaps; distinguish collection completion from legal review.

Final quality check

• Each disputed window has issue-specific requests, with irrelevant categories expressly excluded rather than silently omitted.
• Contract citations identify the executed version and relevant amendments.
• Each repository has a custodian or access contact and an assigned collection owner.
• Native schedules and associated data are verified or expressly outstanding.
• Received records have stable IDs and usable page, clause, or cell references.
• Privilege routing remains separate from collection and production status.
• Every material gap is resolved, accepted by counsel with reasons, or assigned with a next-action date.
• Legal sources and cited project evidence have been checked against underlying material.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and chronology capabilities can support review of collected project records. Explore the chronology viewer for event analysis and trial preparation for downstream evidence work. The checklist remains the legal team’s work product; counsel determines scope, verifies sources, and resolves gaps. Book a demo to discuss your construction-document workflow.

Frequently asked questions

Should every project document be requested immediately?

Not necessarily. Prioritize collection against disputed issues while addressing preservation separately. Expand requests when initial records reveal another relevant period, custodian, or cause. Document scope decisions and their reasons.

Are PDF schedules enough?

They may show reported dates but leave logic, calendars, or constraints unresolved. Request native files where available. If unavailable, specify which questions the remaining records cannot answer and who will assess alternatives.

How should subcontractor records be handled?

Create separate rows identifying the holder, records, access route, and responsible coordinator. Link performance and cost backup to the same delay windows without assuming the general contractor holds complete records.

Can the checklist double as a production tracker?

It can link to one, but collection and production answer different questions. Preserve separate statuses for receipt, responsiveness, privilege review, and production. A collected document is not automatically ready or required for production.

Sources

• Federal Rules of Civil Procedure: Rules 26(b)(1) and 26(b)(5)(A), governing federal discovery scope and protection claims.
• FAR 52.243-4, Changes: federal contract-specific change, notice, and adjustment provisions.
• Lusk Mechanical Contractors, Inc. v. GSA, CBCA 7759: suspension and critical-path analysis, pages 8–10.

Scope: General professional workflow guidance, not advice for a particular matter.

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.