Skip to main content

How do I document why the final forecast on a production code has changed?

Do not overwrite the figures. Register each new deviation as a separate expected addition, and use transactions when you move money. That way the history is stored.

Do not overwrite the figures. Register each new deviation as a separate item, an expected addition, and use transactions when you move money between production codes. That way you have the history in one place.

How to do it

  1. When a new deviation occurs, create a new expected addition on the production code with + Add → Expected Addition, instead of changing the amount on an existing one.

  2. In the description, write what the deviation concerns and why it was entered.

  3. If you are going to move money between production codes, do it with + Transaction in Prod. codes. The transaction shows both which code the money came from and which it went to, and you can find it again in the Transactions tab on the production code.

  4. If you want to see what has happened over time, click History at the top right of the production code.

A production code opened in AIMZ with the Add menu open. 1 points to the option Expected Addition in the Add menu, 2 to the Transactions tab in the overview panel, and 3 to the History button at the top right.

Good to know

  • Each item becomes a trail you can go back to. A figure that has been overwritten does not tell you why it changed.

  • Transactions always sum to zero on the project.

  • A transaction changes the revised budget. If you want the final forecast to change, the planned costs must also be moved.

Related questions

Did this answer your question?