The promotion makes sense on paper. The ops manager who built the firm’s compliance program from scratch, who knows where every policy lives and why every procedure exists, and who has been the de facto CCO for three years while carrying the ops title has earned the broader role. The firm is growing. The job needs to grow with it.
What does not get discussed in the promotion conversation is what happens to compliance during the transition period. Not the policy, not the platform, and not the written supervisory procedures, those stay. What leaves with the ops manager’s old role is the institutional memory, the informal ownership, and the habit of attention that kept the compliance program running without anyone formally noticing.
There’s a window that opens when that person steps into the new role. Sixty to ninety days, sometimes longer. During that window, nobody owns compliance the way it was owned before. The new person hasn’t started yet, or has started but is still finding their footing. The promoted ops manager is managing their own transition and can’t carry both jobs. The firm keeps moving.
This is when things fall through. And they fall through in a specific order.
Week One Through Three: The Calendar Nobody Is Watching
The first thing that breaks is timing. Compliance programs run on calendars: attestation cycles, marketing review queues, vendor renewal dates, and trade surveillance exceptions that need to be cleared on a defined schedule. When the person who owned those calendars steps into a new role, the calendar doesn’t disappear. It just stops having someone watching it.
The items that were due last Tuesday don’t announce themselves as overdue. They sit. The attestation that was supposed to go out on the first of the month doesn’t go out. The vendor whose annual review was due in the second week of the transition doesn’t get reviewed. The marketing piece that was submitted for compliance approval before the transition sits in a queue that nobody is actively managing.
None of this is visible from the outside. The firm is operating normally. Clients are being served. Revenue is coming in. The compliance calendar is running three weeks behind and nobody has noticed yet because the person who would have noticed is now focused on something else.
The risk that accumulates in weeks one through three isn’t dramatic. It’s a gap in the attestation cycle, a delayed vendor review, a marketing approval that’s taking longer than it should. Each one is recoverable. Together they represent the beginning of a documentation trail that will need explanation if an examiner asks about the period.
Week Four Through Six: The Institutional Memory Problem
By week four, the new person, whether an external hire or an internal transition, is starting to ask questions. Where does the marketing review process live? Who approves employee personal trading disclosures? What’s the procedure for flagging a trade surveillance exception?
The answers to these questions exist. They’re in the written supervisory procedures, the compliance platform, the shared folder that the previous person organized. What is not in any of those places is the context: why the procedures were built the way they were, which vendors require closer attention, which advisors have historically needed more supervision, and which exceptions have been recurring patterns versus one-off anomalies.
The promoted ops manager knows all of this. They built it. But they’re not available to walk someone through it in the depth required, because they’re now managing their own expanded responsibilities. The fifteen-minute conversation that would transfer the critical context keeps getting pushed to next week.
What fills the gap is improvisation. The new person makes reasonable decisions with the information available to them. Most of those decisions are fine. Some of them miss the context that would have made them better. A trade surveillance exception that was flagged as low-risk based on a pattern the previous person understood gets cleared without the same judgment being applied. A vendor renewal gets processed without the specific documentation standard the previous person maintained because nobody told the new person the standard existed.
The compliance program keeps running. It’s running slightly differently than it was. The difference isn’t visible yet.
Week Seven Through Ten: The First Real Gap
This is when something concrete breaks, not a near miss, but an actual documented failure that will need to be addressed.
The most common version: an attestation cycle that closed with incomplete documentation. The cycle ran, and most employees completed it, but the tracking and follow-up the previous person handled manually, including individual emails to stragglers, spreadsheet reconciliation, and confirmation that every supervised person’s record was updated, did not happen with the same rigor. The cycle shows as complete. The underlying documentation has gaps.
The second most common version: a marketing piece that went live without a completed compliance review. The new person was working through the review queue, the advisor was under deadline pressure, and something went out before the formal approval was logged. The review may have happened informally. The record of it didn’t happen at all.
The third: a vendor whose re-review was due during the transition window and didn’t get done. Not because anyone decided to skip it, but because nobody was tracking the renewal calendar closely enough to catch the date before it passed.
Any one of these is a correctable finding. The problem is that they tend to cluster in the same 60–90 day window, which means when the new CCO gets settled and starts doing a program audit, or when an examiner asks about the period, the gaps tell a story. Not a story of negligence, but a story of a compliance program that was not built to run without a specific person’s active attention.
That’s the real finding. Not the missed attestation or the late vendor review. The infrastructure that depended on one person’s habits rather than the program’s own structure.
The Question Worth Asking Before the Promotion Happens
Most firms handle the compliance transition the way they handle most personnel transitions: they post the job, find a replacement, and expect the new person to pick up where the last one left off. The written procedures exist. The platform is there. The handoff should be straightforward.
What the written procedures do not capture is the operating rhythm, the specific habits of attention that kept the compliance program current. The person who checked the vendor renewal calendar every Monday morning. Who knew that one particular advisor consistently submitted marketing content late and needed a proactive check. Who maintained the attestation tracking spreadsheet in a specific way that made completions auditable.
These habits aren’t written down because they were never recognized as compliance infrastructure. They were just how that person worked. When that person transitions out of the role, the habits leave with them, and the program runs on the documentation alone until someone builds the habits back.
The firms that navigate this transition cleanly do not avoid it. They anticipate it. The compliance transition plan gets as much attention as the org chart change. The outgoing person documents not just the policies and procedures but the operating rhythm: what gets checked when, what the recurring exceptions look like, where the judgment calls live. The incoming person has a ramp that includes the context, not just the files.
And the compliance infrastructure itself, including the calendars, workflows, and escalation logic, is built to run on its own by surfacing what needs attention without depending on someone remembering to look.
The 60–90 day window is real. It opens every time someone who informally owned compliance moves into a role where that’s no longer their primary job. The firms that close it quickly are the ones that saw it coming and built for it. The ones that discover it later are the ones that find out during an exam that their compliance program was one person’s habits, not a system.
Smartria’s compliance calendar, automated workflows, and escalation logic are built to keep the program running through transitions, not because the right person is watching, but because the system is. If your firm is navigating a compliance ownership change, [that is the conversation worth having before the gap opens, not after.]
