# BRD-208 — A score below the threshold means fixing the data, not re-vetting

> Where the vetting score is below the carrier or use-case threshold, the underlying brand data must be corrected before a re-vet.

- **Rule ID:** BRD-208
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.vetting_score`
- **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:** External record we cannot query — reported as a warning to verify
- **Fix type:** Wait on an external system or a required interval
- **Required by:** AWS, Sinch, Infobip
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-208/

## Why this rule exists

The score is computed from the brand data and the public record behind it, so re-running the same examination against the same inputs returns the same number — and the cooldown means you only get to find that out every three months. The productive move is unglamorous: correct the address, publish the phone number, fix the website, then re-vet.

## How to fix it

Work the inputs the score reads: an exact address match, a phone that answers, a website that names the business, social profiles, a mailbox on the brand domain. Then re-vet once, after the cooldown. Done when the underlying data has changed before the second examination.

## Check this yourself

**Have you corrected the data the score reads — address, phone, website, mailbox, social profiles — before ordering another vet?**

1. Treat a low score as a data problem, not a verdict. Most of its inputs are things you control.
2. Work them in order: an exact address match, a phone that answers, a website that names the business, social profiles, a mailbox on the brand domain.
3. Then re-vet once, after the cooldown.

*What wrong looks like:* The same examination is re-run against unchanged inputs and returns the same number — and the three-month cooldown means that is the only answer available until spring.

## Notes

The score and its threshold are held by the vetting provider. What the user has to do is treat a low score as a data problem rather than a verdict — most of the inputs are things they control, and BRD-211 lists the few that they do not.