A review meeting transcript is the start of five downstream outputs, not just one: the client follow-up email, the CRM activity log, the trade authorization DocuSign request, the planning software update task, and the next-meeting calendar item. Each must fire reliably within the post-meeting window, each must be retained under Rule 4511 / Rule 204-2, and each must satisfy the Reg BI Care Obligation §240.15l-1(a)(2)(ii) requirement that the recommendation chain be documented end-to-end. Then, once a quarter, the firm runs an AI pass against the CRM to surface every open action item past SLA — the "did I actually do what I promised the client?" report — with the client-recovery email template ready for the items that slipped. This lesson installs the one-transcript-five-outputs post-meeting routing and the quarterly SLA audit, both essential to a 200-household practice that wants to stay defensible.

One Transcript, Five Outputs — The Routing Architecture

The L2 Ch3.2 five-artifact Rule 4511 bundle is the input. The post-meeting routing fans it out into five distinct downstream artifacts, each landing in a different system, each on a different SLA, each retained separately.

Output 1 — Client Follow-Up Email

The same-day follow-up email (covered in detail in L2 Ch2.3 for discovery; the structure is analogous for review). For a review meeting it includes: the three planning decisions made, the action items committed by client + advisor + third party, the rationale citation for each Reg BI recommendation, and the next meeting date. SLA: 12 minutes from meeting end. Routes through the Rule 2210 principal pre-use review queue for hybrid practices. Archived under Rule 204-2 / Rule 4511.

Output 2 — CRM Activity Log Entry

A structured Wealthbox / Salesforce FSC / Redtail Engage / Practifi activity log entry containing: meeting type (review), date / duration, attendees, the three planning conversations addressed, the decisions made, the action items routed, references to the upstream prep pack and the downstream Reg BI memos. The L2 Ch8 lesson on structured output (JSON / Markdown for CRM imports) makes this loadable as a single API call. SLA: 12 minutes from meeting end. The CRM becomes the single-source-of-truth for the household relationship state.

Output 3 — Trade Authorization (DocuSign + Custodian)

For any decision in the meeting that requires a custodian-bound trade — the Roth conversion, the rebalance, the QCD execution, the trade-direction change — the DocuSign trade authorization request goes out to the client and the custodian-form package (Schwab, Fidelity, Pershing, BNY Mellon) goes to the custodian queue. Each carries the Reg BI rationale memo as cover. SLA: 24-48 hours from meeting end depending on complexity; client signature triggers custodian execution. Archived end-to-end.

Output 4 — Planning Software Update Task

For any plan-revision implication — new SS claim assumption, revised retirement age, IPS amendment, Roth conversion modeled with cash-flow impact — the RightCapital / eMoney / MoneyGuidePro plan-revision task lands in the planner's or advisor's queue with the meeting's rationale attached. SLA: 5 business days from meeting end for non-urgent revisions; same-day for trade-authorization-bound revisions. The L2 Ch5 IPS update lesson covers the IPS-side revision in detail.

Output 5 — Next-Meeting Calendar Item

The next review meeting scheduled into the advisor's and client's calendar — quarterly check-in, annual review, six-month rebalance follow-up, or the specific cadence the IPS / engagement letter specifies. SLA: at meeting end. The Calendly / Microsoft Bookings / Acuity integration that automates this is the L4 Ch5 productivity-stack design point; for L2 Ch3.3 the discipline is that no meeting ends without the next meeting on the calendar.

The Locked Routing Prompt — One Pass, Five Outputs

The L2 Ch1.1 anatomy-locked prompt for the routing:

Role. You are a senior CFP-certificant advisor finalizing the post-meeting routing. You never invent facts. You produce structured output suitable for downstream API ingestion.

Context. The attached five-artifact bundle is from a review meeting today with [Client Name]. Decision log entries identify the recommendations, alternatives considered, client affirmations, and advisor commitments. Action items list identifies the next steps with owner and due date. Firm's downstream destinations: Wealthbox (CRM), DocuSign (trade auth), Schwab Advisor Center (custodian), RightCapital (planning), Calendly (calendar), Smarsh (archive).

Task. Produce five outputs in parallel: (1) Client follow-up email per the L2 Ch2.3 eight-component template. (2) Wealthbox activity log entry in JSON suitable for API ingestion. (3) DocuSign trade authorization request package per the firm's templated forms with Reg BI rationale memo as cover. (4) RightCapital plan-revision task per the planner queue format. (5) Calendly next-meeting invitation per the agreed cadence.

Format. Each output labeled clearly. Each carries its SLA tag (12 min, 24-48 hr, 5 days, immediate). Each references the upstream bundle ID.

Constraints. (1) Do not invent any decision or action not in the bundle. (2) Trade-authorization output must enumerate the Reg BI alternatives from the decision log. (3) Plan-revision output must cite the specific Monte Carlo / IPS / assumption change. (4) Calendar output must default to the firm's standard cadence unless the bundle specifies otherwise. (5) For any output destination not configured for this client, write [need: configure destination]. (6) Marketing language forbidden. (7) Per-output retention metadata required (SLA, archive destination, lookup key).

