The Star Trader and the Missing Limit
A proprietary trading desk at a mid-sized securities firm has produced 40% of the firm's revenue for three consecutive years. The desk's head trader has been with the firm for eleven years, reports directly to the CEO rather than to the head of trading, and has authority to approve his own trades up to $50 million notional. The risk function's limit framework sets a value-at-risk limit of $8 million for the desk, monitored daily. For eight months, the desk's reported VaR has clustered between $7.6 million and $7.9 million, never breaching. A new risk analyst notices that the desk's positions include a large illiquid position in a private credit fund that the VaR model values using a stale mark from the fund's administrator, updated monthly. The analyst recalculates VaR using a proxy index and gets $14 million. She raises it with her manager, who says the model is validated and the desk is a major revenue contributor, and asks her to "document the proxy as an alternative view" rather than escalate.
1. Identify the control failures in this setup and explain how the reporting structure and the stale mark interact to conceal risk.
Read the worked answer
The control failures compound each other, which is why the reported VaR looks so stable.
Reporting line. The head trader reports to the CEO, not to the head of trading. This removes the layer of management that would ordinarily challenge position-taking and set limits. It also means the desk's limit breaches would escalate to the CEO, who has a direct interest in the revenue the desk produces. Independence is compromised at the top, not at the bottom.
Self-approval. Authority to approve his own trades up to $50 million notional means the first line is also its own second line for a large part of the book. No pre-trade limit check is performed by anyone with an incentive to say no.
The stale mark. The private credit fund position is valued monthly by the administrator. A VaR model that consumes that mark treats an illiquid asset as if it repriced monthly. Between marks, the model sees no volatility, so the position contributes almost nothing to VaR. The desk's reported VaR is therefore not measuring the risk of the position; it is measuring the absence of price updates. The clustering between $7.6 million and $7.9 million against an $8 million limit is a symptom, not a comfort: when a model cannot see a risk, the reported number drifts toward the limit without breaching, because nothing in the model is generating the variation that would push it through.
The interaction. The stale mark suppresses measured risk; the reporting line suppresses challenge; the self-approval suppresses pre-trade control. Each failure would be serious alone. Together they mean the desk's true risk is invisible to everyone except the analyst who looked.
The proxy recalculation. The $14 million figure is not necessarily exact, but it demonstrates that the model's output is highly sensitive to the valuation input. A risk number that moves by 75% when a mark is replaced by a proxy is not a reliable limit measure.
2. The analyst's manager asks her to document the proxy as an "alternative view" rather than escalate. Evaluate this instruction and advise the analyst on her professional obligations and practical options.
Read the worked answer
The instruction is a request to downgrade a material risk finding to a footnote. The analyst should not comply as framed, and the reasoning matters more than the conclusion.
The finding is not an alternative view. An alternative view is a different but defensible interpretation of the same evidence. Here the evidence is that the primary model consumes a stale mark and the proxy produces a materially higher risk estimate. Documenting that as an alternative view would leave the official VaR at $7.9 million and the limit framework operating on a number the analyst believes understates risk by roughly 75%. If the firm later suffers a loss on the position, the documentation trail will show the analyst identified the issue and it was filed rather than escalated.
Her professional obligations point in one direction. Risk professionals are expected to report material risk issues through the appropriate channel, to avoid misrepresenting risk, and not to allow commercial pressure to suppress a finding. The manager's reference to the desk being a major revenue contributor is precisely the pressure that the obligation exists to resist.
Practical options, in order:
- Put the finding in writing to her manager. State the recalculation, the method, and the conclusion that reported VaR understates risk. Ask for a decision in writing. This converts a conversation into a record.
- Escalate within risk. If the manager will not escalate, go to the next level in the risk function, then the CRO. Most firms' policies protect good-faith escalation of risk concerns.
- Use the whistleblowing or speak-up channel if internal escalation is blocked. This is not disloyalty; it is the mechanism the firm has for exactly this situation.
- Document her own analysis fully, including the proxy methodology and its limitations, so the work stands on its own.
She should also be clear about what she is and is not claiming. She is not claiming the proxy is the true VaR; she is claiming the primary model is unreliable for this position and the true risk is materially higher than reported. That claim is defensible and should be escalated, not filed.