How to Give a Transitioning Client a Real Date Their Account Will Finish Moving
To give a transitioning client a real completion date, do not quote one number. Quote two: the date most of the account lands, and the later date the tail clears. Build both from the start line, the ACATS floor, prep and signature time, the expected reject rate, and custodian queue time. AI sharpens each input; the advisor owns the promise.
The most damaging sentence in a transition is "it should only take a couple of weeks." It is almost always wrong, the client remembers it, and every day past it erodes the trust the whole move depends on. Clients sitting in the dark period between resignation and a fully moved account are already anxious, and a blown estimate is what turns anxiety into a call to the old firm. The instinct is to avoid the question or pad it with a vague range, but both read as evasive. There is a better answer: a completion date built from the parts that actually determine it, quoted as a range with named assumptions, and updated as the move progresses. Here is how to construct one you can defend and, more importantly, hit.
Why one date is always the wrong answer
A book move is not a single event with a single duration. It is a pipeline of accounts, each running its own cycle, with a long tail of items that settle weeks after the bulk of the money has landed. Quoting one date forces you to pick between two lies: an early date that ignores the tail, or a late date that makes you look slow on the 90 percent of assets that actually moved on time. Neither builds trust.
The fix is to separate two milestones the client cares about differently. The first is the "working" date, when most of the household's assets and the accounts they transact in have landed and the relationship is functional again. The second is the "complete" date, when the residual tail, the fractional shares, the annuity paperwork, the account frozen by a corporate action, has fully cleared. Telling a client "most of your money will be in place and usable by this date, and the last few odds and ends will finish by this later date" is both honest and reassuring, because it matches what they will actually experience. It also protects you, because the residual that lands in week seven is expected rather than a failure.
The six inputs that set a real completion date
A defensible date is the sum of six components, each of which you can estimate before the move and refine during it.
1. The start line. The ACATS clock cannot start until the receiving account is open and the transfer initiation form can be submitted, which usually depends on the advisor's registration being effective. If the U4 or RIA registration is not yet approved, the real start date is later than resignation day, and pretending otherwise is where most estimates go wrong. The transition paperwork sequencing that governs this is laid out in checklists like the Kitces 17-step breakaway transition process, and the start line is the first number you fix.
2. The ACATS floor. Once a clean full transfer is submitted, the timing is set by rule, not by effort. Under FINRA Rule 11870, the carrying firm validates within one business day and completes within three business days of validation, and FINRA's overview of customer account transfers confirms most accounts move through ACATS on this schedule. A clean account therefore has a floor of roughly six business days. You cannot compress this window, so it is the irreducible core of every estimate.
3. Prep and signature time. Before the TIF is submitted, someone has to extract the account data, build the forms, and collect client signatures. This leg is highly variable and usually the largest controllable chunk, because signature latency across a household can add days or weeks. Batching signatures by household compresses it, and it is often the difference between a fast and a slow book.
4. The expected reject rate. Some accounts will go not-in-good-order and run the cycle again. A book with a high NIGO rate does not just add a fix; each reject restarts the validation window. So your date has to price in the probability and cost of rejects, which is a function of the registration mix, the custodians involved, and how much you validate before submission.
5. Custodian queue time. The rule sets the maximum validation window, but a busy carrying firm's processing queue adds real days that no rule governs, a hidden delay documented in how custodian processing queues add days to every concurrent repaper. Estimate it from recent experience with that custodian, not from the rulebook floor.
6. The residual tail. Fractional shares, annuities, alternative investments, accounts frozen by a life event or corporate action, and anything ACATS does not carry will settle after the main transfer, sometimes months later. The tail is what separates the working date from the complete date, and naming it up front is what keeps a late residual from reading as a failure.
Turn the six inputs into two dates
Add the components, but do it as a range, not a point. For the working date, take the start line, add prep and signature time for the bulk of accounts, add the ACATS floor, add expected custodian queue time, and add a buffer for the share of accounts you expect to reject once. That gives you a most-likely window for when the transacting accounts and the majority of assets land. For the complete date, add the residual tail on top, sized by how many annuities, alts, and frozen registrations the book actually contains.
Quote the range with the assumption attached, the way a good throughput model forces you to. The related discipline of modeling a book's speed from concurrency, cycle time, and first-pass yield, covered in the repaper throughput model, is the same math viewed from the team's side; here you are translating it into a promise a single client can hold you to. The output the client hears is simple: "Based on your two custodians and the trusts in your accounts, most of your money should be in place by the week of X, and the annuity and a couple of small items should finish by Y. If a transfer bounces, it can add a few days, and I will tell you the moment it does."
Where AI turns the estimate into a live forecast
A static date printed on day one is only as good as the assumptions behind it, and the assumptions change as the move runs. This is where automation does real work, and it is the intersection that matters for a transition tool: not a faster form, but a sharper and self-updating forecast.
Before the move, an AI-native platform reads the book's statements and flags the inputs a human estimates by feel: the registration mix that predicts NIGO risk, the fractional and annuity positions that define the residual tail, and the settlement or pending-activity conditions that would push an account's start later. FastTrackr's document intelligence extraction is built to surface exactly these from a statement, and its advisor transition platform validates forms against custodian-specific rules before submission so the expected reject rate, one of the six inputs, drops. FastTrackr reports results like a 95 percent reduction in NIGO and moving books with zero NIGO in a two-week window; those are the company's reported figures rather than an independent benchmark, but the effect on a forecast is direct, because fewer rejects means fewer restarted clocks and a tighter, earlier date.
During the move, the same system tracks each account's ACATS status across custodians, so the forecast updates as accounts validate, reject, or land. That converts the day-one estimate into a live completion date the advisor can share with confidence, and it flags slippage early enough to tell the client before they notice. What AI does not do is make the promise or the judgment calls. It does not decide whether to wait on a large tax-sensitive position or exclude it, it does not choose how to word the update to an anxious client, and it never submits to a custodian on its own. The framing FastTrackr holds to is the right one here: AI drafts the forecast and validates the inputs, the professional owns the date and the conversation.
The table below maps each input to what sets it and where automation sharpens the estimate.
| Forecast input | What sets it | Where AI sharpens the estimate |
|---|---|---|
| Start line | Registration approval, account opening | Flags dependencies and readiness before day one |
| ACATS floor | FINRA Rule 11870, fixed by rule | Cannot change it; models it accurately per transfer type |
| Prep and signature time | Data extraction, household signature latency | Extracts data fast; supports household signature batching |
| Expected reject rate | Registration mix, custodian, pre-validation | Validates forms pre-submission, lowering the rate |
| Custodian queue time | Carrying firm processing load | Estimates from live status across concurrent moves |
| Residual tail | Fractionals, annuities, alts, frozen accounts | Identifies tail assets up front so they are scheduled, not a surprise |
The client conversation that protects the book
The date is only half the job; how you deliver it decides whether it builds trust. Lead with the working date because it is the one that changes the client's experience, name the complete date so the tail is expected, and state the one assumption most likely to move the date, usually a reject or a slow custodian. Then commit to proactive updates rather than waiting for the client to ask, because the anxious client who has not heard from you is the one who calls the old advisor. A short "your first account landed today, everything is on track for the week we discussed" is worth more than any polished timeline, and a live status view makes that message a matter of routine rather than a scramble. For consultants running many books at once, the same forecasting discipline is what lets transition consultants commit to dates across a portfolio of clients without hedging every one, and the advisor transition case study shows what that looks like when the estimate and the actual landing line up.
A real completion date is not a guess dressed up with confidence. It is six estimable inputs, quoted as two dates with a stated assumption, and updated as the move runs. Give the client that, hit it, and the move itself becomes the proof that they made the right choice following you.
Frequently asked questions
Why should I give a client two dates instead of one?
Because a book move has two milestones the client experiences differently: the point where most of their assets have landed and their accounts are usable again, and the later point where the residual tail of fractionals, annuities, and frozen accounts fully clears. A single date forces you to either ignore the tail and look wrong when it lands late, or pad for the tail and look slow on the money that actually moved on time. Two dates match reality, so the late residual is expected rather than a failure.
What is the fastest an account can realistically move?
For a clean full transfer, the floor is set by rule, not by effort. FINRA Rule 11870 gives the carrying firm one business day to validate and three business days after validation to complete, so a clean account moves in roughly six business days once submitted. But that floor assumes the registration is effective, the forms are correct, the account is in a transferable state, and the custodian queue is not backed up. The real date adds your prep and signature time and any reject cycles on top of that irreducible six-day core.
What most often makes a completion date slip?
Three things: a start line that was later than assumed because registration was not yet effective, a not-in-good-order reject that restarts the validation clock, and a residual tail that was never named up front. All three are predictable. You fix the first by fixing the start line before you quote a date, the second by validating forms before submission to cut the reject rate, and the third by identifying the tail assets during planning so they are scheduled into the later date rather than discovered as a surprise.
How does AI make a completion date more accurate?
It sharpens the inputs and keeps the date live. Before the move, it reads the book's statements to flag the registration mix that predicts reject risk, the fractional and annuity positions that define the tail, and the pending activity that would delay an account's start. During the move, it tracks each account's ACATS status across custodians so the forecast updates as accounts validate, reject, or land, and it surfaces slippage early. It does not make the promise or the wait-versus-exclude decisions, and it never submits to a custodian on its own; the advisor owns the date and the client conversation.
Should I share the date if I am not certain of it?
Yes, but share it correctly. Certainty is not the standard; a defensible estimate with named assumptions is. Quote a range rather than a point, state the working date and the complete date, name the one assumption most likely to move it, and commit to proactive updates. Clients do not expect a transition to be instantaneous. They expect to know what is happening and to hear from you before they have to ask, and a well-constructed range that you update beats a confident single date that you miss.
