Project Cost & Margin Intelligence
Spot sustained cost and schedule pressure. Review the highest-risk projects first, then trace each flag to its monthly cost evidence.
Projects ranked for review
Longest qualifying streak first, then deepest average shortfall. Select a project to inspect its monthly evidence.
| Project name | Region | Latest CPI | Latest SPI | At-risk months | Why it needs review |
|---|
Definitions, scoring and validation
Amounts are summed by project and calendar month. CPI = earned value / actual cost. SPI = earned value / budgeted cost, a schedule proxy rather than a task-network measure. Ratios are calculated from unrounded totals, not averaged from source ratios. A missing month or unavailable ratio breaks a streak. Flags cover any qualifying streak in the supplied history, not only an ongoing streak in the latest month.
At-risk months count distinct months belonging to CPI or SPI streaks of at least two months, without double-counting overlaps. The ranking score is longest qualifying streak + its mean shortfall below 0.90 (less than 1); ties use project name. It is a rule-based priority score, not a probability or an estimated financial loss. Average CPI is the arithmetic mean of each project's latest monthly CPI.
“Model accuracy” is precision: confirmed flagged projects / all flagged projects. A project is confirmed if any of its source records has answer_key.is_margin_risk = Y. Labels are used only for validation, never for scoring. All 30 projects are positive under this definition, so this dataset cannot establish false-positive performance. This demo is not a trained ML model.
Source caveats: all workbook rows are retained, including accounting months outside project start/end dates. The source has only 1–2 cost-code records per project-month; it is not a complete project ledger. Monetary values are INR. Source CPI/SPI are rounded; this app recomputes project-month ratios from amounts.