Transition SLAs: Setting Repaper Turnaround Times a Recruiting Team Can Actually Commit To
Set transition SLAs by splitting the repaper timeline into segments you control and segments you do not. ACATS settlement and custodian validation are fixed by rule; intake, form build, and exception resolution are yours. Commit only on the controllable segments, tier by account complexity, and measure against submission dates, not settlement dates. That is an SLA you can hit.
A recruiting team wins an advisor partly on the promise that the move will be fast and clean. Then the operations team inherits that promise as a number it never agreed to, misses it on the first complex book, and the advisor's trust in the whole firm takes the hit. The fix is not to stop making commitments. It is to make commitments that map to what operations can actually control, and to say them in a way that survives contact with a trust account and an ACATS reject. This is how to build transition SLAs that hold.
Why the six-day ACATS number is not an SLA
The most common mistake is quoting the ACATS transfer cycle as if it were a transition SLA. A clean ACATS transfer completes in about six business days once the receiving account is open and in good order, with the carrying firm required to validate or take exception within three business days, as FINRA's customer account transfer rules lay out. That number is real, and it is also almost useless as a promise, because it describes one clean account after all the hard work is already done, not a book move.
A book is not one account, and the six days measures only the segment where the least can go wrong. The full transfer timeline by asset type shows how much lives outside that window: the data assembly before submission, the accounts that reject and rebook, and the assets that never touch ACATS at all. Continuity's breakdown of how long an advisor book transition really takes makes the same point from the field: the headline transfer figure and the lived transition timeline are different animals. Quote the six-day number as your SLA and you have promised the easy middle of a process whose hard parts sit on either side of it.
Decompose the timeline into fixed and controllable segments
An SLA you can hit starts by separating the parts of the timeline governed by rule and counterparty from the parts your desk owns. You commit on the second set and you communicate honestly about the first.
Fixed segments (not yours to promise):
- ACATS settlement cycle once a clean transfer is submitted and validated.
- The carrying firm's validation or exception window.
- Any medallion signature guarantee, transfer-agent step, or issuer paperwork on assets that fall outside ACATS.
- Registration effectiveness and U4 timing, which gate when repapering can even begin.
Controllable segments (where your SLA lives):
- Intake completeness: how fast and how cleanly you capture account data before drop day.
- Form build and pre-submission validation: how fast a specialist turns clean data into a submittable, low-NIGO package.
- Exception resolution: how fast a reject or a non-ACATS asset gets diagnosed and moved.
- Status visibility: how fast the advisor gets a truthful answer about where each account stands.
| Segment | Governed by | Typical shape | Your SLA lever |
|---|---|---|---|
| Registration and U4 | Regulator, new firm | Days to weeks, fixed | None, communicate it |
| Intake to submission | Your desk | Hours to days | Document extraction, checklists |
| ACATS validation and settle | Custodians, NSCC | About six business days clean | Pre-validation to avoid rejects |
| Exception resolution | Your desk plus counterparties | Days to weeks | Dedicated exception owner |
| Non-ACATS assets | Transfer agents, carriers | Weeks to months | Parallel workstream, early start |
Once the timeline is split this way, the SLA writes itself: you commit tightly on intake-to-submission and on how fast you resolve exceptions, and you set expectations rather than promises on the settlement and non-ACATS segments.
Tier the commitment by account complexity
A single blanket turnaround number fails because accounts are not uniform. Promising the same repaper speed for a clean individual brokerage account and a multi-trustee trust holding alternatives is how you miss. Tier the SLA instead, and tie each tier to whether the account rides straight through or breaks into an exception.
A practical three-tier structure:
- Tier one, straight-through: clean brokerage and standard retirement accounts that ride ACATS with no special handling. Commit an aggressive submission SLA here, because these are the roughly four in five accounts that should flow without drama. The straight-through processing rate is the number that predicts the whole move, so tier one is also where you protect your headline speed.
- Tier two, standard exceptions: accounts with a known wrinkle, a registration detail, a beneficiary re-designation, a margin or options feature that does not carry. These need handling but are predictable, so commit a longer, still firm SLA.
- Tier three, complex and non-ACATS: trusts and entities, restricted or control stock, annuities, alternatives, and held-away assets that move on their own tracks. Here you commit to a start date and a communication cadence, not a completion date, because too much of the timeline sits with transfer agents and carriers.
Tiering does two things. It makes your fast promise credible because it is scoped to the accounts that can actually be fast, and it makes the slow accounts a managed expectation instead of a broken promise.
Measure against submission, not settlement
The metric you attach to the SLA decides whether it is fair. Measure the desk against the dates it controls. The cleanest primary SLA metric is time-to-submission: from receipt of complete intake data to a validated package submitted to the custodian. That segment is almost entirely the desk's work, so holding the team to it is fair and actionable.
Settlement date is the outcome the advisor feels, so you report it, but you do not put the desk's SLA on it, because a custodian's validation queue and NSCC's cycle are not the desk's to control. Splitting the two, an internal submission SLA the team owns and a reported settlement estimate the advisor tracks, keeps accountability where the work is while still giving the advisor the whole-journey number they care about. The under-30-day repapering benchmark for ops directors is a useful outcome target, but the way you hit it is by driving the submission segment hard and keeping NIGO low, not by leaning on the custodian.
The levers that let you commit tighter
An SLA is only as aggressive as your process lets it be. Two levers move the controllable segments enough to let you promise more without missing.
The first is killing the data-entry and NIGO tax on the intake-to-submission segment. Hand-keying statement data is slow and error-prone, and every reject adds a one-to-three-week rebook that blows any SLA. AI document intelligence pre-fills forms from the brokerage statement and pre-submission validation catches the fields that cause most rejects, which both shortens the submission segment and stops the exceptions that would otherwise wreck the tier-one number. That is the core of what an advisor transition platform buys you: a shorter, more predictable controllable segment, which is exactly what an SLA needs.
The second is parallelism on the non-ACATS work. Complex and held-away assets have long, mostly-fixed timelines, so the only lever is to start them on day one rather than treating them as residual cleanup. Firms and transition consultants who launch the annuity and alternatives paperwork in parallel with the ACATS submissions compress the total move even though they cannot compress each individual step. The advisor transition case study shows the compounding effect of shortening the controllable segments across a real book.
Set SLAs this way and the recruiting promise and the operational reality finally line up. The team commits to what it controls, scopes the commitment to account complexity, measures against the dates it owns, and uses tooling and parallelism to keep tightening. That is an SLA an advisor can trust, which is ultimately what the recruiting team was trying to sell in the first place.
Frequently asked questions
Why can't I just promise advisors the six-business-day ACATS timeline? Because that number describes one clean account after the receiving account is open and the transfer is in good order, not a book move. The six days measures only the settlement segment, where the least can go wrong. It excludes the data assembly before submission, the accounts that reject and add one to three weeks of rework, and the assets that never ride ACATS. Quote it as your SLA and you have promised the easy middle of a process whose hard parts sit on both sides of it.
What part of the transition timeline should a repaper SLA actually cover? Only the controllable segments: intake completeness, form build and pre-submission validation, and exception resolution. The fixed segments, ACATS settlement, the carrying firm's validation window, registration and U4 timing, and non-ACATS transfer-agent steps, are governed by rule and counterparties, so you communicate expectations on them rather than committing. The cleanest SLA metric is time-to-submission, from complete intake data to a validated package submitted, because that segment is almost entirely the desk's own work.
How should I structure transition SLAs across different account types? Tier them. Tier one is straight-through brokerage and standard retirement accounts, roughly four in five of a book, where you commit an aggressive submission SLA. Tier two is accounts with a known, predictable wrinkle like a beneficiary re-designation or a non-carrying feature, where you commit a longer but firm SLA. Tier three is trusts, entities, restricted stock, annuities, and held-away assets, where you commit to a start date and a communication cadence rather than a completion date because the timeline sits with transfer agents and carriers.
Should the operations team's SLA be measured on submission or settlement? Submission. Time-to-submission is almost entirely the desk's work, so holding the team to it is fair and actionable. Settlement is the outcome the advisor feels and you should report it, but a custodian's validation queue and the NSCC cycle are outside the desk's control, so putting the team's SLA on settlement punishes them for a counterparty's pace. Keep two numbers: an internal submission SLA the team owns and a reported settlement estimate the advisor tracks.
What lets a team commit to tighter transition SLAs? Two levers. First, remove the data-entry and NIGO tax on the intake-to-submission segment: document extraction pre-fills forms from statements and pre-submission validation catches the fields that cause most rejects, which shortens the segment and prevents the one-to-three-week rebooks that break any SLA. Second, run non-ACATS assets in parallel from day one rather than as residual cleanup, so the long fixed timelines on annuities and alternatives overlap the ACATS work instead of extending past it.
