How do I trace a delay from cause to cost?

Tracing a delay from its cause to its financial consequence is the core challenge in construction claims and forensic scheduling. The information exists, but it is spread across five or more systems and the joins between them are manual.

Bildstak federates the chain:

Step 1 — Identify the cause event Start with the source: a late instruction, a variation order, unforeseen ground conditions, or an employer-caused disruption. This typically appears as an RFI or a site instruction in Procore or Aconex. Bildstak shows you the document, the date it was raised, and who holds the ball.

Step 2 — Establish notice Bildstak pulls the RFI thread — who was notified, when, and what was said — confirming that the contractor gave timely notice as required by the contract. This is the contemporaneous record that validates the entitlement.

Step 3 — Map the programme impact With Primavera P6 connected, Bildstak compares the accepted baseline schedule against the current programme at the affected activities. It shows how the delay event pushed the critical path and by how many days, and whether there was float that absorbed part of the impact.

Step 4 — Cite the contract clause Tag the entitlement clause (FIDIC 8.4, NEC X2, JCTMB Clause 25, etc.) and Bildstak links it to the delay record, supporting the argument that the event was a qualifying cause of delay.

Step 5 — Quantify the cost From the ERP (SAP, Maconomy, or spreadsheets), Bildstak draws the actual cost incurred in the delay period — site preliminaries, extended supervision, idle plant — and attributes it to the event.

The output is a complete, cited cause-to-cost chain that can be exported as a claims narrative. Every link in the chain names its source: the RFI ticket, the P6 activity ID, the cost ledger line.