Contractual Risk Intelligence Engine.
Forge reads your project documents, extracts signals and governing rules, resolves delay attribution, and computes net contractual exposure — automatically.
Beta Notice: Forge is in active development. Features described here are continuously refined based on real-world testing.
The Reasoning Pipeline
Forge operates through a structured reasoning chain. Each layer feeds the next — from raw text to a defensible financial conclusion.
📄 Documents → Signals + Constraints
The engine separates two types of intelligence from every document: Signals (events that change project state, requiring triage) and Constraints (governing rules that define how signals translate into impact — LDs, penalties, weather entitlements, notice windows).
🔗 Activity Linkage
Each signal is semantically matched to its corresponding CPM activity using pgvector similarity search, composite scoring (semantic + temporal + WBS + trade), and configurable confidence thresholds.
⚖️ Responsibility Attribution
The LLM infers the responsible party for each delay signal: CONTRACTOR, OWNER, THIRD_PARTY, or FORCE_MAJEURE. Attribution confidence is tracked and displayed.
🔄 Concurrency Resolution
Delay intervals are projected onto the activity timeline and swept using a sweep-line algorithm. Overlapping windows are resolved into net attribution: contractorDays, ownerDays, concurrentDays.
⚓ Milestone Anchoring
Delay pressure propagates upstream to project milestones. Forge computes Risk Drift — predicting future slippage from emerging signals that have not yet hit the schedule baseline.
💰 Confirmed vs. Potential Exposure
The engine separates Confirmed Exposure (materialized delay) from Potential Exposure (emerging risk signals). Leading indicators are now clearly separated from trailing stats.
🚨 Automated Urgency Scoring
Every risk signal is automatically scored into one of three tiers — Act Now, Monitor, or Watch — based on critical path proximity, float buffer, and contractual severity. This ensures the most time-sensitive issues surface first, regardless of confirmed cost.
⏳ Statutory Notice & Time-Bars
Automated contractual countdown clocks track notice windows for FIDIC (28-day notice), NEC4 (8-week notice), and AIA A201 (21-day notice) to permanently prevent condition-precedent forfeitures.
🛡️ SCL Dispute Bundling & SHA-256 Sealing
Compiles contemporaneous site records into formal SCL Protocol hearing dossiers stamped with high-entropy SHA-256 checksums and expert Statement of Truth.
👥 Multi-Tier Clean-Room RBAC
8-tier stakeholder model with field-level redaction automatically sanitizing contractor profit margins, labor multipliers, and litigation counsel notes from external views.
🔑 Enterprise SSO & SCIM 2.0
Native SAML 2.0 / OIDC federation with Okta, Azure AD, and PingFederate, complete with automated SCIM 2.0 user lifecycle provisioning and soft de-provisioning.
🔮 Prospective Time Impact Analysis (What-If TIA)
Aligned with SCL Delay Protocol Principle 4. Planners inject hypothetical fragnet disruption events into the contemporaneous CPM schedule in memory—modeling critical path shifts, quantifying € exposure, and auto-drafting statutory delay notices.
Reference
Guides
From Information System to Reasoning Engine
Traditional construction tools are read-only. They display data — Gantt charts, cost reports, dashboards. You manually synthesise what connects a late concrete pour to a contractual penalty.
Forge crossed a different threshold. It doesn't just display information; it reasons about it. It evaluates contract rules, interprets delay causality, resolves concurrent responsibility, and computes the financial consequence — deterministically. That's what separates analytics from intelligence.
The strategic goal: answer the questions construction executives actually ask — "Which delays are truly ours? What is our real penalty exposure? Are we protected by concurrency? Which signals need attention right now?" — in real time, not retrospectively.
© 2026 Forge Project Intelligence. All rights reserved.