Budget consumption measures how much of a defined cost budget has been used. Percent complete estimates how much agreed work has been completed. They require different inputs and should not be substituted for one another. A gap is a review signal, not proof of an overrun, because timing, work mix, procurement, rework, or progress-measurement rules may explain it.
Terms used in this guide. fee: the amount charged to the client; cost: the expense included in the stated project model; margin: revenue left after the included costs; margin percentage = that amount / revenue × 100; baseline: the approved original plan kept for comparison.
In plain words
Budget consumption tells you how much of the budget has been spent. Percent complete tells you how much of the work is done. They are two different questions, and a project can be 68% through its money while only 55% through its work. The gap is not proof of trouble, but it is the first place to look.
Who this helps: Project managers and team leads who write status reports, and finance partners who read them.
Questions this guide answers:
- What is the difference between budget consumption and percent complete?
- What does it mean when spending is ahead of progress?
- How do you check whether a project is on budget?
Margin words: gross, contribution, managed margin, budget, forecast and the roles named here are defined once in the margin vocabulary.
Start with a small example
A CRM rollout has a cost budget of USD 100,000. The team has spent USD 68,000 (68% of the budget consumed). The 100 planned work items are treated as equal in size for this example, and 55 have been accepted by the client (55% complete). With work items of different sizes you would weight them by planned effort or use milestones instead.
- Budget consumption answers a money question: how much of the budget is gone?
- Percent complete answers a delivery question: how much of the work is finished?
The two numbers only make sense together. Here spending is 13 points ahead of progress. A rough straight-line check says that if the remaining work costs the same per item as the work so far, finishing needs about 68,000 ÷ 0.55 = USD 123,636, which is USD 23,636 over budget. That is an illustration under strong assumptions (equal items, an unchanged mix of work, no early purchases), not an estimate at completion. It is a reason to find out why, not an answer.
What does each measure answer?
Budget consumption answers a financial question: how much supported cost has been recorded relative to a chosen budget? Percent complete answers a delivery question: how much of the defined work is complete? The denominator and evidence must be named for both figures.
Budget consumption = actual costs recorded to date / defined cost budget x 100
Percent complete = completed work / total defined work x 100
The second expression is conceptual unless the project has a governed method for valuing completed work. Counting completed tasks equally may misstate progress when tasks differ greatly in size. A milestone-weighted, quantity-based, or formal earned-value method can be more defensible if the rules and evidence fit the work.
How formal earned value differs
In EVM, the Department of Energy defines earned value as completed work expressed in budgeted-cost terms and actual cost as the amount spent for work performed. Formal percent complete is therefore tied to earned value and budget at completion, not merely a project manager's subjective estimate. A services dashboard that shows a manually entered completion percentage is providing useful context, but it is not automatically an EVM system.
In Managed Margin, cost to date comes from approved timesheet hours and posted expenses, shown per cost category beside the estimate and expected total. Progress context is recorded by the team. The application does not calculate earned value.
Worked example: 68% consumed and 55% complete
A project has a USD 90,000 deliverable budget for the supported consumption measure. By the review cut-off, it has USD 61,200 of applicable recorded cost. The delivery owner reports 55% complete under the team's stated milestone method.
| Input or result | Value | What it means |
|---|---|---|
| Defined deliverable budget | USD 90,000 | The denominator for this consumption measure. |
| Supported actual cost to date | USD 61,200 | Labor and included actual cost through the cut-off. |
| Budget consumption | 68% | USD 61,200 / USD 90,000. |
| Reported completion | 55% | Progress under the stated milestone method. |
| Simple gap | 13 percentage points | A signal to investigate, not a forecast. |
The project has consumed budget faster than its reported progress. Possible explanations include intentionally senior-heavy discovery, an early software purchase, rework, delayed client decisions, additional scope, or an optimistic completion assessment. The gap does not tell reviewers which explanation is true, and it does not calculate the final cost.
What should reviewers ask when the figures diverge?
| Check | Question | Evidence |
|---|---|---|
| Cut-off | Do cost and progress cover the same date? | Timesheet close, invoice accrual policy, progress-status date. |
| Denominator | Which costs does the budget include? | Approved baseline and documented exclusions. |
| Progress method | How was completion determined? | Milestones, accepted quantities, or documented weights. |
| Timing | Did an early cost purchase support later work? | Purchase order, service period, and delivery schedule. |
| Delivery | Was effort spent on rework or blocked work? | Issue log, change record, and resource-level hours. |
| Scope | Has approved work or price changed? | Signed change and labelled baseline version. |
DOE guidance for formal project analysis emphasises current, accurate, complete, repeatable, and auditable data, and describes triggered metrics as reasons to investigate rather than automatic evidence of failure. The same discipline improves a lighter services review even when the organization is not using EVM.
What if completion is ahead of consumption?
The opposite gap also needs investigation. Using the same USD 90,000 deliverable budget as the worked example above, suppose the project instead has USD 43,200 of recorded cost by the review cut-off, and the delivery owner reports 65% complete.
| Input or result | Value | What it means |
|---|---|---|
| Defined deliverable budget | USD 90,000 | Same denominator as the worked example above. |
| Supported actual cost to date | USD 43,200 | Labor and included actual cost through this cut-off. |
| Budget consumption | 48% | USD 43,200 / USD 90,000. |
| Reported completion | 65% | Progress under the same stated milestone method. |
| Simple gap | 17 percentage points | Still a signal to investigate, not proof of an underrun. |
The team may have delivered efficiently, but cost entries may also be late, an invoice may be missing, early milestones may be overweighted, or lower-cost work may happen first. Do not declare an underrun until the cut-off, accrual treatment, progress method, and remaining work have been checked.
How does this play out on a multi-site infrastructure rollout?
Consider a professional-services firm deploying network switches, access points, and workstations across 40 branch sites for a client, priced against a defined cost budget and tracked site by site. The two measures above diverge in specific, predictable ways at different stages of a rollout like this.
- At kickoff, sites vary enormously in size — a 5-user branch and a 200-user regional hub both count as "one site." Counting completed sites equally overstates progress once the small sites are done first. Handling: use the milestone-weighted or quantity-based progress method described above, weighted by site size or connected-device count, not a simple site count.
- Mid-rollout, the team buys hardware for the remaining sites in one bulk order to secure a vendor discount, so consumed budget jumps to 70% while only 40% of sites are actually deployed. Handling: this is the "Timing" check from the review-questions table above — confirm the early purchase supports later work before treating the gap as an overrun, and track it the way a margin variance review would.
- At a scope change, the client adds 10 more branch sites partway through. If the cost budget is revised but the site count used for percent complete is not, every subsequent report looks like a growing overrun that scope caused, not spend. Handling: apply the "Scope" check above — update both denominators from the same signed change record, at the same time.
- At monthly review, field technicians report some sites "90% done" before formal acceptance testing has run. Handling: the "Progress method" check calls for accepted quantities as evidence, not a technician's verbal estimate — do not let self-reported completion outrun what has actually passed sign-off.
- At project close, the last few sites are cost-complete but stuck waiting on client-side scheduling for final acceptance, so spend hits 100% while reported completion lags for weeks. Handling: the "Delivery" check applies here too — document the block explicitly rather than forcing a site to 100% complete to close the file early.
In every case, the gap between the two measures is the same kind of signal described above: a reason to ask a specific question, not a verdict on the rollout.
Limitations and safe interpretation
- A percentage is only as reliable as its cut-off, cost coverage, and progress method.
- Actual cost can lag work when invoices or cost entries arrive later.
- Progress can lag spending when costs are incurred before related work is completed.
- A manually supplied completion estimate is not earned value unless a formal EV method supports it.
- Neither measure estimates remaining effort or final project margin.
Use the comparison to create a better question, then test that question against source records and the remaining plan. For the broader method, read planned versus actual project margin. To turn the finding into a repeatable operating process, see the project margin review cadence guide.
At the office: Mei reads two numbers at once
An illustrative story with invented figures, to show how the idea works in a real office.
Mei, a project manager on a CRM rollout, has a USD 150,000 budget. Her report shows USD 96,000 spent: 64% consumed. Her team lead says the work is about 50% complete.
A manager asks, “Are we over budget?” Mei answers, “Not yet, but spending is fourteen points ahead of progress, and I want to know why.” She checks and finds USD 9,000 of equipment was bought early, which explains part of the gap, and two tasks took longer than planned, which explains the rest.
Her report lists both causes and the action for each. A single number, 64%, would have either alarmed everyone or told them nothing.
Who compares the two measures, and when?
| Step | Owner | Checkpoint |
|---|---|---|
| Define progress | Delivery lead | One method for percent complete is agreed (for example, by milestones) |
| Fix the cut-off | Project manager and finance | Cost and progress cover the same date |
| Compare | Project manager | Gap between consumption and complete is calculated |
| Explain the gap | Project manager | Late invoices, rework, a rate change or a mismatch in method |
Frequently asked questions
Is a gap always a problem?
No. It is a prompt to ask why. Many gaps close when delayed work is completed or timing differences reverse.
Which is more reliable, consumption or percent complete?
Check the evidence behind both measures. Posted costs can lag the work, while accepted deliverables can provide objective completion evidence. Reconcile the cut-off, missing costs and completion criteria before interpreting a gap.
How do these relate to margin?
Spending ahead of measured progress is a review trigger, not a final-margin forecast. Estimate the remaining work and costs, reconcile timing differences and compare forecast total cost with the agreed fee before drawing a margin conclusion.
What is the difference between budget consumption and percent complete?
Budget consumption says how much of the cost budget is spent. Percent complete says how much of the work is finished. If 68% of the budget is spent but only 55% of the work is done, the project is spending faster than it is delivering.
What is the difference between a cost budget and a fee?
A cost budget is what the firm approves to spend delivering the work. The fee is what the client pays. The margin is the difference, so a project can use 100% of its cost budget and still make money if the budget was set below the fee.
- How to Manage Fixed-Fee Project Margins in Consulting
- Project Baseline Handoff: From Sales to Delivery
- Weekly Project Margin Review: Checklist and Actions
Continue the sequence: guides to read next
- Project Budget Consumption: Formula and What It Tells You: the formula for the consumption side
- Project Margin Variance: Formula, Example and Causes: what to do when the gap appears
- Planned vs Actual Project Margin: turning the comparison into a margin view
- Project Margin Review Cadence: how often to check the gap
Sources and methodology
- U.S. Department of Energy, Earned Value Management. Used for the definitions of planned value, earned value, actual cost, baseline, and the warning against reading cost without progress.
- U.S. Department of Energy, Earned Value Management System and Project Analysis Standard Operating Procedure. Used for data-quality and investigation principles in a formal EVM context.
- Managed Margin's cost-to-date workflow was reviewed against the current Managed Margin application on 26 September 2026. The worked example is original and illustrative.