Home · Try the Engine · Daubert / FRE 702 Disclosure
Free Court-Ready Generator

Daubert / FRE 702 Expert Disclosure — Generated in 30 Seconds

Drop in your baseline + current XER pair, fill in the case caption, download a court-ready expert disclosure DOCX. Mathematically verifiable. Forensically defensible. Free.

What you'll get: a complete starter FRE 702 / Daubert disclosure with topology hash + engine version, jurisdiction-aware methodology section, and amber [FILL IN] placeholders flagging every section that needs analyst-supplied facts. What you won't get: a finished filing — you must review every paragraph before serving. (Note: Proposed FRE 707, the AI-evidence rule, is pending; target effective date late-2026.)

30s
Generation time
SHA-256
Topology hash
FRE 702
Federal Rule of Evidence
$0
Cost
Build Yours

Disclosure Builder

Disclosure Builder

Required fields are marked with *. The live preview on the right updates as you type.

1. Schedule Pair

Both files are written to temporary files on the server while the disclosure is generated, then deleted. They are not kept.

2. Expert Witness Identity

FRE 702 requires the expert to be qualified by knowledge, skill, experience, training, or education.

3. Case & Retention

Drives the procedural rule citation and disclosure format.

4. Forensic Methodology

Per AACE 29R-03 Recommended Practice. Multi-method satisfies SCL Protocol §11.5 dual-method validation.

Privacy. Your two schedule files are sent to mcp.criticalpathpartners.ca, written to temporary files there while your disclosure is generated, and deleted as soon as it is ready. The generated DOCX, which contains what you typed above, is kept for 24 hours so the download link works, and is then deleted. Each request also leaves one log line, kept for 30 days: the time, the jurisdiction, the method, whether it succeeded, and a one-way hash of the schedule's activity network. It does not contain your name, your IP address, or anything else from the form or the files. Your IP address is held in the server's memory to apply the limit of 10 generations per hour and is not written to any file or log by this service. The company that hosts the server keeps its own records of requests. Nothing is sold.
Submitting…

Disclosure Generated — Verification Manifest

This manifest is embedded in the DOCX. Any third party can re-run the engine on the same XER pair and confirm the topology hash matches.

Engine version
cpm-engine v2.9.47
Topology hash (SHA-256)
—
Computed_at
—
Methodology
—
Jurisdiction
—
Verify this disclosure on /verify →
Read this before you file

This is a starter disclosure. You must review every paragraph before serving.

CPP's tools are forensically defensible because they refuse to claim what they can't prove. This disclosure is a scaffold computed from your XER pair only. It cannot incorporate the evidence-side facts a real expert opinion requires.

Amber placeholders

[FILL IN: ...] tags flag every section requiring analyst-supplied facts.

The DOCX will render highlighted amber placeholders for case caption, expert qualifications, prior-testimony list, hourly rate, and per-event causation narrative. You must replace each one before serving the disclosure.

XER-only inputs

Computed from XER schedule data only. Add evidence-side facts manually.

The engine sees CPM logic, durations, dates, and float. It does not see RFIs, change orders, daily reports, photos, weather, or correspondence. Per FRCP 26(a)(2)(B), your disclosure must integrate those evidence streams.

Methodology coverage

Single-method outputs are not Daubert-bulletproof.

A windows-only or TIA-only opinion can be challenged on reliability grounds. Selecting "Multi-method dual-validation" computes both MIP 3.3 and MIP 3.8 and surfaces any divergence — the standard SCL Protocol §11.5 dual-method cross-check.

What you do get

Mathematically verifiable computation with topology hash.

The CPM engine output, schedule-pair drift, and topology hash embedded in the DOCX are reproducible — a third party running the same XER pair through the same engine version gets the same hash. That's the floor for FRE 702 reliability.

No fabricated authority

Citations verified by CPP forensic-correctness audit.

Every case, treatise, and recommended practice cited in the disclosure scaffold has been independently verified. No fabricated authorities. See the cpm-engine repo + audit logs.

Notice to opposing counsel

The starter scaffold is, by design, conservative.

Default language uses "computed" and "the engine concludes" rather than "the expert opines" until you sign and certify. Replace the placeholders with your professional opinion language before serving.

Why CPP

Three things no other forensic tool ships.

We compete on math you can verify, citations you can re-check, and an engine you can read. Everything we publish has a manifest.

// 01

Topology hash on every disclosure

Every output carries an SHA-256 hash of the input XER topology + engine version. Third parties can verify the math hasn't been quietly changed via /verify on this same MCP server.

// 02

No fabricated case citations

Every legal authority cited has been independently verified during CPP's forensic-correctness audit. We removed five fabricated cases from earlier drafts. Read the audit log.

// 03

Engine source, manifest, and tests are public

The CPM engine, its calendar logic, its constraint propagation, and its 1,315 unit tests plus the JS↔Python cross-validation harness are all open. github.com/danafitkowski/cpp-cpm-engine

// 04

Used by forensic delay analysts at [coming soon: customer logos]

Currently in active use on real claims for construction, infrastructure, and energy projects. We'll list specific cases as our engagement letters allow.

Working a real claim?

Book a consult before serving the disclosure.

CPP runs a 30-minute review of any starter disclosure generated here at no cost. We flag missing evidence-side facts, methodology gaps, and Daubert-vulnerable language — before opposing counsel does.

Schedule a Consultation →