How do I assemble an EOT claim with Bildstak?

Question

Accepted Answer

Bildstak's Claims Builder assembles an EOT claim by tracing the delay chain — cause event → RFI notice trail → programme slippage → contract entitlement clause → cost quantum — across every connected source, then exports a cited PDF package ready for submission. An Extension of Time claim lives or dies on the integrity of its chain of evidence. Bildstak automates the assembly across the sources that normally have to be reconciled by hand:

- Cause event — identify the delay event (late instruction, variation, unforeseen condition) from your document or RFI system (Procore, Aconex).
- Notice trail — the Claims Builder pulls the RFI thread that documents when you raised the issue, confirming timely notice under the contract.
- Programme impact — Bildstak reads your Primavera P6 (or equivalent) schedule and shows how the event pushed the critical path, comparing planned vs. current completion.
- Contract clause — you tag the relevant clause (e.g. FIDIC Sub-Clause 8.4, NEC Compensation Event) and the Builder attaches it to the record.
- Cost quantum — SAP, Maconomy or your ERP cost data is drawn in to quantify prolongation, preliminaries and direct costs attributable to the event.

Every link in the chain is cited back to its source document or data row, so the reviewer can trace the logic without asking for supplementary files. The finished package exports as a PDF.

Because Bildstak uses the IFC GlobalID as its join key, physical elements affected by the delay — a section of structure, a plant item — connect the BCF coordination issues, the cost lines and the schedule activities automatically. Bildstak is built to run this on complex programmes with no BIM as well, using P6 activity codes as the join spine for heavy-civil work.

Book a scoping call to see the Claims Builder on your own programme data.

كيف أُجمِّع مطالبة EOT باستخدام Bildstak؟

Related questions