Talk to CPP.
Forensic schedule analysis, EOT support, and claims consulting. Send your matter and CPP replies within one business day.
Pick the one that fits.
Subject pre-filled with “CPP engagement inquiry” and four short lines to complete, including the parties on all sides: they are screened for conflicts before any file is opened. One analyst reads every message: no auto-responder, no junior triage, no sales pipeline.
Call
If voicemail picks up, leave a callback number and a one-sentence description of the matter. Reply within one business day.
Intro call
A 15-minute intro call is the usual starting point. Email or phone reaches Dana directly, and the call books the same week.
Before You Send
What helps CPP scope a forensic engagement.
- Project type and sector: e.g. municipal infrastructure, nuclear refurbishment, commercial fit-out, mining
- Current dispute status: notice phase, EOT submitted, mediation, arbitration, or litigation
- The XER file(s): baseline plus updates if you have them; CPP works with what you can share
- Correspondence record: RFIs, change directives, design responses, access logs, where available
- Target turnaround: the preliminary assessment comes back in days, not weeks; a full forensic analysis is scoped per matter, and the calendar is set by how fast the update chain and records arrive
NDA on request: CPP signs a standard mutual NDA before any documents move. None of the above is required to start a conversation; it just shortens the back-and-forth on scoping.
Looking for something different?
Setting up Claude Desktop, claude.ai web, Cursor, or Cline to use the CPP forensic MCP server? → the connection guide walks through the JSON snippet and the URL for each client.