CIRO Trader study materials
CIRO Trader study resources

The Option Overlay That Doubled the Risk

CIRO Trader · Put your knowledge to work in context.

All case studies

The Option Overlay That Doubled the Risk

A client with a balanced portfolio and a stated maximum drawdown tolerance of 10% is pitched a structured note linked to an equity index. The note pays a coupon of 6% annually but includes a knock-in barrier at 70% of the initial index level. If the barrier is breached, the client's principal is exposed to the full downside of the index from the initial level, not from the barrier. The note is principal-protected only if held to maturity and only if the issuer remains solvent. The salesperson's illustration shows the coupon and the protection but not the knock-in scenario. The client's file records the 10% drawdown limit. The note is issued by a single A-rated bank, and the client's portfolio already has 15% exposure to that bank's paper.

1. Is the note suitable for this client? Explain the analysis, not just the conclusion.

Read the worked answer

Suitability requires matching the product's risk to the client's stated tolerance and existing exposures. Here the note's payoff is not what the illustration implies.

The 6% coupon is compensation for selling downside protection. If the index falls below 70% and stays there at maturity, the client loses principal measured from the initial level - so a 40% index decline produces roughly a 40% loss, not a 30% loss. That is incompatible with a 10% maximum drawdown tolerance unless the position is small enough that the portfolio-level drawdown stays within limits.

The issuer concentration is a second problem. The client already holds 15% of the portfolio in that bank's paper; adding a note whose principal protection depends entirely on the same issuer increases correlated exposure. If the bank's credit deteriorates, both the existing paper and the note's protection are impaired at the same time.

The salesperson's illustration omitted the knock-in scenario. Presenting the coupon and the protection without the loss scenario is misleading, even if every statement in the illustration is literally true.

2. What must the salesperson have disclosed, and what does the omission suggest about the firm's controls?

Read the worked answer

The salesperson needed to disclose: the knock-in mechanics and that the barrier measures loss from the initial level; that principal protection is conditional on issuer solvency and holding to maturity; the issuer credit risk; the liquidity terms (structured notes often have limited secondary markets); and the fees embedded in the note.

The omission of the knock-in scenario is the most serious. A payoff diagram that shows only the coupon and the protected zone is not a balanced presentation. The client cannot evaluate a product whose downside is invisible.

The omission also suggests a control weakness: if the firm relies on salesperson-prepared illustrations, there should be a review process confirming that downside scenarios are shown. The fact that the illustration reached a client with a documented 10% drawdown limit indicates that review either did not happen or did not test for suitability.

3. If the client insists on investing, what conditions would make a limited allocation defensible?

Read the worked answer

A small allocation can be defensible if the portfolio-level drawdown remains within the 10% tolerance under the knock-in scenario. That requires sizing the position so that the worst-case loss, weighted by probability and correlated with the rest of the portfolio, stays inside the limit.

It also requires written acknowledgment from the client that they understand the knock-in, the issuer dependence, and the illiquidity - and a documented rationale from the advisor explaining why the position is consistent with the client's objectives despite the mismatch at full size.

The issuer concentration should be addressed separately: either reduce the existing bank exposure or cap the combined exposure. Simply adding the note and calling the client 'aggressive' in the file would not cure the problem.