# POL-217 — The terms should carry the standard boilerplate

> The terms of service must include the standard boilerplate: severability, assignment, entire agreement, waiver, force majeure and notices.

- **Rule ID:** POL-217
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `terms of service body`
- **Severity:** LOW — Best practice. Worth fixing, rarely fatal on its own.
- **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 privacy policy or SMS terms
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-217/

## Why this rule exists

Each of these does one job that only shows up when something goes wrong — a struck-out clause taking the rest with it, a right lost because it was not enforced once — and their absence is the clearest signal that a document was assembled rather than drafted. The assignment clause needs care for a messaging programme: consent must be excluded from it, which is POL-072.

## How to fix it

Add the boilerplate block, and exclude messaging consent from the assignment clause explicitly. Done when all six are present and the assignment clause names the carve-out.

## Example of a compliant value

```text
If any part of these terms is unenforceable the rest continues to apply. We may assign these terms; your text messaging consent is not assigned with them.
```