# OPS-109 — The scrub process needs writing down, version dates included

> The registry access and scrub process must be documented, including the registry version date used for each scrub.

- **Rule ID:** OPS-109
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `scrub process documentation`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Human check — only someone holding the document can settle it
- **Fix type:** Supply evidence only you hold
- **Required by:** FCC
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-109/

## Why this rule exists

The defence to a registry claim is the scrub, and a scrub with no record of which registry version it used cannot answer the only question that matters — whether the number was on the list at the time. Documenting the process is also what makes the freshness requirement auditable rather than aspirational.

## How to fix it

Write down who holds the registry subscription, how often it is refreshed, where the scrub runs in the send pipeline, and store the version date with every scrub result. Done when any past send can be tied to the registry version that cleared it.

## Example of a compliant value

```text
Scrub log: send acme-2026-03-04, registry_version 2026-03-01, 40,000 in, 312 removed.
```

## Check this yourself

**Can any past send be tied to the registry version that cleared it?**

1. Write down who holds the registry subscription, how often it is refreshed, and where the scrub runs in the send pipeline.
2. Store the version date with every scrub result — most scrub tooling logs a result and a count and drops the version.

*What wrong looks like:* A scrub with no record of which registry version it used cannot answer the only question that matters: whether the number was on the list at the time.

## Notes

Documentation and logs inside the brand. What the user has to do is keep the version date specifically — most scrub tooling logs a result and a count and drops the version, which leaves the record unable to answer the question it exists for.