How to build a discovery request and response tracker for Construction Delay Claims

Build the tracker around individual production requests, then link each request to the disputed delay window, response language, produced records, and unresolved evidence gap. Record verified response dates, objections and withholding, production identifiers, and the next responsible reviewer separately. The resulting deliverable is a request-level control record showing whether counsel can trace schedule versions, access restrictions, notices, and claimed costs to responsive evidence. It should also show precisely what remains outstanding, who must address it, and what evidence supports closing the request.

When to use this workflow

Use this workflow when counsel serves or receives document requests concerning late completion, disrupted sequencing, access restrictions, changes, acceleration, or related construction costs. It supports outside counsel coordinating discovery with project personnel and in-house teams collecting records from operations, scheduling, accounting, and project platforms.

The scope is document-request tracking, not a complete delay analysis or litigation calendar. The procedural references concern US federal district-court litigation. For state litigation, arbitration, or contract appeals proceedings, use the applicable rules and orders instead. Contractual entitlement and notice questions depend on the executed agreement, incorporated terms, governing law, and project facts. This is a general professional workflow, not advice for a particular dispute.

What you need

Assemble these inputs before entering response status:

• Discovery records: served requests, service evidence, written responses, objections, extension agreements, relevant orders, and discovery correspondence.
• Contract records: executed agreement, amendments, scheduling requirements, change and notice provisions, and relevant releases.
• Delay definition: claimed windows, affected activities and work areas, alleged causes, competing explanations, and claimed cost categories.
• Project records: baseline and updated schedules, native schedule files, narratives, RFIs, submittals, daily reports, photographs, meeting minutes, procurement records, and cost ledgers.
• Production records: transmittals, production identifiers, native-file associations, redaction records, and applicable privilege descriptions.
• Collection map: repositories and contacts for the owner, contractor, designer, scheduler, and relevant subcontractors, distinguishing available records from those requiring further investigation.

Assign stable source IDs before review. Keep a request's scope separate from counsel's assessment of whether the available evidence supports the delay theory.

Use the template

Copy the Construction Delay Claims — Discovery response tracker below into your working document or spreadsheet. It is a working table, not a dedicated software module. Use one parent row per request and linked subrows for distinct schedule periods, custodians, or deficiencies.

Request / direction identifies the requesting party, set, and request number, plus whether your team is responding or reviewing another party's response. Preserve numbering after scope changes.

Service / dates links service evidence, the initial calculation, confirmed response date, production milestones, and extensions or orders. In a spreadsheet, separate these details into linked cells so the current deadline is visible without erasing its history.

Response / withholding captures response paragraph citations, commitments, objections, and withholding statements. Evidence / gaps links production ranges, native files, exact pages or spreadsheet cells, and missing components. A transmittal alone does not establish coverage.

Use Status for states such as “response pending,” “received—unverified,” “partial—gap assigned,” or “closed on stated scope.” Owner / action identifies who moves the row forward and when. Resolution / proof cites the agreement, supplemental response, reviewed production, or counsel decision supporting closure.

Step by step

1. Give each request a stable identity and issue link

Preserve the request verbatim in a linked source record; use a short description in the tracker. Map it to notice, causation, concurrency, mitigation, damages, or another identified issue. Identify the relevant delay window and affected activity where known.

Distinguish schedules covering a foundation-access restriction from procurement records concerning later equipment delivery. Labeling both “delay documents” hides different custodians and proof gaps. For incoming requests, identify which client repositories may contain responsive records; for outgoing requests, identify the expected evidence categories without assuming their existence.

Federal discovery covers nonprivileged information relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. Use that framework when evaluating scope. See Rule 26(b)(1).

Record: request ID, direction, issue link, period, and source citation.

2. Verify response dates against the controlling record

Locate service evidence before calculating a response date. For federal party production requests, Rule 34(b)(2)(A) generally provides 30 days after service. Requests delivered under Rule 26(d)(2) instead use the first Rule 26(f) conference as the trigger; stipulations or orders may alter the period. See Rule 34(b)(2)(A).

Have counsel verify the applicable trigger, service circumstances, time computation, and controlling agreements or orders. Preserve the initial calculation when an extension changes the current date. Separately track the written-response deadline and stated or agreed production milestones; receipt of a response does not establish receipt of documents.

Record: service proof, calculation basis, confirmed dates, confirming lawyer, extensions, and production milestones.

3. Translate each request into a document coverage check

Identify records addressing the request as written or subsequently narrowed. For schedule requests, distinguish baseline, periodic update, recovery schedule, narrative, and native data. Check data dates, calendars, logic, constraints, and revision identifiers rather than assuming similarly named files are interchangeable.

For cost requests, distinguish job-cost detail, subcontractor submissions, labor records, and summaries. For notice requests, identify the communication and responsive evidence of transmission or receipt. Match these categories to the disputed dates, not merely the project's overall duration.

For incoming requests, assign collection tasks by repository and custodian. For outgoing requests, identify the coverage needed to assess the response. These are review recommendations, not universal production requirements: scope remains subject to the request, objections, agreements, and governing procedures.

Record: expected categories, repositories, custodians, period coverage, and category-specific gaps.

4. Read responses for commitments and withholding

Separate what the party agrees to provide, what it objects to, and whether it states that responsive materials are being withheld because of an objection. Federal Rule 34(b)(2)(C) requires that withholding statement. An objection entry alone therefore does not capture the full response. See Rule 34(b)(2)(C).

For privilege or trial-preparation protection, Rule 26(b)(5)(A) requires an express claim and a description permitting assessment without disclosing protected information. It does not establish one universal log template. See Rule 26(b)(5)(A).

