Claim substantiation log: The one-page evidence check regulated content needs

A claim substantiation log links every published claim to its supporting evidence, owner, approval, and review date. For regulated BFSI content, it simplifies compliance reviews, reduces contradictory claims, and helps ensure AI systems retrieve accurate, well-supported information.

AI-search guidance increasingly encourages brands to publish more numbers, rankings, and comparisons because specific claims are easier for AI systems to retrieve and quote. In Indian BFSI content, every additional claim creates another evidence obligation that must satisfy Advertising Standards Council of India (ASCI) claim substantiation requirements.

ASCI's Code for Self-Regulation requires descriptions, claims, and comparisons involving objectively ascertainable facts to be capable of substantiation. These ASCI claim substantiation requirements also apply when claims rely on independent research or surveys, which must include the source and date in the advertisement.

A claim substantiation log keeps supporting evidence attached to every approved claim before content reaches compliance review. It complements our IRDAI-versus-GEO guide, which explains why regulated brands often need to make a process or definition, rather than a marketing claim, the citable unit.

How to document claim substantiation in India

A claim substantiation log is a structured record that links every approved claim to its supporting evidence, owner, approval, and review date.

Across a large life-insurance account and a leading private-sector bank account, the LexiConn team uses the same discipline: no numerical, performance, projection, or comparative claim enters creative without a traceable evidence record.

Each approved claim should have its own record, including variations used in headings, tables, banners, chatbot responses, and other reusable content.

Review the completed log before content moves to legal or compliance approval. The following issues are among the most common reasons a substantiation record fails review.

• Claim: Record the exact approved wording. Avoid summaries. “Among the fastest” and “opens in five minutes” create different evidence burdens.
• Source document: Name the report, policy wording, product filing, audited data set, or approved internal record. A folder link alone is too vague.
• Date: Record when the evidence was produced or last validated. This also supports source-date disclosure where the ASCI Code requires it.
• Owner: Name the person or role responsible for maintaining the evidence. Avoid a generic department inbox.
• Expiry: Set the date when the claim must be rechecked. Rates, network counts, rankings and survey findings can become outdated while the source remains genuine.
• Approver: Identify the legal, compliance or product authority that cleared the wording and any mandatory qualifier.

A well-maintained claim substantiation log makes periodic reviews easier because every claim already has a documented evidence trail.

Substantiation record template for financial content

A row fails review when the wording differs from the evidence, the source covers another period or product, the comparison uses unequal bases, the owner cannot retrieve the document, or the approval has expired. Missing qualifiers also cause failure when they change how a reasonable reader would understand the claim.

Some metrics are better explained through the underlying process than through a single number. When a figure changes frequently, is difficult to reproduce, or loses important qualifiers outside its original context, describe the mechanism instead.

Replace “claims settled in two days” with the claim-intimation, document-check and assessment process. Replace “earn up to X%” with the balance slabs, calculation method, and rate-effective date.

A claim substantiation log should accelerate publishing rather than delay it. At LexiConn, we use this as a BFSI advertising compliance checklist. It reduces last-minute evidence searches, prevents contradictory claims across channels, and helps AI systems retrieve accurate, well-supported answers.

Regulatory sources: ASCI Code, Chapter I | ASCI Guidelines for Disclaimers

CLAIM SUBSTANTIATION LOG

One row per published claim. Attach or link the exact evidence file and review every entry before release.

Claim	Source document	Date	Owner	Expiry	Approver
Example: “Access 8,000+ network hospitals”	Network list v4 / approved website data	DD/MM/YYYY	Product content lead	DD/MM/YYYY	Compliance lead
Release rule: Do not publish when the source cannot be retrieved, the wording exceeds the evidence, the qualifier is missing, or the expiry date has passed.