Skip to main content

Why does AIMZ recommend measuring against the revised budget instead of contribution margin per trade?

Revenue is not structured per trade, and revenue on production codes only gives a forecast. Compare the final forecast with the revised budget per code, and track contribution margin at project level.

We recommend comparing the final forecast with the revised budget (the revised cost estimate) per production code, and tracking contribution margin (%) and contribution margin amount at project level. The revenue side is not structured per trade the same way as the cost side, and revenue placed on production codes only gives a forecast, not posted revenue.

How to track instead

  1. In Prod. codes, compare Final forecast with Rev. budget per code. If the final forecast is below the revised budget, the trade is doing better than estimated.

  2. The revised budget is corrected for reallocations and for the cost portion of approved Change Order Client, so it reflects the scope you actually have to deliver.

  3. Track contribution margin (%) and contribution margin amount for the whole project on the dashboard, where the revenue forecast is compared with the final forecast.

Prod. codes. 1: The Rev. budget column. 2: The Final forecast column next to it. 3: The project's contribution margin at the top of the page.

Why not contribution margin per trade?

  • Revenue comes from the contract sum, Change Order Client and index regulation (LPS), and is rarely distributed per trade.

  • If you place revenue on the production codes, you can only track the forecast, not posted revenue.

  • Most in the industry do not track revenue per production code.

Good to know

You can still work with revenue per trade if you are used to it. AIMZ can be set up for that. The recommendation above is still the way of working we believe gives the best control.

Related questions

Did this answer your question?