The L3 Ch2 L1 screen identified 18-22 Q4 candidates. The L3 Ch2 L2 sizing memo ran the deep math per household and produced propose-mode JSON outputs the senior advisor reviewed and authorized for advancement. This lesson is the final step: convert the propose-mode memo into a Reg BI-compliant recommendation memo with documented consideration of all alternatives, execute the conversion (trade ticket, custodian conversion form, 1099-R expectations), and archive the complete file under FINRA Rule 4511 and SEC Rule 204-2. The L3 Ch2 sequence completes here. Every artifact produced — the recommendation memo, the trade ticket, the custodian form, the client communication, the CRM activity log, the tax-prep handoff note to the client's CPA, the Smarsh archive package — together constitutes the defensible 2026 Reg BI conversion file. This is the artifact that survives the 2026 SEC exam, the FINRA AWC investigation pattern on inadequate documentation, the L4 Ch8 M&A buyer's diligence query, and the client's CPA's tax-season question.

From Propose to Recommend — Where Reg BI's Four Obligations Attach

The L3 Ch2 L2 propose-mode JSON output is a draft, not a recommendation. Reg BI §240.15l-1's four obligations — Disclosure, Care, Conflict, Compliance — attach at the discrete moment the registered, licensed advisor signs the memo, converting it from a proposal into a recommendation. The L3 Ch1 L2 handoff diagram framed this signoff node as the singular Reg BI documentation point. This lesson operationalizes the attachment by producing the recommendation memo artifact that captures each of the four obligations explicitly.

