How should an RIA build a website claim-review ledger?

An RIA can make website claims easier to review by connecting each material statement to evidence, limitations, an approved version and the exact page where it appears. A claim-review ledger is useful because a true source does not automatically make every sentence written from it accurate. Review what the reader will infer, not only whether a citation exists.

This educational workflow is for US advisory firms. The SEC marketing-rule discussion applies within that rule's scope, and firms should have qualified compliance staff or counsel assess their actual communications. It does not provide a legal conclusion about a particular page.

What counts as a claim worth recording?

Record statements that could change a reader's understanding of the firm's services, qualifications, process, costs or expected benefits. Do not limit the review to performance numbers.

A claim may be a sentence, heading, badge, diagram label or button. "We coordinate every part of your financial life" says more than "we discuss your investment questions." "No hidden costs" is different from a fee schedule. Even a short label can create an expectation the firm cannot demonstrate.

Start with statements the reader could rely on when deciding whether to contact the firm. Ask what the words imply in their context. A service description placed beside a booking button may be read as a service currently available, not a future plan.

You do not need a bureaucratic record for every connecting word. The ledger's purpose is to expose load-bearing claims and their conditions, not turn a draft into an unreadable wall of internal notes.

How does the SEC marketing rule inform the review?

For communications within its scope, the marketing rule requires more than avoiding obviously false statements. The review should address substantiation, misleading implications and the treatment of benefits alongside risks or limitations.

The SEC's investment-adviser marketing compliance guide describes prohibitions on untrue material facts, misleading omissions, material factual statements without a reasonable basis for believing they can be substantiated on demand, misleading implications and benefits presented without fair and balanced treatment of associated material risks or limitations.

The adopting-rule page links the actual rule material. Use the rule and the firm's qualified reviewer to determine application. A practical ledger does not decide whether every webpage or one-to-one message is an advertisement under the rule.

The SEC's staff marketing FAQs address particular questions. They are staff views, not a replacement for the rule. Do not turn a narrow FAQ answer into blanket permission for a different claim.

What should the claim-review ledger contain?

Keep the exact words, their evidence and their boundaries in the same row. Record the page version so the reviewer knows what is being assessed.

These rows are a proposed editorial structure, not a required SEC form. You can adapt the fields to the firm's process. Keep unresolved facts visible rather than filling them with the most plausible answer.

A useful review state distinguishes unsupported, supported with conditions, ready for the reviewer and approved for an exact version. Do not use a generic green status that makes those different states look equivalent.

How do you tell whether the evidence supports the words?

Compare the statement's audience, time period, conditions and strength with the source. A mismatch on any of those can matter even when the source is credible.

Suppose a fictional draft says, "Our process eliminates conflicts." A document explaining how one conflict is managed does not support that sentence. The writer should identify the actual practice and its limits rather than keeping the broad promise and attaching a citation.

Similarly, a source about a tax rule for one entity or year does not support a sentence for every household. A draft that says "can" may still imply a broadly available option when the necessary conditions are missing. Rewrite the claim to reflect the facts instead of asking a footer to repair it.

Mark external statistics with their population, date and definition. Do not change "respondents" into "all investors" or a reported preference into a demonstrated result. This article supplies no survey statistic; the example is a review test for whatever evidence your page uses.

Where should a limitation appear?

Place it where the reader needs it to understand the claim. A general disclaimer at the bottom cannot do every job.

If a fee illustration excludes other costs, make that boundary clear beside the illustration. If a planning example is fictional, label it where it appears. If a described option depends on entity, plan or jurisdiction, state those conditions in the passage.

The SEC guide's fair-and-balanced discussion is the source for the marketing-rule claim, not a guarantee that any one placement will satisfy the rule. The firm's reviewer should inspect the whole presentation, including headings, emphasis, images and links.

On a mobile page, a condition may appear farther from its headline than the author expected. Inspect actual rendered pages at the relevant widths. A disclosure present in source HTML is not the same as a disclosure readable in the result.

Which other documents should be reconciled?

Compare service and cost claims with the documents that describe the actual engagement. Different wording across a website and an agreement deserves a question, not an automatic rewrite.

Investor.gov's Form ADV brochure bulletin explains disclosures about business practices, fees, conflicts and investment risks. It is useful context for the comparison. The website does not replace the brochure or the advisory agreement.

Investor.gov's fee guidance encourages questions about transaction and ongoing costs and how the professional is paid. If a page presents a simple price, check which work and costs it includes. Do not infer "no other costs" from one line in a schedule.

For a fee-page workflow, see the fee-explanation guide. The claim ledger is broader: it records the evidence path for the sentences across the site, including sentences that are not about price.

What happens when someone changes the page after review?

Treat a meaningful edit as a new review question. An old approval describes the old version, not whatever the page later becomes.

Keep the reviewed copy, supporting sources, images and disclosures together. Compare the new version with that set. A change from "may" to "will," a removed qualifier or an updated diagram can change the meaning without making the text much longer.

The SEC marketing compliance guide explains that the amended books-and-records rule includes requirements to keep copies of advertisements directly or indirectly disseminated. Have the firm determine the applicable requirements and retention process. This ledger is not a substitute for the firm's required recordkeeping.

When the page goes live, read the actual result. Confirm that the reviewed statement, condition and illustration remain together and that the CTA does not add a new promise. A saved draft and a published page are different artifacts.

How can a small team use the ledger without slowing every edit?

Make the review unit specific. Send the reviewer the changed claims, their evidence and the exact rendered version, rather than an unsupported note that the page is fixed.

Assign a person to the source check and a person qualified to give the relevant compliance decision. A writer can correct language and assemble evidence without declaring the firm's legal compliance. The reviewer can return a precise defect that the writer can address.

Group repeated uses of the same claim, but check each context. A statement approved in a detailed educational page may read differently in a short promotional card. Keep the audience and presentation visible when carrying language to another surface.

Use a separate process for testimonials, endorsements or performance content. The testimonial-review guide covers questions a general claim row cannot resolve by itself. The ledger helps find the right review, not bypass it.

What does this process leave unresolved?

It does not determine every legal classification or prove that a source will remain current. It gives the reviewer an inspectable set of claims and evidence.

An unavailable source, conflicting internal records or an unverified service should remain open. Do not call the claim approved because the deadline arrived. If an existing page needs an update, merge or retirement decision, use the article-maintenance framework; that is a different decision from substantiating a sentence.

The bottom line

A citation starts the review; it does not finish it. Keep the exact claim, supported scope, nearby limits and reviewed version together. Then inspect the page the reader actually receives.