# POL-248 — Record who approved the document and when

> The business should record who approved each published policy or terms document, and when.

- **Rule ID:** POL-248
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `document approval record`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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-248/

## Why this rule exists

An appeal or a complaint turns on who decided what and when they decided it, and a document with no approver is one nobody owns — which is exactly the state that lets a stale policy sit live for two years. The record costs a line and it is the difference between an audit trail and a reconstruction.

## How to fix it

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 yourself

**Can you say who signed off the policy text that is live right now, and when?**

1. Record the approver, the date and the version alongside the published document.
2. Keep 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.

## Notes

Internal to the business and invisible to any registration. The user has to keep the record themselves — the same place the POL-028 capture lives is the natural home for it, since the two answer the same question about the same document.