# BRD-232 — Only three registration shapes may skip the automatic vet

> The skip-automatic-vetting flag may be set only for Low-Volume Standard registrations, 527 political organisations, and Campaign-Verify-registered brands.

- **Rule ID:** BRD-232
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.skip_automatic_sec_vet`
- **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:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-232/

## Why this rule exists

The flag suppresses the secondary vet that would otherwise run, and it exists for the three cases where that vet is either unavailable or already discharged by another artefact. Setting it anywhere else does not save a fee — it produces a brand that skipped its verification and lands at the lowest throughput with no finding to explain why.

## How to fix it

Leave the flag unset unless the brand is Low-Volume Standard, a 527 organisation, or registered through Campaign Verify. If it was set to avoid a fee, clear it and accept the automatic vet — the throughput it buys is worth more than the fee it costs.

## Example of a compliant value

```text
skip_automatic_sec_vet: false — unless brand_class is LOW_VOLUME_STANDARD, 527 or CAMPAIGN_VERIFY
```