For incoming requests, counsel should reconcile proposed response commitments with collection results before approving the response. Keep sensitive internal reasoning in a restricted linked record, not a tracker intended for exchange.

Record: response citations, commitments, objections, withholding statements, protection-description references, and clarification questions.

5. Reconcile production against the requested coverage

Compare each delivery with the response commitment and coverage check. Link documents to every request they address, but do not count repeated deliveries of the same file as additional substantive coverage.

For schedules, inspect the actual version and native-file association. A PDF showing activity bars may leave underlying logic or calendars unverified. For daily reports, test coverage of the disputed dates and locations. For cost ledgers, check whether requested transaction detail accompanies a total and whether the entries concern the claimed delay period.

Distinguish absence from the reviewed production from confirmed nonexistence. Likewise, distinguish an opponent's statement about its search from your own verification. Neither should silently become a conclusion that no other responsive records exist.

Record: production ranges, exact evidence locations, covered periods, duplicates, missing native associations, and completeness questions.

6. Convert gaps into specific follow-up actions

Describe each deficiency using the request number, response commitment, delivery reviewed, missing component, and clarification sought. “Production incomplete” is less useful than identifying an absent update for a specified data date.

Prioritize gaps affecting the disputed delay theory. In Lusk Mechanical Contractors, the CBCA found the suspension duration reasonable and emphasized the lack of established critical-path impact for an additional interior-work suspension. This fact-specific federal procurement decision illustrates why event evidence and schedule-impact evidence should remain distinct; it is not a universal private-contract rule. See Lusk, pages 8–10.

For incoming requests, the next action may be further collection or response clarification. For outgoing requests, prepare a bounded inquiry and record counsel's escalation decision under the applicable procedures and orders.

Record: precise question, citations, owner, internal target date, and escalation decision.

7. Close only the scope that has been verified

Recheck supplemental responses and productions against the identified gap. Close the row when its recorded scope is resolved, or document counsel's decision not to pursue the remaining issue. Cite the supporting production, correspondence, or scope agreement.

Closure does not mean the evidence proves entitlement. Complete schedule production may undermine the claimed delay, while resolution of a discovery objection may leave the factual dispute intact. Keep distinct gaps open in linked subrows and assign responsibility for any identified follow-up; do not substitute a generic “monitor” note.

Record: closure basis, reviewer, source proof, qualifications, and linked open issues.

Worked example

Fictional scenario: Alder Quay Development sues Briar Span Builders over late completion of a private warehouse. Briar Span counterclaims for an alleged 18-day foundation-access delay and $240,000 in extended field costs. Alder Quay identifies late switchgear delivery as a competing cause. All parties, documents, amounts, and facts below are fictional.

Briar Span's counsel reviews three outgoing requests. Service proof is stored as SR-01. A written extension, EXT-01, sets September 30, 2026, for responses and October 7, 2026, for the initial production; counsel has confirmed both dates. RESP-01 and transmittal TR-01 establish timely receipt, not substantive completeness. Review on October 12 identifies these gaps:

The tracker changes counsel's next decision. Timely receipt does not justify describing the production as complete or as proving an 18-day owner-caused critical-path delay. The PDFs leave schedule-data coverage uncertain, the reopening email describes a proposal, and the equipment forecast does not establish delivery.

Counsel can now send three bounded inquiries rather than demand every project record. No entry assumes the missing evidence exists. The separate delay analysis must evaluate schedule impact and competing causes after these coverage questions are addressed.

Common mistakes

• Treating receipt as completion. Use “received—unverified” until versions, periods, and response commitments have been checked.
• Collapsing project and discovery dates. Keep the claimed work window separate from response and production milestones.
• Accepting filenames as schedule-version proof. Inspect data dates and revision information; identify unresolved native components.
• Treating silence as nonexistence. Write “not located in reviewed production,” then seek clarification.
• Closing after a promise to supplement. Verify delivery or record the agreed scope reduction and counsel's reason for accepting it.

Final quality check

• Every row links to the served request, current response, and scope modifications.
• Current dates have supporting records and an identified confirmer.
• Schedule entries distinguish versions, data dates, and native-file gaps.
• Production citations resolve to the actual page, file, or spreadsheet cell.
• Objections, withholding statements, and protection claims remain distinguishable.
• Coverage conclusions separate missing evidence from confirmed nonexistence.
• Every open issue has an owner and action; every closure has supporting proof.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, chronology, evidence analysis, redaction, and production. Use those capabilities to examine records underlying tracker entries, with the chronology viewer supporting review of disputed project events. The tracker remains counsel's work product: lawyers verify dates, assess completeness, and decide follow-up strategy. To discuss this document-review workflow, book a demo.

Frequently asked questions

Should incoming and outgoing requests share one tracker?

They can if direction is unmistakable. Incoming requests require collection and response tasks; outgoing requests require coverage review and deficiency follow-up. Separate sections may make responsibility clearer.

Does a schedule PDF resolve a request for schedule records?

Not necessarily. Compare the request and response commitment with the delivery. Identify whether native data, narratives, or revision history remain within scope; do not assume one format is always required.

How should one document responsive to several requests be recorded?

Use the same stable document ID in each relevant row and explain its coverage. Preserve production identifiers and version relationships so repeated delivery is not mistaken for additional evidence.

Can the tracker double as the delay analysis?

Keep them linked but distinct. The tracker records discovery coverage and tasks. Delay analysis evaluates sequencing, causation, overlapping events, and costs. A closed request or missing document does not decide those questions.

Sources

• Federal Rules of Civil Procedure: Rules 26 and 34.
• 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.