The recommendation memo is structured per regbi-conversion-recommendation-schema v2.3 (extending the v2.1 sizing schema). It contains six required sections: (1) Recommendation Summary (the specific conversion recommended with size, date, source account, destination account), (2) Disclosure (Care/Conflict/Compliance under §240.15l-1, ADV Part 2A reference, fee impact narrative), (3) Care Obligation Documentation (the documented application of judgment, the alternatives considered with each rejected-or-modified rationale, the client-specific reasoning grounded in IPS and household state, the source-system + regulatory + client-fit verification log references), (4) Conflict Obligation Documentation (advisor's fee structure, any material conflicts including the standard AUM-fee impact on a Roth conversion that reduces AUM in taxable accounts, the disclosure to the client), (5) Compliance Obligation Documentation (the WSP coverage, the supervisory review chain, the FINRA Rule 4511 retention design), (6) Execution Authorization (the client signoff/acknowledgment evidence, the DocuSign confirmation, the custodian form submission, the post-execution verification).

The Four-Alternatives Discipline at L3 Scale

The L2 Ch7 L2 rollover Reg BI lesson installed the four-alternatives discipline (leave in plan / roll to new employer plan / roll to IRA / take cash). For Roth conversion, the four-alternatives equivalent is: (a) no conversion this year (with explicit rationale and future-year revisit plan), (b) partial conversion at smaller size (with rationale for why the larger proposed size is preferred), (c) the proposed conversion (the recommendation), (d) full bracket-fill or multi-year ladder alternative (with rationale for why the chosen size is preferred over more aggressive options). Each alternative is named, evaluated against the household's lifetime tax position, and the advisor's documented reasoning for selecting the recommendation captures the Care Obligation discharge.

The Hendersons' recommendation memo Care section reads: "Alternatives considered: (a) No conversion — rejected because the Hendersons' pre-RMD horizon (8-10 years before age-73 RMD trigger) projects RMD-driven bracket compression starting at age 73, with projected lifetime tax cost ~$130K higher than even a modest conversion plan; (b) $24K partial conversion — rejected because the lesser size leaves substantial bracket-fill opportunity unrealized and the leverage ratio (~1.6) is below the firm's documented threshold for high-leverage recommendations; (c) $74K conversion (recommended) — accepted because it fills the 22%-to-24% bracket transition, preserves Tier 2 IRMAA position with adequate margin from the $322K cap, avoids the next-tier cliff that $96K bracket-fill maximum would trigger, generates leverage 2.41 above the firm threshold, and coordinates with the higher-earner Social Security delay-to-70 strategy and the open trust-funding line item for parallel resolution; (d) $96K bracket-fill maximum — rejected because the leverage advantage over $74K is marginal (~3%) while the IRMAA margin tightens significantly and the higher-earner SS delay window suggests reserving capacity for 2027-2029 ladder years."

This is the documented application of judgment that converts the AI's propose-mode output into a Reg BI-defensible recommendation. The 2025-2026 FINRA AWC pattern on inadequate rollover documentation hinged on advisors who could not produce this kind of explicit reasoning when examined. The L3 Ch2 L3 workflow ensures every advanced Q4 recommendation has the equivalent documentation.

Conflict and Compliance Obligations

The Conflict section addresses the firm's compensation structure and any potential conflicts. For a standard AUM-fee RIA: "The firm's compensation is the standing AUM fee per the engagement letter and ADV Part 2A. The proposed Roth conversion does not change AUM (the converted amount remains under management, simply moving from traditional IRA to Roth IRA). There is no incremental compensation generated by this recommendation. The recommendation is in the client's best interest under the firm's fiduciary duty under the Advisers Act of 1940 and the duty of care and duty of loyalty articulated in the SEC's 2019 Interpretation Regarding Standard of Conduct for Investment Advisers."

For a hybrid BD/RIA advisor signing under both hats, the Conflict section adds: "Reg BI §240.15l-1(a)(2)(iii) Conflict Obligation applies under BD registration. The recommendation does not generate any transaction-based compensation, commission, ticket charge, or contingent compensation. Cross-reference Form CRS for the full conflict disclosure framework."

The Compliance section addresses the WSP coverage and supervisory chain. "This recommendation is produced within the firm's Roth Conversion Workflow WSP (revision 4.2 effective 2026-09-01). The workflow includes audit-prioritized motion intake (L3 Ch1 L1), handoff-diagram-defined structure (L3 Ch1 L2), three-tier verification specification (L3 Ch1 L3), propose-mode AI generation with system prompt v3.2 and few-shot library v2.5, and senior-advisor signoff under registered representative number / CRD [number]. Supervisory review under FINRA Rule 3110 is conducted at quarterly sampling per the firm's principal-review queue design (L4 Ch3 L2). Retention under FINRA Rule 4511 and SEC Rule 204-2 is established at 5-year-practical policy."

Execution — The Trade Ticket and Custodian Conversion Form

Execution starts with the trade ticket. The senior advisor (or the firm's operations team) generates the conversion trade ticket per the custodian's specifications. For Schwab: the Roth Conversion Form (typically a Distribution and Election Form combined with the Roth IRA acceptance) plus the AUM-driven asset allocation re-confirmation for the Roth account. For Fidelity: the Roth Conversion Request form with the dollar amount, the source IRA account number, the destination Roth IRA account number, and the federal withholding election (typically client elects 0% withholding so the full conversion amount lands in the Roth, and any tax cost is paid separately to maximize Roth growth). For Pershing / BNY Mellon: the IRA Conversion Form with the same elements plus the firm's authorization sign-off block.

The federal withholding election is itself a Care-Obligation-bearing decision. The default custodian withholding is often 10% federal (and state withholding may apply); for a $74K Hendersons conversion, 10% federal withholding would withhold $7,400 from the IRA — that $7,400 doesn't reach the Roth, foregoing tax-free growth, and the household pays tax on $7,400 of distribution. The recommended election is 0% federal withholding (and 0% state where applicable), with the household paying any tax liability via Q4 estimated payment from non-IRA cash. The recommendation memo's execution section documents the withholding election rationale.

The 1099-R expectations: the custodian will issue a 1099-R in January 2027 for the 2026 conversion. The relevant Box 7 distribution code for a Roth conversion is typically code 2 (early distribution with exception applicable — for under-59.5 conversions, though the exception means the early-withdrawal penalty does not apply because of the conversion exception) or code 7 (normal distribution — for over-59.5 conversions). The Box 1 (gross distribution) will show the conversion amount; Box 2a (taxable amount) will reflect the taxable portion after pro-rata; Box 5 (basis) reflects the basis-recovery if non-zero. The recommendation memo documents the expected 1099-R structure so the client and the client's CPA can validate when the form arrives.

Client Communication and DocuSign

The client communication translates the technical recommendation into the household-facing narrative. Two artifacts: the client-facing memo (1-2 page summary of the recommendation, the rationale, the projected current-year tax cost, the projected lifetime savings, the alternatives considered framing in client-accessible language, the SS-delay coordination, the trust-funding flag for parallel resolution) and the DocuSign trade authorization. The client memo is itself a Rule 2210 communication under FINRA principal review and a Marketing Rule 206(4)-1 communication if any case study language is repurposed in firm marketing later — the "clear and prominent" disclosure standard applies if the memo's quantitative projections are referenced in subsequent marketing without the necessary disclaimers.

The DocuSign authorization captures the client's authorization for the specific conversion ($74K Hendersons example), the source account, the destination account, the withholding election, and the date. The DocuSign also includes the disclosures required under Reg BI: the four obligations summary, the standard fee structure reference, the IPS-alignment confirmation, the right to ask questions or decline. Client sign — typically within 7-14 days of the memo — triggers the custodian form submission and the execution.

CRM Activity Log and Tax-Prep Handoff to CPA

The CRM activity log (Wealthbox / Redtail / Salesforce FSC per the firm's standard) captures the workflow's traceable state: "2026-10-15 — Roth conversion recommendation produced (propose-mode v3.2 prompt, schema v2.3, leverage 2.41, sized $74K); 2026-10-16 — Senior advisor signoff and Reg BI memo finalized; 2026-10-18 — Client memo delivered; 2026-10-22 — Client DocuSign signed; 2026-10-23 — Schwab Roth Conversion Form submitted; 2026-10-25 — Schwab conversion executed; 2026-10-26 — Smarsh archive routing confirmed; 2026-11-01 — CPA handoff note delivered; 2027-01-31 — 1099-R receipt expected, client/CPA validation deadline."

The tax-prep handoff note to the client's CPA is the artifact that prevents tax-season surprise. "Dear [CPA], On 2026-10-25, [Client] executed a Roth conversion of $74,000 from their Schwab Traditional IRA (account ending [XXXX]) to their Schwab Roth IRA (account ending [YYYY]). 0% federal withholding was elected; client paid associated tax liability via Q4 2026 estimated payment of approximately $17,300 federal + $266 NIIT + $3,600 IRMAA reserve (the IRMAA impact will be in 2028 Medicare premiums, not 2026 tax). The expected 1099-R will show Box 1 gross distribution $74,000, Box 2a taxable amount $74,000 (no aggregated basis), Box 7 distribution code 7 (over 59.5), Box 4 federal income tax withheld $0. Cross-reference our recommendation memo dated 2026-10-16 for the full rationale. Please confirm receipt and coordinate 2026 tax-return preparation."

The CPA handoff strengthens the COI relationship, signals operational maturity to the household, and ensures the recommendation's tax consequences are properly captured in the client's 2026 1040. The handoff note itself is archived in Smarsh under document_type=cpa_handoff_roth_conversion_2026.

Smarsh Archive Package and Rule 4511 Retention

The complete Smarsh archive package per the household per conversion: (a) the L3 Ch2 L1 screen output JSON identifying the household as advanced (with the leverage ratio and recommended preliminary size); (b) the L3 Ch2 L2 sizing memo JSON with full multi-component cost decomposition; (c) the source-system, regulatory, and client-fit checkpoint logs per L3 Ch1 L3 specifications; (d) the senior-advisor judgment narrative with explicit application of judgment; (e) the L3 Ch2 L3 Reg BI recommendation memo with six required sections; (f) the trade ticket and custodian form; (g) the client memo and DocuSign authorization; (h) the CRM activity log entries; (i) the CPA handoff note; (j) the post-execution custodian confirmation and 1099-R upon receipt; (k) the supervisory review entry from CCO quarterly sampling.

The tagged-Markdown metadata per L2 Ch8 L2: document_type=reg_bi_roth_conversion_complete_2026, household_id, conversion_amount, conversion_date, advisor IDs (senior + CCO), retention_policy=rule_4511_5yr_practical, ai_tool=GPT-4-class, ai_prompt_version=v3.2, ai_schema_version=v2.3, related_records=[screen_output_id, sizing_memo_id, checkpoint_logs_ids, signoff_id, trade_ticket_id, client_memo_id, docusign_id, custodian_form_id, cpa_handoff_id]. The metadata enables CCO sampling, L4 Ch5 ROI dashboard metrics, M&A diligence queries, and SEC exam responses.

The Defensible 2026 Reg BI Conversion File

Together, the artifacts constitute the defensible 2026 Reg BI conversion file. A 2026 FINRA examination on inadequate rollover-style documentation (the pattern that drove the 2025-2026 AWC actions) examines: did the advisor document consideration of all reasonably available alternatives? Yes — the four alternatives are explicitly named and rejected/accepted with rationale. Did the advisor make the recommendation in the client's best interest under Reg BI Care Obligation? Yes — the documented application of judgment ties the recommendation to the household's IPS, lifetime tax position, multi-workflow coordination, and explicit reasoning. Did the advisor disclose conflicts under Reg BI Conflict Obligation? Yes — the standard AUM-fee structure and the absence of transaction-based compensation are documented. Did the firm comply with WSP coverage under Reg BI Compliance Obligation? Yes — the WSP revision is cited, the workflow design is documented, the supervisory review chain is captured.

The same file answers the SEC exam question on Compliance Rule 206(4)-7 (the firm's written-policy implementation), the Marketing Rule question on any repurposed marketing language (the memo's quantitative content is internal-only until explicitly repurposed with disclosures), the Rule 4511 retention question (the archive package is complete, tamper-evident, queryable), and the L4 Ch8 M&A diligence question on operational maturity (the systematic Q4 workflow is documented end-to-end).

Key Takeaways

• Reg BI's four obligations attach at the signoff node — the discrete moment the propose-mode AI output converts into a recommendation under §240.15l-1. The L3 Ch2 L3 workflow operationalizes the attachment.
• The recommendation memo is structured per regbi-conversion-recommendation-schema v2.3 with six required sections: Recommendation Summary, Disclosure, Care Obligation Documentation, Conflict Obligation Documentation, Compliance Obligation Documentation, Execution Authorization.
• The four-alternatives discipline: no conversion / partial smaller / proposed (recommendation) / aggressive larger or multi-year ladder — each named, evaluated, with rationale. Captures the Care Obligation discharge that the 2025-2026 FINRA AWC pattern hinged on.
• Conflict section documents the AUM-fee structure (no incremental compensation from conversion), the Advisers Act fiduciary duty for RIAs, and the Reg BI §240.15l-1(a)(2)(iii) Conflict Obligation for BD/hybrid registrations.
• Execution includes the trade ticket, custodian form (Schwab Roth Conversion Form, Fidelity Roth Conversion Request, Pershing IRA Conversion Form), federal withholding election (recommended 0% with separate estimated payment), and 1099-R expectations (Box 7 code 2 or 7 depending on age, Box 1 gross / 2a taxable / 5 basis).
• Client communication via 1-2 page client memo (Rule 2210 + Marketing Rule 'clear and prominent' if repurposed) and DocuSign trade authorization capturing the specific conversion amount, accounts, withholding, and Reg BI four-obligations summary.
• CRM activity log captures workflow traceable state. Tax-prep handoff note to the client's CPA prevents tax-season surprise and strengthens COI relationship.
• The complete Smarsh archive package — 11 artifacts spanning screen output through 1099-R receipt and supervisory review — constitutes the defensible 2026 Reg BI conversion file. Survives SEC exam, FINRA AWC scrutiny, M&A diligence, and client/CPA tax-season questions.