Why project reporting is different
Reporting on a repeating product line is easy: you have a standard cost, a standard cycle time and months of history to compare against. A project is a one-off, so there is no catalogue baseline. The only reliable yardstick is the plan you authored for this project — its budget, dates and Bill of Resources — measured against what the work is actually doing. That is why good project reports are always comparisons: planned versus done, estimated versus actual, billed versus earned.
The trap most project businesses fall into is that the plan and the actuals live in different places — the budget in a quotation, progress in a site engineer's head, cost in an accounts ledger, billing in a third book — so any KPI stitched together from them is stale the moment it is typed. A reporting system earns its keep by making every metric a roll-up of live records, so the number and the reality behind it can never quietly diverge.
The seven reports every project team needs
Before the KPIs, you need the underlying reports that feed them. On a build-to-order project these seven cover scope, schedule, cost and cash between them.
| Report | Answers | Reads from |
|---|---|---|
| Project view report | Where does this whole project stand — tasks, progress %, dates, budget vs actual? | Project header + all its tasks |
| Task BOR report | What does one task consume — material, labour, machine — and at what planned cost? | Per-task Bill of Resources |
| Master BOR report | What is the total resource requirement across the whole project? | BOR rolled up across all tasks |
| Cost estimation | What is the estimated cost, and how does it compare to budget? | BOR quantity × rate vs budget |
| Resource report | What is in the machine, labour and tool pool, and at what rates? | Resource master |
| Project billing | What has been billed to the customer, by project, resource or milestone? | Project bill header + lines |
| Gantt view | How is the schedule sequenced, and where is it slipping? | Task bars + predecessor links |
These are not seven disconnected exports — they are seven windows onto one dataset. The project view reads the same task records the Gantt draws; cost estimation reads the same BOR lines the task BOR report itemises; the billing report claims against the same tasks the work was tracked on — so a discrepancy between two reports is a signal worth investigating, not a formatting difference.
The KPIs that actually predict trouble
Reports describe; KPIs warn. The metrics below are the ones that turn amber before a project visibly fails, which is the only time acting on them is cheap.
- Progress % — the roll-up of task completion into one project figure. On its own it is optimistic, so it is only trustworthy when paired with cost and schedule.
- Schedule variance — planned finish versus forecast finish, driven by task slippage flowing through predecessor dependencies.
- Cost variance — actual cost against estimated cost and against the original budget, ideally at task level so you can see which task is bleeding.
- CPI and SPI — the earned-value indices that normalise cost and schedule performance into ratios you can compare across projects of different sizes.
- Billed-to-date versus earned — how much has been invoiced against how much work is actually complete, so cash and progress stay in step; alongside resource utilisation across the portfolio.
Earned value made simple — PV, EV, AC
Earned value management (EVM) has a reputation for being complicated, but at its heart it is three numbers and two ratios. If your project already carries a budget and a progress percentage — which any real project system does — you have most of what EVM needs.
Work an example. A project has a budget (BAC) of ₹10,00,000. Halfway through the planned schedule, the plan expected 50% of the work done, so PV = ₹5,00,000. In reality the WBS is only 40% complete, so EV = 0.40 × 10,00,000 = ₹4,00,000. But delivering that 40% has already cost AC = ₹4,50,000 in issued material, labour and machine time. Three plain numbers, and already the story is clear: less has been earned than planned, and it cost more than it should have. INR figures here are indicative — confirm treatment with your CA.
SPI and CPI, and how to read them
The two ratios convert those numbers into performance you can compare across any project, large or small.
- SPI = EV ÷ PV. In the example, 4,00,000 ÷ 5,00,000 = 0.80. Below 1 means behind schedule — the project has earned only 80 paise of value for every rupee it planned to.
- CPI = EV ÷ AC. Here, 4,00,000 ÷ 4,50,000 = 0.89. Below 1 means over budget — each rupee spent bought only 89 paise of budgeted work.
- EAC = BAC ÷ CPI. 10,00,000 ÷ 0.89 ≈ ₹11,24,000 — the forecast final cost if today's cost efficiency holds, a ₹1,24,000 overrun (VAC).
The discipline is to watch SPI and CPI together. A project can sit at CPI 1.0 but SPI 0.8 — on budget but slipping, usually under-resourced; another shows SPI 1.1 but CPI 0.85 — ahead of time but burning cash, often crashed with overtime and hired machines. One index alone will always flatter or frighten you; the pair tells the truth. Read the pillar for how the plan these ratios measure is built: what is project management software.
Still assembling your project MIS from three different spreadsheets?
We can show you a live project — progress, estimated-vs-actual cost, BOR roll-up and a billing report — reconciled on one screen in 30 minutes.
Estimated-versus-actual, the practical KPI
Full EVM is powerful, but many project teams get most of the value from one simpler comparison done rigorously: estimated-versus-actual. Every project and task carries both a budget and an actual budget, and both a planned and an actual finish. When the estimate is built from the Bill of Resources and actuals are booked from real material issue and resource consumption, the gap between the two is the single most useful line in any project report. Because the BOR is itemised by resource group and code, that gap can be read at the resource line, the task or the whole project — the same number at three altitudes — which lets a review move from "we are over budget" to "the crane was on site nine days longer than the plan assumed."
One dataset, four questions answered in a single review
A fabrication shop runs its Monday review on a bespoke skid project. The project view report shows 62% progress against a plan that expected 70% — SPI under 1, so the schedule flags first. Cost estimation shows actual cost 8% above estimate, concentrated in one task's consumables line, so the team knows which purchase to interrogate. The billing report shows two milestones invoiced and a third due on dispatch, so cash is in step with earned value. And the resource-wise Gantt shows the welding bay double-booked next week, explaining the slip before it happens. Four questions — scope, cost, cash and cause — answered from one connected dataset rather than four arguments. This is the profile behind deployments such as Micro India and DVC Process.
Building a project MIS that stays honest
A management information system for projects is only as honest as its inputs: a dashboard fed from a Friday spreadsheet will always lag reality and always be argued with. The design principle is to make each metric a by-product of doing the work, not a separate reporting chore — captured in five moves.
How Fast Project Software reports each metric
Fast Project Software was built so that every report and KPI above is a roll-up of live records rather than a separate spreadsheet. Mapping the metrics to the product:
Because it runs on the shared Fast Suite platform, the reports draw on the same resource, item and party masters as the rest of the suite; material issued through Inventory & Procurement and bills posted to Fast Billing & Accounts feed the actuals automatically, with nothing re-keyed at a boundary. INR pricing is indicative; confirm the commercial and tax treatment with your CA. See pricing.
Frequently asked questions
What are the essential project management reports?
The core reports are a project view report (tasks, progress, dates and budget-versus-actual), task and master Bill of Resources reports that total the resource requirement, a cost-estimation report comparing estimated cost to budget, a resource report of the machine, labour and tool pool, a project billing report of what has been billed, and the Gantt as a live schedule dashboard. Together they answer where a project stands on scope, schedule and cost at any moment.
What are the most important project KPIs?
The KPIs that matter most are progress percentage, schedule variance against planned dates, cost variance of actual against estimated and budget, the cost and schedule performance indices (CPI and SPI), billed-to-date versus work done, and resource utilisation. Each should roll up from real task records rather than being typed into a separate dashboard, so the number and the work behind it never disagree.
What is earned value management (EVM) in simple terms?
EVM compares three numbers. Planned Value (PV) is the budgeted cost of the work that should be done by now. Earned Value (EV) is progress percentage multiplied by budget — the budgeted cost of the work actually completed. Actual Cost (AC) is what that work really cost. From these, SPI = EV / PV and CPI = EV / AC; an index above 1 means ahead of schedule or under budget, below 1 means behind or over. EVM turns a vague feeling of slippage into a defensible number.
How does Fast Project Software produce project reports and KPIs?
Every report is a roll-up of live records, not a re-keyed spreadsheet. The project and each task carry budget, actual budget, progress and dates; the per-task Bill of Resources prices material, labour and machine from a resource master; cost estimation totals the BOR against budget; and project billing records what has been billed. The project view, task BOR, master BOR, cost, resource and billing reports read straight from those records, and Dhruv AI adds dashboards and plain-English questions over the same data.