<!-- Claims substantiation log · from Chapter 24 of The Product 360 Handbook -->

# Claims substantiation log · [Product or launch] · [Date]

**Owner:** [PM] (evidence)   **Wording owner:** [PMM]   **Approver:** [Legal]   **Investor relations review (public companies):** [Name]

| ID | Claim text (exact wording) | Where used | Type: express or implied; quantified, comparative or availability | Evidence (link) | Population and period the evidence covers | Matches the audience of the claim? | Evidence owner | Status (Draft / Approved / Rewrite / Cut) | Review date |
|---|---|---|---|---|---|---|---|---|---|
| C-01 | | | | | | | | | |

## Rules
- No objective claim appears externally without an Approved row.
- A claim that states its own level of support ("tested," "proven," "in pilots") needs at least that level of support.
- Evidence must exist when the claim is made, be retained and cover the same population the claim addresses.
- AI accuracy and autonomy numbers trace to a named eval set or production metric, with date and scope, and state the denominator.
- Claims that the product replaces a professional, or that it acts without human involvement, get extra scrutiny.
- Availability claims match the offer definition's GA, preview and roadmap labels.
- Re-review every row when the model, eval set or product version behind it changes.
