Deal Code Risk System
Track every investment idea by downside, hedge quality, and batting average
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 7
- Confidence
- 97%
The Deal Code Risk System assigns a numerical identifier to every investment idea so its thesis, hedge, downside, result, and owner can be evaluated independently. Rather than relying only on aggregate portfolio profit, the method asks whether each trade was structured to survive a reasonable worst-case outcome and whether a manager repeatedly makes sound decisions. Idea-level attribution produces a batting average: the proportion of distinct ideas that succeed. This separates repeatable skill from a small number of oversized wins and helps transmit one risk philosophy across multiple risk takers. Portfolio construction then becomes a controlled collection of limited-loss ideas rather than an opaque bundle of positions.
Origin
Sander Gerber developed the deal code system after leaving the American Stock Exchange floor and hiring other people to run strategies in his personal trading account. He needed to scale his own risk discipline across multiple risk takers while pursuing persistent profitability.
Core principles
- 01Manage unexpected loss rather than trying to eliminate all losses
- 02Evaluate each investment idea as a distinct unit of risk
- 03Quantify a reasonable worst-case outcome before committing capital
- 04Judge process quality across many decisions, not one outcome
- 05Seek to win more ideas than you lose
How to run it
- 1
Define the investment idea
Describe the thesis, catalyst, expected payoff, and conditions that would invalidate the trade. Treat related positions expressing the same thesis as one idea.
Pro tip Keep the thesis concise enough that another risk taker can restate it accurately.
Watch out Do not disguise one concentrated thesis as several supposedly independent trades.
- 2
Assign a deal code
Give the idea a unique numerical identifier and attach every position, hedge, and adjustment associated with it.
Pro tip Use the code consistently in orders, risk reports, and post-trade reviews.
Watch out Inconsistent coding will corrupt idea-level attribution.
- 3
Map the hedge
Record what risks the hedge removes and what exposures remain. Test whether the hedge would still work during the event or dislocation that threatens the trade.
Pro tip Describe the hedge economically rather than relying only on statistical correlation.
Watch out A historically correlated asset may stop behaving like a hedge during stress.
- 4
Quantify reasonable worst-case loss
Estimate how much the complete idea could lose under a severe but plausible scenario. Include gaps, liquidity deterioration, and hedge slippage.
Pro tip Use event scenarios that could actually change the distribution of returns.
Watch out Do not mistake an ordinary volatility estimate for a worst-case scenario.
- 5
Size for survival
Set exposure so the portfolio can withstand the estimated loss and continue operating. Consider the combined downside of ideas vulnerable to the same event.
Pro tip Reduce size when the downside cannot be bounded with confidence.
Watch out A strong thesis does not justify a position that can threaten survival.
- 6
Score the outcome
After resolution, classify the idea as a win or loss and compare the actual path with the original thesis and downside estimate.
Pro tip Evaluate whether the decision was sound even when the monetary outcome was unfavorable.
Watch out Do not rewrite the original thesis after seeing the result.
- 7
Review the batting average
Measure how frequently each manager wins at the idea level alongside total profit and loss. Investigate dependence on a few unusually large outcomes.
Pro tip Review patterns by strategy, catalyst, and market environment.
Watch out Dollar profit alone can conceal weak, nonrepeatable decision quality.
In the wild
A portfolio manager assigns one code to a merger trade comprising the target shares, an acquirer hedge, and options protecting against deal failure. The team estimates the loss if regulators block the transaction, sizes the position to survive that scenario, and records the final result against the original thesis.
→ The complete economic idea is evaluated coherently instead of treating each security as an unrelated position.
After leaving the trading floor, Gerber developed strategies and hired other people to operate them. Deal codes allowed him to examine each person's hedging, downside, and frequency of successful ideas while applying one risk discipline across the growing account.
→ A personal trading process became a scalable multi-manager risk system.
Common mistakes
Tracking only portfolio-level profit
Aggregate gains can hide repeated poor decisions or dependence on one oversized winner. Review both dollars and the number of successful ideas.
Using vague downside estimates
A label such as low risk is not actionable. Specify the plausible scenario, estimated loss, and assumptions behind it.
Treating statistical correlation as a hedge
Historical co-movement may disappear during the event that matters. Explain why the hedge should work under the relevant stress scenario.
Is it for you?
Best for
It is best for active investors, trading teams, and multi-manager portfolios with discrete investment theses.
Not ideal for
It is not ideal for passive portfolios whose holdings are not managed as individual event-driven ideas.
From the transcript
“a deal code is just a numerical moniker that we put on each trading idea within the book”
“Risk management is not about not losing money. Risk management is about unexpectedly losing money.”
“I think it's not just about winning more dollars than you lose. It's about winning more ideas than you lose.”
From the episode
Inside the Gerber Statistic with Sander Gerber of Hudson Bay Capital
Sander Gerber