Planned-versus-actual margin compares an approved baseline with delivery evidence. Align scope, cost categories and period, but retain actual effective rates so rate variance remains visible. Use recognized revenue for the actual-to-date view and the full remaining-cost forecast for a completion comparison.
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
Planned margin is what the project should earn according to the approved plan. Actual margin is what it has earned so far from recorded hours and costs. Comparing them only makes sense if both use the same cost rules, the same project boundary and the same cut-off date. The rates themselves can differ: the plan uses the approved planning rates, while actuals show the rates that were really paid, and that difference is one of the things the comparison explains.
Who this helps: Project managers, analysts and managers who compare project results with plans.
Questions this guide answers:
- What is planned versus actual margin?
- How do you compare planned and actual project cost?
- What does an actual-to-date margin tell you?
Margin words: gross, contribution, managed margin, budget, forecast and the roles named here are defined once in the margin vocabulary.
Start with a four-week project
A project is sold for USD 40,000. The plan (the baseline) is 700 hours at USD 40, so planned cost is USD 28,000 and planned margin is USD 12,000, or 30%.
| Plan says | Actual is | |
|---|---|---|
| Hours and cost to date | 350 hours, USD 14,000 | 400 hours, USD 16,000 |
| Work completed | 50% | 40% |
- Cost is USD 2,000 ahead of plan.
- Progress is 10 points behind plan.
A rough straight-line check: 400 hours for 40% of the work means about 1,000 hours for all of it, or USD 40,000 of cost, which would leave no margin at all. That is not a prediction, only the reason to look closely now. Planned versus actual margin is this check, done every week: what did we plan, what is the real position, and how much of the work is done?
What exactly should planned and actual mean?
A useful comparison begins with definitions. Full-project planned margin uses the agreed fee less all included planned costs. Actual-to-date margin uses recognized revenue and included actual costs for the same period. Forecast margin uses expected total revenue and actual-plus-remaining costs. Divide each margin amount by its own matching revenue, then multiply by 100. Label the view and cut-off before comparing percentages.
The U.S. Department of Energy describes Earned Value Management as a method that integrates scope, cost, and schedule against an approved baseline. Its guidance also warns that comparing planned and actual cost without measuring physical progress can be misleading. That principle is useful here, but a project-margin comparison is not automatically a formal EVM calculation. Managed Margin does not calculate earned value; its forecast at completion is cost to date plus the remaining plan and expected costs, not an EVM estimate.
Margin asks what remains after included costs. Cost variance asks how actual cost compares with the relevant plan. Progress asks how much agreed work has been completed. The measures inform one another, but one cannot safely stand in for the others.
A six-step planned-versus-actual method
1. Preserve an approved baseline
Store the contract value, scope and exclusions, resource plan, hours by period, cost rates, non-labor costs, shared-cost policy, and approval date. Preserve the original rather than overwriting it when delivery changes. An authorized rebaseline can be useful, but it should have its own effective date and reason.
2. Establish the cut-off and owner
Choose the date through which actuals must be complete and name the person responsible for the update. A calculation made on Monday with Friday's hours missing is not directly comparable with one made after the week is closed. The review record should therefore show both the data cut-off and review date.
3. Capture actuals at useful detail
Record hours by resource and period, plus supported partner, infrastructure, travel, or other costs included by policy. Detail matters because equal total hours can have different costs when role mix or effective pay rates differ. Correct input errors before discussing operational performance.
4. Reconcile the calculation basis
Confirm that planned and actual views use the same commercial value and cost categories. If a scope change, approved price adjustment, or cost-policy change affects the basis, show it explicitly. A five-point margin difference built from two different denominators is not an operational variance until the bases are reconciled.
5. Trace the variance to drivers
Start with hours by resource and period, then test rate changes, team mix, non-labor cost, rework, delay, dependencies, and approved scope changes. Labels such as "delivery issue" or "scope creep" are conclusions, not evidence. Record the specific cause that the available data supports.
6. Decide and document
A review should end with a decision: accept an intentional variance, correct data, change the delivery plan, initiate a commercial scope process, or investigate further. Assign an owner and date. A dashboard can identify a signal; accountability remains a management task.
Worked example: the same hours can hide a different cost
A fixed-price project has an approved value of USD 120,000. The full-project baseline includes USD 78,000 of cost, so planned margin is USD 42,000, or 35%. At the end of week six, compare the planned and recorded labor for those same six weeks. This period view explains a current driver; it does not estimate the cost still required to finish.
| Role and hourly cost | Planned hours to date | Actual hours to date | Planned cost | Actual cost |
|---|---|---|---|---|
| Lead consultant, USD 100 | 120 | 150 | USD 12,000 | USD 15,000 |
| Consultant, USD 65 | 240 | 225 | USD 15,600 | USD 14,625 |
| Analyst, USD 40 | 240 | 225 | USD 9,600 | USD 9,000 |
| Total | 600 | 600 | USD 37,200 | USD 38,625 |
Hours variance = 600 - 600 = 0 hours
Labor-cost variance = USD 38,625 - USD 37,200 = +USD 1,425
Total hours are exactly on plan, yet labor cost is USD 1,425 higher because 30 lead-consultant hours replaced lower-cost effort. That may be justified by risk or quality needs. The calculation reveals the trade-off; it does not judge the decision. Reviewers should ask why the mix changed, whether the remaining plan reflects the new delivery need, and whether a client-approved scope decision exists.
How should the result be interpreted?
| Observation | What it can support | What it cannot prove |
|---|---|---|
| Actual hours exceed planned hours for the same period | A specific effort variance that needs explanation. | That the final project will overrun. |
| Cost rises faster than hours | Review of rate, role mix, shift, or cost-category changes. | That a higher-cost resource was unnecessary. |
| Budget consumption exceeds reported completion | A prompt to examine timing, rework, scope, and remaining effort. | Formal earned-value performance unless EV rules are actually used. |
| Current margin is below planned margin | Reconciliation of the current calculation and its drivers. | A forecast of final margin, as noted in the short answer above. |
The worked example holds total hours constant while shifting work to a higher-cost role. That mix change raises cost without adding fee. Compare the actual cost effect with the baseline; extra hours are a separate possible driver explained in the fixed-price extra-hours guide.
When should the baseline change?
Do not rewrite the approved plan merely because actual performance differs. That removes the reference needed to learn from the variance. A new baseline is more defensible when an authorized commercial or delivery decision changes the work that the project is now expected to perform. Preserve the original, label the revised version, record the approval and effective date, and explain which future periods changed.
For example, assume the client approves a USD 20,000 extension with 240 additional planned hours. Review historical delivery against the baseline that governed those periods. Use the revised, labelled baseline for the new work from its effective date. Management can then see both the original variance and the economics of the approved change instead of blending them into an unexplained percentage.
A reviewer should be able to reproduce the original plan, identify every authorized revision, and state which version is being used in the current comparison. If that cannot be done, resolve the baseline before interpreting margin variance.
How this plays out during a multi-phase software implementation
Consider a 35-person IT consultancy delivering a three-phase CRM implementation for a mid-size distributor: a foundation phase, a workflow-automation phase, and a reporting phase, each priced and approved separately. Applying the six-step method above looks different at each stage of that delivery.
- At phase-1 kickoff. The team is eager to start logging hours before the approved baseline—roles, hours, rates, and scope—is actually locked for that phase. Without step 1 above, the first weekly comparison has nothing stable to compare against. Preserve the phase-1 baseline, with its own owner and approval date, before any actual hours are recorded.
- Mid-phase 1, when an integration breaks. A senior architect burns extra hours resolving an unplanned issue with the client's ERP connector while a junior analyst's planned hours go unused. Total hours can stay close to plan while the role mix—and therefore labor cost—moves, exactly as in the worked example above. Trace the variance to the driver instead of stopping at the aggregate hours figure.
- When the client adds scope mid-phase. A request for extra reporting fields arrives after phase 1 is underway. Blending it into the existing baseline hides both the original variance and the economics of the addition. Treat it as an authorized rebaseline with its own effective date, as described above.
- At phase-2 kickoff. It is tempting to carry the phase-1 team and rates forward unchanged. If a consultant's role or rate has changed since phase 1 was approved, that assumption is now wrong. Re-run the baseline steps for phase 2 rather than copying phase 1's numbers.
- At the monthly portfolio review. A sponsor wants one margin figure across all three phases. That is only meaningful once each phase's calculation basis is reconciled—same revenue and cost definitions, same treatment of the phase-1.5 change—so a single blended percentage does not hide which phase is actually off plan. The professional-services project margin guide covers how this fits into the wider proposal-to-delivery workflow.
Limitations and control checklist
- Actuals can be incomplete, late, incorrectly classified, or entered at the wrong effective rate.
- A baseline can become irrelevant after an approved commercial change unless versions remain visible.
- Actual-to-date cost says nothing by itself about the effort still required to finish.
- Budget consumption is not percent complete, and manually supplied completion is not earned value.
- Margin definitions vary, so cross-project comparisons require a common revenue and cost policy.
Before publishing a result, confirm the cut-off, completeness, baseline version, denominator, included costs, and owner of each material explanation, and keep forecast language out of the summary as noted above.
How Managed Margin applies the method
Managed Margin carries the finalized pricing strategy into delivery as seats filled by named people. Weekly timesheets are recorded and approved, expenses are posted, and project financials show baseline, actual to date and forecast at completion side by side. People and pay can be synced from BambooHR; timesheets are not imported. Explore project margin tracking software.
- How to Calculate Project Margin (Formula + Example)
- Project Budget Consumption: Formula and What It Tells You
- Project Baseline Handoff: From Sales to Delivery
- How to Manage Fixed-Fee Project Margins in Consulting
- What Is Managed Margin? Meaning, Formula and Software
At the office: Tariq builds the comparison
An illustrative story with invented figures, to show how the idea works in a real office.
Tariq, a project analyst, compares a project with a USD 80,000 fee. The plan assumed USD 56,000 of cost, a 30% margin. At the end of May the project is 50% through its plan, so planned cost to date is USD 28,000 (half of 56,000). Recorded cost is USD 30,000.
He first checks the basis. The plan used the approved rate of USD 60 an hour, but some actual hours were recorded at USD 65 for a different grade. He restates them at the plan rate to see the pure effort difference, then at actual rates to see the rate effect.
The comparison shows USD 1,200 from extra hours and USD 800 from rate differences. Tariq reports each separately, because the fixes are different.
Who compares planned and actual margin, and when?
| Stage | Owner | Checkpoint |
|---|---|---|
| Preserve the baseline | Project manager | Contract value, scope, resource plan, hours, rates and approval date are stored unchanged |
| Record actuals | Team and project manager | Hours and costs are entered weekly, classified the same way as the plan |
| Compare | Project manager or delivery lead | Hours by role first, then cost, then margin |
| Decide | Delivery head and account manager | Variance gets an owner, a response and a review date |
| Close out | Finance and project manager | Final figures replace the forecast |
Frequently asked questions
How should I interpret the result?
Look at drivers first (hours, rates, mix, non-labor), then the margin. Treat actual-to-date as a position and forecast separately.
How does this relate to margin variance?
Variance is the difference; this guide is how you build the comparison. See the margin variance guide for reading it.
What is planned versus actual project margin?
It compares the margin the project was priced to earn (the plan, frozen at approval) with the margin it is really earning from recorded revenue and costs. Reviewing it weekly shows a problem while it can still be fixed.
Continue the sequence: guides to read next
- Project Margin Variance: Formula, Example and Causes: explaining the gap
- Why Extra Hours Reduce Margin on a Fixed-Price Project: why every extra hour comes straight off fixed-price margin
- Project Margin Management: What It Is and How to Do It: the project margin management cycle from price to review
- Weekly Project Margin Review: Checklist and Actions: a weekly planned-versus-actual margin review
- Budget Consumption vs Percent Complete: Reading Both: why budget used and work complete are different measures
Sources and methodology
- U.S. Department of Energy, Earned Value Management. Used for the distinctions among planned value, earned value, actual cost, baseline, and progress. This article does not claim that Managed Margin implements formal EVM.
- U.S. Government Accountability Office, Cost Estimating and Assessment Guide. Used as an authoritative reference on cost estimates and managing cost through a project's life cycle.
- Product statements were reviewed against the current Managed Margin application on 26 September 2026. All figures are original educational examples, not customer results or benchmarks.