Close process · Review · 2026-07-18

How to make a close review easier to follow

A practical look at approvals, import history, comments, and change summaries around a forecast version.

Keep the changed assumption visible

Compare the current forecast with its parent so the conversation starts with what moved.

Keep people in the loop

Named approval actions and threaded comments keep the question and response beside the version.

Use summaries as orientation

AI change summaries help a reviewer scan the difference while the underlying version history remains the source of the discussion.

Keep reading

Build a review path your team can explain.

See the live workflow, published plans, and available CSV / Excel imports.