Mark every unverified variable and block export until it is resolved

JSONMarkdown

The requirementstatement

Every unverified variable in a generated draft must be visibly marked, and export must be blocked until each is resolved.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
draft policy placeholder tokens
Where it liveslayer
Policy pagesPOLICY_PAGE
How Ekas settles itdetectability
Human checkHUMAN
Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass
Produce a documentTERMINAL_ARTIFACT
Needs a document that does not exist yet, such as a verbal script, a paper consent form, or QR landing copy. Ekas drafts it.
Who requires itauthorities
TCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

The alternative to marking is guessing, and a guessed retention period ships as a fact — so the marker is what keeps POL-242 enforceable rather than aspirational. The published-document version of this failure is trivially detectable and embarrassingly common: a live policy with {{COMPANY_NAME}} still in it, which is what happens when a draft is exported past its own placeholders.

How to fix itremediation

Leave every unconfirmed value as a visible token rather than a plausible default, and resolve each before publishing. Done when a search of the draft for "{" and "[" returns nothing.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Does a search of this draft for "{" and "[" return nothing?

  1. 1Search the draft for both characters before publishing.
  2. 2Resolve each marked variable with a value somebody confirmed, rather than a plausible default.
  3. 3Do not publish while any marker remains.

What wrong looks like: A live policy with {{COMPANY_NAME}} still in it — trivially detectable, embarrassingly common, and what happens when a draft is exported past its own placeholders.

Notesnotes

The publication-side twin is POL-156, which fails a live page carrying tokens; this is the gate before that page exists. We hold no draft, so the user owns it: do not publish a generated document until every marked variable has been replaced with a value somebody confirmed.

Rules you will hit next

Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.

POL-021Policy URLs must not redirectHighHIGHPOL-023A social profile is not a policy pageHighHIGHPOL-025Exactly one privacy policy must be discoverableHighHIGHPOL-026The policy on the site and the policy attached to the registration must agreeHighHIGHPOL-030Both documents must be linked from the site footer on every pageHighHIGHPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGH

All policy pages rules

POL-243 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works