Project Margin at Completion

A project is halfway through and still appears profitable on costs posted so far, yet unfinished work, supplier claims and unresolved change orders may consume the expected margin. Project margin at completion forecasts the final revenue less total cost, then compares that with the original plan.

IFS documents estimate-at-completion workbench concepts and Procore describes forecast-to-complete management, and both support a forward view, but accounting revenue recognition is a separate standards-dependent question. Define the project boundary to include the approved contract, scope and cost codes, noting that a related warranty or maintenance contract may need separate treatment.

Start with contract revenue using the signed base price and supported changes, because an unsigned request is an opportunity, not automatically secured revenue. Add authorised change orders to the forecast at their accepted price and cost, and keep disputed amounts separate.

Review cost to date by reconciling posted labour, materials, subcontractor bills and allocated equipment costs to the project ledger. Estimate remaining cost by asking delivery managers what is still needed, not simply budget minus spent, since a delayed task can consume more than its unspent allocation, and include open purchase orders and subcontract amounts because they can reveal future spending not yet in the general ledger.

Avoid duplicate cost, as an invoice and its purchase commitment may represent one future obligation, so move it between stages rather than summing both. Forecast labour as remaining hours times realistic rates, accounting for overtime, skills, leave and productivity changes, and check procurement, since late materials, expedited shipping and price escalation can increase completion cost, so confirm live quotes where material.

Allow for rework by putting known quality problems into the best estimate rather than hiding them as unplanned future risk, and watch schedule delay, because more site supervision or equipment rental may follow an extended project even if physical quantities stay constant. Include closeout, since testing, documentation, punch-list work and handover can create real final costs after the main build is done.

Separate contingency from known costs, because a generic contingency is not a substitute for known expected costs, so show the base estimate and the risk allowance under a defined policy, and present claims as scenarios since potential customer reimbursement or supplier recovery may not be certain. Final cost is cost to date plus forecast cost to complete, one simple estimate-at-completion method, so reconcile it with other model views, and margin is forecast final revenue minus forecast final cost, divided by final revenue for a percentage.

Compare with the baseline, because a fall from 20% planned margin to 8% forecast margin should be bridged by scope, price, productivity and cost factors. Watch percentage-of-completion, because a management margin forecast can affect accounting estimates under some methods and specialist accounting review is needed, and update the forecast regularly with dated versions as work progress, contract approvals and supplier bills change the picture.

Check optimism by backtesting forecasts by stage, since repeated late-project cost overruns suggest earlier remaining-cost estimates were weak, consider cash because a profitable project can still require substantial cash before customer milestones pay, show one high-risk subcontract package explicitly instead of averaging it away, and assign ownership so project managers validate physical work and schedule, procurement checks commitments and finance reconciles costs and revenue. For an owner, project margin at completion is the expected economic outcome if the work finishes under current evidence, and it lets the team act before the final invoice proves the margin was lost, so avoid releasing unused contingency to make one month look better, which can mask a real completion risk.