# Text length

## Keep controls short

<!-- rule: short-controls -->

**Rule:** Labels, buttons, badges and status text name the field, action or state in a few words.

**Why:** A control is read in the moment before acting, not studied.

**Do:** “Save invoice.”

**Don't:** “Click here to save your invoice.”

## Explain data in captions

<!-- rule: useful-captions -->

**Rule:** Use one sentence for needed units, dates or limits.

**Why:** The figure above the caption cannot say its unit, its period or what it leaves out.

**Do:** “March revenue in EUR, excluding refunds.”

**Don't:** “An overview of your revenue.”

## Use introductions only when needed

<!-- rule: useful-introductions -->

**Rule:** Add a short introduction only for a purpose or step the title and controls leave unclear.

**Why:** An introduction that repeats the title costs the reader their place on the page.

**Do:** “Upload a CSV with invoice numbers, dates and amounts.”

**Don't:** “Manage your invoices here.”

## Explain consequences in callouts

<!-- rule: useful-callouts -->

**Rule:** Explain a consequence or next step in one or two sentences.

**Why:** A callout earns its interruption by naming the consequence and what to do about it.

**Do:** “Deleting this workspace deletes its reports. Export them first.”

**Don't:** “Think carefully before proceeding.”

**Except:** Keep needed safety, consent and legal details visible, however long. Link to optional background.

## Cut filler

<!-- rule: remove-filler -->

**Rule:** Cut text readers can decide and finish without.

**Why:** Every spare word is read before it can be discarded.

**Do:** “Exports include only filtered rows.”

**Don't:** “Export quickly and easily.”