Cases and sensitivity

Compare explicit downside, base and upside assumptions and test payment delays.

View Markdown
Browse documentation
On this page

Open /reviews and choose Downside, base, upside and timing. These are named assumptions, not probabilities or a statistically calibrated confidence interval.

Compare three cases

  1. Select an approved plan for an active goal.
  2. Choose different saved scenarios for downside and upside.
  3. Preview the report.
  4. Inspect the goal value, outcome, assurance, scenario names and exceptions.

The base case is the current operating outlook, not a frozen copy of the plan. The approved plan supplies the goal context. The selected scenarios are evaluated against current inputs through the same engine used for decision review.

Naming a scenario “downside” does not guarantee it is numerically worse for every goal. Inspect the assumptions and results. Previewing these cases does not apply their decisions.

Test an outstanding expectation

Optionally choose an active, unfinished expectation and test delays through a selected range of 1–90 days. The report evaluates the starting date and each whole-day delay.

For each date, inspect the goal value, minimum dated cash, first cash-floor breach in the 13-week window, and calculation exceptions. Other active goals are also checked. A delay can move cash across a month boundary and change a monthly goal even when the total obligation remains the same.

Interpret the limit

A supported passing range is bounded by the tested dates and model inputs. Missing verification, outstanding manual conditions and overdue obligations can prevent a supported limit. A delayed event beyond the dated weekly window cannot establish a passing liquidity result for that event.

The report never promises that a customer will pay by the modeled date or that no unmodeled bill will arrive. See Weekly cash for the dated calculation’s limits.

Preserve the review

Save the report with a name, reason and reviewer. Exceptions become review tasks. Later source, goal or scenario changes make the saved scope stale rather than rewriting it.

Use Reviews and sign-off for ownership. Use Decisions and scenarios when you are ready to apply a proposed operating change.