Calculation guide

Project Margin Variance: Formula, Example and Causes

Calculate the change in dollars and percentage points, then move beyond the headline to the resource, rate, scope, and cost drivers underneath it.

Short answer

Project margin variance is the difference between two margin results calculated on a consistent basis. In dollars, subtract baseline margin from current margin. For margin rates, subtract the baseline percentage from the current percentage and report the result in percentage points. Reconcile revenue, included costs, scope, and cut-off dates before interpreting the difference.

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

Margin variance is the difference between the margin you planned and the margin you have now. You can show it in money (for example −USD 4,800) or as a change in the margin percentage (for example −4 percentage points). The number matters less than finding its cause: more hours, higher rates, a different team mix, extra costs or less revenue.

Who this helps: Project managers who explain their projects, finance analysts who prepare the numbers and leaders who read the reports.

Questions this guide answers:

  • What is the margin variance formula?
  • What causes project margin variance?
  • What happens to project margin when pay rates increase?
  • How do you explain a margin variance to a client or manager?

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 project is priced at USD 50,000 with planned cost of USD 20,000: planned margin USD 30,000, or 60%. Halfway through, 120 hours of rework at USD 50 add USD 6,000 of cost.

Planned and current margin
PlannedCurrent forecast
CostUSD 20,000USD 26,000
MarginUSD 30,000USD 24,000
Margin %60%48%
  • Variance in dollars: 24,000 − 30,000 = −USD 6,000.
  • Variance in percentage points: 48% − 60% = −12 points.

Project margin variance is the gap between the planned margin and the current one. A number is not enough: you must say what moved. On a project the usual causes are hours, the mix of senior and junior roles, rates and scope.

Which project margin variance formula should you use?

Use two related calculations because they answer different questions. Dollar variance shows the absolute economic change on the chosen basis. Percentage-point variance normalises that result against revenue. Do not call a move from 30% to 24% a "6% decline": it is a decline of 6 percentage points, or 20% relative to the original 30% rate.

Core formulas

Margin amount = revenue basis - included costs

Margin percentage = margin amount / revenue basis x 100

Dollar variance = current margin amount - baseline margin amount

Percentage-point variance = current margin % - baseline margin %

"Current" must have a precise meaning. It may be an actual-to-date calculation, a formally revised baseline, or a separately governed forecast. Those are not interchangeable. Managed Margin shows the actual to date and a forecast at completion as separate figures and reports variance in points against the baseline for each.

Worked example: a six-point margin change

A fixed-price project has an approved fee of USD 100,000 and a full-project cost baseline of USD 70,000, leaving USD 30,000 margin. A revised forecast identifies USD 6,000 of additional cost to complete the same scope. Forecast total cost is USD 76,000 and forecast margin is USD 24,000, or 24%. This example compares full-project baseline with forecast at completion; it assumes no fee change.

MeasureBaselineCurrent comparisonVariance
Revenue basisUSD 100,000USD 100,000USD 0
Included costUSD 70,000USD 76,000+USD 6,000
Margin amountUSD 30,000USD 24,000-USD 6,000
Margin percentage30%24%-6 percentage points

The headline is not the diagnosis. Suppose the USD 6,000 comprises USD 3,600 of additional senior hours, USD 1,400 of partner cost, and USD 1,000 of approved infrastructure cost. Reviewers can now separate an intentional technical intervention from an avoidable delivery issue and a client-approved requirement.

How do you explain project margin variance?

DriverEvidence to inspectQuestion to ask
Hours variancePlanned and actual hours for the same resource and periodWas the estimate wrong, was there rework, or did scope change?
Role-mix varianceHours transferred between roles with different cost ratesWas senior intervention deliberate and documented?
Rate varianceApplicable rate and effective dateDid staffing, location, shift, or pay policy change?
Non-labor costPartner, infrastructure, travel, or other supported itemsWas the cost planned, approved, and classified consistently?
Commercial changeApproved scope, fee, and baseline versionsShould the original baseline remain the comparison, or is a labelled rebaseline needed?

The Department of Energy's project-management lexicon defines cost variance within EVM as earned value minus actual cost. That is not the formula above. Calling both measures "cost variance" creates avoidable ambiguity, so label project-margin variance explicitly and keep formal EVM terminology for EVM calculations.

Choose the comparison pair before calculating

