CP 312: Model change control separates code changes from assumption changes
A model review should identify what changed, why and the financial effect. Data, assumption and implementation changes need distinct checks, even when they appear in one release.
Original practice scenario
For an original long-term cash-flow model update, run old and new code on the same data and assumptions, then change one input category at a time. Reconcile differences and document interactions. A matching total alone does not prove every benefit calculation is correct.
Study check
Write the assumptions, the decision being supported and one limitation. Use the current course syllabus for the required terminology and scope; this introductory guide is not a complete course summary.
Reading sources
ActNet editorial guide · October 1, 2026 · Original illustrative examples.
0
0 replies