# OPS-201 — The consent experience itself must be versioned and retained

> A capture of the exact language and action used to secure consent must be retained and versioned per consumer.

- **Rule ID:** OPS-201
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.message_flow`
- **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:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** CTIA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-201/

## Why this rule exists

Disclosure wording changes over time, so a single current screenshot cannot evidence a consent given two revisions ago. Versioning is what lets you answer which text a specific consumer saw, and it is the only defence when the wording has since improved.

## How to fix it

Version the disclosure text and store the version identifier on each consent record, so any past consent can be replayed exactly as the consumer saw it.

## Example of a compliant value

```text
Each opt-in stores disclosure_version=2026-03-a alongside the timestamp; we retain the full text of every version.
```