Baseline versus actual-to-date is useful for current observation only when both views cover a meaningful basis. Planned-to-date versus actual-to-date is better for explaining period performance. Original baseline versus authorized revised baseline explains a commercial or delivery decision. Forecast versus baseline is a different exercise because it requires the remaining plan and expected costs as well as actuals; do not label a forecast from actuals alone.

Also handle edge cases explicitly. If approved revenue is zero, a margin percentage cannot be calculated on that denominator. If the revenue basis changes, show the old and new basis as separate rows. If the baseline margin is negative, percentage-point variance remains arithmetically valid, but relative percentage-change language can become confusing and should be avoided.

Controls, limitations, and a review checklist

  1. State the baseline version, current version, and data cut-off.
  2. Confirm the revenue basis and time boundary on both sides. If an approved fee change changes the denominator, show that revenue effect separately from cost changes.
  3. Reconcile every included cost category and effective rate.
  4. Report percentage changes as percentage points when subtracting rates.
  5. Trace material changes to evidence rather than assigning a generic cause.
  6. Read cost and margin alongside progress and remaining scope.
Limitation

An actual-to-date margin variance does not include unrecorded future effort. It can show what has changed so far, but it cannot establish final profitability without a separate estimate-to-complete process.

For the full operating method, read planned versus actual project margin. If the key question is whether spend is ahead of progress, continue to budget consumption versus percent complete.

How Managed Margin handles the current comparison

In Managed Margin, approved timesheet hours are costed at each person’s actual hourly cost effective on the work date, when available, otherwise at the seat’s finalized planning rate, and posted expenses are added. Project financials show the variance in points and name the drivers in money. Project margin tracking software explains the workflow and visibility controls.

At the office: Lena explains a four-point drop

An illustrative story with invented figures, to show how the idea works in a real office.

Lena, a project manager, has a USD 120,000 project planned at a 28% margin, which is USD 33,600. On the latest forecast of the final cost it is at 24%, which is USD 28,800. The variance is −USD 4,800, or −4 percentage points.

She asks what changed. Revenue is the same. Hours are up: the team worked 100 extra hours at a cost of USD 48 an hour, and 100 x 48 is USD 4,800. The variance is entirely extra hours.

Her report says: “The margin is down four points because of 100 extra hours on the data mapping task. The client changed the format twice. If the contract entitles us to it, we will raise a change request for the added work; if not, we absorb it and say so.” She has named the number, the cause and the next step.

When do you explain margin variance, and who does it?

Explaining variance across the lifecycle
StepOwnerCheckpoint
DetectProject managerBaseline version, current version and data cut-off are stated
Break it downProject manager and financeHours, role mix, rate, scope and non-labor cost are separated
ExplainProject manager, with the delivery leadEach driver has evidence, not an assumption of “scope creep”
RespondDelivery head and account managerOperational or commercial action, with an owner and a date

Frequently asked questions

Which variance formula should I use?

Dollar variance for amounts and percentage points for rate changes, both on a consistent basis.

How do you explain variance?

Split it into hours, rate, role mix, non-labor cost and revenue effects, with evidence for each.

Is a negative variance always bad?

It is a signal. Check whether it comes from timing, scope change or real cost growth before acting.

What is the project margin variance formula?

Dollar variance = current (or forecast) margin amount minus planned margin amount. Percentage-point variance = current margin % minus planned margin %. For example, a USD 100,000 fee with planned cost USD 70,000 (30%) and USD 6,000 of extra cost to complete gives a variance of −USD 6,000 and −6 points (24%).

What happens to project margin when pay rates increase?

If the client fee stays fixed, a higher applicable employee-cost rate increases labor cost for the affected hours. For example, 200 remaining hours moving from USD 60 to USD 66 add 200 × (66 − 60) = USD 1,200. On an unchanged USD 40,000 full-project fee, that reduces forecast margin by 3 percentage points before any labor-linked charges.

Use the rate’s effective date: do not apply the increase to earlier hours unless that is the actual approved cost treatment. Add any associated labor-based cost changes, update the remaining forecast and keep the original baseline. Sales can understand the total cost effect without receiving a named employee’s pay record; see sharing margin with separate employee-cost permissions.

Sources and methodology

  • U.S. Department of Energy, Project Management Lexicon of Terms. Used to distinguish formal EVM cost variance and percent-complete terminology from project-margin calculations.
  • U.S. Department of Energy, Earned Value Management. Used for baseline, planned value, actual cost, and progress distinctions.
  • Product statements were reviewed against the current Managed Margin application on 26 September 2026. All figures are original educational examples.