The Quarterly SLA Audit — "Did I Actually Do What I Promised the Client?"

The post-meeting routing is the prevention; the quarterly SLA audit is the recovery. Once per quarter the firm runs an AI pass against Wealthbox / Salesforce FSC / Redtail Engage / Practifi to surface every open action item past its SLA: the client follow-up that drafted but never sent, the trade authorization that DocuSign sent but the client never signed, the plan revision that landed in the planner queue and never closed, the third-party introduction that the advisor promised in March and hasn't made by June.

The AI pass is structurally simple: pull all open action items, group by household, group by owner, group by category, sort by days-past-SLA descending. The advisor / CCO reviews the high-days list first. Each item gets a disposition: (a) close — was completed but not logged, (b) escalate — client-recovery email + immediate action, (c) defer — agreed with client to push, (d) document and close — no longer applicable. The L3 Ch1.1 workflow audit lesson treats this as the practice's most important hygiene routine; the L3 Ch10.1 archive lesson confirms each disposition is logged.

The Client-Recovery Email Template

When an action item past SLA is identified during the audit and the client did not receive what was promised, the client-recovery email is the operational response. The template:

Subject: "Following up on what I promised at our [Date] meeting"

Opening (one sentence). "Looking through our notes from the [Date] meeting, I noticed I committed to [specific action] by [original due date] and haven't yet delivered."

Direct acknowledgment. "I'm sorry I missed that — it doesn't reflect the service I want to provide for you."

Concrete recovery plan. "I'll have [specific deliverable] to you by [new specific date], with [any new context]."

Confirmation. "Please let me know if that works, or if you'd prefer to discuss on a quick call this week."

Sign-off + firm-standard footer.

The Reg BI Care Obligation framing: ongoing monitoring includes following through on commitments. A missed commitment doesn't itself violate Reg BI, but a pattern of missed commitments combined with no documented recovery is structural evidence of a Care Obligation gap. The recovery email + the closing log entry together demonstrate the recovery discipline.

The Quarterly Audit Prompt

The L2 Ch1.1 anatomy-locked prompt for the quarterly audit:

Role. You are the firm's CCO / operations lead running the quarterly SLA audit. You produce structured reports for advisor review.

Context. The attached export from Wealthbox / Salesforce FSC contains all open action items across the firm's households as of [date]. Each carries owner, due date, status, category, household identifier, and creation date.

Task. Produce a structured report: (1) Total open action items by category. (2) Items past SLA — list each with household, owner, days past SLA, category, original commitment context. (3) High-priority list — items past SLA by 30+ days where the advisor was the committed owner. (4) Client-recovery email drafts for the high-priority list — one per item per household. (5) Trend analysis — items past SLA this quarter vs prior quarter, by category.

Format. Structured table for items past SLA. Each client-recovery email draft formatted per the firm's template. Trend analysis as one paragraph plus chart-friendly data.

Constraints. (1) Do not invent any action item context not in the source data. (2) Client-recovery emails must reference the specific commitment and original meeting date — pull from the CRM activity log. (3) For any item where the original commitment context is unclear, write [need: advisor to confirm context]. (4) Marketing language forbidden. (5) High-priority email drafts must include explicit apology and concrete recovery plan with new specific date.

The Reg BI Care Obligation Integration

The Care Obligation under §240.15l-1(a)(2)(ii) requires the registered person to "exercise reasonable diligence, care, and skill" in formulating and providing recommendations, and to "have a reasonable basis to believe that the recommendation is in the best interest of the customer based on the customer's investment profile." The post-meeting routing + quarterly SLA audit operationalize the "reasonable diligence" component end-to-end. Every recommendation flows from the meeting through five reliable downstream channels; every commitment past SLA is surfaced and either completed or transparently deferred with documentation.

The 2025-2026 FINRA AWC pattern on inadequate rollover Reg BI documentation is the cautionary case. Many of those AWCs reveal that the firm in question had Reg BI memos for the original recommendation but no documented follow-through evidence — the trade was queued, the custodian form was sent, but the client signature was never followed up on, or the plan revision was never closed. The integrated routing + quarterly audit closes those gaps.

The L3 Ch10 Archive and the L4 Ch7 Substantiation Loop

The L3 Ch10.1 lesson on the Zocks-to-Wealthbox-to-Smarsh pipeline develops the archive pickup of every downstream artifact: the follow-up email, the CRM activity log entry, the trade authorization, the plan revision task, the next-meeting calendar item, and the quarterly audit report itself — all retained under Rule 204-2 / Rule 4511. The L4 Ch7 substantiation file uses these as the contemporaneous evidence for any AI capability claim the firm makes about its workflow ("we follow up on every commitment within X days"; "we close X% of action items within their SLA"). The audit's trend analysis becomes the M&A diligence proof point in L4 Ch8.

The Trade Authorization Path — DocuSign + Custodian Mechanics

