Key Takeaways
- Direct project margin shows what remains after costs directly attributed to delivery.
- Fully loaded project margin subtracts allocated overhead, providing a broader view of project profitability.
- Consistent labor-cost and overhead-allocation policies make margin comparisons more reliable across projects.
- Review planned, actual, and forecast margin throughout delivery while there’s still time to address changes in scope, staffing, cost, or revenue.
Project margin measures how much project revenue remains after the costs included in the calculation. Looking at margin in two ways provides a more complete picture: Direct margin accounts for delivery-related costs, while fully loaded margin also includes the project’s allocated share of overhead. Comparing the two helps professional services organizations determine whether a margin issue stems from the way the work was delivered or from the organization’s broader cost structure.
Although the formula is straightforward, the result is only meaningful when cost policies are clear and applied consistently across projects, clients, and service lines.
What Is the Project Margin Formula?
Project margin is calculated by subtracting the costs included in the organization’s policy from project revenue, dividing by project revenue, and multiplying by 100. Direct and fully loaded margin use the same structure but include different costs.
Direct project margin
Direct project margin accounts for costs tied to the engagement, including employee delivery costs, contractors, project-specific expenses, materials, and travel. The resulting margin shows how much the project contributes before including its share of overhead.
Direct project margin = (Project revenue - Direct project costs) / Project revenue x 100
Because the calculation isolates delivery economics, it supports project reviews, pricing analysis, and professional services KPI reporting that compares planned and actual performance.
Fully loaded project margin
Fully loaded project margin includes allocated overhead and direct project costs. It shows how much project revenue remains after the engagement absorbs its share of the organization’s operating costs.
Fully loaded project margin = (Project revenue - Direct project costs - Allocated overhead) / Project revenue x 100
Comparing direct and fully loaded margin can inform pricing and reveal profitability patterns by client or service line. Accelo’s project financials connect project budgets, costs, revenue, and forecast profitability, so teams can see whether expected margin changes during delivery.
How Are Project Margin, Gross Margin, and Markup Different?
Project margin, gross margin, and markup often come up in the same pricing discussion, but the calculations aren't interchangeable. Project margin and gross margin generally use revenue as the denominator, with the cost definition determining what each figure represents. Markup uses cost as the denominator and shows how much the price exceeds that cost.
A 25% markup does not produce a 25% margin. If cost is $80 and the price is $100, the markup is 25%, while the margin is 20%.
Which Costs Should Be Included in Project Margin?
Margin comparisons only hold up when you apply the same policy across projects. Similar engagements can show very different margins if one calculation includes labor burden or allocated overhead while another does not, or if write-offs are handled differently. Documenting how each category is treated keeps the calculation consistent from one review to the next.
Direct labor and employer costs
Direct labor covers employee time traceable to the engagement, including delivery, project management, technical review, and project-specific coordination. The labor cost used in the margin calculation may also include employer-paid costs such as payroll taxes, benefits, insurance, paid time off, and retirement contributions.
Organizations may use actual employee costs or standard cost rates by role or level. Either approach can support reliable margin comparisons when you document the costs included in each rate and apply them consistently. The U.S. Bureau of Labor Statistics Employer Costs for Employee Compensation separates wages and salaries from benefit costs, illustrating why salary alone may understate the cost of delivery labor.
Project expenses and revenue adjustments
Contractor fees, client-specific software, travel, materials, and other costs that can be traced to the engagement should also be included in direct project costs. Reimbursable expenses require consistent treatment on both sides of the formula. If the client reimbursement is included in project revenue, include the related expense as a cost.
Write-offs and discounts are handled differently because they generally affect the revenue attributed to the project rather than create another delivery cost. If the related labor cost is already included, recording the write-off as an additional cost would count it twice. The organization’s project accounting policy should define how revenue, costs, billing adjustments, and write-offs are reflected in project margin.
How to Allocate Overhead to a Project
Overhead allocation determines how much of the organization’s shared operating costs is assigned to each project. No method will trace those costs perfectly, but the selected basis should reasonably reflect how projects use shared support and remain consistent across comparable engagements.
Allocation by direct labor hours
Under this method, the organization divides its overhead pool by the direct labor hours expected across client projects. The resulting hourly rate is then applied to the direct labor hours consumed by each engagement.
For example, if the organization has $500,000 in annual overhead and expects 25,000 direct labor hours, the overhead rate is $20 per direct labor hour. A project requiring 900 direct labor hours would receive $18,000 in allocated overhead.
Direct labor hours can provide a reasonable allocation basis when management, finance, technology, and other shared support generally increase with the amount of delivery effort a project requires. The method becomes less representative when projects with similar hours require very different levels of administrative or specialist support.
Allocation by billable hours
Billable-hours allocation spreads overhead across the hours billed or expected to be billed to clients. The calculation is similar to the direct-labor-hours method, but the denominator excludes nonbillable time.
This approach can be useful when the organization plans pricing and profitability around billable capacity. However, the overhead rate depends heavily on the utilization assumptions behind it. If the organization generates fewer billable hours than planned, each billable hour must absorb more overhead than the original rate assumed.
Review the billable utilization rate alongside the overhead rate so changes in billable capacity do not leave shared operating costs underallocated.
Allocation by direct labor cost
Direct-labor-cost allocation divides the overhead pool by total direct labor cost for the same period and applies the resulting percentage to each project. As a result, projects with higher labor costs receive more allocated overhead, even when they use the same number of delivery hours.
This method can be useful when an organization wants projects to absorb overhead in proportion to its investment in delivery labor. However, it may allocate substantially more overhead to projects staffed by senior or specialized employees, whose higher compensation is already included in direct project costs. Organizations should consider whether that outcome produces a useful basis for comparing project margins.
Revenue-based overhead allocation
Revenue-based allocation calculates overhead as a percentage of expected or recognized project revenue. If annual overhead is $500,000 and planned revenue is $2.5 million, the overhead rate is 20%. A $100,000 engagement would therefore receive $20,000 in allocated overhead.
The method is straightforward and may work reasonably well for organizations with consistent service models. It becomes less representative when project economics vary widely. A high-fee engagement requiring relatively little delivery support may receive more overhead than a lower-fee project that requires substantial coordination, management, or finance involvement.
A fixed percentage can also support early pricing and planning when detailed project estimates are not yet available. The organization should still compare that planning assumption with its actual overhead rate as delivery progresses.
Which overhead allocation method should a professional services organization use?
Choose the method that best matches your operating model. That choice may depend on:
- Whether support requirements generally follow delivery hours, billable hours, labor cost, or revenue
- How much billing models and project types vary across the organization
- Whether time and labor-cost data are complete enough to support the calculation
- How easily the method can be maintained and applied across projects
- Whether the resulting margins provide useful comparisons between similar engagements
Some organizations use a detailed allocation method for internal profitability reporting and a simpler percentage during early pricing. When you use multiple methods, label each margin view clearly so you don't compare estimates and actual results on different bases.
Document which costs belong in the overhead pool, how the allocation rate is calculated, and how often it is updated. Revisit the method when staffing, utilization, service mix, or the operating cost structure changes enough to affect the assumptions behind it.
Project Margin Example for a Professional Services Firm
Consider a $120,000 engagement with $80,000 in direct project costs and $18,000 in allocated overhead. Example inputs include:
Step-by-step calculation
First, calculate direct margin:
($120,000 - $80,000) / $120,000 x 100 = 33.3%
Then calculate the fully loaded margin:
($120,000 - $80,000 - $18,000) / $120,000 x 100 = 18.3%
The project contributes $40,000 before overhead, producing a 33.3% direct margin. After allocating $18,000 of overhead, the contribution falls to $22,000 and the fully loaded margin to 18.3%. Comparing those results can help the organization determine whether similar work is priced and staffed appropriately.
If direct project margins look healthy while company-level EBITDA remains weak, fully loaded margin can show whether shared operating costs are contributing to the gap.
Understanding 10%, 20%, and 30% Project Margins
A margin percentage has little context without clear underlying costs. A 20% direct margin and a 20% fully loaded margin describe different project economics, and the interpretation may also change by billing model, service line, risk, or strategic value.
What does a 10% project margin mean?
A 10% project margin means $0.10 of every revenue dollar remains after the included costs. If the figure is fully loaded, the project contributes 10% after allocated overhead. If it is a direct margin, shared costs still need to be considered.
What does a 20% project margin mean?
A 20% project margin means $0.20 of every revenue dollar remains after the included costs. On a $100,000 project, that equals $20,000 before any costs excluded by the organization’s policy.
What does a 30% project margin mean?
A 30% project margin means $0.30 of every revenue dollar remains after the included costs. A higher percentage may reflect pricing, delivery efficiency, scope control, or staffing mix, but the calculation alone doesn't show which factor drove the result.
How Should Project Margin Be Used During Delivery?
Margin analysis is most valuable while a project is active, when adjustments to scope, staffing, costs, or billing can still affect the outcome. Comparing planned, actual, and forecast margin shows whether the assumptions used to price the project still hold as delivery progresses.
Use margin variance to investigate scope drift.
Margin variance shows the financial effect of a project moving away from its original plan. A decline may come from additional effort, higher expenses, unbilled scope, a more expensive staffing mix, write-offs, or lower expected revenue. Identifying the cause helps the team determine whether to revise the remaining estimate, adjust the delivery plan, or pursue a change order.
Reviewing margin alongside project management for professional services data connects the financial variance with changes in scope, schedules, estimates, and staffing.
Use client-level margin to improve pricing.
Client-level margin shows whether revenue generated across a client’s projects translates into profit. A large account may produce substantial revenue while also requiring additional oversight, more expensive staffing, recurring rework, frequent write-offs, or billing exceptions. Reviewing projects together reveals whether those costs reduce the value of the overall client relationship.
The same review can expose revenue leakage. Unrecorded time, out-of-scope work that never becomes a change order, missed billable expenses, and recurring billing adjustments can all reduce the revenue captured from delivered work. MGI Research identifies consulting hours delivered but not captured in time-tracking systems as one example of revenue leakage in professional services. Professional services automation (PSA) software helps reduce these gaps by keeping agreed scope and rates aligned with recorded time, expenses, approvals, and billing.
Use margin forecasts to guide delivery decisions.
Margin forecasts combine actual performance to date with updated estimates for remaining revenue, effort, and costs. When the expected margin changes, leaders can identify whether staffing, contractor spending, scope, or the remaining delivery plan is driving the difference and decide what to adjust while the project is active.
Utilization and profitability dashboards show whether a declining margin is isolated to one project or recurring across clients and service lines. Combined with resourcing and capacity planning, they also show whether the remaining work can be completed with the available people, skills, and capacity.
How Accelo Supports Project Margin Visibility
When project plans, staffing, time, billing, and financial data live in separate systems, teams must reconcile them before they can understand why margin is changing. Accelo brings that information together, giving professional services teams a current view of project performance and predicted profitability.
Accelo’s AI capabilities for professional services can surface project and financial risks, identify gaps in time and delivery records, and help teams evaluate staffing or replanning options. Automatic time capture provides a more complete record of project time, strengthening the labor-cost data used in margin calculations. Predicted profitability then reflects how changes in staffing, scope, costs, and delivery plans may affect the expected result.
Book a demo to see how Accelo can help you monitor project margin and proactively respond to changes during delivery.
Frequently Asked Questions
How do you calculate project margin?
Subtract the project costs included in your policy from project revenue, divide the result by project revenue, and multiply by 100. For fully loaded margin, subtract allocated overhead as well as direct project costs.
Should overhead be included in project margin?
Include overhead when the goal is to understand fully loaded project profitability. Keep a separate direct-margin view so you can evaluate delivery performance without blending it with shared operating costs.
What is the difference between direct and fully loaded project margin?
Direct project margin subtracts delivery-related costs. Fully loaded project margin also subtracts an allocated share of overhead. The difference shows how shared operating costs affect the project’s contribution.
Should labor burden be included in project cost?
Yes, when project margin is intended to reflect the full cost of employee delivery time. Labor burden refers to employer-paid costs beyond wages or salary, such as payroll taxes, benefits, insurance, paid time off, and retirement contributions. These costs may be included in actual employee costs or incorporated into standard cost rates, as long as the same approach is applied consistently.
How often should project margin be reviewed?
Review margin often enough to act while the project is still active. Many organizations include planned, actual, and forecast margin in weekly or monthly project reviews, with more frequent reviews for high-risk engagements.
What is the difference between project margin and gross margin?
Project margin measures an engagement's profitability using the costs defined by the organization. Gross margin measures revenue minus cost of services and may be calculated at the project, practice, service-line, or company level.
What is the difference between margin and markup?
Margin divides profit by revenue. Markup divides profit by cost. If a service costs $80 and sells for $100, the markup is 25%, while the margin is 20%.
.svg){kind=small}
.svg)
