Why overruns are silent
Project margins rarely vanish in one dramatic event. They leak — an extra week on erection here, more steel than planned there, a hired crane kept a fortnight longer than the schedule assumed. Each slip is small, and none of them announces itself. By the time the loss is obvious, the money is already spent and the schedule already blown. The overrun was not sudden; it was invisible.
It is invisible for a structural reason: in most project shops the plan and the actuals live in different places. The estimate sits in a quotation spreadsheet, material issue in a stores register, progress in the site engineer’s head, and cost in an accounts book that reconciles months later. Nothing compares the plan to reality in real time, so nothing raises a flag. The fix is not more reports — it is putting the budget and the actual on the same records, keyed to the same tasks, so the comparison is automatic.
Two things to track — money and time
“Budget vs actual” is usually said about money, but a project has two budgets that both overrun, and they feed each other. Track both.
| Axis | Planned figure | Actual figure | What the gap tells you |
|---|---|---|---|
| Cost | Budget (from the estimate) | Actual budget (real consumption) | Whether the job is making the margin you quoted |
| Schedule | Planned finish date | Actual finish date | Whether the job is running late — and racking up time-based cost |
| Progress | Planned % at this date | Actual progress % | Whether reported completion matches spend |
The two axes are linked. A task that slips its finish date usually keeps consuming labour and machine time, so a schedule overrun becomes a cost overrun. And progress is the honesty check between them: if a task is 40% complete but has consumed 70% of its budget, something is wrong regardless of what the finish date says. Every project and task carries a budget and an actual budget, a planned and an actual finish date, and a progress percentage — the three numbers that, read together, tell you whether a job is under control.
Where actual cost comes from
A budget-vs-actual view is only as good as the “actual” half. Estimates are easy to hold; actuals are where most systems fall down, because capturing them means connecting the plan to what really happened on the floor. Actual cost accrues from three sources, each keyed to the task:
- Material issued against the task. When stock is drawn from the store against a specific task, the planned Bill of Resources consumption becomes real material cost. This is the store-issue link covered in project material management.
- Labour and machine time booked to the task. Real man-hours and machine-hours, priced from the resource master, turn planned effort into actual cost.
- Progress and status updates. Progress %, dated task logs and status changes record where the work has actually reached, so completion can be read against spend.
Because all three post to the same task the estimate was built on, the actual accumulates right next to the budget — no reconciliation, no re-keying. That is the difference between a system that shows you the overrun and a stack of spreadsheets that explains it afterwards.
The report project owners actually run
Ask a project owner which report they open first and it is not the Gantt — it is budget vs actual. A good project view report lays each task’s budget beside its actual, its planned finish beside its actual finish, and its progress %, so the whole project’s health is one screen. The tasks that matter jump out: the one 80% through its budget at 50% progress, the one already past its planned finish, the one quietly consuming a machine it was not supposed to need.
Rolled up, those task figures become the project’s position: estimated cost versus actual cost to date, planned versus actual completion. Dhruv AI can layer plain-English questions and insight summaries on top — “which tasks are over budget?” — through a safe read-only query sandbox, and WhatsApp, email and SMS alerts can push a warning when a task crosses a threshold, so the owner does not have to be watching the screen to catch the slip.
See budget vs actual on a live project
We can show you each task’s budget beside its real consumption and its progress % — the exact view that catches an overrun early — in a 30-minute demo on your own job.
Catching the slip early
Seeing the variance is only useful if you can act on it, and acting early is worth far more than acting accurately-but-late. When a task shows its budget draining faster than its progress, the levers are still available: re-sequence the work on the Gantt, move a resource, tighten scope, or flag a variation to the customer. When the same signal arrives at handover, all you can do is absorb the loss. The value of live budget-vs-actual is measured in the weeks of warning it buys.
It also compounds across projects. A shop that reviews estimated-versus-actual on every finished job learns which tasks it habitually underestimates, and folds that back into the next estimate. The variance report is not just a control on today’s project — it is the feedback loop that makes tomorrow’s quote sharper.
How Fast Project Software tracks budget vs actual
Fast Project Software holds a budget and an actual budget, a planned and an actual finish date, and a progress percentage on every project and every task — so budget-versus-actual is built in, not bolted on. Material issued against a task through Inventory & Procurement, labour and machine time priced from the resource master, and dated task logs all post to the same task the estimate was built on, so the actual accrues beside the plan. The project view report lays it out task by task, Dhruv AI answers cost-versus-budget questions in plain English, and alerts push warnings when a task crosses a threshold. It serves ETO, fabrication, EPC and construction teams; pricing is indicative and in INR — see pricing.
Frequently asked questions
How do you track budget vs actual on a project?
Track budget vs actual by holding both figures on the same task-keyed records. The budget comes from the cost estimate; the actual accrues from material issued against the task, labour and machine time booked to it, and progress updates. Because both numbers hang off the same task, the variance is computed automatically rather than reconciled at month-end. Track it on two axes — cost (budget vs actual budget) and schedule (planned vs actual finish date) — with progress percent as the honesty check between them.
Why do project cost overruns stay hidden until it is too late?
Overruns leak in small increments — an extra week, more material, a machine hired longer — and none announces itself. They stay hidden because the plan and the actuals usually live in different systems: the estimate in a quotation sheet, material in a stores register, progress in someone's head, cost in an accounts book that reconciles months later. With nothing comparing plan to reality in real time, the trend is only visible after the money is spent. Putting budget and actual on the same task makes the trend visible while you can still act.
What actual figures should a project track?
Track actual cost and actual schedule against their planned counterparts. Actual cost accrues from three sources keyed to each task: material issued from stores against the task, labour and machine hours booked to it, and the progress and status updates that record where the work has reached. Actual schedule is the real finish date against the planned one. Read alongside progress percent, these tell you whether reported completion matches the money and time already spent.
What is the difference between budget and actual budget on a task?
The budget is the planned cost of the task, set from the estimate before work starts. The actual budget is the real cost the task has consumed as work proceeds — the material issued, and the labour and machine time booked, against it. Holding both on the same task lets you read the variance directly: a task 80% through its budget at 50% progress is a warning you can see immediately, rather than a loss you discover at handover.
How early can budget-vs-actual tracking catch an overrun?
As early as the data is captured. When material issue, labour and machine booking and progress updates post live against each task, a task whose budget is draining faster than its progress shows the warning while the levers are still available — re-sequencing work, moving a resource, tightening scope, or flagging a variation to the customer. The same signal at handover only lets you absorb the loss, so the value of live tracking is the weeks of warning it buys.