The question this page answers
Which alternatives were considered against this commitment's plan, how does each compare with it, and which one was chosen?
What you see
- 1The Buying/Discounts switch, over the scenario table.
- 2The Chosen badge and its door to the decision record.
- 3Buying scenarios, with New buying scenario.
Scenarios is the library of what was considered against one commitment's buy. A scenario is a named diff over the plan, never a copy of it: a style with no override keeps the plan's depth, and taking a style to nothing records it as dropped from the range rather than as a depth of zero. Nothing is edited here. Every depth, drop and price move is made on the desk, where the working copy lives, and this page is where the kept results are read back.
A switch at the top reads Buying or Discounts. Buying is the scenario table, headed Buying scenarios (Buying decision history once the commitment has closed), with a search box and, where one was chosen, a Chosen badge beside its name and a door to its decision record. The table's columns are Scenario, Status, Products, Recorded buy, Margin, Saved and By, and each row has a Compare press. Status is one phrase per state: Draft alternative, Chosen decision, Awaiting approval, or Not taken. Every scenario stays in the table, declined ones included, newest first, twelve to a page.
Ticking one row compares it with the current plan; ticking two compares them with each other. The comparison names the recorded buy, units and margin for each side, and each compared row carries its own doors: Review changes, Edit scenario for a draft (which opens it on the desk), Details, and Outcomes for a scenario that was not the chosen one. Details opens a drawer with buy at cost, change from plan and budget status, followed by the changed products. Estimates are labelled beside the summary. Changes, Cost details and Activity tabs separate product changes from supporting information. Activity retains the source scenario and its evaluation evidence. In the drawer, an envelope nobody declared reads None declared.
Buying baseline and recorded costs, a press beside the heading, holds the plan's own reading: one sentence counting how many scenarios were considered, how many became the plan or were declined, and which one frees the most money; two figures, Scenarios and Backed; and two doors, Where the money goes (the margin the plan buys at each level of spend) and Work the buy.
What to do
- Press New buying scenario to open a fresh working copy on the desk, or New demand scenario to start one from demand assumptions instead.
- Tick one row to compare it with the current plan, or tick two to compare them with each other.
- Open a compared row's own doors: Review changes, Edit scenario for a draft, Details, or Outcomes.
- Press the switch to read Discounts instead of Buying.
Saving, backing and declining a scenario are pressed on the desk's scenario row, not here: Record a scenario, Promote a scenario and Decline a scenario. There is no delete. A diff that moves the envelope goes back for re-approval rather than taking effect, and a working copy with changes not yet saved has to be recorded before it can be backed.
When it is empty or failed
While the page reads:
Reading the range and what was considered against it.
Before any scenario is kept:
Nothing has been considered against this plan yet.
With no commitment in the address, or one this tenant does not hold:
No commitment is chosen.
No commitment with that id.
Where a read fails, nothing is shown rather than a figure with holes in it:
Commitment failed to load.
The range did not load. Nothing is shown rather than a buy with holes in it that look like zeroes.
Where no style on the commitment can be costed, the page prints the served reasons, or where none was served:
No style here is costed.
A scenario table that did not load says so and is not an empty library:
Scenarios could not be loaded. Refresh to try again.