# OPS-149 — Live content has to keep matching the registration

> Traffic must continue to match the registered use case and the registered samples, not merely have matched them at approval.

- **Rule ID:** OPS-149
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `live traffic against the registered use case and samples`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** TCR, T-Mobile, Twilio, Telnyx, Vonage
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-149/

## Why this rule exists

The samples are a promise about the programme, and programmes drift: a transactional campaign starts carrying a seasonal offer, an account-notification campaign adds a survey. Nobody re-reads the registration when writing a new template, so the drift is gradual and nothing flags it until the traffic no longer resembles what was approved.

## How to fix it

Review live templates against the registered samples on a schedule, and register a new campaign — or change the use case — before sending a category the registration does not describe. Done when every template in production would be recognised by somebody reading the registration.

## Check this yourself

**Would somebody reading your registration recognise every template now in production?**

1. Put the live templates next to the registered samples and read them together, on a schedule.
2. Register a new campaign — or change the use case — before sending a category the registration does not describe.
3. Nobody re-reads the registration when writing a new template, so the drift is gradual and nothing flags it.

*What wrong looks like:* A transactional campaign starts carrying a seasonal offer; an account-notification campaign adds a survey. The samples were a promise about the programme, and the traffic no longer resembles what was approved.

## Notes

Absorbs MSG-279, the same duty from the message-content side. Requires the live templates. What the user has to own is the review: the approval-side rules — MSG-141 and OPS-USECASE-SCOPE — check what was submitted, and neither of them sees what was added afterwards.