How to prepare a deposition outline from case documents for Construction Delay Claims

Prepare a construction-delay deposition outline by converting disputed project events into witness-specific question sequences supported by exact document references. Start with the pleaded delay theory, executed contract, and contemporaneous schedules; connect each factual objective to the witness’s knowledge, supporting records, contrary evidence, and unresolved gaps. The deliverable is an examination outline with stable exhibit references, foundation questions, schedule and notice inquiries, conditional follow-ups, and assigned open issues—not merely a chronology or a list of project documents.

When to use this workflow

Use this workflow when litigation counsel or an in-house construction disputes team has a defined witness, disputed delay period, and sufficient project records to identify competing explanations. It suits examinations of project managers, superintendents, schedulers, owner representatives, and organizational designees. Adjust technical questions to the witness’s actual responsibilities.

The task is preparing an examination, not completing discovery or proving the entire claim. Identify whether the disputed remedy is additional time, compensation, acceleration costs, disruption damages, or relief from liquidated damages. That choice determines which schedule effects and cost consequences matter.

This guide uses a US practice orientation. The cited federal civil rules govern federal district-court proceedings, not automatically state litigation, arbitration, or contract appeals boards. Check the applicable forum rules and orders separately. Contractual rights require analysis of the executed language, governing law, facts, and project context. Federal Rules of Civil Procedure, Rule 1. (uscourts.gov)

What you need

Assemble a controlled source set:

• Case and witness materials: pleadings, relevant discovery responses, deposition notice or organizational topics, prior statements, role descriptions, and periods of involvement.
• Contract records: executed agreement, scheduling specifications, amendments, notice provisions, change procedures, extensions, releases, and relevant payment documents.
• Schedule evidence: baseline and updates, native files where available, data dates, calendars, logic, constraints, narratives, and revision history.
• Event records: RFIs, submittals, daily reports, access restrictions, meeting minutes, photographs, procurement logs, weather records, and correspondence.
• Consequences and responses: mitigation proposals, resequencing instructions, staffing records, claimed-day calculations, cost ledgers, and subcontractor submissions.

Assign stable document IDs and preserve production identifiers. Identify the witness’s capacity and any agreed examination limits. Keep attorney analysis separate from potential exhibits. Missing schedule logic, attachments, or delivery records should remain stated gaps, not assumed facts.

Use the template

The companion template is Construction Delay Claims — Deposition outline. You can copy this table into your working document or spreadsheet. Use one row per examination objective and place longer question sequences beneath corresponding row IDs.

“Fact to test” states a factual proposition, not a desired legal conclusion. It accommodates both a potential admission and an unresolved inquiry. “Witness basis” identifies observation, authorship, receipt of a report, or organizational knowledge. “Source / pinpoint” identifies the document, page or clause, schedule version, and relevant activity ID.

“Questions / branch” records the opening question and follow-up if the witness agrees, denies, or cannot recall. Distinguish contradictions from missing information. “Exhibit status” records completeness and preparation for proposed use, not an admissibility ruling. Assign an owner and next action to each unresolved row.

Step by step

1. Define the examination’s factual decisions

Select decisions this witness can inform: who restricted access, what work was ready, which successor activities depended on it, what notice was sent, and what alternatives were considered. Connect each objective to a claim or defense without asking a project witness to decide contractual entitlement.

Federal discovery reaches nonprivileged information relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. Use that distinction to evaluate background inquiries, while checking applicable orders. Federal Rule of Civil Procedure 26(b)(1). (uscourts.gov)

Separate the occurrence of an event, its responsibility, its schedule effect, and its financial consequence. A witness may establish only one of these.

Record: topic, fact to test, connection to the disputed remedy, and examination priority.

2. Match topics to the witness’s knowledge

Identify employment dates, project responsibilities, site presence, reporting relationships, and schedule involvement. Separate firsthand observations from information received through meetings or reports. For reported information, ask who supplied it, when, and through which record.

