Building a downside scenario for a managed account

A downside scenario asks how capital and access might change if adverse conditions occur together. It neither predicts a crisis date nor establishes the maximum possible loss. Its purpose is to expose sensitive assumptions rather than base decisions only on ordinary or optimistic conditions.

Define the decision question before the number

Are you examining value declines, time to usable funds or several accounts’ dependence on one host? A single table without an objective can mix those questions. Record currency, horizon and covered assets, expressing firm personal needs without private payment details.

Separate assumptions into layers

Market moves, changing exit costs, margin constraints and withdrawal delays are different phenomena. For each layer, document the source or rationale and exclusions. Where actual information is limited, describe the scenario as educational and bounded; missing information must not become zero risk.

A hypothetical combined effect

Suppose opening value is 1,000 units in a simple scenario without leverage or cash flows. A twenty-percent decline reduces it to 800. If a separate additional cost of 10 has not already been included, the calculated remaining value is 790. Record access delays separately. This example determines neither probability nor a loss ceiling.

What belongs in a scenario table?

• The assumed event and selection rationale.
• Affected assets or routes and common dependencies.
• The calculation method with clear units and basis.
• Value effects and access-time effects shown separately.
• Limitations, unavailable data and the decision question.

Remember shared effects

Several managers may rely on the same market factor or infrastructure under pressure. Combining independent scenarios without considering that relationship can create an incomplete picture. Conversely, do not count one shared charge or loss twice. Explain the combination method within the evidence’s scope.

Examine sensitivity to assumptions

Check what happens when one important assumption changes. If a small difference makes the plan inconsistent, highlight that dependency. Selecting only a scenario that makes an earlier decision appear acceptable is not independent review. No finite set of scenarios covers every possible event. Retain assumption dates and versions; changes in account structure or withdrawal routes require reassessing the earlier scenario.

The output is a better question, not an automatic instruction

Record unresolved conditions, the no-action alternative and independent-review needs. When reviewing accounts, read scenarios alongside actual service terms and use calculation tools with defined assumptions. This framework recommends no allocation, guarantees no capital resilience and claims no complete live stress model in the product.