← Journal

Practical Guides · 18 October 2026

Give every marketing claim an evidence owner before it enters the calendar

A practical weekly claim ledger helps small teams separate opinion from objective promises, find the evidence before publication and retire wording when its support expires.

By María José Ospina · 4 min read

Large illuminated advertising screens above Piccadilly Circus in London
Advertising screens at Piccadilly Circus, photographed on 21 December 2017. Archive image illustrating how audiences encounter the final claim, not the internal copy document. Photography: Oast House Archive / Geograph (CC BY-SA 2.0)
In this article

A content calendar can tell a team what goes live on Tuesday. It cannot tell them whether the promise inside that post is ready to be published. The missing layer is a claim ledger: a small record that connects every objective statement to its evidence, owner, qualification and review date.

The calendar hides a different kind of risk

Content planning usually starts with formats, channels and deadlines. That is useful for production, but it can conceal the harder question: what is the audience being asked to believe?

“Available now”, “our most effective treatment”, “the leading option”, “customers save time” and “better for the planet” are not merely lines of copy. They can be understood as objective claims. In the UK, the government’s plain-language guidance says that if a business makes a claim about a product, it must be able to prove it. CAP Code rule 3.7 goes further: marketers should hold documentary evidence before distributing or submitting a marketing communication for publication.

The important word is before. Evidence gathering is not a rescue task for after a complaint. It is part of editorial production.

Large illuminated advertising screens above Piccadilly Circus in London
Advertising screens at Piccadilly Circus, photographed on 21 December 2017. Archive image illustrating how audiences encounter the final claim, not the internal copy document. Photograph: Oast House Archive. Image source: Wikimedia Commons. CC BY-SA 2.0. No modifications.

Start with the audience’s interpretation

Teams often classify wording according to intention: “we meant that as enthusiasm” or “it was only a caption”. The ASA’s published guidance uses a different test. It considers the likely interpretation of a claim in context, not the marketer’s intention.

That means apparent puffery can become objective when the product, visual or surrounding wording gives it a measurable meaning. A testimonial does not solve the problem either. CAP guidance says a genuine customer testimonial may appear in advertising, but it is unlikely on its own to substantiate an objective claim. Comparisons such as “best”, “leading” or “cheaper” require evidence broad enough for the comparison being made.

A practical default is simple: if a reasonable customer could ask “how do you know?”, put the line in the ledger.

Build a seven-field claim ledger

The ledger can live in the same system as the content plan. It does not need to become a legal database. Each row needs seven fields:

  1. Exact claim: copy the wording as it will appear.
  2. Likely takeaway: write the meaning a customer could reasonably infer.
  3. Evidence: link the source, record or dataset that supports it.
  4. Scope and date: note geography, sample, product version and when the evidence was created.
  5. Owner: name the person responsible for confirming that the support is still valid.
  6. Qualification: record any limitation that must travel with the claim.
  7. Review status: mark it draft, substantiated, qualified or remove, with a review or expiry date.

The scope field matters because true information can still be stretched. A result for one service, market or period should not quietly become a universal brand promise. The review date matters because prices, availability, product specifications and comparative positions change.

A woman reviewing printed documents beside a computer workstation
Shenita Brown reviews documents before structured data entry on 16 April 2013. Archive image used to illustrate a documented review process; it does not depict The Creative Design UK. Photograph: Sue Brink / NAVFAC. Image source: Wikimedia Commons. CC BY 2.0. No modifications.

Review the delivered asset, not just the copy document

A claim is created by the whole communication: headline, image, caption, price, landing page and anything material left out. CAP rules state that qualifications may clarify a claim but must not contradict it, and must be presented clearly. A small disclaimer cannot repair a headline whose main message is broader than the evidence.

So the final check should happen on the rendered asset and destination page. Ask whether the qualification is visible where the promise is made, whether the visual implies a result the text avoids, and whether the landing page still matches the ad.

AI assistance makes this review more important, not less. The ASA’s June 2026 guidance says the advertising rules are media-neutral and that an advertiser remains responsible for the final output, including automated campaigns. A fluent draft can accelerate production; it cannot become the evidence owner.

What the ledger cannot do

A ledger is a governance habit, not legal advice. It does not replace specialist review for regulated sectors, environmental claims or complex comparative advertising. It can also create false comfort if the linked evidence is weak, out of date or narrower than the public wording.

Its value is operational: uncertainty becomes visible before publication, when the team can still change the claim without wasting production work.

The decision for Monday morning

Add one rule to the weekly planning meeting: no objective claim enters the calendar without an evidence link, a named owner and a review date.

If the evidence is missing, there are only three honest options: obtain it, narrow the wording or remove the claim. That decision may make a piece of content quieter. It also makes the brand’s language easier to defend, update and trust.

Sources

0 likes

0 comments

Leave a comment. We read every one, and they appear once approved.

Working on something this applies to? Tell us.

Start a project