Loading...
compliance

Investment Recommendation Rationale and Best Interest Memo

This memo records why a specific investment recommendation was made, what client facts were relied on, and which alternatives were considered. Use it to create a clear audit trail for suitability and best-interest reviews.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Financial Services · Wealth Management · Broker Dealer Compliance · Registered Investment Advisory

Overview

The Investment Recommendation Rationale and Best Interest Memo template is a compliance form for documenting why a specific investment recommendation was made, what client facts were relied on, and which alternatives were considered before the recommendation was finalized. It is built to capture the decision trail in a structured way: client and account context, objectives and constraints, information sources, the selected strategy, the alternatives rejected, and the reviewer attestation.

Use this template when a recommendation needs to be defensible to a supervisor, compliance team, or auditor, especially when the choice is not obvious or when the client’s situation includes tradeoffs such as liquidity limits, time horizon constraints, or special account rules. The form is also useful when a firm wants a consistent record across advisors so the rationale is documented in the same order every time.

Do not use it as a generic client intake form or a substitute for broader suitability documentation. If no recommendation is being made, or if the decision is already fully captured in another required workflow, this memo may be unnecessary. It also should not collect more PII than needed; the point is to document the basis for the recommendation, not to recreate the entire client file. When completed well, the memo gives reviewers enough context to understand the recommendation, the tradeoffs, and the audit trail without having to reconstruct the decision from scattered notes.

Standards & compliance context

  • Limit collection to the minimum necessary PII and include a clear disclosure about how client information will be used and retained.
  • If the form is public-facing or client-accessible, ensure the fields, labels, and validation meet WCAG 2.1 AA accessibility expectations.
  • Use consent language only where your process actually requires it, and make the anonymous submission option available only if it is permitted by policy.
  • The review and attestation section should create an audit trail that shows who reviewed the recommendation, when it was reviewed, and what was approved.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice and Consent

This section sets the purpose of the submission, captures any required consent, and explains how the form handles PII and anonymous submission.

  • Purpose of this memo
  • Client consent to record and retain recommendation details (required)
  • PII minimization acknowledgement (required)
  • Anonymous submission requested

    Use only if your workflow allows anonymous internal review. Do not use for client-identifying records.

Client and Account Context

This section identifies the account and relationship context so the recommendation can be evaluated against the right client record.

  • Client name (required)
  • Client or household ID

    Use an internal identifier if available. Avoid collecting SSNs or other unnecessary identifiers.

  • Account type (required)
  • If other, specify account type
  • Relationship type (required)

Client Objectives, Constraints, and Risk Profile

This section records the client facts that should drive the recommendation and shows which constraints shaped the decision.

  • Primary investment objectives (required)
  • If other, describe the objective
  • Risk tolerance (required)
  • Time horizon (years) (required)
  • Liquidity needs (required)
  • Special constraints or restrictions
  • If other, describe the constraint

Information Relied Upon

This section documents the sources and facts used so reviewers can see what the recommendation was based on.

  • Information relied upon (required)
  • If other, specify the information source
  • Key facts summary (required)

    Summarize the client facts that materially influenced the recommendation. Avoid unnecessary personal data.

  • Material information not available

    If any material facts were unavailable, explain what was missing and whether the recommendation was still appropriate.

Recommendation and Alternatives Considered

This section states the selected strategy and the other options that were reviewed before the final choice was made.

  • Recommended product or strategy type (required)
  • If other, specify the recommended strategy
  • Recommendation summary (required)

    State the recommendation clearly and concisely.

  • Alternatives considered (required)
  • Alternative name (required)
  • Why this alternative was not selected (required)

Best Interest Rationale

This section explains why the selected option was preferred and what tradeoffs were accepted or mitigated.

  • Best-interest basis (required)
  • If other, describe the basis
  • Rationale narrative (required)

    Explain why the recommendation is suitable or in the client’s best interest, including trade-offs and why the selected option is preferable.

  • Known trade-offs or risks

    Document any material risks, limitations, or trade-offs disclosed to the client.

Review, Attestation, and Audit Trail

This section closes the loop with reviewer approval, attestation, and supporting documents for compliance review.

  • Supervisor review required
  • Reviewer name
  • Review date
  • Attestation (required)
  • Supporting documents

    Upload only documents necessary to support the recommendation.

How to use this template

  1. Start by entering the submission purpose and confirming whether client consent to record is required, then use the anonymous submission option only if your process allows it.
  2. Fill in the client and account context with the minimum necessary identifiers and select the account type and relationship type that match the recommendation.
  3. Document the client’s objectives, risk tolerance, time horizon, liquidity needs, and any special constraints, using the 'other' fields only when the standard options do not fit.
  4. List the information sources you relied on, summarize the key facts, and note any missing information that could affect the recommendation.
  5. Record the recommended strategy, the alternatives considered, and a specific best-interest rationale that explains why the chosen option was preferred despite any tradeoffs.
  6. Complete the review, attestation, and supporting documents section so the memo has a clear reviewer, date, and audit trail before it is filed.

