A project can look profitable while hidden delivery costs accumulate elsewhere in the business. Begin by defining what counts as the project, when work is recognised and which costs belong to it. Invoice totals alone do not establish margin. Management needs a consistent basis for comparing assignments with different delivery schedules, resource needs and levels of completion across the reporting period.
Create a project code that follows the work from quotation through purchasing, time recording and billing. Link direct supplier charges and staff effort to that code where practical. Keep common overhead separate until an allocation policy is agreed. An allocation can help decision making, but it should not disguise the difference between a cost caused by one project and a business cost that continues regardless.
Reconcile the project view to the accounts. Check that contractor invoices have not been counted both as direct costs and within an allocated departmental total. Include work performed but not yet invoiced and costs expected to complete the assignment using an appropriate, documented methodology. Make estimates visible and update them when scope changes. An apparently strong margin can disappear if remaining work is simply left out.
Imagine a hypothetical installation company delivering fixed price fitouts. One job has high billed revenue but requires repeated site visits caused by an unclear specification. Time records and additional materials reveal the cost of rework. Another smaller job performs better because delivery is controlled. The comparison helps management investigate quotation and approval practices rather than rewarding projects solely for their final invoice value.
Use several margin views only when their purpose is clear. Direct contribution may inform scheduling, while a fuller cost view can support pricing and capacity decisions. Do not present them under the same label. Investigate exceptional results with the project manager and distinguish a recording error from a commercial problem. Keep approved scope changes and client variations alongside the figures so the explanation remains traceable.
Close each reporting cycle with actions on overruns, change orders and estimates to complete. Feed completed project learning into future quotations. A project reporting review can help establish practical coding and allocation rules, giving owners a clearer view of where value is created and which apparent profits rely on missing costs, unrecorded time or optimistic assumptions about the remaining work.