Delay Intelligence for Indian EPC Projects
Cause analysis, contractor scoring, and the root-cause patterns Excel project tracking can never surface. Stop blaming the contractor; start fixing the system.
Free Starter tier — no credit card
Every project review meeting blames the same contractor — and is wrong half the time
Indian EPC project reviews tend to converge on a single villain: the sub-contractor who slipped. The data, when somebody bothers to assemble it, often tells a different story — drawing release was 21 days late, material indent was raised after work-front opened, the client's PMC sat on submittal approval for 32 days. The contractor was 11 days late on top of all that. Excel project tracking can record dates; it cannot tag a cause to each delay. So every review repeats the same story, and the same blame, until the same contractor walks away from the next project.
How it actually works
Five mechanics, each anchored to a specific Indian EPC failure pattern.
10+ delay cause taxonomy
Material delay, drawing delay, client delay, PMC approval delay, regulatory/permit delay, land access issue, subcontractor dispute, force majeure, client payment delay, design change. Each milestone delay is tagged with a cause; the dashboard surfaces the dominant pattern.
Contractor reliability scoring
Each contractor scored on weighted on-time delivery, average delay duration, and milestone value handled. The scorecard is data-driven, ranked, exportable. Award decisions stop being relationship calls.
Time-weighted stagnation
Replaces binary 14-day flags with severity gradient: a milestone stuck for 21 days is 1.5x worse than one stuck for 14 days. Health score reflects severity, not just count.
Root-cause pattern surfacing
The dashboard surfaces patterns: 'Drawing release delays caused 38% of your milestone slips this quarter' — the kind of insight that drives a process change, not a project-by-project firefight.
Client/PMC delay attribution
Delays attributable to the client or PMC are tagged separately. Your contract claims (extension of time, idle resource compensation) get an evidence trail instead of a 6-month memory game.
Excel project tracking vs MS Project vs KaptIQ Delay Intelligence
| Capability | Excel sheet | MS Project / Primavera | KaptIQ |
|---|---|---|---|
| Date tracking | Manual, drifts | Yes, Gantt-driven | Yes, with cause tagging |
| Cause taxonomy | Free-text notes, useless at scale | Custom fields, rarely used | 10+ standard causes, mandatory tag |
| Contractor scoring | Gut feel | Not native | Weighted on-time + duration + value |
| Pattern surfacing | End-of-year ad-hoc analysis | Custom reports, requires expertise | Live dashboard, dominant cause ranked |
| Client delay attribution | Email trail, contested at claim time | Not native | Tagged + timestamped from delay event |
How this looks per vertical
The same capability adapts to each vertical's billing structure.
Common questions
Can I add custom delay causes for my vertical?
Yes. The 10+ standard causes ship out-of-box; you can add vertical-specific ones (e.g., 'PUF panel galvanisation queue' for cold storage).
How is contractor reliability scored?
Weighted score: on-time milestone delivery rate (40%) + average delay duration (30%) + milestone value handled (30%). Configurable per company.
Does it surface our own internal delays?
Yes. Internal delays (drawing release, material indent, design change) are tagged the same way as external delays. The data isn't biased toward blaming external parties.
Can the contractor scorecard be exported for tendering decisions?
Yes. PDF export with the contractor's history across all your projects — useful for award meetings.
Does it support Extension of Time (EOT) claim documentation?
Yes. Client-attributable delays are tagged + timestamped from the delay event itself, building an evidence trail. When the contract claim cycle starts 3 months later, the data is already structured.
How does time-weighted stagnation differ from a 14-day flag?
Binary flags lose information: a milestone stuck 14 days and a milestone stuck 28 days look the same. Time-weighted severity scales linearly: 28-day stagnation has 2x the impact on health score.
Can I see only my projects, not the whole portfolio?
Yes. Role-based filtering means PMs see only their projects; Director-Projects sees the portfolio; Group CFO sees all entities. Multi-tenant by company_id.
Is this just another dashboard, or does it drive action?
Drives action. Dominant delay causes feed the daily Action Queue with specific milestones to unblock. The dashboard is a side-effect of the action engine, not the product itself.
Ready to stop running this in Excel?
Free Starter tier. Add your first 3 projects. See your Action Queue tomorrow morning.
Also relevant for: