Record who approved the document and when
The requirementstatement
The business should record who approved each published policy or terms document, and when.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- document approval record
- 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
- Supply evidenceTERMINAL_EVIDENCE
- Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
- Who requires itauthorities
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Keep a record of the approver, the date and the version alongside the published document. Done when you can say who signed off the text that is currently live.
Check this yourselfattestation
No tool can settle this one for you. Here is the check, and what wrong looks like.
Can you say who signed off the policy text that is live right now, and when?
- 1Record the approver, the date and the version alongside the published document.
- 2Keep it where the submission-day capture lives — the two answer the same question about the same document.
What wrong looks like: A document with no approver is one nobody owns, which is exactly the state that lets a stale policy sit live for two years.
Notesnotes
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-248 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.