Short reads from the people who ran the mandate.

Where it starts: clearing and settlement

Every operations career in capital markets starts the same way, learning that a trade isn't done when it's executed, it's done when it settles. T+2 became T+1, netting at NSCC compresses thousands of offsetting trades into a single position, and the daily discipline is simple to state and hard to live: check that everything actually settles, and if it doesn't, find out why before it becomes someone else's problem tomorrow.

This is where you learn the instinct that defines the whole career: the platform is built for the trade that behaves. The one that doesn't, the mismatched instruction, the late confirmation, the broker who reports a position differently than the custodian, becomes a manual exception the moment it deviates from the expected path. Nobody designed it that way on purpose. It is just where the product roadmap stopped and a person started.

The first real gap: domestic proxy

Move from settlement into shareholder communications and the same pattern reappears at a larger scale. A single US proxy vote travels from the issuer's DEF 14A filing to the transfer agent, to DTC's systems, to Broadridge, which ingests and redistributes the agenda to roughly ninety-seven percent of beneficial holders, to the broker-dealer, which transforms it again for its own client interface, before it finally reaches the investor. Four transformation steps for one shareholder communication, each one a fresh opportunity for the instruction to drift from what the issuer actually filed.

This is where NOBO and OBO classification, non objecting and objecting beneficial owners, first taught me that the system wasn't built to see the actual investor at all. The issuer doesn't know who its shareholders are. It knows who its broker-dealers are, and trusts that the cascade downstream reconstructs the rest correctly. Most of the time it does. When it doesn't, the vote is wrong, and nobody upstream necessarily finds out.

The same gap, multiplied: global proxy

Then the scope widens again, and this is where it stops being one chokepoint and becomes more than a hundred of them. Managing shareholder communications and proxy voting internationally means Switzerland's filing windows, Japan's record date logic, Brazil's notarised power of attorney requirements, and India's NSDL and CDSL e voting timelines, all live simultaneously, all subject to change without a central notice, none of them written down in a single place a new team member could simply read.

Almost none of this lives in any product. The platforms were built to handle the common case, the standard deadline, the expected format. Everything outside that, which in a hundred plus markets is most of it, gets absorbed by operations. We built the workarounds. We tracked which countries needed physical signatures. We remembered which custodian in which market still required a fax, an actual fax, well into this decade. None of it showed up on a roadmap, because from the product team's perspective, the job looked done.

The throughline

What connects clearing and settlement, domestic proxy, and global proxy isn't three different problems. It is the same one, appearing at a larger scale each time the aperture widens: the infrastructure handles the expected case, and a person becomes the seam for everything else.

The reason that seam matters is that it is holding up something real, actual capital, actual ownership, actual votes on actual corporate decisions. When it fails, a shareholder gets disenfranchised or a position settles wrong, not because anyone was careless, but because the person holding the exception in their head made a mistake a machine would not have made, or left the firm before writing it down.

What would actually change this is not less complexity. Every jurisdiction will keep doing its own thing regardless of what infrastructure sits underneath it. What changes it is encoding the deadline, the notarisation rule, and the settlement logic directly into the transaction itself, so the system checks the current rule at execution instead of relying on someone remembering it correctly at seven in the morning. That is not a smaller job. It is a different one, and it is overdue.