Suitability language: promising the right product to the wrong client

An adviser is wrapping up a client email. The client file shows a moderate risk tolerance, a five-year horizon, and a stated goal of capital preservation with modest growth. The adviser has a structured note in mind. The recommendation itself is defensible. The sign-off is where it goes wrong: “Honestly, this is perfect for you, you cannot go wrong here.” Two short phrases, sent in a second, and the file that is supposed to justify the fit now sits behind a promise the file does not actually make.

This is the quiet failure mode of suitability. Most advisers know they cannot guarantee a return. Far fewer notice when their everyday language guarantees a fit. The words assert that a suitability judgment has been made and came out clean, when the underlying analysis may be thin, undocumented, or simply not that certain. That gap is where complaints, uphold decisions, and enforcement live.

The obligation the words are standing in for

Suitability is a documented process with a defined shape. Under MiFID II (Article 25(2)) and the FCA’s COBS 9A, a firm giving a personal recommendation must obtain information on the client’s knowledge and experience, financial situation including capacity for loss, and investment objectives including risk tolerance, then recommend only what is suitable on that basis. In the United States, FINRA Rule 2111 and Reg BI (the SEC’s Regulation Best Interest) impose a comparable reasonable-basis and customer-specific standard. The common thread across all of them: suitability is a conclusion you reach after assessing a specific client against a specific product, and you have to be able to show your work.

Language like “this is perfect for you” or “ideal for someone like you” is a claim that this whole process has already happened and produced a confident yes. When it has not, or when the file will not carry the weight of the word “perfect,” the sentence has manufactured a suitability assertion out of nothing. A reviewer reading the email later cannot tell the difference between a rigorous recommendation and a warm reassurance. Neither can the client. Neither, eventually, can an ombudsman.

The fit claim is a different animal from the performance guarantee

Compliance training drills the performance guarantee hard: never say “this will return 8%,” never say “guaranteed.” Advisers absorb that. The fit claim slips through because it sounds like service, not like a promise. “This is exactly what you need” feels like attentiveness. What it actually does is assert the output of the suitability assessment as a certainty. A performance guarantee overstates what the product will do. A fit claim overstates what you know about the client and how cleanly the two match. Both are assertions the record has to support, and the second one is far easier to say by accident.

A pattern guide for suitability-overreach language

Below is a working reference you can paste into a desk procedure or an onboarding deck. The left column is the phrase that asserts a fit the file may not support. The right column is a phrase-level rewrite that says the true thing: this is a considered option tied to what you actually documented. The rewrites are deliberately small. The goal is to keep the adviser’s warmth while removing the manufactured certainty.

Read the right column again and notice what each rewrite does. It anchors the claim to something (the profile, the documented criteria, the stated tolerance), it keeps the downside visible, and it lets the recommendation be a recommendation instead of a verdict. None of this makes the adviser sound weak. It makes the file and the email say the same thing, which is the entire point of a suitability record.

A quick self-test before anything goes out

• Does the sentence assert a fit as a fact? If so, can I point to the line in the file that supports it?
• Have I turned a category (“people like you,” “everyone your age”) into a substitute for this client’s own assessed profile?
• Have I called a risk-bearing product “safe,” “perfect,” or “cannot go wrong”?
• If a reviewer read only this email, would they think the suitability work was more certain than it was?

For a deeper treatment of how these fit claims map to specific product recommendations, our suitability language guide works through worked examples by product type.

Where a pre-send check actually fits

Most of these lines are written by people who are trying to be helpful. The adviser is not gaming the rule. They are being warm at the end of a long email, and “this is perfect for you” is what warmth sounds like under time pressure. That is exactly the category of risk a pre-send check is built for: the careless line a well-intentioned employee does not notice, caught in the seconds before it leaves.

To be clear about the boundary: this is a check against accidental overreach, not a security control. It will not stop someone determined to mis-sell, and it is not an adversarial barrier. What it does is flag the fit claim while the message is still on the adviser’s screen and offer the short, phrase-level rewrite, so the sentence that goes out matches the file. In practice VerbaPulse flags “this is perfect for you” and suggests “this aligns with the objective in your profile,” in the drafting window, before send.

It also sits in front of the tools you already run, rather than competing with them. Archiving and supervision platforms (Smarsh, Proofpoint and the like) capture and review what was said after the fact. A pre-send layer reduces how many of these fit claims reach that queue in the first place, which is cheaper for everyone than surfacing them in a lookback or, worse, in a client complaint.

The takeaway

Treat the fit claim as a regulated statement, because it is one. Before an advice email or chat goes out, make sure every sentence that asserts suitability points back to something real in the client file, and strip the words that promise a flawless match: “perfect,” “ideal,” “cannot go wrong,” “exactly what you need,” “safe for you.” Put the seven-line pattern guide on the desk, run the four-question self-test, and let a pre-send check catch the ones that slip through when the day is busy. The recommendation can stay confident. The certainty has to be earned by the record.

This is general information, not legal advice. Confirm your obligations against MiFID II, FCA COBS 9A, FINRA Rule 2111, Reg BI, or the specific regime that applies to your firm.