Broker communications go to a principal for approval
Author
Audrey
NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.
Date Published
Advisors write to clients constantly: market updates, product explanations, follow-ups after a meeting. At a broker-dealer a lot of that writing is retail communication, and the firm has a process for reviewing it. A registered principal looks at the piece before it goes out.
An AI assistant makes the writing faster. It can turn a few notes into a clear email, adapt a standard explanation to a client's situation, or produce a newsletter draft. It can also, if it is connected to the email or publishing tool, send what it wrote. That is where the firm's review process gets bypassed without anyone intending it.
The problem in the compliance team's terms
The chief compliance officer does not want to stop advisors from using AI. Banning it will push the use into personal accounts the firm cannot see. They want the review that already exists to apply to AI-drafted communications as clearly as it applies to everything else.
That means the send step, or the distribution step, has to be a decision a principal made, with a trace of it. A guideline that reminds advisors to "run it past a principal" depends on memory under a deadline.
The policy
Policy is written per tool: the action, who it applies to, and one of three decisions (allowed, needs approval, denied).
Action | Who | Decision |
|---|---|---|
Read client notes, product material, and approved content | Advisors' assistants | Allowed |
Draft a client communication | Advisors' assistants | Allowed |
Distribute a retail communication | Advisors' assistants | Needs approval |
Drafting is open. The tool that distributes the communication is set to needs approval, so the call waits for a decision before anything reaches a client.
Who approves, and where
The request is routed to a named approver or role: a registered principal, or the principal group the firm designates. They answer in Slack or the web inbox, and the firm can choose the channel the principals already use during the day.
The approval covers one communication. The next piece is a new request. That fits how principal review already works, where each piece is reviewed on its own, and it means the firm does not have to trust that an earlier approval still applies to a later draft.
What the Record of Decisions shows
The Record of Decisions keeps an entry per decision: who asked, which agent, which tool, the decision, who approved, and when. For communications review, the firm can see several things at once.
- Every AI-drafted communication that was submitted for distribution, and the advisor whose session produced it.
- The principal who approved each, and when.
- The communications that were denied, so a rejected piece leaves a trace as well.
That gives the compliance team a searchable history of how AI-drafted communications moved through review. It supplements the firm's existing review records, which still hold the content and the principal's markup. The Record of Decisions adds which agent was involved and when the decision was made.
Describe it plainly to anyone who asks: it is a working record of what policy decided and who approved.
What this does not do. It does not review the content, and it does not tell the firm that a communication meets any standard. The principal does that. It also does not replace the firm's supervisory procedures or its records retention. It makes sure the review step is asked and answered for AI-drafted pieces.
Related scenarios
- No off-channel messaging: messaging tools denied so communications stay on approved channels.
- CFPB portal responses confirmed: a regulatory response waits for the compliance officer.
- Marketing-rule evidence for an RIA: the record of AI-assisted advertising.
- Sending for signature asks first: an outbound legal action waits for a decision.
Get started and put the same line on your communication tools.

