What you actually get.

Self-contained DCMA 14-Point assessment of a baseline-vs-current XER pair. One file, no dependencies, opens in any browser — drop it on a network share and your PMO sees the same dashboard you do.

• Executive summary with overall grade and the three to five findings most likely to surface in cross-examination
• 14-criterion drill-downs — logic, lags, hard constraints, BEI, missed tasks, float distribution, critical-path reasonableness, each with pass/fail rationale
• Baseline vs current variance — activity-level slip, added/removed activities, retroactive baseline edits
• Slip register ranked by impact to project finish
• BEI / CPLI / SPI metrics with industry benchmarks and contextual reading
• GAO-16-89G + CPP Quality Overlay grade with embedded reproducibility manifest

Windows analysis (AACE MIP 3.3 — Observational / Dynamic / Contemporaneous As-Is) across the full update chain. The HTML dashboard is the analyst's working document; the DOCX narrative is the owner-deliverable executive read.

• Per-window cause attribution with critical-path-impact gate and per-party day buckets that sum to project drift
• Concurrent delay matrix — per window × per party — with WOET 4-state day classifier
• Notice-gate review per SCL Protocol §3 (paired with evidence ledger when claim-workbench is run alongside)
• Baseline stability check flagging retroactive edits, added/removed activities, completion reversals
• Dual-method validation against collapsed-as-built result with documented gap reconciliation
• Per-window CSVs for downstream pivot work, expert workpapers, and exhibit preparation

But-for analysis (AACE MIP 3.8 — Modeled / Subtractive / Single Simulation). Independent recomputation of project drift via subtractive removal of delay activities from the as-built schedule. The validation step opposing counsel demands.

• As-built finish vs but-for finish per delay event, with cumulative roll-up across the event population
• Per-event float erosion showing which removals matter to project finish and which are absorbed
• Subtractive simulation log recording every activity edit so the calculation is reproducible
• Dual-method gap report against the windows-analysis result — flags any divergence that needs analyst reconciliation before submission
• Methodology disclosure identifying what the technique can and cannot conclude

Prospective TIA with fragnet insertion against a contemporaneous baseline. The forward-looking method when a delay event has occurred but its impact on remaining work is the question.

• Fragnet insertion for each delay event — added activities, logic ties, calendar assignments, constraint treatment
• Modeled / additive / multiple-base CPM forward-pass with pre- and post-impact finish dates
• Per-event impact quantification in working days, with float-erosion accounting
• Cumulative impact tracking when multiple events are modeled in sequence
• Owner-vs-contractor delay attribution with concurrent-delay handling per SCL Protocol
• DOCX narrative formatted for inclusion as a TIA exhibit in an EOT submission

Probabilistic finish-date forecast with sensitivity analysis. Suitable for executive briefings, owner risk reviews, or as the quantitative spine of a contractor's schedule-acceleration case.

• P10 / P50 / P80 / P90 completion-date forecasts using linear-interpolation percentiles per AACE convention
• Sensitivity tornado identifying the activities whose duration uncertainty drives finish-date variance
• Scenario comparison — baseline risk profile vs mitigated profile, with side-by-side finish-date distributions
• Convergence diagnostics confirming iteration count is sufficient for the reported percentile precision
• QRAMM maturity badge per AACE 122R-22, naming the maturity tier the inputs support
• DOCX narrative with input assumptions, methodology disclosure, and what the simulation does not establish

The full owner-submission-ready Extension of Time package. Cover letter, per-event exhibits, forensic workbook, mitigation report, supporting-documents index, and an internal QC pass — assembled as one indexed bundle.

• DOCX cover letter framed for owner submission, naming the contract clauses and notice provisions invoked
• Per-event exhibits — one DOCX per delay event with cause, attribution, contemporaneous notice, impact quantification
• Forensic workbook (XLSX) — per-window math, per-event roll-up, attribution buckets, formulas left visible for owner-side review
• Mitigation report documenting steps taken to reduce or absorb impact, per SCL Protocol mitigation duty
• Supporting documents index cross-referencing every cited RFI, change order, daily report, and correspondence item
• Owner-submission QC markdown — internal pre-flight check for completeness, citation accuracy, exhibit cross-references

Defensive equivalent of the EOT package. Tests the opposing party's claim against ten defense theories, then assembles the rebuttal letter, defense workbook, and dashboard for response.

• DOCX rebuttal letter structured to match the opposing party's submission, theory by theory
• XLSX defense workbook with per-event findings and the math behind each defense theory
• HTML rebuttal dashboard for internal counsel review and deposition prep workpapers
• Ten defense theories tested: no critical-path impact, concurrent delay, pacing, no notice, failure to mitigate, causation gap, float ownership, scope-change disguise, self-caused acceleration, LD cap
• Per-theory evidence pull citing the contemporaneous record items each theory rests on

Evidence-triage layer underneath the forensic report. Takes one folder of mixed correspondence (MSG / PDF / DOCX / XLSX) plus the full XER update chain and produces a unified analysis the analyst works from.

• Evidence ledger CSV — every correspondence item parsed, dated, sender-classified by analyst-supplied domain mapping
• Schedule chain-diff CSV across the full update chain — TASKPRED add/remove, constraint flips, retroactive baseline edits, completion reversals
• Rolling baseline — every activity carries the baseline date it had when it first appeared in the chain
• Trust score JSON flagging statistical patterns (zero-duration-variance schedules, no-new-activities, every-activity-hits-baseline) — correlation, not causation
• Slip-to-evidence cross-reference with NER-extracted recurring actors flagged for analyst follow-up review
• HTML dashboard stitching all of the above into one navigable working surface