Goals, plans, and change explanations
Set cash targets, preserve the approved outlook, and explain how the path changes.
Browse documentation
On this page
A goal says where the business wants to be. A forecast says what the current evidence and assumptions imply. A plan preserves the outlook approved as the starting point for pursuing a particular goal version.
Set a cash goal
Open /goals. Choose one of two metrics:
| Metric | Meaning |
|---|---|
| Ending cash at a month | Cash must reach the target at the selected end month |
| Minimum month-end cash | Each month-end in the selected interval must meet the floor |
Choose the reporting currency, dates, amount and a clear name. Add explicit manual conditions where needed, such as preserving a team. A passing cash calculation cannot establish that a manual condition is satisfied.
Drafts let you prepare a goal without introducing an active approval constraint. Activate it when ready. Select a primary goal for the progress page; other active goals still matter in decision evaluation.
Preserve a plan
Review the current goal result, assumptions and limitations, then save a named plan. The save is pinned to the preview you inspected. If financial inputs changed, refresh and review again.
The snapshot retains the exact goal version, forecast inputs and outputs, formula versions, financial revision, actual journal lines, evidence references, coverage and limitations. Later imports or assumption changes do not overwrite it.
Revising a goal creates a new version. Earlier plans continue to refer to their original version. Approve a new baseline when you adopt the revised goal; do not compare unlike definitions as though only business performance changed.
Review progress
Use /progress for current cash, target headroom, the latest plan, and prioritized review actions. Save subsequent outlook reviews from the goals workflow to preserve how expectations changed over time.
A numerical result and its assurance are separate. Unsupported currency, missing periods or unavailable calculations cannot report success. Provisional data can still produce a number whose limitations need attention.
Explain a change
The bridge compares compatible snapshots through the deterministic engine in a documented order:
- Calendar and actuals cutoff.
- Posted activity, including corrections and reversals.
- Reviewed expectations and allocations.
- Posting templates and chart mappings.
- Driver and model assumptions.
- Remaining forecast settings.
Each step records its contribution and supporting references. Interactions belong to the later step in this order. Contributions plus the explicit residual equal the total change in minor units.
A bridge is a model explanation, not proof of real-world causation. Incompatible formula versions or unavailable intermediate results leave attribution partial rather than inventing a complete explanation.
Preserve and share carefully
Inspect saved history and download the retained calculation record when needed. These records contain company financial inputs and references. They are not a full installation backup and should be shared accordingly.
Continue with Decisions and scenarios or Reviews and sign-off.