Intelligence
Build Scenarios, Compare Options, and Explain the Result
Build at least two scenario options, make assumptions visible, and present leadership a clear recommended path with one or two alternatives.
Updated June 5, 2026
Build a scenario
Use scenarios when you need to compare choices instead of looking at one recommendation alone: what happens if you defer, what changes under a tighter budget, which bundle of work should go first. Before building, confirm the asset list, costs, and risk context are clean.
- 01Open Scenarios.
- 02Choose the relevant scope.
- 03Select or build the option set to compare.
- 04Review the cost and risk implications.
- 05Compare the outputs before treating one as the answer.
Use at least two options so the result is a real comparison, such as repair versus replace, inspect versus defer, or phased versus immediate replacement.
Interpret and explain
Make assumptions visible: estimated cost, expected risk reduction, timing, confidence, and missing data. If a cost is rough, label it rough. Read each option by asking what it costs, what it reduces, what remains exposed, and what is deferred into later periods.
Present and revise
Present one recommended path and one or two alternatives, not every option. If the scenario output feels unrealistic, check scope, asset data cleanliness, and whether assumptions match operations. A good scenario helps people decide faster; if it cannot be explained in plain language, it is not ready. Revise after major work, updated readings, vendor estimates, condition changes, budget changes, or new dependency information.
Still need help?
Reach out for broken behavior, account-specific help, or billing questions.