Three shared saved plans
The operator maintains exactly three plan slots. Each saves its name, start, comment, opening-cash override, rules, manual cash, operational overrides and custom lines. A plan is shared across Model scenarios: selecting Upside or Downside changes linked economics but keeps its independent payments. Use different plan slots for different operational planning windows or alternatives; they are not additional Model scenarios.
Use thirteen complete calendar weeks
Start week is normalized to a Monday, and the plan spans thirteen consecutive real ISO weeks. Each header shows the week identity and actual date range. The whole window must fit within forecast; historical weeks and weeks beyond the Model horizon are unavailable. The default tries the next complete week and falls back to a complete forecast-start week if necessary. A fiscal-year boundary does not turn the window into thirteen arbitrary equal accounting periods.
Set opening cash deliberately
Opening Cash override is optional. Blank uses linked Model beginning cash for the plan start; a number sets explicit plan opening cash without changing the Model balance sheet. The linked amount remains visible for comparison. Put the reason in Plan comment if the operational starting position differs. This override is independent of weekly receipt/disbursement changes and can materially affect every later funding result.
Choose how saved dates move
Keep input calendar dates moves only the planning window. Dated manual amounts and overrides can fall outside it but remain saved. Move inputs by relative week shifts manual/override dates, payment anchors and explicit dated payments by the same offset as the window. Timing Profile offsets stay relative to their source weeks. Review Outside this window after a shift rather than assuming every saved payment is still included.
Duplicate into an existing slot
Duplicate plan copies the current plan’s inputs and comments into another saved slot and selects that copy. Replacing a customized target asks for confirmation; Undo can restore it. The copy is independent of later source-plan edits. Browser persistence and native model files retain the saved plan state; there is no automatic cloud planning library or unlimited plan creation.
Documents the current implemented behavior. Numerical examples are synthetic, not market assumptions.