What Is Project Margin?
Project margin is project revenue minus the selected project costs under an explicit revenue, cost, period, currency, and allocation definition, often also expressed as a percentage of project revenue.
Labor basis, contractors, vendors, expenses, allocations, exclusions, currency, and period.
Amount, percentage, formula, source drill-down, forecast, actual, variance, and limitations.
Make the definition traceable to source records.
A trustworthy measure or transition names its object, formula or authority, period, evidence, owner, limitations, and downstream consequence.
Define the boundary
Name the client, project, document, transaction, capacity period, revenue, cost, or handoff state and what is included or excluded.
Use comparable source data
Align periods, currencies, statuses, versions, roles, classifications, accounting treatment, and authoritative records.
Record the transition or formula
Preserve the actor, time, decision, calculation, source objects, conditions, communication, and intended consequence.
Explain uncertainty and exceptions
Show missing records, estimates, assumptions, disputes, corrections, data-quality limits, and the accountable recovery path.
Questions that prevent false confidence.
Use these prompts when designing reports, choosing software, issuing client records, or transferring responsibility.
DefinitionCan two informed people identify or calculate the state in the same way?
SourceCan every material number, document, decision, and payment be traced to an authoritative record?
OwnerIs one role accountable for verification, correction, communication, and closure?
UseDoes the result support a responsible action without overstating certainty or encouraging harmful optimization?
Project margin, answered.
Why does this definition matter?
Without stable boundaries, teams compare incompatible records, automate ambiguous states, and mistake activity or estimates for verified outcomes.
Can software define this automatically?
Software can enforce a selected definition, but the organization must choose sources, boundaries, authority, exceptions, and responsible use.
How should a team apply this page?
Map one real engagement, identify the source records and owners, then test a normal path, correction, and meaningful exception.
Make the definition operational.
Connect it to authoritative records, ownership, evidence, limitations, and recovery.