Wall Crossing and Restricted Lists

A bank's investment banking division is advising a company on a takeover. Its trading desk, on the other side of an information barrier, has no idea this deal exists and can keep trading the company's stock freely. Then someone on the trading desk needs to be told — maybe to help structure the financing, maybe to advise on market impact. The moment that happens, that person has crossed from the "public" side of the firm to the "private" side, and they can never fully cross back for that piece of information.

This deliberate, controlled disclosure across an information barrier is called wall crossing. It isn't a leak or a breach — it's a formal, logged process. Before anyone is told the material non-public information, compliance requires them to be formally "brought over the wall": they acknowledge in writing that they now hold restricted information, understand the trading restrictions that follow, and agree not to pass it on further.

The moment someone crosses, their name and the affected security go onto the firm's restricted list (or "grey list," depending on severity). Anyone on that list — and often the whole team or desk they sit on — is barred from trading the named security, recommending it to clients, or discussing it in research, until the deal becomes public or is abandoned. The restricted list is checked automatically before trades execute, precisely so a wall-crossed employee can't (even accidentally) place an order that would look exactly like trading on inside information, because that is exactly what it would be.

The system only works if crossings are rare and deliberately gated — every crossing widens the circle of people who could leak or misuse the information, so compliance teams push hard to keep deal teams as small as possible and to log every single crossing with a timestamp and a reason.