How to Staff and Structure an Advisor Transition Desk at a Growing RIA
A dedicated transition desk needs four roles: an intake owner who captures account data before drop day, repaper specialists who build the paperwork, an exception handler for accounts that break, and a desk lead who sequences the pipeline. Plan the load as in-flight accounts per person, not advisors, and add capacity through tooling before headcount.
Most RIAs stumble into transition operations the same way. The first breakaway advisor is handled by whoever on the operations team has time. The second and third are squeezed in between everything else. Then recruiting lands four advisors in a quarter, the shared ops team drowns, NIGO rates climb, accounts sit in limbo, and the recruiting operations director gets a call asking why a $180 million book has been stuck for six weeks. The problem is not effort. It is that transition work was never given a structure of its own. This is how to build one.
Why a transition desk is different from your operations team
General operations and transition operations look similar and are not the same work. Day-to-day operations run steady-state processes: trades, billing, service requests, account maintenance. The volume is predictable and the tasks repeat on a known rhythm. Transition work is bursty, deadline-driven, and front-loaded with data assembly that has to happen before a hard compliance event, the advisor's U4 going live at the new firm, after which the advisor transition repapering clock is running and every day of delay is AUM sitting outside your fees.
Mixing the two guarantees the transition work loses. Steady-state operations has SLAs and angry clients when a trade breaks, so it wins the attention contest every time, and the transition backlog quietly grows until it becomes a retention problem. A transition desk exists to give the bursty, high-stakes work protected capacity that cannot be raided the moment a service ticket spikes.
The trigger to build one is volume plus concurrency. A firm doing one or two transitions a year does not need a desk. A firm that expects to run three or more advisor moves at once, or more than roughly six to eight in a year, has crossed the line where ad hoc handling starts costing measurable AUM and staff burnout.
The four roles on a transition desk
A functioning desk separates four responsibilities. At a small firm one person may wear two hats, but the responsibilities are distinct and should not be blurred, because each fails in a different way.
1. Intake owner. Owns everything that happens before drop day: collecting statements, confirming registrations and tax IDs, cataloguing account types, and flagging the assets that will not ride ACATS. This role is the single biggest determinant of downstream NIGO, because most rejects trace to bad or missing data captured at intake. The transition intake checklist a recruiting ops director should run is this person's core artifact.
2. Repaper specialist. Builds and submits the new-account paperwork, maps positions to the receiving custodian's forms, and drives each account through validation to submission. This is the production engine of the desk, and its throughput is what you are actually staffing for.
3. Exception handler. Owns the accounts that break: ACATS rejects, restricted positions, trusts and entities, held-away assets, and anything that falls outside straight-through processing. Roughly one in five accounts becomes an exception, and exceptions consume time out of proportion to their count, so giving them a dedicated owner keeps them from clogging the specialists' queue.
4. Desk lead. Sequences the pipeline across concurrent moves, sets priorities, owns the status view leadership asks about, and decides when to escalate. This is also the role that interfaces with compliance and with the receiving custodian. At scale the desk lead is a coordinator, not a producer.
| Role | Owns | Primary metric | Fails when |
|---|---|---|---|
| Intake owner | Pre-drop-day data capture | Data completeness at submission | Rushes intake, seeds downstream NIGO |
| Repaper specialist | Form build and submission | Accounts submitted per week | Overloaded, straight-through work stalls |
| Exception handler | Rejects and non-ACATS assets | Exception aging | Exceptions pile up unowned |
| Desk lead | Pipeline sequencing and status | On-time transition completion | Becomes a producer, loses the overview |
Set the load by in-flight accounts, not by advisors
The most common staffing mistake is planning capacity in advisors. Advisors vary enormously: a $90 million book might be 120 clean accounts, while a $90 million book heavy on trusts, alternatives, and held-away assets might carry the same headline AUM with three times the operational load. Staff to the work, and the unit of work is the in-flight account, weighted by complexity.
Build your model on a planning assumption you calibrate to your own data, not a borrowed benchmark. A workable starting assumption is that one repaper specialist can actively carry a set number of in-flight accounts at a time, with clean brokerage accounts counting as one unit and complex registrations counting as two or three. Track your actual throughput for two or three transitions and replace the assumption with your measured number. The point is the method: capacity equals specialists times accounts-per-specialist, and both sides are things you measure rather than guess.
Concurrency is the multiplier that breaks naive plans. Five advisors arriving in the same month is not five times one transition; it is a peak load that lands on the same desk at the same time, and if your capacity is sized for the average you will miss the peak badly. The playbook for managing concurrent transitions without adding headcount is really about surviving that peak through sequencing and automation rather than hiring for a spike that then goes idle.
Add capacity through tooling before headcount
When the desk is underwater, the reflex is to hire. Often the cheaper and faster lever is to raise the throughput of the specialists you already have, because a large share of transition hours goes into two tasks that automate well.
The first is data entry from statements. Hand-keying registrations, account numbers, and positions off brokerage statements into custodian forms is the most repeated task on the desk and the origin of most errors. AI document intelligence reads the statement and pre-fills the forms, which lifts a specialist's account-per-week number without adding a person. The second is pre-submission validation, which checks each form against known ACATS reject patterns before it goes out, so the exception handler is not buried in preventable rebooks.
The sequencing rule is simple: raise per-person throughput with tooling first, and hire only when your measured accounts-per-specialist is already strong and volume still exceeds capacity. Hiring into an inefficient process just multiplies the inefficiency, and adds fixed cost that hurts when recruiting has a quiet quarter. The advisor transition case study shows the effect of automating the high-volume data work before scaling the team.
When to build in-house versus lean on consultants
Not every firm should own the whole desk. The build-versus-partner decision turns on how steady your recruiting is. A firm with lumpy, unpredictable recruiting cannot justify full-time transition headcount that sits idle between deals, and is better served by variable capacity from transition consultants who flex up for a move and down after. A firm with a steady recruiting engine and predictable concurrency benefits from an in-house desk that accumulates institutional knowledge and moves faster because it knows your custodians and your compliance team.
Many firms run a hybrid: an in-house core of a desk lead and an intake owner who hold the process and the relationships, with specialist and exception capacity added from consultants during peaks. The classic 17-step breakaway transition process documented by Kitces is a good baseline for the work either model has to cover, so you can decide role by role which parts you own and which you rent.
Measure the desk so you can defend its headcount
A transition desk is a cost center until you measure what it protects, at which point it becomes the operational lever that preserves AUM in every move. Track it. The operational metrics a recruiting ops director should actually track give you the scorecard, but three numbers carry the staffing conversation with leadership.
Accounts-per-specialist-per-week is your throughput and the direct input to capacity planning. NIGO rate is your quality signal and the thing tooling should be visibly moving. Time-to-full-repaper is the outcome leadership feels, because a shorter number means AUM starts earning fees sooner and clients spend less time in the anxious limbo where they are most likely to leave. When you can show that a marginal hire or a tooling investment moves those three numbers, the headcount discussion stops being a plea and becomes a return calculation.
The industry data on transfer mechanics supports the urgency. A clean ACATS transfer runs about six business days once the receiving account is open and in good order, with the carrying firm validating or taking exception within three business days, per FINRA's customer account transfer rules. But a reject can add one to three weeks of diagnosis and resubmission, and the recent ACATS system upgrades that trimmed the standard cycle do nothing for the accounts your process rejects. A well-structured desk exists to keep accounts on the six-day path instead of the three-week one, at scale, which is exactly where a growing RIA earns or loses its retention numbers.
Frequently asked questions
When does an RIA need a dedicated transition desk instead of using its operations team? When transition volume and concurrency cross the point where ad hoc handling costs measurable AUM. A rough line is expecting to run three or more advisor moves at once, or more than six to eight in a year. Below that, the shared operations team can absorb the work. Above it, steady-state operations will always win the attention contest, the transition backlog grows unowned, and NIGO and timeline both suffer. A desk gives the bursty, deadline-driven work protected capacity that a service ticket spike cannot raid.
How many people do I need on a transition desk? Staff to in-flight accounts, not advisors, because a book's operational load depends on account complexity far more than headline AUM. Separate four responsibilities, intake, repaper production, exception handling, and desk lead, then size the production capacity from your measured accounts-per-specialist throughput times the number of specialists. At a small firm one person can hold two roles, but keep the responsibilities distinct because each fails differently. Measure your throughput over two or three transitions and plan from that number rather than a borrowed benchmark.
Should I hire more staff or buy transition software first? Raise the throughput of the staff you have before adding headcount. A large share of transition hours goes into statement data entry and catching rejects, both of which automate well: document intelligence pre-fills forms from statements, and pre-submission validation catches the fields that cause most NIGOs. Lifting per-person throughput with tooling is cheaper and faster than hiring, and it avoids adding fixed cost that hurts in a slow recruiting quarter. Hire only when your measured throughput is already strong and volume still exceeds capacity.
When should a firm use transition consultants instead of building the desk in-house? When recruiting is lumpy and unpredictable. Full-time transition headcount that sits idle between deals is hard to justify, so variable consultant capacity that flexes up for a move and down after fits better. Firms with steady, predictable recruiting benefit from an in-house desk that learns their custodians and compliance team and moves faster. A common hybrid keeps an in-house core of desk lead and intake owner and rents specialist and exception capacity during peaks.
What metrics prove a transition desk is worth its cost? Three. Accounts-per-specialist-per-week is throughput and the input to capacity planning. NIGO rate is quality and what tooling should visibly improve. Time-to-full-repaper is the outcome leadership feels, because faster repapering means AUM earns fees sooner and clients spend less time in the limbo where attrition happens. When a hire or a tooling investment demonstrably moves those three, the headcount conversation becomes a return calculation rather than a request.