The third output is the operational pinch point. A trade authorization for a Roth conversion, a rebalance, a QCD execution, or a fee deduction involves three sequential systems: the firm's internal documentation (Reg BI memo cover + recommendation), DocuSign for client signature, and the custodian-specific form package (Schwab Advisor Center for ACATs / Roth conversion forms; Fidelity Wealthscape for the equivalents; Pershing NetX360+ for theirs; BNY Mellon Pershing legacy for traditional accounts; AdvisorEngine / Apex / Altruist for newer custodian relationships).

Each custodian has its own form versions, Medallion-guarantee requirements for certain amounts, NIGO trigger list (covered in L2 Ch7.1), and processing SLAs. The routing prompt must produce the right custodian's form references; a generic "trade authorization" output that doesn't tie to the household's actual custodian creates a NIGO loop and a 24-48 hour SLA breach. The L2 Ch7.1 NIGO pre-check workflow is the firm-scale defense; for L2 Ch3.3 the routing prompt must pull the household's custodian from the Wealthbox / Salesforce FSC record and produce the correct custodian-specific package.

The Reg BI memo cover that accompanies the trade authorization is the artifact most likely to be examined in a FINRA exam or SEC sweep — it documents the recommendation rationale, the alternatives considered, the client-specific reason, and the principal review signoff. The cover must be drafted with the L2 Ch3.2 decision-log entry as its source-of-truth so the chain from meeting decision → memo → trade authorization → custodian execution is reconstructable.

The Recovery Discipline as a Firm-Level Asset

The quarterly audit's recovery work is not a sign of failure — it is a sign of practice maturity. Every practice produces past-SLA items. Practices without an audit don't see them; the items just compound until a client complaint surfaces or a regulator asks. Practices with an audit see them quarterly and address them systematically. The number that matters is the past-SLA count quarter-over-quarter trend: a practice whose Q1 audit shows 80 past-SLA items, whose Q2 shows 50, whose Q3 shows 35, and whose Q4 shows 25 is demonstrating compounding operational improvement. The L4 Ch5 ROI dashboard tracks this as a leading-indicator metric alongside NIGO rate, follow-up SLA, and households per advisor.

The client conversation about a missed commitment is often easier than advisors expect. The pattern that lands: a direct, brief, factual recovery email that names the original commitment, the miss, the new specific deliverable, and the new specific date — without excessive apology or hedging — typically resolves the relationship without escalation. Clients who receive the recovery email respond at very high rates (industry observation across major CRM-platform user data: 85%+ respond within 48 hours, and the response is usually thanks + acceptance of the new date). The relationship strengthens. The advisor's reputation as someone who follows through compounds.

Monday Morning Deployment

Implementation: (1) After the next review meeting, manually walk through the five-output routing — what email, what CRM entry, what trade auth, what plan task, what calendar item. (2) Configure the locked routing prompt against the firm's downstream destinations (Wealthbox or Salesforce FSC, DocuSign, custodian form templates by custodian, RightCapital or eMoney task formats, Calendly or Microsoft Bookings). (3) Schedule the quarterly SLA audit at end-of-month for the next three months — at minute zero, just to see the data. (4) On the first audit, review every item past SLA personally, send client-recovery emails as needed, log every disposition. (5) After three quarters, the audit becomes routine; the past-SLA count drops as the routing reliability improves; the practice's Care Obligation evidence trail becomes systematic. The L4 Ch5 ROI dashboard captures the trend as a quarterly board-level metric; the L4 Ch7 substantiation file logs the audit history for any AI-derived workflow-discipline marketing claim; the L4 Ch8 M&A diligence pack uses the trend as a top-quartile-valuation proof point.

Key Takeaways

• One transcript, five outputs: client follow-up email (12 min SLA), CRM activity log (12 min), trade authorization + Reg BI memo (24-48 hr), plan revision task (5 days for non-urgent), next-meeting calendar (immediate).
• The locked routing prompt produces all five outputs in parallel from the L2 Ch3.2 five-artifact bundle, each labeled with SLA, archive destination, and lookup key.
• Quarterly SLA audit surfaces every open action item past SLA via an AI pass against Wealthbox / Salesforce FSC / Redtail Engage / Practifi — the "did I actually do what I promised the client?" report.
• Client-recovery email template: subject + opening acknowledging the original commitment + direct apology + concrete recovery plan with new date + confirmation + firm footer. Closes the Care Obligation gap when items slip.
• Reg BI Care Obligation §240.15l-1(a)(2)(ii) requires reasonable diligence; the routing + audit operationalize diligence end-to-end. The 2025-2026 FINRA AWC pattern on incomplete rollover documentation is the cautionary case the integrated workflow closes.
• L3 Ch10.1 archive captures all five outputs + the audit report; L4 Ch7 substantiation file uses the trend data; L4 Ch8 M&A diligence uses the audit history as a quality proof point.
• Monday deployment: walk through five-output routing manually on next meeting, configure routing prompt, schedule quarterly audit at end-of-month — within three quarters the past-SLA count drops and the Care Obligation trail becomes systematic.