# BRD-267 — Every brand field must be within its maximum length

> Each brand text field must be within the strictest cap its downstream targets enforce.

- **Rule ID:** BRD-267
- **Layer:** Brand (`BRAND`)
- **Checks:** `all brand text fields`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **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:** Telnyx, TCR, Twilio, Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-267/

## Why this rule exists

Over-long values are truncated or rejected depending on the provider, and Bandwidth applies the cap at provisioning rather than at vetting — so a brand can verify successfully and then fail when numbers are attached to it, which is the point at which nobody is looking at the brand record any more.

## How to fix it

Shorten the named field to its cap. Where a legal name genuinely exceeds 100 characters, use the first line of the IRS-registered name — that is what BRD-007 asks for anyway. Done when every field is inside its limit.

## Example of a compliant value

```text
company_name: Acme Coffee Co, LLC — 19 of 100 characters
```

## Notes

Caps are the strictest across the documented targets, which is Telnyx for most fields: displayName, companyName, email, street, city, website ≤100; ein, phone, state ≤20; postalCode, stockSymbol ≤10; country exactly 2. TCR is looser on several, so a value inside these passes everywhere.