For a federal organizational deposition, Rule 30(b)(6) requires reasonably particular topics and testimony about information known or reasonably available to the organization. It also requires a good-faith conference about examination topics. Organize these rows around organizational knowledge rather than only the designee’s participation. Federal Rule of Civil Procedure 30(b)(6). (uscourts.gov)

Record: knowledge basis, organizational topic if applicable, and subjects requiring another witness. Include questions about records and personnel consulted, without seeking privileged communications.

3. Assemble event records with precise references

For each disputed event, gather the instruction or restriction, contemporaneous report, relevant schedule update, notice, response, and mitigation evidence. Distinguish the event date, document date, and later retrospective account.

Read complete email chains and attachments. Check corrected minutes and whether photographs establish location and date. “Crew stood down” does not alone establish why, for how long, whether other work was available, or whether completion moved.

Keep supporting and adverse records together. Identify which record supports each question; do not cite an entire production range when a specific page is available. Prepare neutral foundation questions before presenting an apparent inconsistency.

Record: exact pinpoints, proposed exhibit references, completeness status, competing evidence, and any date uncertainty.

4. Test schedule causation without assuming it

Connect the event to identified activities and the contemporaneous schedule’s data date, logic, calendars, float, and constraints. Ask who entered progress, changed relationships, or revised durations. Distinguish an affected activity from an affected completion milestone.

Prepare branches for other constraints during the same window: late procurement, incomplete predecessor work, staffing shortages, or restricted access elsewhere. Simultaneous events are subjects for investigation, not automatic concurrency conclusions. Ask whether the witness understood the schedule effect contemporaneously or formed that view later.

In Lusk, the CBCA denied suspension-related compensation, finding the suspension reasonable and emphasizing missing critical-path proof for an additional interior-work suspension. This fact-specific federal procurement decision illustrates an evidentiary problem; it does not establish a universal rule for private-project claims. Lusk, pages 8–10. (cbca.gov)

Record: activity IDs, schedule version, causal proposition, alternative explanation, and technical-review owner.

5. Draft notice, authorization, and mitigation sequences

Read the actual contract. Identify the asserted notice trigger, sender, recipient, delivery method, required contents, and follow-up obligations. Ask what happened and what records demonstrate; reserve compliance, waiver, and amendment consequences for counsel’s analysis.

Distinguish an instruction to perform changed work from authority to approve time or money. Ask who issued and received it, how it was understood, and whether a contemporaneous reservation or response exists. Inspect relevant extensions and releases before framing questions about preserved demands.

For mitigation, examine available work fronts, resequencing, procurement alternatives, staffing decisions, and why options were rejected. A proposed alternative is not necessarily feasible; test prerequisites, resources, safety constraints, and expected effects.

Record: clause citation, factual sequence, delivery evidence, and unresolved authority or feasibility issues.

6. Prepare foundation and answer-dependent branches

For key exhibits, ask how the witness recognizes the record, who created or maintained it, what system produced it, and whether the version is complete. For schedules, distinguish familiarity with the displayed report from knowledge of underlying model inputs.

Federal Rule of Evidence 901 requires evidence supporting a finding that an item is what its proponent claims; knowledgeable-witness testimony is one example. Authentication alone does not establish the truth of every entry or resolve other admissibility objections. Federal Rule of Evidence 901. (uscourts.gov)

If an entry is accepted, explore its basis. If disputed, identify the specific error and contrary source. If unknown, identify knowledgeable people and records. Keep one factual proposition per question.

Record: foundation questions, denial and uncertainty branches, and remaining evidentiary concerns.

7. Sequence and rehearse the outline

Order the examination by role and disputed event, not production order. Establish responsibilities and record systems, then develop event facts, schedule consequences, notice, mitigation, and supported cost consequences. Reserve comparison questions until both records have a foundation.

