Project margin is the share of a project’s revenue left after its delivery costs: (revenue − included costs) ÷ revenue × 100. Decide first which costs count, labor only or also commission and overhead, and use the same basis whenever you compare projects, or planned with actual margin. A current margin is an observation, not a final forecast.
In plain words
To calculate project margin, subtract the project’s costs from its revenue, then divide by the revenue and multiply by 100. The only tricky part is deciding which costs to include. Write the list down and use it the same way every time, so the margins of different projects, and the plan and the actual, can be compared fairly.
Who this helps: Junior project managers, analysts and sales managers who have never calculated a project margin.
Questions this guide answers:
- How do you calculate project margin?
- What is the project margin formula?
- Which costs belong in a project margin calculation?
- What is a project margin calculation example?
Margin words: gross, contribution, managed margin, budget, forecast and the roles named here are defined once in the margin vocabulary.
Start with one small project
A project is sold for a fixed fee of USD 40,000 and the firm counts USD 30,000 of cost against it. Margin = 40,000 − 30,000 = USD 10,000. Margin % = 10,000 ÷ 40,000 × 100 = 25%.
The arithmetic is that simple. The skill is deciding which costs count (labor only? commission? overhead?), because two firms can use the same formula and get different answers. The rest of this guide shows how to settle that and how to compare planned and actual on the same basis.
What is the project-margin formula?
Project margin = approved project revenue basis - included delivery costs
Project margin % = project margin / approved project revenue basis x 100
The arithmetic is straightforward. The useful work is defining each input. "Project revenue basis" might be an approved fixed fee for an internal management view. "Included delivery costs" might include labor, employment overhead, subcontractors, infrastructure, travel, commission, or other project costs. If the definition changes between reports, the percentages are not directly comparable.
Keep this internal project-control calculation separate from statutory revenue recognition. IFRS 15 requires entities applying IFRS to recognize contract revenue according to performance obligations and transfer of promised goods or services. A management dashboard using an approved fee does not replace that accounting policy.
Which revenue and costs should be included?
Finance should approve one written basis for the use case. The UK Infrastructure and Projects Authority advises cost estimators to document methodology, assumptions, exclusions, evidence, and ownership. That guidance is aimed at major projects, but the control principle is useful for services work: readers must know what the number contains.
| Input | Question to answer | Example policy |
|---|---|---|
| Revenue basis | Which approved amount is the denominator? | Signed fixed fee, excluding taxes collected for authorities. |
| Labor | Which cost rate and hours are used? | Internal pay-cost rate multiplied by planned or recorded hours. |
| Labor overhead | Are employment on-costs included? | A governed percentage of labor cost. |
| Other direct cost | Which non-labor items belong to the project? | Subcontractor, infrastructure, travel, or visa cost when applicable. |
| Commercial cost | Is commission inside the project view? | A stated percentage of the approved fee. |
| Shared cost | Is this shown inside gross margin or as a separate layer? | Keep it separate so direct project economics remain visible. |
Worked example for a fixed-price services project
Assume an approved fixed fee of USD 100,000. The firm's internal project-margin policy includes commission, pay-rate labor, labor overhead, and infrastructure. The figures are synthetic and are not a benchmark.
| Component | Calculation | Amount |
|---|---|---|
| Approved fee | Revenue basis | USD 100,000 |
| Sales commission | 5% x USD 100,000 | USD 5,000 |
| Planned labor | Role hours x governed pay-cost rates | USD 42,000 |
| Labor overhead | 15% x USD 42,000 | USD 6,300 |
| Infrastructure | Included project items | USD 4,000 |
| Included costs | 5,000 + 42,000 + 6,300 + 4,000 | USD 57,300 |
Project margin = USD 100,000 - USD 57,300 = USD 42,700
Project margin % = USD 42,700 / USD 100,000 x 100 = 42.70%
The 42.70% result describes this stated cost basis. If a USD 7,000 share of central delivery-management cost is allocated separately, the amount after that shared cost is USD 35,700, or 35.70%. In Managed Margin, a cost like this is a cost rule that moves the result from the margin before that cost towards margin after all included costs; neither figure is operating or net margin.
The USD 5,000 commission line above is also a common source of confusion between teams. A salesperson quoting the deal may only see the gross spread between the fee and delivery cost before commission and overhead are removed; finance sees the fully-loaded figure. See gross contribution versus net margin for sales for why those two views can legitimately disagree without either being wrong.
How should planned and actual margin be compared?
Use the approved baseline for the planned side and complete, period-appropriate entries for the actual side. Compare role-level hours before looking at the overall percentage. Twelve extra hours can have a small total-hours effect but a larger cost effect if the work moved to a more expensive role.
Managed Margin shows three figures for each service order: the baseline, the actual to date from approved time and posted costs, and a forecast at completion that adds remaining allocations and expected costs. On fixed-price work the actual to date needs the revenue recognized so far; hours alone do not establish earned revenue. Read the actual figure beside budget consumption and remaining scope, and the forecast as a calculation, not a guarantee.
Project-margin calculation checklist
- Name the approved revenue basis and its effective date.
- List every included and excluded cost category.
- Confirm that hours, rates, currency, and time periods are consistent.
- Calculate the dollar margin before the percentage.
- Reconcile the result to its source inputs.
- For actuals, confirm that entries are complete through the stated cut-off.
- Explain material changes in role mix, rates, scope, or non-labor cost.
- Label shared-cost, gross-margin, and accounting views separately.
How does the calculation hold up across a multi-wave data-migration project?
Consider a fixed-fee migration delivered in several waves. At each review keep three views separate: the approved full-project baseline; recognized revenue and costs through the cut-off; and forecast total revenue and cost at completion.
For an illustrative USD 100,000 contract, assume finance has recognized USD 40,000 revenue and recorded USD 30,000 included cost. Actual-to-date margin is (40,000 − 30,000) / 40,000 = 25%. If remaining work is forecast to cost USD 45,000, total forecast cost is USD 75,000 and forecast margin is 25% of the full USD 100,000 fee. Subtracting only USD 30,000 from the full fee would show USD 70,000 of headroom for remaining costs and profit, not 70% actual margin.
Wave-level views are useful when revenue and costs are allocated using a documented policy and reconcile to the engagement total. Invoices, cash receipts and recognized revenue are not interchangeable. Use missing time, acceptance evidence and remaining scope to assess the forecast before escalating a variance.
What does project margin not tell you?
Project margin does not by itself measure delivery quality, cash collection, revenue-recognition compliance, schedule feasibility, client satisfaction, workforce capacity, operating margin, or net margin. It also cannot predict costs that have not been estimated or recorded. A well-calculated percentage supports a decision; it does not make the decision.
For a complete operating workflow, read the project margin management guide and the planned-versus-actual review checklist.
- How to Audit a Project Margin Spreadsheet
- How to Price a Project to a Target Margin: Formula and Example
- Project Margin Rollups: Formula & Example
- How to Structure a Project Margin Spreadsheet
- Utilization vs Project Profitability
At the office: Joe works out his first project margin
An illustrative story with invented figures, to show how the idea works in a real office.
Joe, a junior project manager, is asked for the margin on a USD 60,000 fixed-price job. His finance colleague gives him the cost list: staff time USD 36,000, travel USD 3,000 and software USD 1,000. Costs total USD 40,000.
Revenue minus costs is 60,000 minus 40,000, which is USD 20,000. Divided by revenue that is 20,000 / 60,000, or 33.3%.
Joe writes the cost list next to the answer (direct costs only, no overhead or commission), because next quarter someone will ask what was included. A margin without its cost list cannot be compared with another margin.
When is project margin calculated, and who owns each calculation?
| Stage | Owner | Checkpoint |
|---|---|---|
| Pricing (planned margin) | Presales consultant | Revenue basis and every included cost category are listed |
| Handover (baseline) | Project manager | Planned margin is frozen as the comparison point |
| During delivery (actual and forecast) | Project manager and finance | Same cost boundary, same period, complete entries |
| Closeout (final) | Finance | Recognized revenue and final costs reconcile; lessons go back to presales |
Frequently asked questions
How should planned and actual margin be compared?
Use consistent cost categories, recognition policy and cut-off. For actual-to-date margin, match recorded costs with recognized revenue through that date. For a full-project comparison, use forecast completion revenue and costs against the original baseline. Explain rate and scope changes instead of forcing identical inputs.
What does project margin not tell you?
It does not show firm profit, cash flow or the quality of work. See the profit versus cash guide.
How do you calculate project margin?
Subtract the costs your firm includes from the project revenue to get the margin amount, then divide by the revenue and multiply by 100. For example, a USD 100,000 fee with USD 65,000 of included cost leaves USD 35,000, a margin of 35%.
What if the project revenue is zero?
The margin amount (revenue minus costs) can still be measured, but the margin percentage is undefined when revenue is zero, because it divides by revenue. Report the amount and say the percentage is not calculable; do not show 0%.
Continue the sequence: guides to read next
- Planned vs Actual Project Margin: comparing the calculation across stages
- What Is Managed Margin? Meaning, Formula and Software: the margin definition this calculation feeds
- Contribution Margin vs Net Margin vs Gross Margin: three margins from one project
Sources and methodology
- IFRS Foundation, IFRS 15 Revenue from Contracts with Customers. Used to distinguish an internal project-control revenue basis from statutory revenue recognition.
- UK Infrastructure and Projects Authority, Cost Estimating Guidance. Used for assumptions, exclusions, evidence, ownership, and consistent-baseline principles.
- The Managed Margin formula boundaries and weekly-rate treatment were reviewed against the current Managed Margin application on 26 September 2026. All figures are illustrative.