# OPS-159 — A registered campaign must expect to carry traffic

> A campaign should be registered only when it will actually send; sustained inactivity triggers dormancy suspension.

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

## Why this rule exists

Registering ahead of a programme that does not exist yet wastes a non-refundable vetting fee and risks a dormancy suspension after roughly two weeks of silence. It also produces the empty-shell registrations that make reviewers stricter with everyone.

## How to fix it

Register when you have subscribers and a send schedule. If the programme is seasonal, plan at least occasional traffic to avoid dormancy suspension.

## Example of a compliant value

```text
Weekly promotional sends beginning the week of approval.
```