Prioritize essential inquiries against the available examination time. Rehearse transitions between schedule versions and inspect every cited page against the exhibit set. Use stable proposed exhibit references; update the mapping when actual exhibit numbers are assigned. Do not place unverified calculations in questions as established facts.

Record: final sequence, priorities, exhibit mapping, and named responsibility for unresolved issues.

Worked example

Entirely fictional scenario: Alder Quay Builders claims that owner Baystone Labs caused an 18-day completion delay on a private laboratory project by withholding Level 2 access. Counsel will depose Baystone’s project manager, who attended coordination meetings but did not maintain the contractor’s schedule.

The fictional agreement’s section 12.3 requires written delay notice to Baystone’s designated representative within seven calendar days after the contractor recognizes the delaying event. This is invented wording, not a legal rule or standard term. The project manager is that designated representative.

An April 6 daily report, AQ-041, records a Level 2 crew stand-down. Meeting minutes BS-018 attribute the access restriction to Baystone. Update U04 shows delayed ceiling closure; procurement log AQ-052, dated April 8, lists controls equipment as pending. Email AQ-061, dated April 9, lists the project manager as recipient and includes a delay-notice attachment. Delivery metadata and native U04 logic are missing. Counsel has no verified calculation connecting the restriction to all 18 claimed days.

The records justify narrower inquiries, not the assertion that Baystone caused 18 days. D01 tests responsibility and scope. D02 tests a competing constraint without treating pending equipment as proven concurrent delay. D03 separates sending, receipt, and recognition of the event. Counsel should obtain the missing sources and redirect technical questions to a knowledgeable scheduler rather than press this witness to supply unsupported causation opinions.

Common mistakes

• Adding incident durations together. Examine overlapping windows and ask how each event affected the relevant milestone instead of summing stand-down days.
• Treating a later schedule as contemporaneous. Identify its data date, revision history, and retrospective assumptions before comparing site records.
• Treating an RFI response as a time award. Separate clarification, work authorization, contractual authority, and approval of additional time.
• Asking every witness expert scheduling questions. Establish responsibilities first; direct model assumptions to their author or another informed witness.
• Turning missing records into admissions. Ask about custodians, searches, and record practices without assuming the underlying event never occurred.

Final quality check

• Essential questions connect to disputed issues and the witness’s knowledge or organizational capacity.
• IDs, pages, clauses, activity IDs, and schedule versions match inspected sources.
• Event dates, document dates, and retrospective accounts remain distinct.
• Supporting and adverse records accompany each material topic.
• Notice questions follow executed provisions and identified trigger facts.
• Key exhibits have foundation questions and uncertainty branches.
• Proposed exhibits have been checked for privilege, confidentiality restrictions, and completeness.
• Open issues are resolved or assigned to a named reviewer with a next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its deposition preparation capabilities include document review and evidence analysis; the chronology viewer supports examination of event sequence. Use these capabilities to inform the lawyer-maintained outline, retaining counsel’s source verification, witness assessment, and examination strategy. To discuss applying this workflow to construction project records, book a demo.

Frequently asked questions

Should the outline follow chronology or disputed issues?

Organize by disputed event, with chronology inside each event. Keep a short master timeline for orientation, but group access, schedule effects, notice, and mitigation questions concerning the same restriction.

What if only PDF schedules are available?

Record what the PDFs show and leave uncertain. Ask about authorship, data dates, updates, and underlying files. Do not infer hidden logic or calendars from a bar chart; assign native-file collection and technical review.

How should an organizational outline differ?

Map questions to designated topics and distinguish organizational information from personal recollection. Ask which records and personnel informed preparation. Apply the forum’s requirements rather than importing federal Rule 30(b)(6) into another proceeding.

Should damages questions appear here?

Include them when this witness can explain event-linked costs, such as idle labor or extended supervision. Test actual versus estimated charges, overlapping periods, and other contributing work. Direct accounting methodology to witnesses with the necessary basis.

Sources

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

Scope: general professional workflow guidance using the supplied research cutoff of October 13, 2026, 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.