Skip to content
All library documents

Naming Caps and Spreads in Monthly Sum Options

Article Quant Q&A · Author: sooprise
Read the original

Summary

The document addresses how to describe a cap or spread attached to a monthly sum option. It asks whether these elements should be categorized as features or limits, highlighting that terminology may depend on the audience and the purpose of the description.

The answer recommends “boundary conditions” when speaking with quantitative practitioners, and “terms” or “features” when speaking with traders. This is a naming distinction, not an explanation of how caps or spreads affect an option’s payoff, valuation, or risk. No contract specification, pricing method, or example is provided, so the guidance is useful mainly for communication and documentation. It does not establish a universal industry standard; the suggested wording is presented as the respondent’s own practice and varies by audience.

Key ideas

  • A cap or spread on a monthly sum option can be described using different terms depending on the audience.
  • “Boundary conditions” is suggested for communication with quantitative practitioners.
  • “Terms” or “features” is suggested for communication with traders.
  • The document offers terminology guidance rather than payoff or valuation analysis.

Tags

OptionsDerivatives pricing
Full text
# How Would You Categorize A Cap or Spread On A Monthly Sum Option?


# How Would You Categorize A Cap or Spread On A Monthly Sum Option?












I'm just trying to determine the appropriate naming convention for a category that holds cap or spread, or in other words, what category can I put cap and spread (in this context) into? Are they "Features" of a monthly sum option, or "Limits" ... I really don't know.

## Answer by Brian B (score 2, accepted)

https://quant.stackexchange.com/a/2111

When speaking with quants, I call such things Boundary Conditions. With traders I tend to use Terms or Features.

Shown in full with attribution under the source's licence. Licence: CC BY-SA 4.0 (Stack Exchange)

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.