Scenario Packs: Base, Upside and Downside That Never Pass as Actuals
Rexfin lets you edit forward assumptions, save a scenario, and add it to a board pack, always labelled UNAUDITED, and never able to touch the verified actuals underneath.
By The Rexfin team
A board deck usually needs more than the actuals. It needs a base case, maybe an upside, maybe a downside, and increasingly a sensitivity view showing which assumption moves the number most. The risk with adding any of that to a pack that also contains your verified financial statements is contamination: a projected figure that reads, at a glance, like a cited one. Rexfin’s scenario packs solve that with one hard rule: a scenario can flex the future, but it can never change how the past is displayed, and it can never lose its label.
Editing a scenario
The draft plan editor lets you change forward-looking driver assumptions (growth rate, gross margin, days sales outstanding, and the like) in a small, curated set of driver cells. Change a number and the projection recomputes immediately, client-side, no server round trip. The anchor actuals column next to it (the historical figures the projection builds from) is rendered as plain text with no input element at all. It isn’t locked by convention; there’s structurally nothing to click, because that column is computed once from the actual data and never touched by anything you edit in the draft. This holds whether the underlying actuals are the filed, cited tier or an internal unaudited tier.
Every draft carries an always-visible “DRAFT” banner, in text, not just a color, plus dashed amber styling and column tags distinguishing “actual” from “draft.” If you enter a driver value outside a sane range, Rexfin rejects it loudly: an alert, not a silent clamp to the nearest acceptable number.
Happy with a case, you save it. A saved scenario name, its driver values, and the horizon it covers all persist, and the same saved scenario shows up both in the forecast workspace and as something you can add to an export.
Adding scenarios to a board pack
A scenario section is optional on the board pack, the presentation export, and the tenant-branded template fill. Turn it on with a single checkbox, explicitly labelled UNAUDITED, and it’s off by default: an export with no box checked is byte-for-byte the same as a pack with no scenario feature at all.
When you do include it, the section shows the scenario name, the full set of driver assumptions behind it, a three-way comparison against the other saved cases, a sensitivity view showing which driver moves the outcome most, and a short paragraph on how the roll-forward was computed. Every figure in that section is computed by the same engine that runs the interactive draft editor, so the number in the deck and the number in the app are guaranteed to match: there’s exactly one place scenario math happens, not a separate export-time recalculation that could drift from what you saw on screen.
What the gate does before any of this
Rexfin’s export gate checks that your verified statements reconcile before it allows an export at all, and it runs completely before any scenario content is even considered. Scenario sections carry no gate status of their own: they’re not part of what gets verified, because they’re not actuals. A pack’s clean-or-caveated verdict is locked in before the scenario section exists, which means checking the scenario box can never upgrade a caveated pack to a clean one, and it can never introduce a new reason for a pack to be blocked. It only adds an unaudited appendix on top of whatever the actuals already earned.
Who this is for
This is for anyone who needs to show a board or an investor more than one version of the future without ever letting that version get mistaken for a verified number: an FP&A lead prepping a board pack with a downside case, a CFO who wants a sensitivity table next to the actuals, an analyst stress-testing a plan before committing to it. If your deck only ever needs the historical statements, you’ll never touch this. The moment someone in the room asks “what if,” it’s the difference between a labelled assumption and a number that looks like it came from the ledger when it didn’t. See the product tour hub for the rest of what Rexfin’s dataroom covers.
Part of Rexfin Product Tour: Every Number Traceable