Best practices

  • Write the rationale around the client’s facts, not around product features alone.
  • Use progressive disclosure so only the fields relevant to the account type or strategy appear to the user.
  • Mark required fields only where the information is truly necessary for the decision record.
  • Capture missing information explicitly instead of leaving blanks that force reviewers to guess.
  • Name the alternatives in plain language and explain the specific reason each one was not selected.
  • Attach the source documents that support the recommendation at the time of submission, not later from memory.
  • Keep the narrative concise but specific enough that a reviewer can follow the logic without outside context.

What this template typically catches

Issues teams running this template most often surface in practice:

A generic rationale that does not explain why this client needed this specific recommendation.
Alternatives considered are listed but the reason they were rejected is left blank or too vague.
Risk tolerance, time horizon, and liquidity needs are inconsistent with the recommendation narrative.
Missing information is not documented, making it unclear whether the recommendation was made with incomplete facts.
Supporting documents are referenced in the narrative but not attached to the record.
The reviewer section is completed after the fact without a clear date or attestation.
The form collects more client data than needed for the recommendation record.

Common use cases

Retirement rollover recommendation review
An advisor documents why a rollover strategy was recommended for a client leaving an employer plan. The memo captures the account context, the alternatives considered, and the tradeoffs around fees, liquidity, and investment options.
Managed portfolio selection for a high-net-worth client
A wealth manager records why one managed strategy was selected over other available models. The narrative ties the choice to the client’s objectives, risk tolerance, and any special constraints that narrowed the field.
Liquidity-sensitive recommendation for a business owner
A representative explains why a more liquid or more conservative strategy was chosen because the client may need access to cash for operating needs. The memo makes the liquidity constraint visible to reviewers.
Supervisor review of a complex account change
A compliance reviewer uses the memo to verify that the recommendation was supported by the facts in the file and that the advisor considered reasonable alternatives. The attestation and supporting documents create the audit trail needed for sign-off.

Frequently asked questions

When should this memo be used?

Use it whenever a representative recommends a specific investment product, allocation, or strategy and needs to document why it is in the client's best interest. It is especially useful when the recommendation involves tradeoffs, higher fees, liquidity limits, or a non-obvious alternative. If the recommendation is routine and already covered by a separate suitability workflow, this memo can still serve as the supporting record. It should be completed close to the recommendation date so the rationale reflects the facts actually relied upon.

Who should complete and review this form?

The advisor, broker, or investment professional making the recommendation should complete the core narrative and alternatives section. A supervisor, compliance reviewer, or designated reviewer should complete the review and attestation section when required by firm policy. If multiple people contributed to the recommendation, the form should identify who gathered facts, who drafted the rationale, and who approved it. Clear ownership helps preserve the audit trail.

What client information belongs in the memo?

Include only the client facts that were actually used to support the recommendation, such as objectives, risk tolerance, time horizon, liquidity needs, and special constraints. Avoid collecting unnecessary PII or duplicating data that already exists elsewhere unless it is needed to explain the decision. The form is designed around data minimization, so the key is to document the decision basis, not to create a full client profile. If information is missing, note the gap and how it affected the recommendation.

How does this template support compliance and audit review?

The template creates a structured record of the facts relied upon, the alternatives considered, the rationale for the selected strategy, and the reviewer attestation. That makes it easier to show how the recommendation was formed and what tradeoffs were acknowledged. The supporting documents field also helps link the memo to notes, disclosures, research, and account records. In practice, this reduces the risk of a vague after-the-fact explanation.

What are the most common mistakes when using this form?

Common mistakes include writing a generic rationale that could apply to any client, failing to list alternatives, and leaving the tradeoff discussion blank. Another frequent issue is marking every field as required even when some information is not applicable, which creates poor completion quality. Teams also sometimes forget to note missing information or to attach the documents that support the recommendation. The form works best when it is specific, concise, and tied to the actual facts reviewed.

Can this memo be customized for different account types or strategies?

Yes. The account type, relationship type, and strategy fields are meant to be adapted for brokerage, advisory, retirement, or other account contexts. You can also tailor the alternatives list and the best-interest basis options to match the products your firm actually uses. If a strategy does not fit the standard options, the 'other' fields and narrative sections let you capture the exception without forcing a bad fit. Keep the core audit trail intact even when you customize the labels.

What should be attached in supporting documents?

Attach the documents that actually informed the recommendation, such as research notes, product comparisons, client meeting notes, disclosures, or account statements. Only include materials that are relevant to the decision and permitted under your firm's retention rules. The goal is to make the rationale traceable without over-collecting sensitive information. If a document is referenced in the narrative, it should be easy for a reviewer to find it.

How should this be rolled out across a team?

Start by defining when the memo is mandatory, who completes each section, and what evidence is required for review. Then standardize the field meanings so advisors do not interpret risk tolerance, alternatives, or best-interest basis differently. A short training session with examples of good and bad entries usually improves consistency quickly. It also helps to pair the form with a review checklist so compliance can spot missing rationale before submission.

Go deeper on the topic

Related concepts
  • Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
  • Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
  • A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
  • AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
Related guides

Ready to use this template?

Get started with MangoApps and use Investment Recommendation Rationale and Best Interest Memo with your team — pricing built for small business.

Get Started