1---2name: draft-expert-report-on-construction-delay-and-damages3task_id: arbitration-international-dispute-resolution/draft-expert-report-on-construction-delay-and-damages4description: Ensures a construction delay expert report conducts a proper concurrency analysis, applies the relevant home office overhead methodology correctly, resolves float ownership under the contract, and logs all cross-document inconsistencies.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-expert-report-on-construction-delay-and-damages8---910# Skill: Construction Delay and Damages Expert Report1112## 1. Subject-matter triage1314- Treat the assignment as a tribunal-facing expert report for construction delay, damages, and lost-profits analysis in international arbitration.15- First inventory the full source set and confirm whether there is one integrated chronology or multiple competing timelines, cost bases, or scope narratives.16- If the source documents contain more than one delay event, cost period, contract milestone, or damages theory, enumerate them before analysis and keep a separate row or subsection for each.17- If only one event or one damages strand is actually in scope, say so expressly and explain why the other potential categories are not analyzed.1819## 2. Failure modes the skill is correcting2021- Computes delay damages without first isolating each delay event and its critical-path effect, causing the report to blur distinct causation questions.22- Identifies overlap between owner-caused and contractor-caused delay but fails to deduct the overlapping period, overstating compensable delay.23- Applies home office overhead or similar head-office absorption logic without checking the correct billing base, project period, and approved extensions, producing a distorted daily rate.24- Treats float as automatically available to the claimant without first determining who owns it under the contract or schedule convention.25- States lost-profits or other downstream damages without tying them to the delay window, causation chain, and contractual or arbitral authority governing recoverability.26- Fails to reconcile differences among source files on dates, milestones, costs, completion status, scope, or mitigation, leaving the tribunal without a reliable source hierarchy.27- Writes conclusions as assertions rather than analysis, especially where a legal or damages proposition depends on a named authority or established practice rule.28- Omits a clear record of assumptions, exclusions, and uncertainty, making the expert opinion difficult to test.2930## 3. Legal frameworks / domain conventions that apply3132- Delay analysis must be anchored to critical path causation, not merely to chronological slippage; identify whether each event affected completion, a milestone, or a discrete workstream.33- Concurrency requires identification of overlapping delay periods and a judgment whether overlapping causes independently delayed the same critical path segment; the report should distinguish true concurrency from sequential delay.34- Float ownership depends on the contract and scheduling convention; the report must state the governing rule used and apply it before assigning compensability.35- Home office overhead should be presented through a transparent absorption or unabsorbed-overhead methodology, with the billing base, project duration, and compensable delay period clearly separated.36- Change-order or directive payments, if any, must be offset against the associated claimed amount to avoid double recovery.37- Lost profits, if claimed, must be tied to a recognized recoverability standard, including proximate cause, reasonable certainty, and any contractual limitation or arbitral constraint reflected in the record.38- Cross-document inconsistency analysis requires the report to identify conflicting versions, explain the effect of the conflict, and state which source is treated as controlling and why.39- Where the source record references legal standards, contract clauses, or arbitral rules, cite the controlling authority by name and section/article as the report states the proposition.4041## 4. Analytical scaffolds4243- Start with a concise expert identity, independence, instructions, and scope statement.44- Set out the project background: parties only as the record uses them, contract structure, milestones, baseline schedule, and any revisions relevant to delay or cost.45- Build a chronology that separates contractual milestones, actual progress, delay events, suspension periods, extensions, change directives, and completion/termination markers.46- For each delay event:47 - describe the event,48 - identify the affected work or milestone,49 - assess critical-path impact,50 - assign responsibility,51 - note any mitigation or acceleration evidence,52 - state the time impact and how it was measured.53- For overlapping delay events:54 - compare the affected periods,55 - determine whether they are truly concurrent,56 - isolate the overlapping window,57 - deduct or exclude that window from compensable delay where the governing rule requires it.58- For float:59 - identify the contractual or scheduling convention,60 - determine who owns the float,61 - explain whether the claimed delay exhausted or merely consumed available float,62 - state the effect on compensability.63- For overhead and delay-related damages:64 - use a clear stepwise method,65 - identify the relevant cost pool or billing base,66 - confirm the correct project performance period,67 - apply the delay period only after excluding non-compensable overlap or excluded days,68 - state the resulting allocation without compressing the steps.69- For lost profits:70 - separate past lost profits, future lost profits, and any revenue-related claim,71 - identify the causal link to the delay or disruption,72 - state the basis for projection, assumptions, and any record support,73 - address mitigation, offset, and uncertainty.74- For partial payments or offsets:75 - identify any payment already made on the same item,76 - deduct it from the claimed amount,77 - explain the netting logic.78- For each inconsistency:79 - quote or paraphrase the conflicting versions only as needed and avoid unnecessary repetition,80 - state the source hierarchy,81 - explain the chosen version,82 - identify the impact on the calculation or opinion.83- Where a proposition depends on law, contract text, or arbitral practice, name the authority and section/article rather than stating the conclusion bare.8485## 5. Vertical / structural / temporal relationships8687- Preserve the hierarchy from project fact to schedule analysis to delay causation to quantum, rather than mixing them in a single narrative.88- Keep temporal order explicit: baseline, variation, delay event, overlap, mitigation, extension, completion, and damages period.89- Distinguish vertical relationships between parent project milestones and subordinate work packages so that a delay to a subpackage is not mistaken for project completion delay.90- Distinguish horizontal relationships among parallel workstreams, especially where one stream may be delayed while another remains unaffected.91- When the record contains competing dates or amounts, present both versions, identify the downstream effect, and then state the authoritative version used for the calculation.9293## 6. Output structure conventions9495- Tribunal-ready expert report with:96 - title page and expert identification;97 - qualifications, independence, instructions, and materials relied upon;98 - executive summary of opinions;99 - project background and chronology;100 - methodology for delay, concurrency, float, and quantum;101 - detailed delay analysis by event;102 - concurrency and float analysis;103 - damages analysis, including overhead and any lost-profits theory;104 - offsets, mitigation, and adjustments;105 - cross-document inconsistency log;106 - assumptions, limitations, and reservations;107 - concluding opinions.108- Use clear headings and subheadings that mirror the analytical sequence, not a checklist copied from the source instructions.109- For every distinct issue or event, state the scale of the issue, cross-reference interacting documents or clauses, and explain the practical consequence for the damages opinion.110- Include a plain-language reconciliation note wherever source files diverge on dates, costs, progress, or scope.111- If the report depends on a legal or contractual proposition, cite the authority in-line and tie it to the specific analysis point.112- Keep the report self-contained and tribunal-ready; do not assume the tribunal will infer missing steps or supply omitted calculations.