The RIA Recruiting Operations Director's Transition Intake Checklist: The Data Points to Capture Before U4 Drop Day
The transition intake happens before the advisor resigns, and it determines whether repapering runs clean or stalls. As a recruiting operations director, your job is to capture the right client and account data in advance, structure it so it flows into your CRM and account-opening workflow, and stay on the correct side of the pre-resignation data line. Capture too little and you rekey everything under deadline pressure. Capture the wrong things too early and you create a compliance problem before the advisor has even dropped their U4.
Here is the intake checklist, organized by what it is for and where the boundaries sit.
The pre-resignation data boundary comes first
Before any field goes into a spreadsheet, settle what the advisor may and may not take before the resignation date. If both firms are Broker Protocol members, the Protocol permits a narrow, defined set of client contact fields and nothing more. If a firm has left the Protocol, the rules change entirely. This is not an operations judgment call; it is a compliance and, often, legal one.
Two things belong to compliance and counsel, not intake: what the advisor pre-stages before resignation, and what data can move at all. Our Broker Protocol compliance checklist on what you can take and where software draws the line covers the permitted fields, and the boundary between what covers your workflow and what does not is laid out in exactly what the Protocol covers and what it does not. Build your intake template so it only holds fields that are cleared to hold. The full account detail that fills in the rest is captured after the U5, from the client's own statements.
Client identity and contact data
The Protocol-permitted contact set is the backbone of the early intake. Capture it cleanly and structure it for your CRM, whether that is Redtail, Wealthbox, or Salesforce Financial Services Cloud, from the start:
- Client name and preferred name
- Home and business address
- Phone numbers
- Email address
- Account title as it will register at the new firm
- Household grouping, so related accounts move and report together
Getting the household relationships right at intake is what lets you sequence transfers and communication by relationship value later.
Account and asset data
This is the layer that drives ACATS and account opening, and much of it is finalized post-U5 from statements rather than pre-staged. Track these fields per account:
| Field | Why it matters at intake |
|---|---|
| Account type and subtype | Determines the receiving account to open and whether ACATS will validate the type |
| Registration / ownership | Trust, joint, individual, entity; drives titling and signer authority |
| Custodian and account number | Identifies the delivering firm for the transfer instruction |
| Tax ID / SSN | Must match the carrying firm's record or the transfer rejects |
| Approximate assets and positions | Flags nontransferable or restricted holdings early |
| Cost basis and elections | Preserves tax treatment and beneficiary detail on retirement accounts |
| Beneficiary designations | Required to reconstruct IRA and retirement registrations accurately |
The reason to capture asset detail early is that nontransferable positions and account-type mismatches are two of the most common ACATS reject drivers. Flagging them at intake means you plan the residual or liquidation path before submission instead of discovering it as a NIGO.
Where document intelligence replaces manual intake
The account layer is exactly where hand-keying breaks down. Pulling account numbers, tax IDs, registrations, and positions off client statements by hand, across a full book, is slow and error-prone, and every mistyped field becomes a downstream reject. Document intelligence extracts those values directly from the source statements and forms, so the intake record is populated from the document rather than a rushed rekey. Inside an advisor transition platform, that structured intake feeds pre-submission validation and account opening without a second round of data entry.
Turning intake into a repeatable operation
For an operations director running more than one transition at a time, the intake checklist is not a one-off document; it is a template you standardize and reuse. Consultants who run transitions at scale, and transition consultants FastTrackr serves, treat intake as the front of a repeatable pipeline where the same fields, in the same structure, flow through validation to repaper every time. That standardization is what lets you onboard concurrent advisors without the intake step becoming the bottleneck. A worked outcome of running intake this way is in this advisor transition case study.
FAQ
When should transition intake actually start? Intake planning starts well before the resignation date, but the fields you capture pre-resignation must stay within what compliance and the Broker Protocol permit. The full account and asset detail is captured after the U5, from the client's own statements, not pre-staged from the current firm's systems.
What client data can I capture before the advisor resigns? If both firms are Broker Protocol members, only the narrow set of contact fields the Protocol permits, name, address, phone, email, and account title. Anything beyond that, or any situation where a firm has left the Protocol, is a compliance and legal question, not an operations decision.
Which fields drive ACATS acceptance? Account type, registration, tax ID, custodian and account number, and asset transferability. A mismatch on tax ID or account title, or a nontransferable position, is a common reject cause, so capturing and validating these accurately at intake prevents downstream NIGOs.
Can intake feed my CRM directly? Yes. Structuring the checklist to your CRM's fields, whether Redtail, Wealthbox, or Salesforce Financial Services Cloud, from the start means household and account records flow through without rekeying, and document intelligence can populate the account layer directly from statements.
