Verify a result
Check whether a scenario's numbers can be trusted, see where every input came from, and export the evidence.
Where: Scenarios→a solved scenario→Verify
Verify answers one question: can you trust this scenario's numbers? It checks that the result adds up, shows where every input came from, runs the model's own validation rules, and confirms the answer came from the current version of the model. You can export all of it.
Read the dot on Verify
The Verify button carries a colored dot. Hover it for the reason.
| Dot | Reason |
|---|---|
| Red | n validation rule(s) failing |
| Amber | Solved against an older model version, Result has an unexplained residual, n validation rule(s) not passing, or a confidence below Verified |
| Green | Verified against the current model |
On a scenario that hasn't solved, the tooltip reads "Solve this scenario first — Verify needs a result." BASE DATA has no Verify.
Open Verify
Select a solved scenario and click Verify. A drawer opens on the right, headed with the scenario and the model. Press Esc or click Close to shut it.
The first line is the overall confidence badge (Verified, Estimated, Stale or Unverified) and its main reason, for example that the parts add up to your goal's value, or that the scenario was solved against an earlier revision and needs regenerating. If you re-trace a KPI while the drawer is open, it updates.
Read each section
| Section | Shows |
|---|---|
| Result | Your goal's value, then whether its parts add up: Σ components = n — reconciles ✓, or the part that doesn't (n unexplained) with each line itemized. |
| KPIs · n verified · n estimated | Each KPI with its value, badge and whether its parts add up. |
| Inputs | Every change this scenario makes, tagged ← you (override), and every value from your workbook, tagged with its ← Sheet!Cell. On a model built from a workbook, changes are in your sheet's own words. With no changes: "No overrides — the base / as-built scenario." |
| Checks | Whether the model passes its validation rules, and how many pass. |
| Trail | Which revision of the model the scenario solved against, whether that's still current, why it ran, and how long the solve took. |
What to do from each section:
- Re-trace for full detail (Result) appears when the breakdown wasn't captured. It solves the scenario again and works out every part, which can upgrade it from Estimated to Verified.
- Re-trace for detail (KPIs) does the same for one KPI.
- In Result, each binding limit shows what one more unit is worth, marked unit values: exact or unit values: estimated. compute exact runs one extra solve with the plan's yes/no decisions fixed, so the values become exact.
- Open the validation report to see and fix the failing rules (Checks) closes Verify and opens the validation drawer; see Validation.
- Re-solve against the current model (Trail) appears when the model changed after the scenario solved. It closes Verify and runs the scenario again.
Export the evidence
Click Export and pick Evidence JSON or Evidence Markdown. The file downloads as
verify-<scenario>.json or .md. Where your workbook or brief spelled a name more than one way and the
model keeps one spelling, the file gives the name in your own spelling.
The Markdown file has everything in the drawer plus two sections the drawer doesn't show: the scenario's financial statements, checked against your goal's value, and a manifest of the source file and the model version it was solved against. As the drawer's footer says: "Assembled from the trace, source-data mapping, validation, and version history. Export is unsigned."
Limits
- The drawer is 460 pixels wide.
- Exports are unsigned.
- Verify needs a solved scenario; Base works too, BASE DATA doesn't.
Related
- Read results: Prove this number for one KPI
- Validation: the model's validation rules
- Run a what-if: regenerating stale scenarios
- Credentials: what the build itself proved
KPIs and custom metrics
Choose the numbers every scenario reports: add a KPI RIA suggests, build your own from two metrics, and rename, reorder or remove them.
Edit data in a model
Change a model's input numbers in a spreadsheet-style grid, save them as a what-if or preview them on the base model, and run the result.