FINRA & Broker Protocol Expertise: How to Evaluate a Transition Technology Vendor
The transition technology vendor market in 2026 has two distinct categories that are usually marketed identically: vendors built by engineers who learned FINRA from documentation, and vendors built by people who lived inside FINRA-regulated workflows. The first category produces software that works fine for the 80% standard case and breaks at every edge case. The second category produces software that handles the edge cases as native functionality, because the people who built it spent years handling them manually.
Telling the two apart in a vendor demo is straightforward if you know what to ask. Here are the seven questions, the answers that signal real expertise, and the answers that signal marketing.
Question 1: "Show me how your platform handles a Form U4 amendment for a disclosure event."
Why this works: Form U4 amendments for disclosure events (customer complaint, regulatory matter, financial disclosure) are the highest-stakes compliance work in advisor onboarding. They appear on the advisor's permanent BrokerCheck record and can affect their career for years. A vendor that handles this well has built compliance functionality into the core of the platform.
Marketing answer: "We export to your CRD filing system." This means the platform doesn't actually handle U4 amendments — it just hands off to whatever system the firm is already using.
Real-expertise answer: "We auto-populate the amendment with prior disclosure history, generate the narrative consistent with the prior filing language, run a consistency check against the existing U4, and route to compliance for narrative review before filing. The narrative review is mandatory; we don't allow direct submission."
The difference: the real answer reflects awareness that U4 narrative drafting is Band 3 attorney work that requires structured AI support, not full automation. A vendor that claims to fully automate U4 narratives is either misrepresenting their capability or building software a compliance officer shouldn't use.
Question 2: "Walk me through how your platform handles a Broker Protocol move with both signatories versus a non-Protocol move from a former signatory like Morgan Stanley."
Why this works: This question requires the vendor to demonstrate awareness of the post-2017 Protocol landscape. The five permitted information fields are the same in both cases. What changes is the receiving firm's documentation requirements, the client-initiated-contact rules, and the dark-period operational sequence.
Marketing answer: "Our platform supports the Broker Protocol." This is a non-answer that doesn't address the actual operational difference.
Real-expertise answer: "For Protocol-to-Protocol moves, we generate the resignation-day documentation, the Protocol list, and the client contact workflow timed to start at resignation. For non-Protocol moves (Morgan Stanley, UBS, Citi former-signatory), we generate the tombstone-only announcement workflow, defer client outreach to client-initiated contact, and stage the receiving-firm documentation for fast turnaround when contact does occur. We don't enable advisor-initiated outreach in the non-Protocol case."
The difference: the real answer reflects awareness that the legal framework determines the workflow, not just the speed.
Question 3: "How does your platform handle FINRA Rule 11870 exceptions?"
Why this works: FINRA Rule 11870 governs customer account transfers through ACATS. A typical 500-account book contains 50-100 accounts that don't transfer cleanly via standard ACATS — non-transferable assets, position-restricted holdings, alternative investments, annuities held outside brokerage, proprietary fund positions. Real vendors have pre-built workflows for these exceptions. Marketing-only vendors handle them as one-off manual exceptions.
Marketing answer: "We integrate with custodian ACATS systems." This addresses the 80% case and ignores the 20% that determines whether the timeline holds.
Real-expertise answer: "We pre-identify Rule 11870 exceptions during data validation, route them to the appropriate non-ACATS transfer process (annuity rollovers, alternative investment specific workflows, custodian-specific exception forms), and track each through completion. Exception throughput typically determines transition timeline at the 60-day mark."
Question 4: "What's your Reg S-P documentation workflow for an incoming Protocol move?"
Why this works: Regulation S-P governs how firms handle nonpublic personal information. The May 2024 amendments tightened requirements substantially, including a 72-hour breach notification rule. RIAs receiving Protocol moves need documented procedures for receiving and storing the five permitted fields. Vendors that don't address this leave the receiving firm exposed.
Marketing answer: "We're SOC 2 compliant." SOC 2 covers the vendor's data security; it doesn't address the receiving firm's Reg S-P procedural compliance.
Real-expertise answer: "We generate the Reg S-P attestation documentation specific to each transition — receipt of Protocol information, storage location and access controls, retention period, disposal procedure. The receiving firm's compliance officer signs the attestation. We log the entire chain for the firm's compliance file."
Question 5: "How does your platform handle a U5 narrative that's adverse to the advisor?"
Why this works: When the departing firm files a Form U5 with adverse narrative content (suggestions of compliance issues, ambiguous reason-for-termination language, financial-disclosure-event content), the advisor has limited time and limited mechanisms to respond. A vendor that addresses this is engaging with the real post-resignation workflow.
Marketing answer: "We monitor BrokerCheck for U5 updates." This is monitoring, not workflow.
Real-expertise answer: "We flag the U5 within 24 hours of filing, surface the narrative content for advisor and counsel review, generate the structured response framework (factual contest vs. interpretive response vs. arbitration referral), and track the response through filing. We don't draft the substantive response — that's attorney work. We provide the structural and procedural support."
The pattern again: real expertise stops at the band boundary. Marketing claims to handle Band 3 work that no vendor should be doing.
Question 6: "Show me your custodian-specific form library for [specific custodian]."
Why this works: Custodian form libraries are a known weak point in the vendor market. Fidelity, Schwab, and Pershing each maintain their own forms with regular updates. A vendor with a stale form library generates rejected forms that look correct but fail at custodian validation. The only way to know is to see the actual library.
Marketing answer: "We support all major custodians." This is meaningless without seeing the specific forms.
Real-expertise answer: "Here's our current Fidelity Wealthscape form library — last refreshed 14 days ago. Here's our automatic-update process; when Fidelity issues a new form version, we update within 5 business days. Here's our audit log showing every form version change over the past 12 months. We let you specify form version overrides per advisor if needed."
Demand to see the actual form library and the actual update audit log. Vendors with the right answer have these ready. Vendors with the wrong answer make excuses.
Question 7: "What's your average NIGO rate, and how do you measure it?"
Why this works: NIGO (Not In Good Order) rate is the single most diagnostic metric in transition workflows. Industry baseline is 15-25% on manual processes. Vendors with real automation report 1-5%. Vendors who can't measure NIGO rate are usually somewhere in between, but they don't actually know.
Marketing answer: "We help reduce NIGOs." Notice the lack of a number.
Real-expertise answer: "Our 2025 measured NIGO rate across [X thousand] form submissions was [Y%]. We measure by custodian rejection or correction request post-submission. Here's our NIGO rate trend by custodian over the last 12 months and our remediation pathway for each NIGO category."
FastTrackr AI reports 95% NIGO reduction versus manual processes — measured at the custodian rejection layer, not at our internal validation layer. The distinction matters: internal validation can pass a form that custodian validation still rejects, so measuring at the custodian layer is the only honest metric.
The Negative Indicators
Beyond the seven questions, three vendor patterns reliably indicate marketing-over-expertise:
Indicator 1: No compliance officer on the founding team. A transition platform with no founding-team compliance officer has the wrong DNA. The compliance considerations show up everywhere — in form library updates, U4 narrative handling, Reg S-P procedures, NIGO categorization — and a team that didn't include compliance expertise from day one will have gaps.
Indicator 2: Generic "AI-powered" language without specifics. "We use AI to streamline transitions" doesn't say what the AI does. Real expertise produces specific descriptions: "Our document understanding model extracts beneficiary data from 47 statement formats with 99.2% field-level accuracy on our test set."
Indicator 3: No public NIGO rate or compliance audit data. Vendors with real numbers publish them. Vendors without real numbers talk about "significant reductions" without specifying what they're reducing or by how much.
What to Ask for in a Vendor RFP
For a structured RFP, the seven questions translate to seven required deliverables:
- Sample Form U4 amendment workflow demonstration (live, not slides)
- Protocol vs. non-Protocol workflow documentation
- Rule 11870 exception handling specification
- Reg S-P attestation template (actual generated document)
- U5 response framework documentation
- Custodian-specific form library with audit log
- NIGO rate by custodian for prior 12 months
If a vendor can't provide all seven, they're a Band 1 form-filling tool, not a transition compliance platform.
Frequently Asked Questions
How can I tell if a transition technology vendor has real FINRA expertise?
Ask seven specific questions in any vendor demo: (1) how they handle Form U4 amendments for disclosure events, (2) the operational difference between Protocol and non-Protocol moves, (3) FINRA Rule 11870 exception handling, (4) Reg S-P documentation workflow, (5) U5 narrative response process, (6) custodian-specific form library with update audit log, and (7) measured NIGO rate by custodian. Real expertise produces specific answers; marketing produces generic claims.
What's a red flag in a transition vendor demo?
Three red flags: (1) the founding team has no compliance officer or former FINRA staff, (2) the "AI" claims are generic ("AI-powered transitions") rather than specific ("document understanding extracts beneficiary data with 99.2% accuracy"), and (3) the vendor can't provide a public NIGO rate measured at the custodian rejection layer. Any of the three indicates marketing-over-expertise.
Why does FINRA Rule 11870 expertise matter for transition vendors?
FINRA Rule 11870 governs ACATS customer account transfers. A typical 500-account book contains 50-100 accounts that don't transfer cleanly via standard ACATS — non-transferable assets, position-restricted holdings, alternatives, annuities outside brokerage. Real vendors have pre-built workflows for each exception type. Marketing-only vendors handle them as one-off manual exceptions that extend the timeline.
What does Reg S-P require for a transition vendor?
Reg S-P requires documented procedures for receipt, storage, and disposal of nonpublic personal information, with a 72-hour breach notification rule under the May 2024 amendments. The vendor's SOC 2 compliance covers the vendor's data security but doesn't address the receiving firm's Reg S-P procedural compliance. Real vendors generate transition-specific Reg S-P attestation documentation for the receiving firm's compliance file.
How should NIGO rate be measured?
NIGO rate should be measured at the custodian rejection or correction-request layer, not at the vendor's internal validation layer. Internal validation can pass forms that custodian validation still rejects, so internal-only metrics overstate effective accuracy. Industry baseline on manual processes is 15-25%. Vendors with real automation report 1-5% NIGO rate measured at the custodian layer with public audit data.
Do transition vendors automate Form U5 narrative content?
No reputable vendor should fully automate Form U5 narrative content. The U5 narrative has adversarial implications, appears permanently on the advisor's BrokerCheck record, and is sometimes the basis for FINRA arbitration. It is Band 3 attorney work. Real vendors provide structural and procedural support for the response — flag the U5, surface narrative content for review, track the response — without drafting substantive content.
How current does a vendor's custodian form library need to be?
Custodian form libraries should be updated within 5 business days of any custodian-issued form version change. Stale form libraries generate forms that look correct but fail custodian validation — producing NIGOs that have nothing to do with the form content. Demand to see the vendor's actual form library plus the audit log showing every form version change over the past 12 months.
What's the difference between a Band 1 form-filling tool and a transition compliance platform?
A Band 1 form-filling tool generates and routes forms but doesn't address compliance workflow — U4 amendments, Protocol vs. non-Protocol logic, Rule 11870 exceptions, Reg S-P documentation, U5 response, NIGO measurement. A transition compliance platform handles the compliance workflow alongside the form generation. The distinction usually shows up in pricing (compliance platforms cost 3-5x more) and in capability (compliance platforms handle the 20% of cases that determine the timeline).
The transition technology vendor market has consolidated around two real models: form-filling tools that work fine for the 80% standard case, and compliance platforms that handle the 20% that determines whether timelines hold. The pricing reflects the difference. The marketing usually doesn't. The seven questions above are the working test for which category any given vendor actually sits in.
Related: Meeting Assistant · Advisor Transitions Platform
