Fixed-price project margin is the fixed project revenue less the delivery costs included by the firm. Because extra delivery effort does not automatically increase the agreed price, margin falls when hours, rates, or other costs exceed the approved assumptions. Protect it with defined scope, a costed resource baseline, periodic actuals, and explicit change decisions.
In plain words
In a fixed-price project the client pays an agreed amount no matter how many hours the work takes. So if the team needs more hours than planned, the extra cost comes straight out of your margin. Protecting margin means agreeing the scope clearly, keeping a plan to compare against and pricing any change to the work.
Who this helps: Project managers, delivery leads and sales managers who sign or run fixed-price work.
Questions this guide answers:
- How do you protect margin on a fixed-price project?
- Why do fixed-price projects lose money?
- What is margin on a fixed-fee consulting project?
Why is fixed-price margin exposed to extra delivery effort?
In a fixed-price arrangement, the client receives price certainty for a defined scope. The January 2026 UK government pricing guidance states that fixed price depends on fixed scope and transfers delivery risk for the defined service to the supplier. Although public procurement contracts can be more complex than a consulting engagement, the central relationship still applies: if the revenue basis stays fixed while supplier cost rises, supplier margin falls.
Project margin = agreed fixed revenue − included delivery costs
Project margin % = project margin ÷ agreed fixed revenue × 100
This does not mean every unfavourable difference is scope creep. A variance can come from an underestimated task, a more senior role performing the work, a rate change, rework, an approved scope change without a corresponding commercial change, or an unplanned direct cost. The review should identify the driver rather than assign a label first.
Example: baseline, actual and forecast margin on a fixed-price IT project
Assume a USD 100,000 fixed-price engagement with USD 60,000 planned labor and USD 10,000 other included cost. Baseline margin is USD 30,000, or 30%.
At review, forecast total labor is USD 72,000, including work already done and the remaining plan. With unchanged USD 10,000 other cost, forecast total cost is USD 82,000 and forecast-at-completion margin is (100,000 − 82,000) / 100,000 = 18%. The deterioration is USD 12,000, or 12 percentage points. Inspect role effort, substitutions and effective rates to explain it.
This is a completion forecast, not actual-to-date margin. For example, if recognized revenue to date is USD 40,000 and recorded cost for that period is USD 32,000, actual-to-date margin is 20%. Both views are useful: one measures the recorded position, the other includes the remaining work. A forecast is only as complete as those inputs.
What controls protect margin on a fixed-fee project?
Margin on a fixed-fee job is protected by a handful of habits, each with a named owner. A project manager is accountable for most of them after handover; presales and finance own the rest before it.
| Control | Owner | When | Checkpoint |
|---|---|---|---|
| Define scope before pricing | Presales lead | Before the quote | Deliverables, assumptions, exclusions, acceptance and change mechanism are written |
| Cost the proposed team | Presales consultant | Before the quote | Roles, rates, allocation, duration and material non-labor costs are preserved |
| Check delivery feasibility | Delivery lead | Before approval | The cheapest mix is rejected if it cannot deliver |
| Approve one baseline | Final approver | At sign-off | The original budget and resources stay identifiable afterwards |
| Record actual effort by period | Project manager | Weekly | Same roles and time units as the plan |
| Compare progress with budget use | Project manager | Monthly | Budget used is not mistaken for scope completed |
| Record changes explicitly | Project manager and account manager | At each request | The baseline is never erased to hide a variance |
| Assign a decision owner | Delivery head | At each review | Every material variance has an operational or commercial response |
Scenario: the monthly margin review
Using the earlier example (USD 100,000 fee, USD 60,000 planned labor, USD 10,000 other cost, baseline margin 30%), the project manager runs the review in four steps.
- Read the forecast. Forecast labor is USD 72,000 (work done plus the remaining plan), so forecast margin is (100,000 − 82,000) ÷ 100,000 = 18%.
- Find the driver. Hours by role show 150 extra hours of senior review at USD 80 an hour (USD 12,000): the analysts’ output needed more checking than planned.
- Write the decision record. Affected role: senior consultant. Plan value, current value, likely driver, owner and response date.
- Choose the response. Operational (change the remaining role mix) or commercial (raise a change request if the client caused the work).
The project manager reports the planned-versus-actual position; she does not wait for the margin to hit zero. PMI’s fixed-price project case study stresses the same principles: defined scope, a project baseline, progress assessment and captured actual cost. Managed Margin does not claim formal earned-value forecasting; it supports the planned-versus-actual comparison.
How does Managed Margin handle fixed-price work?
Managed Margin prices each service order from resource profiles and planning rates on a weekly or monthly loading grid, applies your cost rules (for example sales commission, delivery management, contingency and corporate overhead) and shows gross delivery margin, contribution margin and margin after all costs. For a fixed-price service order the quoted price is the revenue basis, so you can compare several staffing and price options before one is chosen.
Finalizing one pricing strategy makes it the approved pricing baseline — the agreed plan — with each line’s planning rate kept as a snapshot. Other strategies stay saved. After the work is won, handover records the client’s purchase order, signed agreement or an approved exception, and delivery accepts it. Delivery turns the finalized plan into seats, names the people who fill them, records weekly timesheets (entered by the project manager and then approved), posts expenses and applies approved change requests without overwriting the baseline.
Project financials then show the baseline, actual to date and forecast at completion side by side. Actual to date uses approved time, posted costs and, for fixed price, the revenue finance has recognized; the forecast adds the remaining allocations and expected costs. Both are calculations on recorded data, not AI predictions. On fixed-price work, actual-to-date margin appears once finance records the revenue recognized so far, because hours alone do not establish earned revenue. Learn how the approved pricing baseline moves into delivery, or see track fixed-price project margin during delivery.
- How a Discount Affects Project Margin: Formula and Example
- Budget Consumption vs Percent Complete: Reading Both
- Project Budget Consumption: Formula and What It Tells You
- Profit vs Cash Flow on a Project: How Payment Terms Matter
- Project Margin Review Cadence
- From ROM to Fixed Price: What Evidence You Need First
- How Much Contingency to Add to a Project Estimate
Real example: a delivery lead spots a fixed-price problem early
An illustrative story with invented figures, to show how the idea works in a real office.
Dev, a delivery lead, runs a USD 150,000 fixed-price project planned at a 30% margin, so planned cost is USD 105,000. At the halfway review the team has used 60% of the planned hours with 45% of the work done.
If the team keeps working at this pace, the project would need about a third more hours than planned (60 ÷ 45). Dev works out a rough effect, assuming progress stays at this pace and all of the planned cost moves with hours: cost would rise by roughly USD 35,000 to USD 140,000, which would take the margin from 30% to about 7% (150,000 − 140,000 = 10,000, or 6.7%). He treats this as a warning, not a forecast: he asks the team for an estimate of the remaining work, and he raises it that day, not at the end.
The team finds that the client asked for two extra rounds of approvals and a new test environment, none of it in the plan. Dev prices them as a change request. The client agrees to pay USD 25,000 for them. The fee becomes USD 175,000, and the margin lands at 20% instead of 7%.
When do you protect fixed-price margin, and what comes before and after?
| Stage | Owner | Checkpoint |
|---|---|---|
| Propose | Presales lead | Scope, exclusions and change mechanism are in the proposal |
| Hand over | Project manager receiving the deal | Baseline, role plan and assumptions are accepted |
| Deliver | Project manager | Weekly effort and monthly margin review are on the calendar |
| Change | Account manager and project manager | Every change request is priced and approved before work starts |
| Close | Project manager and finance | Plan and outcome are compared and the lessons go back to presales |
Fixed-fee project margin: frequently asked questions
How much extra effort can a fixed price absorb?
With unchanged revenue and other costs, divide the planned margin amount by the marginal cost of each additional hour, including labor-linked charges. If role mix changes, cost the extra hours by role rather than using one fixed blend.
Should I reprice when scope changes?
Price the change, not the whole project, unless the contract allows otherwise. Use the change-order process.
How do you manage margin on a fixed-fee project in a consulting firm?
Price from a costed team, freeze one baseline at sign-off, record actual hours by role every week, review forecast margin monthly against the baseline, price every change before work starts, and give each variance an owner. If hours run over with no change request, the overrun comes straight out of margin.
Continue the sequence: guides to read next
- Planned vs Actual Project Margin: comparing planned and actual margin
- Why Extra Hours Reduce Margin on a Fixed-Price Project: the arithmetic of extra hours
Sources and methodology
- UK Cabinet Office, Risk Allocation and Pricing Approaches, January 2026. Used for fixed-scope, price-certainty, and supplier-risk principles.
- Project Management Institute, Managing fixed-price projects using earned value management. Used for baseline, progress, and actual-cost control concepts, not as a claim that Managed Margin implements EVM forecasts.
- The worked example is original. Product claims were reviewed against the current Managed Margin application on 26 September 2026.