# POL-247 — Do not claim a generated document makes the brand compliant

> Neither the product nor its output may claim that a generated policy makes the brand compliant or approved.

- **Rule ID:** POL-247
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `product export copy`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Human check — only someone holding the document can settle it
- **Fix type:** Supply evidence only you hold
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-247/

## Why this rule exists

Carriers and the DCAs make that determination, and nobody else can — so a claim of compliance is both untrue and the reason a business stops checking. It is a specific failure of tools like this one: the more confident the output looks, the less likely anyone is to read the rejection reasons when they arrive.

## How to fix it

Describe what the document does — it covers the requirements the registry knows about — rather than what it achieves. Done when nothing in the output or the interface promises approval.

## Check this yourself

**Does anything you say about this output promise compliance or approval, rather than describing what it covers?**

1. Read the interface copy and the document's own front matter for any claim of being compliant, approved, or carrier-ready.
2. Describe what it does — it covers the requirements the registry knows about — rather than what it achieves.
3. As a user: do not treat a clean run as an approval.

*What wrong looks like:* The more confident the output looks, the less likely anyone is to read the rejection reasons when they arrive. Carriers and the DCAs make that determination and nobody else can.

## Notes

Nothing in a registration records the claims made around it. The obligation is on whoever writes the product copy, and on the user not to treat a clean run here as an approval: the registry is a strict superset of what was researched, not a guarantee about any particular reviewer.