Regulatory Navigation Without Compromise

There’s a particular sound an examiner makes when the documentation they asked for has to be assembled instead of produced.

It’s the sound of a structure that was built around the regulator instead of through them.

Two Failure Modes That Look Like Navigation

Most middle-market institutions and the sponsors that work alongside them treat regulatory navigation as a compliance overhead — something the legal and risk functions handle after the deal closes, when the examiner shows up, when the rule lands. That posture survives in calm periods. It does not survive an active examination cycle.

The first failure mode is jurisdictional arbitrage as strategy. The deal moves to the most permissive structure available, the documents lean on the gap between two regimes, and the institution assumes the structural advantage will compound faster than the regulator will close the gap. Sometimes that’s true for a cycle. Across two cycles it almost never is — regulators learn faster than the arbitrage compounds, and the structures that depended on the gap have to be re-papered under duress, usually at the worst possible moment.

The second is compliance bolted on after the fact. The product gets designed, the structure gets papered, the deal closes, and then a parallel compliance file gets built to justify the structure to whichever regulator turns up to examine it. When the documentation exists, it’s a defensive document — written to a hypothetical examiner, not to the actual rationale that shaped the deal. When the examiner asks the harder follow-up — why this counterparty, why this trigger, why this carve-out — the file doesn’t answer and the firm assembles the response in real time.

Both failure modes look like regulatory navigation from inside the firm. From the regulator’s seat they look like the same posture: a structure that was not built to be examined.

What a Working Framework Actually Looks Like

The institutions that close cycles cleanly share four components. None of them are exotic. All of them are disciplined.

A regulatory taxonomy mapped to the product, not to the function. Most firms organize regulatory exposure by who handles it — legal handles X, compliance handles Y, treasury handles Z. The discipline is to organize it by which regulator examines which structural feature, so the team that designed the feature is the team that owns the conversation when the question arrives. Bolting “compliance review” onto the end of a product cycle is the structural mistake; building the regulator into the product-design team is what survives an exam.

Documentation written contemporaneously, not retrofitted. The rationale for a counterparty choice, a trigger level, a covenant carve-out, a jurisdictional structure — written at the moment the choice was made, by the person who made it. Examination-grade documentation is not a stack of memos; it’s a real-time record of how the structure took the shape it took. Firms that build this discipline find that the examiner’s question is a conversation. Firms that don’t find it’s an audit. (The same documentation-at-decision discipline shows up in model governance — we worked through it in When the Model Says No.)

A named regulatory owner per product with an active two-way relationship. Not a quarterly compliance update — a relationship where the regulator’s last substantive conversation with the firm was inside the last sixty days, and the firm knows what’s on the examiner’s mind before the examination opens. This is built one conversation at a time, in calm periods. It cannot be assembled when an inquiry arrives.

An escalation path for regulatory inquiry that mirrors the credit escalation path. When a regulator asks a question that warrants escalation, who has authority to respond? At what level does it move from line response to senior management response? When does it warrant board notification? Firms that write this down before the inquiry arrives respond in days. Firms that improvise spend the first two weeks debating authority — the same failure mode that traps credit escalation, applied to regulatory inquiry. (We laid out the parallel escalation discipline for structured-credit covenants in The Board Question Structured Credit Should Ask More Often.)

Three Questions the Board Should Ask Every Cycle

Once the framework is in place, the oversight cadence collapses to three questions.

1. If an examiner asked for the rationale behind any of our top five structural decisions this period, does the documentation exist today or would we have to assemble it? A board that hears “we’d assemble it” has a structure built for calm. A board that hears “it exists, written by the person who made the decision, dated” has a structure built for examination.
2. For each of the regulators whose oversight matters to us, when was the last substantive two-way conversation, and what was its content? Substantive is the qualifier that does the work. Quarterly attestation is not a conversation. A working relationship is.
3. What part of our current structure is sitting on a jurisdictional or regulatory arbitrage that the relevant regulator has not yet tested? Naming it is the first move. Pretending it isn’t there is the failure mode.

Three questions, ten minutes of board time per period. That cadence is what separates institutions that get examined from institutions that get surprised.

“Regulators don’t surprise the institutions that built for them. They surprise the ones that built around them. Examination is confirmation, not discovery.”

Why This Matters More Across the Next Cycle

Basel III endgame finalization, the reshaping of the SEC’s private fund rules after the Fifth Circuit vacatur, AIFMD II implementation across European credit vehicles, the rising volume of state-level scrutiny on private credit and middle-market direct lending — the regulatory surface in 2026 and 2027 is wider than it has been since the Dodd-Frank cycle. The institutions that have been building examination-grade documentation in real time across the last three years will read the new perimeter and adjust at structure-design level. The institutions that have been treating compliance as overhead will discover the perimeter the same way they discovered the last one — through inquiry letters they cannot answer in the timeframe the regulator expects.

Thirteen years inside GE Capital Special Situations taught the same lesson at scale. A hundred-plus portfolio companies, $45 billion in transaction volume, working alongside the OCC, the Fed, the FDIC, and a half-dozen state authorities — the deals that closed cleanly across the cycle were the ones where the regulator’s questions were anticipated in the term sheet, not in the exam. The deals that didn’t were the ones where the structural advantage was real until the examiner asked the second question.

At Pluribus Capital, regulatory navigation is built into the structure design before the first commitment letter goes out. Examination is confirmation, not discovery. That’s the operating standard. The next cycle will test it, and the framework has to be built before the test.